From: Soeren Sonnenburg <sonne@debian.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Uhhuh. NMI received for unknown reason b0 on CPU 0.
Date: Sat, 11 Apr 2009 08:16:24 +0200 [thread overview]
Message-ID: <1239430584.10277.2.camel@localhost> (raw)
[-- 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 --]
next reply other threads:[~2009-04-13 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 6:16 Soeren Sonnenburg [this message]
2009-04-13 11:56 ` Uhhuh. NMI received for unknown reason b0 on CPU 0 Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1239430584.10277.2.camel@localhost \
--to=sonne@debian.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.