From: Pavel Machek <pavel@ucw.cz>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MCE going wild, 14 megs of this in the logs
Date: Mon, 31 Mar 2008 16:02:44 +0200 [thread overview]
Message-ID: <20080331140243.GA6212@ucw.cz> (raw)
In-Reply-To: <200803301657.53232.gene.heskett@gmail.com>
On Sun 2008-03-30 16:57:53, Gene Heskett wrote:
> Greetings;
> Mar 30 16:46:42 coyote kernel: [469249.031832] MCE: The hardware reports a non
> fatal, correctable incident occurred on CPU 0.
> Mar 30 16:46:42 coyote kernel: [469249.031838] Bank 1: d400400000000152
> Mar 30 16:46:42 coyote kernel: [469249.031841] MCE: The hardware reports a non
> fatal, correctable incident occurred on CPU 0.
> Mar 30 16:46:42 coyote kernel: [469249.031844] Bank 2: d40040000000017a
>
> Its always the same 2 addresses reported, and every 15 seconds. So I have the
> non-fatal part of MCE now turned off, & 2.6.24.4 rebuilding.
>
> I saw this once before, and a nearly round the clock run of memtest86 gave my
> memory a clean bill. Processor is an XP-2800, biostar mainboard with NForce2
> chipset. Is this possibly a known artifact of this hardware?
Thats expected. If ECC can correct the problem, memtest will pass.
I had similar problems, and was told by AMD that I had cpu with bad L2 cache.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2008-03-31 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 20:57 MCE going wild, 14 megs of this in the logs Gene Heskett
2008-03-30 23:49 ` Jiri Kosina
2008-03-31 14:02 ` Pavel Machek [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=20080331140243.GA6212@ucw.cz \
--to=pavel@ucw.cz \
--cc=gene.heskett@gmail.com \
--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