From: Chris Snook <csnook@redhat.com>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: log spamming
Date: Fri, 01 Feb 2008 15:47:41 -0500 [thread overview]
Message-ID: <47A3856D.70906@redhat.com> (raw)
In-Reply-To: <200802011044.42919.gene.heskett@gmail.com>
Gene Heskett wrote:
> Greetings;
>
> I just rebooted to a new config of 2.6.24, basically trying to strip out the
> building of modules I don't use. And I enabled a couple of checks that
> weren't checked in the kernel-hacking menu. .config posted on request.
>
> Now the messages log is being spammed at 2-5 second intervals by these:
> Feb 1 10:41:08 coyote kernel: [ 3085.501037] MCE: The hardware reports a non
> fatal, correctable incident occurred on CPU 0.
> Feb 1 10:41:08 coyote kernel: [ 3085.501042] Bank 1: d400400000000152
> Feb 1 10:41:08 coyote kernel: [ 3085.501045] MCE: The hardware reports a non
> fatal, correctable incident occurred on CPU 0.
> Feb 1 10:41:08 coyote kernel: [ 3085.501048] Bank 2: d40040000000017a
>
> Always the same 2 addresses. Is this telling me I should be running memtest86
> for a couple of cycles?
Those two addresses are in the same cache line, but they are *not* in the same
128-bit ECC block. This is probably a northbridge problem, not a RAM problem.
It's not necessarily a hardware problem. I wouldn't be surprised if you swapped
CPUs and still got the same result, due to BIOS misconfiguration.
-- Chris
prev parent reply other threads:[~2008-02-01 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 15:44 log spamming Gene Heskett
2008-02-01 20:47 ` Chris Snook [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=47A3856D.70906@redhat.com \
--to=csnook@redhat.com \
--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