From: Dave Jones <davej@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mike Fedyk <mfedyk@matchmail.com>,
Paul Gortmaker <p_gortmaker@yahoo.com>,
marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bluesmoke/MCE support optional
Date: Fri, 1 Mar 2002 13:55:48 +0100 [thread overview]
Message-ID: <20020301135547.F7662@suse.de> (raw)
In-Reply-To: <20020301024710.GF2711@matchmail.com> <E16gmBy-0003V5-00@the-village.bc.nu>
In-Reply-To: <E16gmBy-0003V5-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Mar 01, 2002 at 12:31:18PM +0000
On Fri, Mar 01, 2002 at 12:31:18PM +0000, Alan Cox wrote:
> > > + ranging from a warning message on the console, to halting the machine.
> > > + Your processor must be a Pentium or newer to support this - check the
> > > + flags in /proc/cpuinfo for mce. Note that some older Pentium systems
> > > + have a design flaw which leads to false MCE events - for these and
> > > + old non-MCE processors (386, 486), say N. Otherwise say Y.
>
> Its not necessary to say N. On a pentium box with the newer MCE setup code
> you must force MCE on. On non MCE capable CPU's we just dont set it up.
The help text should probably document the nomce boot option too.
btw, anyone else posting in this thread getting crap like..
http://www.codemonkey.org.uk/duhhh.txt ?
I've got them from two different threads now, which is starting
to get annoying.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-03-01 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 15:01 [PATCH] bluesmoke/MCE support optional Paul Gortmaker
2002-03-01 0:11 ` Alan Cox
2002-03-01 7:18 ` Paul Gortmaker
2002-03-01 11:51 ` Alan Cox
2002-03-01 9:56 ` Dave Jones
2002-03-01 2:47 ` Mike Fedyk
2002-03-01 12:31 ` Alan Cox
2002-03-01 12:55 ` Dave Jones [this message]
2002-03-03 10:57 ` Paul Gortmaker
2002-03-03 13:53 ` Alan Cox
2002-03-01 15:10 ` Marcelo Tosatti
2002-03-01 17:29 ` Alan Cox
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=20020301135547.F7662@suse.de \
--to=davej@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mfedyk@matchmail.com \
--cc=p_gortmaker@yahoo.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