From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: bragason@uni-freiburg.de (David Thor Bragason)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.6: Machine Check Exception: 0x 106BE0 (type 0x 9).
Date: Wed, 4 Jul 2001 18:08:51 +0100 (BST) [thread overview]
Message-ID: <E15Hq8x-0001AR-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.SOL.4.30.0107041820070.27099-100000@sun2.ruf.uni-freiburg.de> from "David Thor Bragason" at Jul 04, 2001 06:27:08 PM
> I stress that 2.4.4 still compiles and runs without a problem. Does this
> make any sense for a hardware problem? Was there any new hardware (cpu)
> check introduced in 2.4.5? I'd be very grateful for any tips,
Yes. 2.4.5 reports MCE rather than praying the detected error or out of
tolerance event did anything bad
2.4.6 has a "nomce" boot option too
next prev parent reply other threads:[~2001-07-04 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 16:27 2.4.6: Machine Check Exception: 0x 106BE0 (type 0x 9) David Thor Bragason
2001-07-04 17:08 ` Alan Cox [this message]
2001-07-06 19:51 ` frank
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=E15Hq8x-0001AR-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bragason@uni-freiburg.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).