Description of problem: sporadically my system hangs completly Version-Release number of selected component (if applicable): Linux version 3.9.2-200.fc18.x86_64 (mockbuild@bkernel02) (gcc version 4.7.2 20121109 (Red Hat 4.7.2-8)(GCC)) How reproducible: not really - it comes sporadically Steps to Reproduce: 1. 2. 3. Actual results: /var/log/messages is completly without error last time the problem occure the system brings a text-terminal with these informations: drm_kms_helper panic occured TSC 43e4e83e9be7 Processor context corrupt Expected results: Additional info:
Today there was another freeze with these informations at the console: drm_kms_helper: panic occurred shutting down cpus with NMI - going to text console RIP INEXACT mce hardware error TSC 126a532020dd run the above through mcelog-ascii .... the system freeze before it can restart
I have the same problem and recently the occurrences have become quite frequent (daily!). I am using kernel 3.10.9-100.fc18.x86_64. The latest lock up was preceded by a buch of messages in /var/log (see first attachment). The kernel panicked and I could only take a picture of the text console (2nd attachment).
Created attachment 789852 [details] excerpt form /var/log/messages prior to panic
Created attachment 789853 [details] picture of text console after panic
Could my problem be related to bug 917081?
(In reply to Rutger Noot from comment #5) > Could my problem be related to bug 917081? Yes, it's possible.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.