From: Joerg.Schilling@fokus.fraunhofer.de (Joerg Schilling)
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Verification of audio CD copy?
Date: Thu, 04 Jun 2009 13:53:35 +0200 [thread overview]
Message-ID: <4a27b5bf.cPoi0Pw0+4IexjhC%Joerg.Schilling@fokus.fraunhofer.de> (raw)
In-Reply-To: <5bdc1c8b0906031621j24ffdfadl79075793a6c2edd6@mail.gmail.com>
Mark Knecht <markknecht@gmail.com> wrote:
> mark@lightning ~/Desktop/cdda2wav $ readcd dev=1000,0,0 -c2scan
> Read speed: 7056 kB/s (CD 40x, DVD 5x, BD 1x).
> Write speed: 7056 kB/s (CD 40x, DVD 5x, BD 1x).
> Capacity: 263932 Blocks = 527864 kBytes = 515 MBytes = 540 prMB
> Sectorsize: 2048 Bytes
> readcd: Success. mode select g1: scsi sendcmd: no error
> CDB: 55 10 00 00 00 00 00 00 14 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 26 00 00 00
> Sense Key: 0x5 Illegal Request, Segment 0
> Sense Code: 0x26 Qual 0x00 (invalid field in parameter list) Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.001s timeout 40s
> Copy from SCSI (1000,0,0) disk to file '/dev/null'
> end: 263932
> ^C^C^C 1911 cnt: 49
>
> ^C^C^C
>
> I cannot get out of this so far. Hate to think I need to reboot!
I already mentioned the reason for the SCSI error......
If you cannot get out of this by typing ^C and you did not disable
the signal from your shell, this is a kernel bug.
Jörg
--
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
prev parent reply other threads:[~2009-06-04 11:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 1:03 [gentoo-user] Verification of audio CD copy? Mark Knecht
2009-06-03 2:42 ` Paul Hartman
2009-06-03 2:48 ` Mark Knecht
2009-06-03 3:50 ` Dale
2009-06-03 9:03 ` Joerg Schilling
2009-06-03 19:34 ` Mark Knecht
2009-06-03 19:38 ` Dirk Heinrichs
2009-06-03 19:41 ` Mark Knecht
2009-06-03 19:45 ` [gentoo-user] " Nikos Chantziaras
2009-06-03 20:23 ` Joerg Schilling
2009-06-03 20:45 ` Paul Hartman
2009-06-04 22:04 ` Jesús Guerrero
2009-06-05 10:21 ` Joerg Schilling
2009-06-05 20:25 ` Jesús Guerrero
2009-06-03 8:59 ` [gentoo-user] " Joerg Schilling
2009-06-03 2:50 ` [gentoo-user] " Nikos Chantziaras
2009-06-03 8:57 ` [gentoo-user] " Joerg Schilling
2009-06-03 22:54 ` Mark Knecht
2009-06-03 23:17 ` Joerg Schilling
2009-06-03 23:21 ` Mark Knecht
2009-06-03 23:32 ` Mark Knecht
2009-06-04 1:57 ` Mark Knecht
2009-06-04 8:02 ` Joerg Schilling
2009-06-04 19:13 ` Mark Knecht
2009-06-04 19:38 ` Alan McKinnon
2009-06-04 20:39 ` Mark Knecht
2009-06-05 9:48 ` Alan McKinnon
2009-06-05 10:01 ` Joerg Schilling
2009-06-05 13:49 ` Mark Knecht
2009-06-05 15:59 ` Paul Hartman
2009-06-05 16:01 ` Paul Hartman
2009-06-06 3:10 ` Mark Knecht
2009-06-06 15:00 ` Joerg Schilling
2009-06-06 19:21 ` Mark Knecht
2009-06-08 14:16 ` Joerg Schilling
2009-06-08 17:13 ` Mark Knecht
2009-06-08 18:32 ` Joerg Schilling
2009-06-08 19:04 ` Mark Knecht
2009-06-08 19:25 ` Paul Hartman
2009-06-08 21:04 ` Mark Knecht
2009-06-05 14:23 ` Paul Hartman
2009-06-05 14:44 ` Mark Knecht
2009-06-04 8:00 ` Joerg Schilling
2009-06-04 11:53 ` Joerg Schilling [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a27b5bf.cPoi0Pw0+4IexjhC%Joerg.Schilling@fokus.fraunhofer.de \
--to=joerg.schilling@fokus.fraunhofer.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox