From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Eric <eric@cisu.net>
Cc: lkml@nitwit.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6: The hardware reports a non fatal, correctable incident occured on CPU 0.
Date: Sat, 10 Jan 2004 00:30:32 +0100 [thread overview]
Message-ID: <3FFF3998.9010209@gmx.de> (raw)
In-Reply-To: <200401091712.02802.eric@cisu.net>
Eric wrote:
> On Friday 09 January 2004 10:48 am, lkml@nitwit.de wrote:
>
>>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.
>
> Check your hardware CPU/MOBO/RAM. Overheating? Bad Ram? Cheap mobo?
> MCE should not be triggered under any circumstances unless it is a kernel
> bug(RARE, I believe the MCE code is simple) or you REALLY have a hardware
> problem. As said before, the bios is resetting your fsb to 100 as a fail-safe
> because something bad happened.
> BTW, check your setup, an AMD 2200+ should run at 1.8ghz i believe. If you
> are setting your FSB or multiplier too low, that might also be triggering a
> problem. A quick google lists amd xp2200+ as 1800mhz
Yes, I would also say that. With my Athlon XP 1700+ (1.466 GHZ, FSB
133MHZ) clocked at 2.2GHz (FSB200) I get MCE errors, but at 2.1GHz not,
even though I can't find stability issues at 2.2GHz. Nevertheless I
run the system at 2.1GHz.
Prakash
next prev parent reply other threads:[~2004-01-09 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 16:48 2.6: The hardware reports a non fatal, correctable incident occured on CPU 0 lkml
2004-01-09 17:35 ` 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 [this message]
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=3FFF3998.9010209@gmx.de \
--to=prakashkc@gmx.de \
--cc=eric@cisu.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@nitwit.de \
/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.