Uhhuh. NMI received for unknown reason b0 on CPU 0.

Uhhuh. NMI received for unknown reason b0 on CPU 0.

[Soeren Sonnenburg]

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

Dear all,

I just got this error on a samsung nc 10 netbook running 2.6.29.1:

Message from syslogd@x at Fri Apr 10 16:31:48 2009 ...
s3 kernel: Uhhuh. NMI received for unknown reason b0 on CPU 0.

Message from syslogd@x at Fri Apr 10 16:31:48 2009 ...
s3 kernel: You have some hardware problem, likely on the PCI bus.

Message from syslogd@x at Fri Apr 10 16:31:48 2009 ...
s3 kernel: Dazed and confused, but trying to continue

The thing operates as normal but leaves me (and the kernel!) confused?!

Should I be worried?
Soeren
-- 
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: Uhhuh. NMI received for unknown reason b0 on CPU 0.

[Alan Cox]

On Sat, 11 Apr 2009 08:16:24 +0200
Soeren Sonnenburg <sonne@debian.org> wrote:

> Dear all,
> 
> I just got this error on a samsung nc 10 netbook running 2.6.29.1:
> 
> Message from syslogd@x at Fri Apr 10 16:31:48 2009 ...
> s3 kernel: Uhhuh. NMI received for unknown reason b0 on CPU 0.
> 
> Message from syslogd@x at Fri Apr 10 16:31:48 2009 ...
> s3 kernel: You have some hardware problem, likely on the PCI bus.
> 
> Message from syslogd@x at Fri Apr 10 16:31:48 2009 ...
> s3 kernel: Dazed and confused, but trying to continue
> 
> The thing operates as normal but leaves me (and the kernel!) confused?!
> 
> Should I be worried?

Possibly. NMI normally comes from things like dud memory.

I would try memtest86 for a few hours just to be sure, and also if you
can reproduce it load the edac base module and set it to poll for pci
errors.

It could also be arising from a software error triggering hardware so
knowing if its reproducable and how/when will be useful.