All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Arthur Perry <kernel@linuxfarms.com>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: GART error 11 (fwd)
Date: 27 May 2004 19:13:52 +0200
Date: Thu, 27 May 2004 19:13:52 +0200	[thread overview]
Message-ID: <20040527171352.GA36906@colin2.muc.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0405271135280.18743@tiamat.perryconsulting.net>

On Thu, May 27, 2004 at 12:05:38PM -0400, Arthur Perry wrote:
> And perhaps this may be the case, maybe the hardware should not report
> these errors (which may not actually be gart errors after all) just
> because the GART has been set up.
> However, my failure mode seems to be that I only get these errors when the
> agp driver is loaded on a machine that does not have an agp bus.
> I also have IOMMUs disabled in the BIOS by default.

The kernel will allocate an aperture if there isn't one (over memory
when needed) 

> The BIOS is not enabling the GART at all, so it must be done by the
> kernel. A boot into DOS will show the Gart Aperture Control Register set

Correct. 

> to all zeros, where a boot to Linux 2.4 w/AGP will boot with them enabled.
> Again, the failure mode recognised so far is that the "gart errors" appear
> when this register is set up.
> 
> What the user sees at this point is even though they have the
> "GART error reporting enable" disabled, they still see "GART" errors.

The GART error MCE does not work properly in K8. Normally the BIOS
disables it, but some early kernels managed to still enable
it through a backdoor.

You can rule that out by using an recent 2.4 kernel.org kernel or
the SLES8-SP3 kernel if you want a distribution kernel (no idea
if RH has the fix or not) 

But it's possible that it's really a different MCE.


> 
> If you are suggesting that there may be a real hardware error here that is
> being misinterpreted by the kernel, my next course of action is to collect
> that real error syndrome and decode it.

Yes, that's a good idea. 

> 
> I can volunteer to assist with fixing this decoding function as well,
> since I have a good test case here.

We already have a patch for that, it just needs a bit more work
before it can be merged.

-Andi

  reply	other threads:[~2004-05-27 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20uGg-17i-23@gated-at.bofh.it>
2004-05-27 15:26 ` GART error 11 (fwd) Andi Kleen
2004-05-27 16:05   ` Arthur Perry
2004-05-27 17:13     ` Andi Kleen [this message]
2004-05-27 15:05 Arthur Perry

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=20040527171352.GA36906@colin2.muc.de \
    --to=ak@muc.de \
    --cc=kernel@linuxfarms.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.