Kernel 2.6.20-1.2933.fc6, infinite loop eats CPU cycles?

PTrenholme · 03-28-2007, 08:41 PM

This may be a hardware problem, but I’ve only noticed it after my last kernel upgrade (to 2.6.20-1.2933.fc6)

After several hours using my laptop, response time goes to pot and the GKrellM CPU monitor shows kernel activity is “eating” all the CPU cycles. To get the system working again, I have to reboot. After rebooting, /var/log/messages shows lots of lines like these:

Code:

Mar 28 18:03:10 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Mar 28 18:03:10 localhost kernel: ide: failed opcode was: unknown
Mar 28 18:03:10 localhost kernel: hdc: drive not ready for command
Mar 28 18:03:12 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Mar 28 18:03:12 localhost kernel: ide: failed opcode was: unknown
Mar 28 18:03:12 localhost kernel: hdc: drive not ready for command
Mar 28 18:03:15 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Mar 28 18:03:15 localhost kernel: ide: failed opcode was: unknown
Mar 28 18:03:15 localhost kernel: hdc: drive not ready for command

(hdc is the DVD R/W unit built into my Gateway MX6436 laptop.)

The problem occurs both when there is a disk in the drive, when the drive is empty, and when the drive door is open, so I’m inclined to think that this may be a kernel problem instead of hardware. But it could, I suppose, be a flaky IDE controller or a loose internal cable.

At this point I thought it might be prudent to ask advice from the forum before attacking the laptop with my screwdriver. (I have, occasionally, used my screwdriver to really screw things up.

)

macemoneta · 03-29-2007, 12:22 AM

I don't think it's the kernel. I have it running on 5 machines: 2 x86 laptops, 2 PPC latops and 1 x86_64 desktop/server.

Loose cable or failed hardware would be my guess. You can try booting a LiveCD/DVD to verify.

indienick · 03-31-2007, 05:21 PM

That's definitely a bad device. I have received identical errors for a hard-drive that recently failed on me.