public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Riesen <alexander.riesen@synopsys.COM>
To: Shawn Starr <spstarr@sh0n.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MCE Error - 2.5.24 - Whats this?
Date: Wed, 26 Jun 2002 09:50:27 +0200	[thread overview]
Message-ID: <20020626075027.GA18667@riesen-pc.gr05.synopsys.com> (raw)
In-Reply-To: <1025068858.5090.1.camel@coredump>

On Wed, Jun 26, 2002 at 01:20:57AM -0400, Shawn Starr wrote:
> I got this message this evening from the syslog:
> 
> 
> MCE: The hardware reports a non fatal, correctable incident occured on
> CPU 0.
> 
> Bank 0: 9409c00000000136
> 
> 
> Is this something I should be worried about?
> 
> Included is the standard dmesg.

Dave Jones had a small parser for these codes:
http://www.codemonkey.org.uk/cruft/parsemce.c

And as it seems the parser lacks a bit of information to completely
decode the message:

~ ./parsemce
Status: (4) Machine Check in progress.
Restart IP invalid.
parsebank(0): 9409c00000000136 @ 0
        External tag parity error
        Uncorrectable ECC error
        CPU state corrupt. Restart not possible
        MISC register information valid
        Error not corrected.
        Error overflow
        Memory heirarchy error
        Request: Generic error
        Transaction type : Data
        Memory/IO : I/O

> Linux version 2.5.24 (root@unknown) (gcc version 3.1) #1 Sat Jun 22 14:58:48 EDT 2002
...

-alex

  reply	other threads:[~2002-06-26  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26  5:20 MCE Error - 2.5.24 - Whats this? Shawn Starr
2002-06-26  7:50 ` Alex Riesen [this message]
2002-06-26 14:57   ` Shawn Starr
2002-06-26 15:15     ` Matti Aarnio
2002-06-26 15:20       ` Shawn Starr
2002-06-26 15:23     ` Richard B. Johnson
2002-06-26 17:37 ` Brian Strand
2002-06-27  9:05 ` Felipe W Damasio

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=20020626075027.GA18667@riesen-pc.gr05.synopsys.com \
    --to=alexander.riesen@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spstarr@sh0n.net \
    /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