From: David Weinehall <tao@acc.umu.se>
To: Andi Kleen <ak@muc.de>
Cc: Dave Jones <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.2, AMD kernel: MCE: The hardware reports a non fatal, correctable incident
Date: Thu, 4 Mar 2004 16:01:17 +0100 [thread overview]
Message-ID: <20040304150117.GE19111@khan.acc.umu.se> (raw)
In-Reply-To: <m3llmgj0xc.fsf@averell.firstfloor.org>
On Thu, Mar 04, 2004 at 12:39:59PM +0100, Andi Kleen wrote:
> 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.
Well, the only way to solve that problem is to test it, right? And what
better way to test it than to switch i386 over to it too :-)
> 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.
Well, losing functionality would be bad.
> Extended register logging for P4 is also not implemented right now,
> but that hardly seems like a needed feature.
No opinion here.
Regards: David Weinehall
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2004-03-04 15:02 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
2004-03-04 15:01 ` David Weinehall [this message]
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=20040304150117.GE19111@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=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
all inboxes | Powered by JetHome®