public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Simon Garner" <sgarner@expio.co.nz>
To: "Andi Kleen" <ak@muc.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: MSI K8D-Master - GART error 3
Date: Tue, 5 Aug 2003 12:45:01 +1200	[thread overview]
Message-ID: <028101c35aea$d2753690$0401a8c0@SIMON> (raw)
In-Reply-To: m3k79t7ykk.fsf@averell.firstfloor.org

Andi Kleen <ak@muc.de> wrote:

> There is nothing in any of my trees that generates such a message.
> If it was GART related  it would be either "GART TLB error ..." or
> "extended error gart error". But even that should not happen anymore,
> see below.
>
> I don't know what the RedHat kernel does, they may have changed the
> MCE handler over the reference port.
>

A quick google brings up this reference:
http://www.iglu.org.il/lxr/source/arch/x86_64/kernel/bluesmoke.c

The error appears to be generated by the code starting around line 152
in that file.

Btw, what is 'bluesmoke'?


>> The system also has an Adaptec 2120S scsi raid card.
>
> Probably the driver is doing something bad with the pci_dma API
> (which uses the GART on x86-64)
>

Certainly I had a lot of trouble with this card, I was pleased the
aacraid driver worked enough to let me even install this time - the Red
Hat GinGin64 installer gave a kernel panic - so I wouldn't be surprised
if this card/driver were the cause. :(


> You can always disable it with mce=off or better mce=0
> as the message seems to be caused by the periodic non fatal MCE check
> timer.
>

What will I lose by disabling this?

I just tried booting with mce=0 and I am still getting the same errors.


> However there was a bug in the MCE handler where it managed to turn on
> an GART related MCE event through the backdoor that doesn't work
> correctly and is sometimes raised spuriously. But at least in the SuSE
> beta9 kernel or recent x86-64.org kernels this should have been
> fixed. But it doesn't generate such a error message anyways,
> so it's hard to know what the exact cause is.
>
> I would suggest to retry with a recent x86-64.org CVS kernel and see
> if it still happens there.
>

I will give that a go and see what happens.

Thanks for the response Andi.

-Simon



  reply	other threads:[~2003-08-05  0:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gC1o.2gU.5@gated-at.bofh.it>
2003-08-05  0:11 ` MSI K8D-Master - GART error 3 Andi Kleen
2003-08-05  0:45   ` Simon Garner [this message]
2003-08-05 13:42     ` Andi Kleen
2003-08-10 22:43       ` Simon Garner
2003-08-10 22:56         ` Andi Kleen
2003-08-12 23:22           ` Simon Garner
2003-08-04  1:05 Simon Garner

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='028101c35aea$d2753690$0401a8c0@SIMON' \
    --to=sgarner@expio.co.nz \
    --cc=ak@muc.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