[lkml]   [2003]   [Aug]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Machine check expection panic
On Wed, Aug 06, 2003 at 04:35:33PM -0600, wrote:
> I decided to try out the new 2.6.0-test2 kernel today but
> ran into a problem with booting it. I narrowed it down to
> the machine check expection code. I get this panic from
> the kernel on boot when I have it enabled
> CPU0: Machine Check Exception: 0000000000000004
> Bank0: f606200000000833 at 0000000000004040
> Kernel Panic: CPU context corrupt.

$ parsemce -b 0 -e 0000000000000004 -s f606200000000833 -a 0000000000004040
Status: (4) Machine Check in progress.
Restart IP invalid.
parsebank(0): f606200000000833 @ 4040
External tag parity error
Uncorrectable ECC error
CPU state corrupt. Restart not possible
Address in addr register valid
Error enabled in control register
Error not corrected.
Error overflow
Bus and interconnect error
Participation: Local processor originated request
Timeout: Request did not timeout
Request: Generic error
Transaction type : Instruction
Memory/IO : Other

Looks like corruption with your L2 cache. Odds are its heat-related.

> I disabled this option in the kernel and recompiled and everything
> went smooth. I figured maybe there could actually possibly be
> something wrong with the CPU but I can boot with RedHat's
> 2.4.20-19 kernel fine which I *think* includes machine check exception
> code. I have no beef with leaving the exception code out but I figured
> someone on this list may want to know.
> Little bit of hardware info:
> Tyan 2466 motherboard
> 2 Athon MP 1200 processors

Matt Mackall : : of or relating to the moon
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:47    [W:0.060 / U:1.928 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site