From: lkml@nitwit.de
To: linux-kernel@vger.kernel.org
Subject: 2.6: The hardware reports a non fatal, correctable incident occured on CPU 0.
Date: Fri, 9 Jan 2004 17:48:10 +0100 [thread overview]
Message-ID: <200401091748.10859.lkml@nitwit.de> (raw)
Hi!
I did have some very scary issues today playing with 2.6. The system was
booted and ran several times today, the longtest uptime was approximately
about an hour.
But then shortly after having booted 2.6 I got syslog messages:
The hardware reports a non fatal, correctable incident occured on CPU 0.
I shut down the machine. After this my Athlon XP 2200+ showed up as 1050MHz in
BIOS an indeed the bus frequency was set to 100 instead of 133 MHz (how can
an OS change the BIOS?!) - nevertheless the CPU should have shown up as
1500MHz. I set it back to 133 MHz - which resulted in the machine did not
even reach the BIOS no more but was rebooting automatically prior to it. I
turned off the machine for some seconds - no change. I turned it off for a
few minutes and the BIOS showed up again - with 1050MHz. So I had to set the
freq back to 133 MHz a second time. I booted my 2.4.21 kernel which seems to
run.
What the fuck is going on here?? As far as I figured out this has something to
do with MCE (CONFIG_X86_MCE=y, CONFIG_X86_MCE_NONFATAL=y) (?).
TIA
Timo
next reply other threads:[~2004-01-09 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 16:48 lkml [this message]
2004-01-09 17:35 ` 2.6: The hardware reports a non fatal, correctable incident occured on CPU 0 Jesper Juhl
[not found] ` <200401091856.16120.lkml@nitwit.de>
2004-01-09 18:10 ` Jesper Juhl
2004-01-09 23:12 ` Eric
2004-01-09 23:30 ` Prakash K. Cheemplavam
2004-01-10 17:16 ` lkml
2004-01-14 4:40 ` Dave Jones
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=200401091748.10859.lkml@nitwit.de \
--to=lkml@nitwit.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