public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Larry McVoy <lm@work.bitmover.com>,
	"Randy.Dunlap" <rddunlap@osdl.org>, Larry McVoy <lm@bitmover.com>,
	linux-kernel@vger.kernel.org
Subject: Re: ECC error in 2.5.64 + some patches
Date: Fri, 28 Mar 2003 00:10:15 +0000	[thread overview]
Message-ID: <20030328001015.GA19146@suse.de> (raw)
In-Reply-To: <20030327163120.GC29195@work.bitmover.com>

On Thu, Mar 27, 2003 at 08:31:20AM -0800, Larry McVoy wrote:
 > > | 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/
 > 
 > slovax /tmp a.out -b 1 -e 9000000000000151
 > Status: (-8070450532247928495) Restart IP valid.
 > 
 > What does that mean?

It means Dave sucks and hasn't done a good enough job on the parser.
parsemce is really really unintuitive to use.

There's some bits missing from your dump. Usually, MCEs look like..

 Sep  4 21:43:41 hamlet kernel: CPU 0: Machine Check Exception: 0000000000000004
 Sep  4 21:43:41 hamlet kernel: Bank 1: f600200000000152 at 7600200000000152

All we have to go on in your example is the bank status code.
(which is -s, not -e. -e would be the 00000000000000004 in the example above. [*])

So, without the missing bits, we have to fake it..

(davej@deviant:davej)$ ./a.out -b 1 -e 1 -s 9000000000000151 -a 0
Status: (1) Restart IP valid.
parsebank(1): 9000000000000151 @ 0
	External tag parity error
	Error enabled in control register
	Memory heirarchy error
	Request: Generic error
	Transaction type : Instruction
	Memory/IO : Reserved

Ignore the Status: line, thats decoded from the (faked) -e 1.

Any the wiser ? 8-)  [*]

		Dave

[*] See, unintuitive, evil and nasty.
    Given the time, I'd start over from scratch.


  reply	other threads:[~2003-03-27 23:59 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 [this message]
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=20030328001015.GA19146@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=lm@work.bitmover.com \
    --cc=rddunlap@osdl.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