From: Mike <maneman@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Machine Check Exception in >2.4.5: Where to comment MCE out?
Date: Thu, 25 Oct 2001 01:27:08 +0200 [thread overview]
Message-ID: <3BD74E4C.8A9BB52C@gmx.net> (raw)
Hi,
I searched the LKML archive and found a 3-post-thread relevant to my
problem between July 4th-6th entitled:
"Re: 2.4.6: Machine Check Exception: 0x 106BE0 (type 0x 9)" here:
<http://uwsg.iu.edu/hypermail/linux/kernel/0107.0/0470.html>
Like the Compaq mentioned in that post, I _also_ have a Compaq LTE 52xx
laptop (5250) which chokes on bootup.
I let this problem sit since 2.4.5 came out because that's when this
problem first occurred. Only recently did I get around to hunt down a
fix.
I understood that I was to "comment out" "MCE" in the sources.
So I did a 'grep -r 'MCE' ./' in the sources and found bunch of
occurrences, the first ones being:
./include/asm-i386/processor.h:#define X86_CR4_MCE 0x0040
/* Machine check enable */
./include/asm-i386/cpufeature.h:#define X86_FEATURE_MCE (0*32+
7) /* Machine Check Architecture */
So now my question is: what exactly should I comment out? One? Both? In
_all_ sources?
Please bear with me as I know next to nothing of C (or any language for
that matter).
Also: i'm not an LKML-subscriber so could you please CC: this to me?
Thanks and cheers,
-Mike
<maneman AT gmx DOT net>
ý:.˱Êâmçë¢kaÉb²ßìzwm
ébïî˱Êâmébìÿêçz_âØ^nr¡ö¦zË\x1aëh¨èÚ&£ûàz¿äz¹Þú+Ê+zf£¢·h§~Ûiÿÿïêÿêçz_è®\x0fæj:+v¨þ)ߣømSåy«\x1eæ¶\x17
\x01\x06ÛiÿÿðÃ\x0fí»\x1fè®\x0fåi\x7f
next reply other threads:[~2001-10-24 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 23:27 Mike [this message]
2001-10-24 23:38 ` Dave Jones
2001-10-24 23:40 ` Alan Cox
2001-10-25 21:24 ` Ricky Beam
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=3BD74E4C.8A9BB52C@gmx.net \
--to=maneman@gmx.net \
--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
all inboxes | Powered by JetHome®