From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Florian Weimer <fw@deneb.enyo.de>, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: [PATCH] AMD64: fix mce_cpu_quirks typos
Date: Thu, 2 Feb 2006 14:17:00 +0100 [thread overview]
Message-ID: <200602021417.00477.ak@suse.de> (raw)
In-Reply-To: <87d5i5or1i.fsf@mid.deneb.enyo.de>
On Thursday 02 February 2006 13:59, Florian Weimer wrote:
>
> > 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.
>
> Someone from AMD told Marc that fixes in pci-gart.c (probably related
> to iommu_fullflush, see the comment there) are supposed to suppress
> the error in the first place. That's why we are a bit confused
> whether the errors are really harmless (our machines do run stable,
> though).
Long ago there was a real bug in this area which caused these GART
errors legitimately, but even what that one was fixed they still
occurred occasionally.
I was told back then that there was a bug in the Northbridge
that causes them occasionally - that is why BIOS turn them off.
The kernel did that eventually too.
Of course there is some probability that you have a driver
that accesses the buffers after unmapping. The GART is currently
not flushed on unmapping because that would be
Normally such drivers are caught though because some other IOMMU
implementations on other architectures have stronger checking in this area.
-Andi
prev parent reply other threads:[~2006-02-02 13:31 UTC|newest]
Thread overview: 5+ 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
2006-02-02 12:59 ` Florian Weimer
2006-02-02 13:17 ` Andi Kleen [this message]
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=200602021417.00477.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