2.6.18-rc5-mm1 -- Fwd: readcd fails to read info from a WinXP created CDR
From: Miles Lane
Date: Sun Sep 03 2006 - 17:09:27 EST
---------- Forwarded message ----------
From: Joerg Schilling <Joerg.Schilling@xxxxxxxxxxxxxxxxxxx>
Date: Sep 3, 2006 1:53 PM
Subject: Re: readcd fails to read info from a WinXP created CDR
To: schilling@xxxxxxxxxxxxxxxxxxx, miles.lane@xxxxxxxxx
"Miles Lane" <miles.lane@xxxxxxxxx> wrote:
Hello Jorg,
I created a large zip file in Windows XP, then formatted a CDR and
dragged the zipfile over to the disk in the file manager. It got
writting fine. I have verified that I can read the CDR in WIndows XP
(it shows up as a UDF disc). But, none of the Linux apps in Ubuntu
6.06.1 can read this CDR, including readcd. This would seem to be a
fault in Linux apps. I got all the debugging info I could using
readcd. Can you take a look and see whether there is anything to be
done to get this working in Linux?
Executing 'read toc' command on Bus 1 Target 1, Lun 0 timeout 40s
CDB: 43 00 02 00 00 00 00 00 04 00
readcd: Success. read toc: scsi sendcmd: no error
CDB: 43 00 02 00 00 00 00 00 04 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 24 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid)
resid: 4
cmd finished after 0.005s timeout 40s
readcd: Cannot read TOC header
This is a well known linux kernel bug.
You should start using Solaris.....
The Linux kernel bastardizes ATAPI transported SCSI commands under some
circumstances.
READ TOC & BLANK are the commands that are usually affected.
Using Solaris with exactly the same hardware verifies that it is a Linux
kernel bug.
----------------------------------------
Can we please get this fixed?
Thanks,
Miles
--
VGER BF report: U 0.500002
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/