Hide Forgot
Description of problem: Fedora 16 randomly reboots the system. This happens in most of the case directly during boot time but may even occur after the system has been running for several minutes. Version-Release number of selected component (if applicable): Fedora 16 How reproducible: Just by starting the system Steps to Reproduce: 1. Start the system 2. Wait for the reboot 3. Actual results: reboot Expected results: no reboot Additional info: At first I thought this might be a hardware issue. I have two systems (Fedora 14 and Fedora 16) which are located on two different HDDs. I was thinking about an issue with the Fedora 16 HDD but S.M.A.R.T doesn't show any errors at all (even after running the extended tests). I even replaced my RAM and the problem seemed to be resolved as this just resulted in no random reboots for two days. Unfortunately the error just reoccurred today and I came to the conclusion that this is no hardware issue as the Fedora 14 system never behaved like this and just runs without complaining. (on the very same PC, except for the HDD)
Can you install kernel-debug and see if there is some kind of trace that gets produced? If you monitor dmesg while the machine is running, is there anything being printed about thermal events or any other errors?
Created attachment 535121 [details] Dmesg output
Thanks for your answer, Josh. I just attached my dmesg output as I couldn't find any fishy messages... I also just installed kernel-debug but unfortunately I don't know how to produce a proper trace as there doesn't seem to be a man page. Just some additional information: After rebooting three or four times, the system seems to calm down. There has never been a random reboot after the system managed to survive for about five minutes.
Don't you forget about me! ;-) Is there nothing further I can do to fix this problem? It's really starting to get on my nerves. Any suggestions are highly appreciated.Thanks a lot!
Are you still seeing this issue with the recent kernel updates in Fedora? Also, looking at the attachment in comment #2, I see you're using the vbox modules. if this still happens, does it happen if you stop using those?
Hello Josh, Nope, the issue is gone now. Thanks a lot for your reply, this is solved now.