From: Willy Tarreau <willy@w.ods.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Nigel Kukard <nkukard@lbsd.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CPU Context corruption
Date: Sun, 12 Sep 2004 08:36:55 +0200 [thread overview]
Message-ID: <20040912063655.GB1444@alpha.home.local> (raw)
In-Reply-To: <1094906455.21088.2.camel@localhost.localdomain>
On Sat, Sep 11, 2004 at 01:40:55PM +0100, Alan Cox wrote:
> On Sad, 2004-09-11 at 12:19, Nigel Kukard wrote:
> > What does this error mean?
> >
> >
> > CPU 0: Machine Check Exception: 0000000000000004
> > Bank 0: 820000001040080F
> >
> >
> > I have a Matsonic 9097c motherboard, 2.4Ghz prescott celeron cpu. This
> > error seems to be random. We have replaced the motherboard & cpu to no
> > avail.
>
> It normally indicates a hardware problem. The precise meaning of all the
> bits is in the Intel chip docs (volume 3). If you've swapped the
> mainboard/cpu it might just be bad RAM.
He can also get precise info with Dave Jones' parsemce tool :
http://www.kernel.org/pub/linux/kernel/people/davej/tools/
It currently says :
Status: (4) Machine Check in progress.
Restart IP invalid.
parsebank(0): 820000001040080f @ 0
External tag parity error
CPU state corrupt. Restart not possible
Bus and interconnect error
Participation: Local processor originated request
Timeout: Request did not timeout
Request: Generic error
Transaction type : Invalid
Memory/IO : Other
Since it says it's neither memory nor I/O, I think it might be related to
a PCI parity error with some card, either during transfers or config access.
Regards,
Willy
next prev parent reply other threads:[~2004-09-12 6:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 11:19 Nigel Kukard
2004-09-11 12:40 ` Alan Cox
2004-09-12 6:36 ` Willy Tarreau [this message]
2004-09-12 7:57 ` Nigel Kukard
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=20040912063655.GB1444@alpha.home.local \
--to=willy@w.ods.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nkukard@lbsd.net \
/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®