public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Larry McVoy <lm@work.bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: ECC error in 2.5.64 + some patches
Date: Thu, 27 Mar 2003 09:00:39 -0800	[thread overview]
Message-ID: <20030327170039.GA26452@f00f.org> (raw)
In-Reply-To: <20030327160220.GA29195@work.bitmover.com>

On Thu, Mar 27, 2003 at 08:02:20AM -0800, Larry McVoy wrote:

> My guess is that this means there was a memory error and ECC fixed
> it.

Nope.

There is an ecc driver for RAM and you'll be able to detect these
using that.  RAM ECC errors in my experience don't cause MCEs, usually
the CPU never notices.

> The only problem is that I'm reasonably sure that there isn't ECC on
> these DIMMs.

Dump the SPD and you can check...  usually the BIOS will tell you too.

> Does anyone have the table of error codes to explanations?  Google
> didn't find anything for this one.

as someone else pointed our, parsemce is what you want

> Message from syslogd@slovax at Thu Mar 27 05:53:49 2003 ...
> slovax kernel: Bank 1: 9000000000000151

Status: (9000000000000151) Restart IP valid.

*Exactly* what this means I don't know --- but I'm guessing the CPU is
overheating.  Check fans, air-flow, etc. and see if that helps.  So
far whenever I've seen the above problem it's *ALWAYS* been related to
the CPU getting too hot.


  --cw

  parent reply	other threads:[~2003-03-27 16:49 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
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 [this message]
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=20030327170039.GA26452@f00f.org \
    --to=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@work.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