From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Vibol Hou <vhou@khmer.cc>, Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Machine check exception? (2.4.6+SMP+VIA)
Date: Sun, 8 Jul 2001 19:28:05 +1200 [thread overview]
Message-ID: <20010708192805.C26213@weta.f00f.org> (raw)
In-Reply-To: <E15IzpL-0006Hq-00@the-village.bc.nu>
In-Reply-To: <E15IzpL-0006Hq-00@the-village.bc.nu>
On Sat, Jul 07, 2001 at 10:41:23PM +0100, Alan Cox wrote:
It means your processor flagged a fault. The b2....115 number
decodes to info about the fault cause if you grab the PIII manual.
Stupid things like overheating. wrong voltages can also trigger it
Is there any reason why, with proper MCE checking for both K7 and PIII
we can't automatically off-line processors when they start doing bad
things?
Sure, its a pretty lousy thing to do, but if you buys you a few
minutes and allows userland to initiate some kind of remedy
(pager("HELP"); system("shutdown"); sort of thing)...
Also, I'm pretty sure I was seeing overheating problems or something
on a K7 at one point, but never saw MCE; I take it this code only
exists fully in -ac kernels? I looked in Linus' tree and couldn't see
anything.
--cw
next prev parent reply other threads:[~2001-07-08 7:28 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
2001-07-07 21:41 ` Alan Cox
2001-07-08 7:28 ` Chris Wedgwood [this message]
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=20010708192805.C26213@weta.f00f.org \
--to=cw@f00f.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vhou@khmer.cc \
/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