From: Jerome Glisse <glisse@freedesktop.org>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: Borislav Petkov <borislav.petkov@amd.com>,
linux-kernel@vger.kernel.org, airlied@linux.ie,
dri-devel@lists.sourceforge.net
Subject: Re: radeon KMS causes GART Table Walk Errors (was: K8 ECC error with linux-2.6.32)
Date: Wed, 16 Dec 2009 19:41:48 +0100 [thread overview]
Message-ID: <20091216184148.GB22703@localhost.localdomain> (raw)
In-Reply-To: <200912161558.30819.johannes.hirte@fem.tu-ilmenau.de>
On Wed, Dec 16, 2009 at 03:58:30PM +0100, Johannes Hirte wrote:
> Am Mittwoch 16 Dezember 2009 08:14:43 schrieb Borislav Petkov:
> > On Tue, Dec 15, 2009 at 11:00:46PM +0100, Johannes Hirte wrote:
> > > This patch (as the BIOS option) will only disable the error reports. The
> > > error itself will still occur, right? So necessary to find out why the
> > > radeon driver trigger this error.
> >
> > Because the graphics driver does aperture accesses with no
> > matching GART translation, and the hw generates mchecks for
> > that. The whole story on GART table walk errors is in section
> > "13.10.1 GART Table Walk Error Reporting" in the document here:
> > http://support.amd.com/us/Processor_TechDocs/32559.pdf
> >
> > I can't say for sure about your BIOS, but if it is done as described in
> > the abovementioned section, the BIOS option should disable logging of
> > the error, which implies reporting too.
> >
> > The patch is still needed for machines that do not have that BIOS
> > option.
>
> Disabling in BIOS doesn't made any difference. The errors were still reported.
> Your patch disabled it. But I think this will make work harder for driver
> developers as they won't get this error anymore. Could this be made changeable
> on runtime/boottime?
>
> I've added drm people to CC as they're responsible for this error.
>
>
> regards,
> Johannes
More context would be usefull. Are you using KMS ? If so is your userspace
KMS capable ? Does this GART error happen all the time or only after sometimes
or when doing somethings specific ?
Cheers,
Jerome
next prev parent reply other threads:[~2009-12-16 18:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 21:02 K8 ECC error with linux-2.6.32 Johannes Hirte
2009-12-11 21:11 ` Johannes Hirte
2009-12-11 21:19 ` Borislav Petkov
2009-12-11 21:39 ` Johannes Hirte
2009-12-11 22:07 ` Borislav Petkov
2009-12-11 22:12 ` Johannes Hirte
2009-12-14 13:26 ` Johannes Hirte
2009-12-14 22:23 ` Borislav Petkov
2009-12-15 7:08 ` Johannes Hirte
2009-12-15 15:30 ` Borislav Petkov
2009-12-15 22:00 ` Johannes Hirte
2009-12-16 7:14 ` Borislav Petkov
2009-12-16 14:58 ` radeon KMS causes GART Table Walk Errors (was: K8 ECC error with linux-2.6.32) Johannes Hirte
2009-12-16 16:41 ` Borislav Petkov
2009-12-17 3:07 ` Johannes Hirte
2009-12-17 7:22 ` Borislav Petkov
2009-12-17 19:03 ` Johannes Hirte
2009-12-18 11:56 ` Borislav Petkov
2009-12-16 18:41 ` Jerome Glisse [this message]
2009-12-16 19:31 ` Johannes Hirte
2009-12-18 13:47 ` Johannes Hirte
2009-12-18 14:44 ` Jerome Glisse
2009-12-18 15:37 ` Johannes Hirte
2009-12-24 19:04 ` Johannes Hirte
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=20091216184148.GB22703@localhost.localdomain \
--to=glisse@freedesktop.org \
--cc=airlied@linux.ie \
--cc=borislav.petkov@amd.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=johannes.hirte@fem.tu-ilmenau.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
all inboxes | Powered by JetHome®