Hide Forgot
Description of problem: Intermittent Hard, Soft lockups and reboots while browsing internet Version-Release number of selected component (if applicable): How reproducible: Intermittent crashes but seems to happen fairly regularly. Possibly every 15 minutes or so. Steps to Reproduce: 1. Reboot after crash 2. Open browser and surf FB 3. Actual results: Sometimes mouse will start start responding Uber Slow and nothing can be clicked. Other times the entire GUI hangs and you cannlt switch to console (Have not tried SSH) Other times the system briefly hangs and then reboots with an MCE error Expected results: No crashes/reboots Additional info: Hardware functioned normally in F14 with no issues. Biggest difference being F14 was using Nvidia driver as opposed to nouveau. Using default nouveau driver in F15 All Default F15 install. (Happens both with fully updated system as well as F15 Gold) Only third party package added is Adobe Flash Square Preview. (Crashes happened both before and after) Seems to possibly happen more in Facebook that others. hard to say Sosreport uploaded
Ignore comments about MCE. Looks like this was just a boot time error about CPU lacking support.
Update: Has now happened in various different GUI Windows. Most recently while attempting to use the Software Updater.
Looks like this is a Nouveau issue instead of firefox. After blacklisting nouveau and installing akmod-nvidia from rpmfusion the system has not crashed since. Since I messed with a lot of different settings I will be reinstalling clean. Let me know if you wish to look deeper into the issue before I get everything set back up. I would like to help get nouveau working correctly but at this point I will be installing the akmod driver in the near future and we can then close this case out if I have not heard anything further.
Are you able to get your Xorg.0.log and dmesg output after one of these occur?
I reinstalled and reconfigured my system since opening the case. So I reinstalled to get the requested information: Fresh install (all defaults), yum update, opened facebook. System hung and then rebooted. Attaching new sosreport, Xorg logs and dmesg run after the system rebooted.
Created attachment 509935 [details] New Sosreport New Sosreport
Created attachment 509936 [details] /var/log/Xorg.0.log
Created attachment 509937 [details] /var/log/Xorg.0.log.old
Created attachment 509938 [details] /tmp/dmesg.txt
The system hung and rebooted at approximately 8:20PM EDT on Saturday June 25th I assume a regular dmesg is sufficient and you do not require one during the hang. The system becomes completely unresponsive and rebooted on its own during this.
Actually, dmesg during the hang would be good. If the GPU is actually in some kind of trouble it's usually very noisy about telling the driver, and, that'll show in dmesg.
Ok. I got some information. There are two scenarios I am seeing. 1) Everything locks up and then reboots. (Including SSH session and mouse) 2) Everything locks up except for ssh and the mouse. This time the crash that happened was number 2. I went to facebook and then used the slide wheel to move the screen up and down. The system hung except for the mouse. The SSH session maintained itself and I was able to run a dmesg. After 5 of these I typed init 3 but the system never exited the xterm. Shortly afterwards it rebooted. Here is an example of those steps: [root@localhost ~]# [root@localhost ~]# dmesg > /tmp/dmesg.txt2 [root@localhost ~]# dmesg > /tmp/dmesg.txt3 [root@localhost ~]# dmesg > /tmp/dmesg.txt4 [root@localhost ~]# dmesg > /tmp/dmesg.txt5 [root@localhost ~]# [root@localhost ~]# [root@localhost ~]# [root@localhost ~]# init 3 [root@localhost ~]# [root@localhost ~]# [root@localhost ~]# [root@localhost ~]# dmesg > /tmp/dmesg.txt6 [root@localhost ~]#
Created attachment 510778 [details] /tmp/dmesg.txt
Created attachment 510779 [details] /tmp/dmesg.txt6
Again this was a freshly installed system. I now have a separate drive just for these recreates. I will attempt the other recreation as well. Since the ssh session sometimes may accept the command right before it crashes. If I time it well enough.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping