public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Foerster <stefan.foerster@mnet-online.de>
To: linux-kernel@vger.kernel.org
Subject: IBM ThinkPad T23: Uhhuh. NMI received for unknown reason 30 on CPU 0.
Date: Thu, 30 Aug 2007 22:52:40 +0200	[thread overview]
Message-ID: <1188507160.4640.18.camel@stefan2> (raw)

Hi all,

on my IBM ThinkPad T23 I often get the following messages (together with
a beep from the speaker):

-------------------
Message from syslogd@stefan2 at Thu Aug 30 22:02:17 2007 ...
stefan2 kernel: Uhhuh. NMI received for unknown reason 30 on CPU 0.

Message from syslogd@stefan2 at Thu Aug 30 22:02:17 2007 ...
stefan2 kernel: Do you have a strange power saving mode enabled?

Message from syslogd@stefan2 at Thu Aug 30 22:02:17 2007 ...
stefan2 kernel: Dazed and confused, but trying to continue

stefan@stefan2:~$ 
Message from syslogd@stefan2 at Thu Aug 30 22:32:08 2007 ...
stefan2 kernel: Do you have a strange power saving mode enabled?

Message from syslogd@stefan2 at Thu Aug 30 22:32:08 2007 ...
stefan2 kernel: Dazed and confused, but trying to continue

Message from syslogd@stefan2 at Thu Aug 30 22:32:08 2007 ...
stefan2 kernel: Uhhuh. NMI received for unknown reason 30 on CPU 0.
------------------

There seems to be no pattern in the "interarrival times" of this signal.
Sometimes I get it about every 30 minutes, sometimes only once a day.

It also doesn't depend on the kernel version. I now see this behaviour
on this notebook for 3 years now.

My current kernel version is 2.6.23-rc3 (plain vanilla kernel), Ubuntu
Gutsy Gibbon.

I have googled "Uhhuh. ..." and got exactly 3 (!) entries, but no
solution. But it seems that this is somehow typical for some notebooks,
especially ThinkPads.

Any ideas ?


Stefan


                 reply	other threads:[~2007-08-30 20:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1188507160.4640.18.camel@stefan2 \
    --to=stefan.foerster@mnet-online.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox