Hide Forgot
I don't know what causes it. It just keeps happening. Version: 3.1.2-1.fc16.i686.PAE I don't remember this happening before. Message from syslogd@annwn at Dec 7 03:41:47 ... kernel:[352188.267489] Uhhuh. NMI received for unknown reason 25 on CPU 0. Message from syslogd@annwn at Dec 7 03:41:47 ... kernel:[352188.267495] Do you have a strange power saving mode enabled? Message from syslogd@annwn at Dec 7 03:41:47 ... kernel:[352188.267497] Dazed and confused, but trying to continue Message from syslogd@annwn at Dec 7 03:49:42 ... kernel:[352663.652060] Uhhuh. NMI received for unknown reason 35 on CPU 1. Message from syslogd@annwn at Dec 7 03:49:42 ... kernel:[352663.652065] Do you have a strange power saving mode enabled? Message from syslogd@annwn at Dec 7 03:49:42 ... kernel:[352663.652067] Dazed and confused, but trying to continue Message from syslogd@annwn at Dec 7 04:01:08 ... kernel:[353349.503837] Uhhuh. NMI received for unknown reason 35 on CPU 0. Message from syslogd@annwn at Dec 7 04:01:08 ... kernel:[353349.503843] Do you have a strange power saving mode enabled? Message from syslogd@annwn at Dec 7 04:01:08 ... kernel:[353349.503846] Dazed and confused, but trying to continue
Is this easily recreatable? Did this start with 3.1.2-1.fc16? What is the newest kernel that doesn't exhibit the problem?
Hi Felipe, Can you attach a dmesg log that captures these. I want to see if any other hardware started to fail before this happened (or even after). Cheers, Don
I am starting to think this was due to some development I was doing with a USB device... it probably was requesting too much power from the USB port or something. I have not seen this in quite some time.