Burning CDs with a CD-ROM is a bad idea

From: gboyce
Date: Fri May 14 2004 - 13:03:19 EST


Hello folks,

Yesterday I made a slight thinko while attempting to burn a CD. Rather
than specifying dev=/dev/hdd, I add dev=/dev/hdc, which is my CD-ROM
drive rather than my cd burner. Whoops!

Now, I believe I've done this before, and recieved an error message.
However, in this particular case with 2.6.6, the system behaved a bit
different.

bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)
ide-cd: cmd 0x1e timed out
hdc: lost interrupt
cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC REQ_FAILED
sector 0, nr/cnr 0/0
bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)
ide-cd: cmd 0x1e timed out
hdc: lost interrupt
cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC REQ_FAILED
sector 0, nr/cnr 0/0
bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)
ide-cd: cmd 0x1e timed out
hdc: lost interrupt
cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC REQ_FAILED
sector 0, nr/cnr 0/0
bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)
ide-cd: cmd 0x1e timed out
hdc: lost interrupt
cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC REQ_FAILED
sector 0, nr/cnr 0/0
bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)
ide-cd: cmd 0x1e timed out
hdc: lost interrupt
cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC REQ_FAILED
sector 0, nr/cnr 0/0
bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)
ide-cd: cmd 0x1e timed out

It's been a day, and cdrecord is still trying. I've tried cancelling or
killing cdrecord with no avail.

root 11461 0.0 0.0 0 0 ? DW May13 0:00 [cdrecord]

This seems like the wrong behavior to me. What I'm not sure of though is
if this is a kernel bug, or some sort of problem with cdrecord. Thoughts?
-
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/