On 2/23/07, Alan <alan@xxxxxxxxxxxxxxxxxxx> wrote:
> Feb 20 23:15:17 localhost kernel: hdb: irq timeout: status=0xd0 { Busy }
> Feb 20 23:15:27 localhost kernel: ide: failed opcode was: unknown
> Feb 20 23:15:27 localhost kernel: hdb: status timeout: status=0xd0 { Busy }
> Feb 20 23:15:27 localhost kernel: ide: failed opcode was: unknown
Your CD-ROM drive stopped responding
> Feb 20 23:17:30 localhost kernel: ide: failed opcode was: unknown
> Feb 20 23:17:30 localhost kernel: hdb: drive not ready for command
> Feb 20 23:17:36 localhost kernel: hdb: status timeout: status=0xd0 { Busy }
> repeats infinitely.
and never came back.
It would be very interesting to know if an older kernel doesn't trigger
this.
I can keep running 2.6.16.41 for a few weeks. If the problem does not
occur by then it is reasonably probably that it is newly introduced.
As I said, I am not able to trigger the problem intentionally :(.
Would it be possible for the kernel to realize that the drive stopped
responding? And make sure that it doesn't make the whole computer
unresponsive...
Regards, Thue
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
