Bug 150287

An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

yes, i've switched to fc4 (and changed the version flag as requested). kernel is
2.6.12-1.1398_FC4. after one day of idling the laptop suddenly stopped
responding. last entries from syslog were:
kernel: hdc: irq timeout: status=0xd0 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hdc: DMA disabled
kernel: hdc: ATAPI reset timed-out, status=0x80
kernel: ide1: reset timed-out, status=0x80
kernel: hdc: status timeout: status=0x80 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hdc: drive not ready for command
kernel: hdc: ATAPI reset timed-out, status=0x80
kernel: ide1: reset timed-out, status=0x80
kernel: cdrom: This disc doesn't have any tracks I recognize!

system running stable for more than two days. kernel is 2.6.12-1.1450_FC4. i
would assume the bug being fixed.

sorry, i've made the last comment to early :(
the machine's still locking up (but the intervalls seem to increase):

kernel: hdc: irq timeout: status=0xd0 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hdc: DMA disabled
kernel: hdc: ATAPI reset timed-out, status=0x80
kernel: ide1: reset timed-out, status=0x80
kernel: hdc: status timeout: status=0x80 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hdc: drive not ready for command
kernel: hdc: ATAPI reset timed-out, status=0x80
kernel: ide1: reset timed-out, status=0x80
kernel: cdrom: This disc doesn't have any tracks I recognize!

Mass update to all FC4 bugs:

An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (2.6.13.2). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.

Please retest with this update, and update this bug if necessary.

Thanks.

unfortunenately the bug's still there. after two days of idling i've logged in
locally and after some (~ 10min.) time the system froze. /var/log/messages follows:

Oct  2 21:50:10 <host> kernel: hdc: irq timeout: status=0xd0 { Busy }
Oct  2 21:50:10 <host> kernel: ide: failed opcode was: unknown
Oct  2 21:50:10 <host> kernel: hdc: DMA disabled
Oct  2 21:50:40 <host> kernel: hdc: ATAPI reset timed-out, status=0x80
Oct  2 21:51:15 <host> kernel: ide1: reset timed-out, status=0x80
Oct  2 21:51:15 <host> kernel: hdc: status timeout: status=0x80 { Busy }
Oct  2 21:51:15 <host> kernel: ide: failed opcode was: unknown
Oct  2 21:51:15 <host> kernel: hdc: drive not ready for command
Oct  2 21:51:45 <host> kernel: hdc: ATAPI reset timed-out, status=0x80
Oct  2 21:52:15 <host> kernel: ide1: reset timed-out, status=0x80

    j.

2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.

Thank you.

unfortunately the freeze still persits with 2.6.14-1.1637_FC4.
error messages are the same as before.

i've removed the cdrom drive from the machine in question and do not see any
system freezes. so i guess i've to get a new cdrom drive :(
i'm just wondering if this kind of problem could be handled by the kernel more
gracefully.

i think the case can be closed now. thanks for your help.

There's only so much we can do with faulty hardware.

Have you tried using a different cable on that device ?
If that's the problem part, it could be cheaper than replacing the whole drive :)

unfortunately it's a laptop cd-rom to be plugged into a costum slot. so no cable
problem. thanks anyway for th hint