mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Avuton Olrich" <avuton@gmail.com>
To: "Rumi Szabolcs" <rumi_ml@rtfm.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon64 + Nforce4 MCE panic
Date: Thu, 13 Jul 2006 00:12:50 -0700	[thread overview]
Message-ID: <3aa654a40607130012h2c18f45av4d05244facaa01a1@mail.gmail.com> (raw)
In-Reply-To: <20060713090146.690d4759.rumi_ml@rtfm.hu>

On 7/13/06, Rumi Szabolcs <rumi_ml@rtfm.hu> wrote:
> Hello!
>
> Tonight I had a kernel panic (full hang) with the following on the console:
>
> CPU 0: Machine Check Exception: 0000000000000004
> Bank 4: b200000000070f0f
> Kernel panic - not syncing: CPU context corrupt
>
> I tried to decode this:
>
> # ./parsemce -e 0000000000000004 -b 4 -s b200000000070f0f -a 0
> Status: (4) Machine Check in progress.
> Restart IP invalid.
> parsebank(4): b200000000070f0f @ 0
>         External tag parity error
>         CPU state corrupt. Restart not possible
>         Error enabled in control register
>         Error not corrected.
>         Bus and interconnect error
>         Participation: Generic
>         Timeout:
>         Request: Generic error
>         Transaction type : Invalid
>         Memory/IO : Other
>
> # echo 'CPU 0: Machine Check Exception: 0000000000000004 Bank 4: b200000000070f0f' | mcelog --ascii --k8
> HARDWARE ERROR. This is *NOT* a software problem!
> Please contact your hardware vendor
> CPU 0 4 northbridge   Northbridge Watchdog error
>        bit57 = processor context corrupt
>        bit61 = error uncorrected
>   bus error 'generic participation, request timed out
>       generic error mem transaction
>       generic access, level generic'
> STATUS b200000000070f0f MCGSTATUS 4
>
> I've been searching for and found some additional info, it
> looks like I'm not the first experiencing this problem:
>
> http://kerneltrap.org/node/4993
>
> Here ^^^ it is suggested that there was some thread about A64 MCEs
> on LKML but I failed to find it so I decided to post... sorry if
> it's redundant.
>
> The kernel is 2.6.16-gentoo-r9 and the CPU is an A64 "Venice" 3500+
> I can post further hw/sw environment information if req'd.

I had this same problem, search the lkml if you're interested in
investigating this further, I had the problem, was told it was
hardware, replaced my motherboard with the same model, the MCE
continued to occur, replaced the motherboard with a different model
and the MCE went away. It was some Biostar IIRC, but you can check the
archives if you really want to find out.

Good luck
-- 
avuton
--
 Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2006-07-13  7:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  7:01 Rumi Szabolcs
2006-07-13  7:12 ` Avuton Olrich [this message]
2006-07-13 11:44 ` Alan Cox
2006-07-14  4:30 ` Allen Martin
2006-07-14  7:37   ` Rumi Szabolcs
2006-07-14 18:18     ` Allen Martin
2006-07-15  7:28       ` Rumi Szabolcs

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=3aa654a40607130012h2c18f45av4d05244facaa01a1@mail.gmail.com \
    --to=avuton@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rumi_ml@rtfm.hu \
    /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

all inboxes | Powered by JetHome®