I got this error message from a problematic cd-RW corrupted :
Nov 12 12:06:23 pcumr70 kernel: hdc: irq timeout: status=0xd0 { Busy }
Nov 12 12:06:23 pcumr70 kernel: hdc: irq timeout: status=0xd0 { Busy }
Nov 12 12:06:23 pcumr70 kernel: scsi : aborting command due to timeout : pid
244873, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 05 9b c5
00 00 01 00
Nov 12 12:06:23 pcumr70 kernel: SCSI host 0 abort (pid 244873) timed out -
resetting
Nov 12 12:06:23 pcumr70 kernel: SCSI bus is being reset for host 0 channel 0.
Nov 12 12:06:23 pcumr70 kernel: scsi : aborting command due to timeout : pid
244873, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 05 9b c5
00 00 01 00
As the drive become foolish, i had to restart (bye bye uptime).
More seriously, i got the same message with a cd-rw correct (the drive wasn't
accessible under the burner, but ok from the dvd drive).
This happens on 7.2,8.2 and 9.0 distributions.
It is certainly not related to hardware failures (the burner's brand are
different), may be to the drive itself (both cdrw's were VERBATIM), but it is
a more general topic : is the kernel supposed to act like this.
As it is may be a kernel issue, it is possibly off-topic, but i ask it
nevertheless :
As the rest was going fine, wouldn't it be possible to force the kernel to
give up in the case of such problem ?
I let the cdrom within the drive for more than 1 hour, and tried continuously
to eject it with no success.
I tried to umount it manually, but supermount complained, i tried eject
/mnt/cdrom, eject /dev/scd0, eject /dev/hdc, ...
Everyting without success but the reboot solution.
I'm not sure whether it is related to the kernel itself or supermount, but as
it was the same reaction with different distributions ...
Stef
