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: Wed, 1 Feb 2006 21:43:19 +0100 [thread overview]
Message-ID: <200602012143.19867.ak@suse.de> (raw)
In-Reply-To: <87ek2mx22i.fsf@mid.deneb.enyo.de>
On Wednesday 01 February 2006 21:21, Florian Weimer wrote:
> > 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...)
>
> Someone tried to track these messages down together with someone else
> from AMD, but they never got it finished.
They could have saved themselves a lot of work by just asking
at the right mailing lists (which is not l-k BTW)
> For reference, here's the lspci -n output for the system. It's a
> two-way Opteron box (248, 2.2 GHz, stepping 10) with 8 GB of RAM.
> (BIOS and chipset details are not available to me at the moment.)
> The MCEs only appeared after a switch to a 64-bit kernel (2.6.15.2),
> adding the second CPU, along with 4 GB of RAM. Previously, the box
> ran 2.6.13 in 32-bit mode, and no MCEs appeared regularly.
The 64bit kernel uses the AGP aperture as IOMMU, the 32bit kernel doesn't.
It's a known documented hardware bug that this causes spurious GART errors.
That is why the BIOS and Linux disable them. Unfortunately the Linux
MCE handler is too thorough and picks them up anyways as corrected events.
-Andi
next prev parent reply other threads:[~2006-02-01 22:55 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 ` [PATCH] AMD64: fix mce_cpu_quirks typos Andi Kleen
2006-02-01 20:21 ` Florian Weimer
2006-02-01 20:43 ` Andi Kleen [this message]
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=200602012143.19867.ak@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