public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: marcelo@conectiva.com.br
Cc: alan@lxorguk.ukuu.org.uk, davej@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bluesmoke/MCE support optional
Date: Sun, 03 Mar 2002 05:57:12 -0500	[thread overview]
Message-ID: <3C820188.5A4F095C@yahoo.com> (raw)
In-Reply-To: <20020301024710.GF2711@matchmail.com> <E16gmBy-0003V5-00@the-village.bc.nu> <20020301135547.F7662@suse.de>

Dave Jones wrote:
> 
> On Fri, Mar 01, 2002 at 12:31:18PM +0000, Alan Cox wrote:
>  >
>  > 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.

This clarifies the P5 behaviour and documents the related boot arguments, 
as suggested by Alan and Dave J. respectively.

Patch against 2.4.19p2.

Paul.

--- Documentation/Configure.help~	Sun Mar  3 05:04:18 2002
+++ Documentation/Configure.help	Sun Mar  3 05:56:49 2002
@@ -17666,8 +17666,12 @@
   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.
+  have a design flaw which leads to false MCE events - hence MCE is
+  disabled on all P5 processors, unless explicitly enabled with "mce"
+  as a boot argument.  Similarly, if MCE is built in and creates a
+  problem on some new non-standard machine, you can boot with "nomce" 
+  to disable it.  MCE support simply ignores non-MCE processors like
+  the 386 and 486, so nearly everyone can say Y here.
 
 Toshiba Laptop support
 CONFIG_TOSHIBA



  reply	other threads:[~2002-03-03 11:01 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
2002-03-03 10:57       ` Paul Gortmaker [this message]
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=3C820188.5A4F095C@yahoo.com \
    --to=p_gortmaker@yahoo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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