From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Legend W." <mrwangxc@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Machine Check Exception !
Date: Sat, 31 Dec 2005 01:04:55 +0000 [thread overview]
Message-ID: <1135991096.28365.46.camel@localhost.localdomain> (raw)
In-Reply-To: <71a51c440512261852u593a2795y@mail.gmail.com>
On Maw, 2005-12-27 at 10:52 +0800, Legend W. wrote:
> parsebank(0): b20000001040080f @ 3
> External tag parity error
> CPU state corrupt. Restart not possible
> Error enabled in control register
> Error not corrected.
> Bus and interconnect error
> Participation: Local processor originated request
> Timeout: Request did not timeout
> Request: Generic error
> Transaction type : Invalid
> Memory/IO : Other
>
> Can anybody please enlighten me what this means or what a possible
> problem behind might be?
Executive summary - your hardware is broken. In this case its reporting
a parity error on external tag bits - presumably cache bits. "Contact
your system vendor for advice" as they say 8)
next prev parent reply other threads:[~2005-12-31 1:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 2:52 Machine Check Exception ! Legend W.
2005-12-27 6:46 ` Nauman Tahir
2005-12-27 17:51 ` Lee Revell
2005-12-31 1:04 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-25 18:37 Machine Check Exception ? Dana Lacoste
2002-01-25 18:48 ` Dave Jones
2002-01-25 10:47 Stephan von Krawczynski
2002-01-25 12:37 ` Marcel Kunath
2002-01-25 16:36 ` Stephan von Krawczynski
2002-01-25 17:22 ` Dave Jones
2002-01-25 16:47 ` Stephan von Krawczynski
2002-01-25 12:40 ` Denis Oliver Kropp
2002-01-25 13:17 ` Dave Jones
2002-01-25 13:26 ` Denis Oliver Kropp
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=1135991096.28365.46.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mrwangxc@gmail.com \
/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