mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [PATCH] AMD64: fix mce_cpu_quirks typos
Date: 01 Feb 2006 20:59:06 +0100	[thread overview]
Message-ID: <p731wymn94l.fsf@verdi.suse.de> (raw)
In-Reply-To: <87fyn2yjpr.fsf@mid.deneb.enyo.de.suse.lists.linux.kernel>

Florian Weimer <fw@deneb.enyo.de> writes:

First please send x86-64 patches cc to the maintainer, things can
get lost in the noise of the list.

> The spurious MCE is TLB-related.  I *think* the bit for the correct
> status code is stored at position 10 HEX, not 10 DEC.  At least I
> still get those MCEs on a two-way Opteron box, even though they are
> supposed to be filtered out.

No, 10 is the correct bit index. But normally it's set by BIOS anyways.

The reason you still see it is that setting the bit here only
prevent MCE exceptions, but it's still logged and the regular polling
picks them up anyways. I have not found a nice way to handle this
(other than adding a ugly CPU specific special case in the middle
of the nice cpu independent machine check handler, which I couldn't 
bring myself to do so far...)

-Andi

       reply	other threads:[~2006-02-01 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87fyn2yjpr.fsf@mid.deneb.enyo.de.suse.lists.linux.kernel>
2006-02-01 19:59 ` Andi Kleen [this message]
2006-02-01 20:21   ` Florian Weimer
2006-02-01 20:43     ` Andi Kleen
2006-02-02 12:59       ` Florian Weimer
2006-02-02 13:17         ` [discuss] " Andi Kleen
2006-02-01 19:14 Florian Weimer
2006-02-01 19:44 ` Dave Jones
2006-02-01 19:49   ` Florian Weimer

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=p731wymn94l.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=fw@deneb.enyo.de \
    --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

Powered by JetHome