Burning CDs with a CD-ROM is a bad idea

Burning CDs with a CD-ROM is a bad idea

[gboyce]

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?

Re: Burning CDs with a CD-ROM is a bad idea

[Jens Axboe]

On Fri, May 14 2004, gboyce@badbelly.com wrote:
> 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

Looks like one of the burning commands confused the drive so much, that
it now refuses to do anything (the above command is a simple medium
removal prevention command, doesn't even need a data transfer).

So I don't think this is a kernel problem. Well maybe we could reset the
device and see if it recovers (do you see any resets in the log?)

-- 
Jens Axboe

Re: Burning CDs with a CD-ROM is a bad idea

[Gregory Boyce]

On Sat, 2004-05-15 at 06:47, Jens Axboe wrote:
> On Fri, May 14 2004, gboyce@badbelly.com wrote:
> > 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
> 
> Looks like one of the burning commands confused the drive so much, that
> it now refuses to do anything (the above command is a simple medium
> removal prevention command, doesn't even need a data transfer).
> 
> So I don't think this is a kernel problem. Well maybe we could reset the
> device and see if it recovers (do you see any resets in the log?)

There was a reset early on, but it was before the majority of errors.

Here is the begining of problem:

May 13 16:38:14 cthulhu hdc: DMA interrupt recovery
May 13 16:38:14 cthulhu hdc: lost interrupt
May 13 16:38:14 cthulhu hdc: status timeout: status=0xd0 { Busy }
May 13 16:38:14 cthulhu hdc: status timeout: error=0x00
May 13 16:38:14 cthulhu hdc: DMA disabled
May 13 16:38:14 cthulhu hdc: drive not ready for command
May 13 16:38:15 cthulhu hdc: ATAPI reset complete
May 13 16:38:15 cthulhu cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC
May 13 16:38:15 cthulhu sector 0, nr/cnr 0/0
May 13 16:38:15 cthulhu bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
May 13 16:38:15 cthulhu cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 13 16:38:15 cthulhu hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)
May 13 16:39:15 cthulhu ide-cd: cmd 0x1e timed out
May 13 16:39:15 cthulhu hdc: lost interrupt
May 13 16:39:15 cthulhu cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC REQ_FAILED
May 13 16:39:15 cthulhu sector 0, nr/cnr 0/0
May 13 16:39:15 cthulhu bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
May 13 16:39:15 cthulhu cdb: 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 13 16:39:15 cthulhu hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)

There are an additional 700K of errors like this before I finally
rebooted the machine the next day.  The machine also refused to let me
burn CDs on the actual CD burner during this time.

--
Greg