Comment 2 for bug 15221

(In reply to comment #1)
> Can you still reproduce this bug?... The kernel messages look to me like it was
> a dirty or dying CD drive, not a cdrecord issue. cdrecord has worked well for
> me in both hoary and breezy.
>

Yes, I still have this problem under Hoary and Breezy RC as well. Although the
output is a little different now. Now, the program hangs at the RESID:64512 line
and actually exited after a while. The dmesg output is a little different:

hdc: lost interrupt
cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC REQ_FAILED REQ_QUIET
sector 0, nr/cnr 0/0
bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
cdb: 00 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)

I'm not so sure the drive is dying. I can read CDs fine and haven't had a
problem yet. Also, I can burn CDs in Windows as well as using Windows XP on
VMWare under Linux. I used this drive with SuSE over a year ago and used
cdrecord on there successfully (but that was kernel 2.4). The burner has just
never worked under Ubuntu.