From: Andi Kleen <ak@muc.de>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.2, AMD kernel: MCE: The hardware reports a non fatal, correctable incident
Date: Thu, 04 Mar 2004 12:39:59 +0100 [thread overview]
Message-ID: <m3llmgj0xc.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1vq6q-7YO-33@gated-at.bofh.it> (Dave Jones's message of "Tue, 02 Mar 2004 23:00:46 +0100")
Dave Jones <davej@redhat.com> writes:
> I'm toying with the idea of marking it CONFIG_BROKEN for 2.6,
> and fixing it up later.
I would actually suggest to switch over to the rewritten MCE handler
from x86-64 for i386 too. IMHO it is much better. It is race free,
does not panic the machine if not needed, CPU independent, follows the
Intel and AMD recommendations, run time sysfs configurable, logs to a
separate device and does lots of other things much better
[of course I'm biased on that a bit]. Disadvantage is that it isn't
as well tested.
I haven't tried it on i386, but i wrote it to be easily portable
to 32bit too. It does periodic MCEs too, but with a much lower
frequency and they could be turned off. I'm considering to turn
them off for x86-64 too, because they seem to only log one bit
ECC errors all the time. But with the new separate log device it's much
less of a problem.
The only thing you would lose is the support for P5 MCEs, but these
could be relatively easily readded if that should be a problem.
Extended register logging for P4 is also not implemented right now,
but that hardly seems like a needed feature.
-Andi
next parent reply other threads:[~2004-03-04 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2004-03-04 15:01 ` Linux 2.6.2, AMD kernel: MCE: The hardware reports a non fatal, correctable incident David Weinehall
2004-03-02 18:00 Davi Leal
2004-03-02 21:55 ` Dave Jones
2004-03-03 8:58 ` Philippe Elie
2004-03-04 4:02 ` Joseph Fannin
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=m3llmgj0xc.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=davej@redhat.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