public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: kwijibo@zianet.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Machine check expection panic
Date: Wed, 6 Aug 2003 18:05:53 -0500	[thread overview]
Message-ID: <20030806230553.GG31810@waste.org> (raw)
In-Reply-To: <3F3182B5.3040301@zianet.com>

On Wed, Aug 06, 2003 at 04:35:33PM -0600, kwijibo@zianet.com 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 : http://www.selenic.com : of or relating to the moon

  reply	other threads:[~2003-08-06 23:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 22:35 Machine check expection panic kwijibo
2003-08-06 23:05 ` Matt Mackall [this message]
2003-08-07  0:27 ` Dave Jones
     [not found] <3F3182B5.3040301@zianet.com.suse.lists.linux.kernel>
     [not found] ` <20030807002722.GA3579@suse.de.suse.lists.linux.kernel>
2003-08-07  1:00   ` Andi Kleen
2003-08-07  1:34     ` Dave Jones
2003-08-10  8:12     ` kwijibo
2003-08-10 13:07       ` Andi Kleen
2003-08-10 21:04         ` kwijibo
2003-08-11 10:15           ` Petr Vandrovec
2003-08-11 11:34             ` Bartlomiej Zolnierkiewicz

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=20030806230553.GG31810@waste.org \
    --to=mpm@selenic.com \
    --cc=kwijibo@zianet.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox