From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ECC error in 2.5.64 + some patches
Date: Thu, 27 Mar 2003 08:22:12 -0800 [thread overview]
Message-ID: <20030327082212.252159e0.rddunlap@osdl.org> (raw)
In-Reply-To: <20030327160220.GA29195@work.bitmover.com>
On Thu, 27 Mar 2003 08:02:20 -0800 Larry McVoy <lm@bitmover.com> wrote:
| I'm getting these on the machine we use to do the BK->CVS conversions.
| My guess is that this means there was a memory error and ECC fixed it.
| The only problem is that I'm reasonably sure that there isn't ECC on
| these DIMMs. Does anyone have the table of error codes to explanations?
| Google didn't find anything for this one.
|
| Thanks.
|
| Message from syslogd@slovax at Thu Mar 27 05:53:49 2003 ...
| slovax kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
|
| Message from syslogd@slovax at Thu Mar 27 05:53:49 2003 ...
| slovax kernel: Bank 1: 9000000000000151
You can try the Dave Jones "parsemce" tool on it, from
http://www.codemonkey.org.uk/cruft/parsemce.c/
--
~Randy
next prev parent reply other threads:[~2003-03-27 16:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 21:28 3ware driver errors Steven Pritchard
2003-03-25 1:01 ` Jeff V. Merkey
2003-03-24 23:44 ` Larry McVoy
2003-03-25 0:07 ` Mark Hahn
2003-03-25 1:25 ` Jeff V. Merkey
2003-03-25 3:12 ` Steven Pritchard
2003-03-25 3:11 ` Kevin P. Fleming
2003-03-25 15:25 ` Ezra Nugroho
2003-03-25 15:26 ` Roy Sigurd Karlsbakk
2003-03-25 16:26 ` Ezra Nugroho
2003-03-27 16:02 ` ECC error in 2.5.64 + some patches Larry McVoy
2003-03-27 16:17 ` Tim Schmielau
2003-03-27 16:27 ` Larry McVoy
2003-03-27 16:39 ` Tim Schmielau
2003-03-27 16:22 ` Randy.Dunlap [this message]
2003-03-27 16:31 ` Larry McVoy
2003-03-28 0:10 ` Dave Jones
2003-03-27 16:31 ` Dave Jones
2003-03-27 17:00 ` Chris Wedgwood
2003-03-27 17:19 ` Dominik Kubla
2003-03-27 17:25 ` Chris Wedgwood
2003-04-15 4:34 ` Bill Davidsen
2003-04-15 13:24 ` Larry McVoy
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=20030327082212.252159e0.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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
all inboxes | Powered by JetHome®