Description of problem: the following troubling message shows up when the laptop resumes from a sleep Message from syslogd@notebook at Dec 23 12:09:22 ... kernel:[26674.150863] Uhhuh. NMI received for unknown reason 3d on CPU 0. Message from syslogd@notebook at Dec 23 12:09:22 ... kernel:[26674.150866] Do you have a strange power saving mode enabled? Message from syslogd@notebook at Dec 23 12:09:22 ... kernel:[26674.150867] Dazed and confused, but trying to continue Version-Release number of selected component (if applicable): How reproducible: everytime Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Are there any issues other than the messages? Is something not working? Is this repeatable?
- issues? no - something not working? no - repeatable? was repeatable, havent seen it in a bit though will post once it shows up. you know i did have a physical changed. i swapped my /dev/sdb for a different exact model disk. i can stick that back in and test. will let you know the results
just saw it again on the new /dev/sdb so it is not a disk issue [root@notebook ~]# Message from syslogd@notebook at Jan 8 08:49:52 ... kernel:[71216.877822] Uhhuh. NMI received for unknown reason 3d on CPU 0. Message from syslogd@notebook at Jan 8 08:49:52 ... kernel:[71216.877826] Do you have a strange power saving mode enabled? Message from syslogd@notebook at Jan 8 08:49:52 ... kernel:[71216.877828] Dazed and confused, but trying to continue and i checked the number of cpus and cpu0 is there and working as far as i can tell.
0) please rename the title of the bug to make it easier to find :') 1) i think i just started getting these after updating today. i have been running kernel-3.13.0-0.rc8.git0.1.fc21.x86_64 for some time without problem but just today started getting these messages periodically.
Created attachment 852214 [details] journalctl of the Uhhuh daze error that started with recent update for me
Created attachment 852215 [details] yum packages updated note that was running kernel-3.13.0-0.rc8.git0.1.fc21.x86_64 while ran update so the kernel didnt update but some of the supporting kernel files did so not sure if that caused confusion that generated error or not. will try to identify which package caused the error.
downgraded updates and then updated few at a time but didnt get the Uhhuh error. however when updated Packages Altered: Updated libudisks2-2.1.1-1.fc20.x86_64 @fedora Update 2.1.2-1.fc20.x86_64 @updates Updated perl-IO-Socket-IP-0.22-2.fc20.noarch @fedora Update 0.26-1.fc20.noarch @updates-testing Updated udisks2-2.1.1-1.fc20.x86_64 @fedora Update 2.1.2-1.fc20.x86_64 @updates history info then got a lockup and errors 20:48:11 BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:840] 20:48:10 WARNING: CPU: 1 PID: 0 at kernel/watchdog.c:272 watchdog_overflow_callback+0x9c/0xd0() but not the Uhhuh error so doesnt seem to have helped identify. since the post-error-downgrades the Uhhuh error hasnt reappeared. wonder if the lockup and error after updating the perl-IO-Socket-IP package are related to the Uhhuh errors? have been having peroidic wifi loss so maybe thats related to the 'strange powersavings mode' of the Uhhuh error.
Created attachment 864058 [details] journalctl Uhhuh error during desktop switch while a sudo was still thinking
*********** 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 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
was intermittent for me but havent seen it since comment#8. currently running kernel-3.13.5-200.fc20.x86_64
Ok. We'll close this out for now. If you see it again, please reopen.
time to re-open already. while running kernel-3.13.5-200.fc20.x86_64 was burning dvd and see that got error again: Message from syslogd@<removed> at Mar 6 04:50:41 ... kernel:[ 9512.588935] Uhhuh. NMI received for unknown reason 2d on CPU 1. Message from syslogd@<removed> at Mar 6 04:50:41 ... kernel:[ 9512.588949] Do you have a strange power saving mode enabled? Message from syslogd@<removed> at Mar 6 04:50:41 ... kernel:[ 9512.588955] Dazed and confused, but trying to continue
Still an issue: Message from syslogd@server at Sep 5 11:56:09 ... kernel:[136160.745044] Uhhuh. NMI received for unknown reason 3d on CPU 7. Message from syslogd@server at Sep 5 11:56:09 ... kernel:[136160.745048] Do you have a strange power saving mode enabled? Message from syslogd@server at Sep 5 11:56:09 ... kernel:[136160.745050] Dazed and confused, but trying to continue Message from syslogd@server at Sep 5 11:56:09 ... kernel:Uhhuh. NMI received for unknown reason 3d on CPU 7. Message from syslogd@server at Sep 5 11:56:10 ... kernel:Do you have a strange power saving mode enabled? Message from syslogd@server at Sep 5 11:56:10 ... kernel:Dazed and confused, but trying to continue uname -a Linux server 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Please reopen I have ssen this intermittantly since updating to FC20. It's a always on server. RAID 6, 24 Gig Ram My server runs boinc-client (GPU Utilised) and VirtualBox, Win 7 Guest How reproducible: intermittant Steps to Reproduce: 1. Wait with a terminal open, could take days. 2. 3. Actual results: Messages above. Expected results: No hung processes. Additional info: Ask for whatever you need and I will make available. I will attach a hardinfo report soon.
Created attachment 934680 [details] A hardware profile of an effected system. This is my servers hardware profile to assist in the identification of the source of the bug.