Description of problem: I experience hard lockups of my system with kernel-smp-2.6.12-1.1390_FC4 after a few minutes <10. kernel-smp-2.6.12-1.1387_FC4 has been running for a few days without problems. Version-Release number of selected component (if applicable): kernel-smp-2.6.12-1.1390_FC4 How reproducible: i've done it twice, both times after about 5 minutes. Steps to Reproduce: 1. boot my system with kernel-smp-2.6.12-1.1390_FC4 from fc4 updates 2. login, check some email for a few minutes 3. Actual results: hard lockup of the system. No mouse movement, doesn't answer to ping. Expected results: stable Additional info: Motherboard: nForce4-based (Asus A8N-E, ) CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ Memory: 2GB Samsung (KVR400X64C3AK2/2G) plenty of cooling, after having tried to get some reponse from the machine i jumped into SETUP after reboot, and the reported processor temp was about 35C
can you try running memtest on this box for a while ? also the output of dmesg, lsmod and lspci would be useful.
[This comment has been added as a mass update for all FC4 kernel bugs. If you have migrated this bug from an FC3 bug today, ignore this comment.] Please retest your problem with todays 2.6.12-1.1398_FC4 update. If your problem involved being unable to boot, or some hardware not being detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE* installing any kernel updates. If in doubt, you can recreate this file using.. mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak mv /etc/modprobe.conf /etc/modprobe.conf.bak kudzu Thank you.
sorry for the delay, I think now that I've found a pattern. It doen't matter which one of the FC4 kernels I run, what does matter however is if i reboot the machine cold or warm. Cold reboot gives a stable system. Warm reboot locks up after a few minutes.
Created attachment 116912 [details] dmesg
Created attachment 116913 [details] lsmod
Created attachment 116914 [details] lspci
try service stop cpuspeed, and see if stability improves. If so, it's likely a bug that's fixed in the current kernel in updates-testing
Just back from a vacation i just tried to reproduce the lockup with 2.6.12-1.1447_FC4smp but it seems to have been fixed. Thanks! Closing this tomorrow after a night of stress tests.