From: hpa@transmeta.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: Machine check exception? (2.4.6+SMP+VIA)
Date: 7 Jul 2001 13:54:19 -0700 [thread overview]
Message-ID: <9i7str$f30$1@tazenda.transmeta.com> (raw)
In-Reply-To: <HDEBKHLDKIDOBMHPKDDKEEAIEMAA.vhou@khmer.cc>
Followup to: <HDEBKHLDKIDOBMHPKDDKEEAIEMAA.vhou@khmer.cc>
By author: "Vibol Hou" <vhou@khmer.cc>
In newsgroup: linux.dev.kernel
>
> Hi,
>
> I was running 2.4.6-stable in SMP mode on a dual P3-1GHz machine (VIA 694D
> Chipset / MSI-6321 M/B + ) and the following message popped up after which
> the system hardlocked (no SysRQ input). What does this message mean?
>
> CPU 1: Machine Check Exception: 0000000000000004
> Bank 1: b200000000000115
> Kernel panic: CPU context corrupt
>
> Message from syslogd@delta at Sat Jul 7 13:18:36 2001 ...
> delta kernel: CPU 1: Machine Check Exception: 0000000000000004
>
> Message from syslogd@delta at Sat Jul 7 13:18:36 2001 ...
> delta kernel: Bank 1: b200000000000115
>
> Message from syslogd@delta at Sat Jul 7 13:18:36 2001 ...
> delta kernel: Kernel panic: CPU context corrupt
>
It means your hardware is bad.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-07-07 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 20:32 Machine check exception? (2.4.6+SMP+VIA) Vibol Hou
2001-07-07 20:54 ` H. Peter Anvin [this message]
2001-07-07 21:41 ` Alan Cox
2001-07-08 7:28 ` Chris Wedgwood
2001-07-08 14:00 ` Alan Cox
2001-07-08 15:33 ` Dave Jones
2001-07-08 17:04 ` Chris Wedgwood
2001-07-08 17:09 ` Dave Jones
2001-07-08 17:18 ` Chris Wedgwood
2001-07-08 20:39 ` H. Peter Anvin
2001-07-08 17:32 ` Vibol Hou
2001-07-08 20:40 ` H. Peter Anvin
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='9i7str$f30$1@tazenda.transmeta.com' \
--to=hpa@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.