All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Gibson <gothick@gothick.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4 and hardware reports a non fatal incident
Date: Thu, 28 Aug 2003 20:02:00 +0100	[thread overview]
Message-ID: <200308282002.00758.gothick@gothick.org.uk> (raw)
In-Reply-To: <20030828084640.68fe827d.rddunlap@osdl.org>

On Thursday 28 Aug 2003 16:46, Randy.Dunlap wrote:
> Use "parsemce" from here:
>   http://www.codemonkey.org.uk/projects/parsemce/
> to decode it.

Hi Randy,

The format seems to have changed rather a lot since that was written.  All I 
get is:

Aug 17 11:25:13 codewave kernel: MCE: The hardware reports a non fatal, 
correctable incident occurred on CPU 0.
Aug 17 11:25:13 codewave kernel: Bank 0: dc0000000000050b

...but what parsemce seems to be expecting is:

 Sample kernel output..
 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
Sep  4 21:43:41 hamlet kernel: Bank 2: d40040000000017a at 540040000000017a
Sep  4 21:43:41 hamlet kernel: Kernel panic: CPU context corrupt

As a result, I'm still no more enlightened.  I can't quite figure out from 
reading the parser what values to put where, as it seems to expect a few 
more than I have.  Any tips?

Ta,

Matt

-- 
"It's the small gaps between the rain that count,
 and learning how to live amongst them."
	      -- Jeff Noon

  parent reply	other threads:[~2003-08-28 20:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 13:48 2.6.0-test4 and hardware reports a non fatal incident Tomasz Czaus
2003-08-28 15:46 ` Randy.Dunlap
2003-08-28 17:28   ` Matt Gibson
2003-08-28 19:02   ` Matt Gibson [this message]
2003-08-28 22:17     ` Randy.Dunlap
2003-08-30 10:49       ` Matt Gibson
2003-08-30 12:44         ` Matt Gibson
2003-08-30 13:35           ` Dave Jones
2003-08-30 13:48             ` Matt Gibson
2003-08-30 13:51               ` Dave Jones
2003-08-30 13:10       ` Dave Jones

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=200308282002.00758.gothick@gothick.org.uk \
    --to=gothick@gothick.org.uk \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.