From: Dave Jones <davej@redhat.com>
To: lkml@nitwit.de
Cc: Eric <eric@cisu.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6: The hardware reports a non fatal, correctable incident occured on CPU 0.
Date: Wed, 14 Jan 2004 04:40:45 +0000 [thread overview]
Message-ID: <20040114044045.GA23845@redhat.com> (raw)
In-Reply-To: <200401101816.22612.lkml@nitwit.de>
On Sat, Jan 10, 2004 at 06:16:22PM +0100, lkml@nitwit.de wrote:
> > 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.
>
> Well, my system did run very stable and in the meantime again does run very
> stable on both, 2.4.21 and Windows XP...
Neither of which check for the presence of these errors.
> > > 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)
> > > (?).
> >
> > Leave it enabled, its a good thing to tell you when you have bad hardware.
> > Its not a kernel problem, but a feature.
>
> Well, it is a good thing to tell me, but it's not a good thing to make my
> system auto-reset itself before reaching the BIOS afterwards...
The non-fatal MCE code doesn't do anything like that. Any odd side-effects that you
observed were very likely due to whatever caused the MCE in the first place.
Dave
prev parent reply other threads:[~2004-01-14 4:43 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
2004-01-10 17:16 ` lkml
2004-01-14 4:40 ` Dave Jones [this message]
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=20040114044045.GA23845@redhat.com \
--to=davej@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox