Re: 2.6.0-test4 and hardware reports a non fatal incident

From: Matt Gibson (gothick_at_gothick.org.uk)
Date: 08/28/03

  • Next message: chas williams: "Re: [lukasz@wsisiz.edu.pl: Re: [Linux-ATM-General] Re: linux-2.4.22 Oops on ATM PCA-200EPC]" 
    To: linux-kernel@vger.kernel.org
Date:	Thu, 28 Aug 2003 20:02:00 +0100

    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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: chas williams: "Re: [lukasz@wsisiz.edu.pl: Re: [Linux-ATM-General] Re: linux-2.4.22 Oops on ATM PCA-200EPC]"

    Relevant Pages

    • RFC: Representation of large hex values
      ... this isn't strictly a kernel thing - but it seems to be a good ... it would seem best to use a distinct format character; ... I don't think there is the necessity to force zero padding, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: Re: [License of kernel components] linux-2.x.y/Documentation/logo.GIF should be logo.PNG?
      ... > AFAIK the GIF patent expired a year ... do you not think that we can support the PNG format through ... kernel hackers use this format before this year: ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] Add getdents32t syscall
      ... and then ask the kernel to fix it later when it was done ... > wrong in glibc. ... This is a totally new format that is totally unnecessary, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH 1/5] kbuild: default kernel image
      ... binary image of the kernel, where compressed images were the normal. ... file format do I need" problems. ... The problem starts happening when boot loaders think they can dictate ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Machine check expection panic
      ... > the kernel on boot when I have it enabled ... > Kernel Panic: CPU context corrupt. ... > Little bit of hardware info: ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)