From: Philippe Elie <phil.el@wanadoo.fr>
To: Dave Jones <davej@redhat.com>, Davi Leal <davi@leals.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.2, AMD kernel: MCE: The hardware reports a non fatal, correctable incident
Date: Wed, 3 Mar 2004 08:58:42 +0000 [thread overview]
Message-ID: <20040303085842.GB399@zaniah> (raw)
In-Reply-To: <20040302215554.GA29752@redhat.com>
On Tue, 02 Mar 2004 at 21:55 +0000, Dave Jones wrote:
> On Tue, Mar 02, 2004 at 07:00:16PM +0100, Davi Leal wrote:
> > What about this message?. Note that the system works. I have not had to
> > reboot. What meens the below message?.
> >
>
> The original plan behind that option was to find hardware faults early,
> but it seems to trigger a lot of false positives for various reasons.
> Part of this problem is that MCEs can also be generated on some hardware
> by doing something silly like reading from a reserved part of your
> motherboard chipset..
>
> There are also CPU errata that can cause them to falsely trigger in
> some unusual cases, but I've not had time to go through the various
> errata datasheets to blacklist affected CPUs unfortunatly.
>
> I'm toying with the idea of marking it CONFIG_BROKEN for 2.6,
> and fixing it up later.
I'm unsure if it's a good idea it's broken only on broken HW, people
wanting stable box try to buy sane HW and don't enable CONFIG_BROKEN
so they will never see if their HW are starting to be out of spec.
Perhaps rewording the option help and the error message to say it's
known to report false positive...
regards,
Phil
next prev parent reply other threads:[~2004-03-03 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 18:00 Davi Leal
2004-03-02 21:55 ` Dave Jones
2004-03-03 8:58 ` Philippe Elie [this message]
2004-03-04 4:02 ` Joseph Fannin
[not found] <1vmlH-3HK-5@gated-at.bofh.it>
[not found] ` <1vq6q-7YO-33@gated-at.bofh.it>
2004-03-04 11:39 ` Andi Kleen
2004-03-04 15:01 ` David Weinehall
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=20040303085842.GB399@zaniah \
--to=phil.el@wanadoo.fr \
--cc=davej@redhat.com \
--cc=davi@leals.com \
--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®