Today Fedora completely froze up, to the point where the Caps Lock key did not function. I found lots of errors in /var/log/messages from this point in time; I'll put a copy in an attachment. I previously reported a similar Eeek in Bug 296641, but the concurrent symptoms were different this time. I rebooted, and then rebooted again using the Fedora 7 LiveCD. I checked the root filesystem (/dev/sda1) with fsck, but it claimed the filesystem was clean. I tried again forcing a check with -f, and a number of filesystem errors were found. (See attachment for output.) It is somewhat alarming that these errors were not fixed during journal recovery. I am wondering whether there is a filesystem corruption bug which is causing the kernel to misbehave, or if this damage is a result of the freeze.
Created attachment 220331 [details] Excerpt from /var/log/messages and output from fsck
This could be caused by failing hardware (disks / memory / power supply.)
Well, this laptop passed a memtest86 recently, and after running a self-check today, smartctl finds no problems with the hard drive. I'm not sure how to detect trouble with the power supply.
Hello, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the Fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged.
I haven't seen this particular problem since I filed this report, though I have had kernel oopses occasionally.
Okay, I'll close INSUFFICIENT_DATA. Please re-open if it returns and thank you for filing originally.