From: Dave Jones <davej@suse.de>
To: Sebastian Droege <sebastian.droege@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.6-dj2] MCE reports 2 non fatal incidents on CPU0 every 2 seconds
Date: Tue, 19 Mar 2002 00:26:41 +0100 [thread overview]
Message-ID: <20020319002641.M17410@suse.de> (raw)
In-Reply-To: <20020318193816.44548361.sebastian.droege@gmx.de>
On Mon, Mar 18, 2002 at 07:38:16PM +0100, Sebastian Droege wrote:
> What exactly is the meaning of these 2 messages?
> MCE: The hardware reports a non fatal, correctable incident occured on CPU 0.
> Bank 0: 1000000000000000
> MCE: The hardware reports a non fatal, correctable incident occured on CPU 0.
> Bank 4: 2200000000000011
>
> I get them right after boot and every 2 seconds
> Is my CPU (it's an 3 year-old P-II 350 running 24/7) dying or what's up?
It may mean I'm having a bad month hacking the mce code, I'll look
into this later... Might be the same dumb mistake as last time
(works on Athlon but Intel behaves differently perhaps)
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
prev parent reply other threads:[~2002-03-18 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 18:38 [2.5.6-dj2] MCE reports 2 non fatal incidents on CPU0 every 2 seconds Sebastian Droege
2002-03-18 23:26 ` 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=20020319002641.M17410@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.droege@gmx.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