Bug 760808

Summary: Linux kernel keeps showing NMI warnings *all the time*
Product: [Fedora] Fedora Reporter: Felipe Contreras <felipe.contreras>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: dzickus, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-02 18:37:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Felipe Contreras 2011-12-07 02:08:39 UTC
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

Comment 1 Josh Boyer 2011-12-07 14:05:36 UTC
Is this easily recreatable?  Did this start with 3.1.2-1.fc16?  What is the newest kernel that doesn't exhibit the problem?

Comment 2 Don Zickus 2011-12-07 16:40:13 UTC
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

Comment 3 Felipe Contreras 2012-02-02 18:37:57 UTC
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.