Messages in this thread | | | Date | Thu, 28 Aug 2003 15:17:08 -0700 | From | "Randy.Dunlap" <> | Subject | Re: 2.6.0-test4 and hardware reports a non fatal incident |
| |
On Thu, 28 Aug 2003 20:02:00 +0100 Matt Gibson <gothick@gothick.org.uk> wrote:
| 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,
| I'm guessing it'll parse it | from one format I don't have a clue about into a more verbose format I don't | have a clue about ;-)
That was insightful. :(
| 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?
Yes, the kernel has decided that your processor only has 1 Bank of MCE register data to report. I don't know how/why. Sorry.
-- ~Randy - 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/
| |