Bug 246789 - Uhhuh. NMI received for unknown reason b1 on CPU 0.
Summary: Uhhuh. NMI received for unknown reason b1 on CPU 0.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-04 21:08 UTC by Tom London
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-12 19:21:12 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Tom London 2007-07-04 21:08:31 UTC 
Description of problem:
Got first kernel crash in quite a while with 2.6.22-0.5.rc7.git2.fc8PAE:

Jul  4 13:58:26 localhost kernel: Uhhuh. NMI received for unknown reason b1 on
CPU 0.Jul  4 13:58:26 localhost kernel: You have some hardware problem, likely
on the PCI bus.
Jul  4 13:58:26 localhost kernel: Dazed and confused, but trying to continue
Jul  4 13:59:49 localhost syslogd 1.4.2: restart.

System was not being stressed: browsing, listening to internet radio.....

Running full Rawhide on Thinkpad X60.

Version-Release number of selected component (if applicable):
kernel-PAE-2.6.22-0.5.rc7.git2.fc8

How reproducible:
Don't know.....

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Dave Jones 2007-07-07 00:52:40 UTC 
As the message suggests..

"You have some hardware problem, likely on the PCI bus."

This doesn't sound like a software problem.  Random NMIs are usually a bad sign.
Comment 2 Tom London 2007-07-07 15:20:06 UTC 
I got these frequently with the 'broken' e1000 drivers of a few months ago, and
not before nor since except this one.....

I filed this just in case there was some similar issue.

I'll close if you like....
Comment 3 Tom London 2007-09-12 19:21:12 UTC 
Haven't seen a repeat.

Closing.
Note You need to log in before you can comment on or make changes to this bug.