linux-kernel - Re: radeon KMS causes GART Table Walk Errors (was: K8 ECC error with linux-2.6.32)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091216164156.GF11618@aftab>
Date:	Wed, 16 Dec 2009 17:41:56 +0100
From:	Borislav Petkov <borislav.petkov@....com>
To:	Johannes Hirte <johannes.hirte@....tu-ilmenau.de>
CC:	linux-kernel@...r.kernel.org, airlied@...ux.ie,
	dri-devel@...ts.sourceforge.net
Subject: Re: radeon KMS causes GART Table Walk Errors (was: K8 ECC error
 with linux-2.6.32)

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. 

Hmm. It would be interesting to know what the BIOS does exactly
on your machine. We could easily find that out by installing the
x86info tool (either prepackaged for your distro or from here:
git://git.choralone.org/git/x86info) and doing as root:

lsmsr MC4 -V3

and sending me the output. Make sure the amd64_edac module is not loaded.

> Your patch disabled it.

Thanks for testing.

> 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?

yep, we have that. You have to set 'report_gart_errors' module parameter
to 1 when loading amd64_edac and GART TLB errors will be reported.

-- 
Regards/Gruss,
Boris.

Operating | Advanced Micro Devices GmbH
  System  | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
 Research | Geschäftsführer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
  Center  | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
  (OSRC)  | Registergericht München, HRB Nr. 43632

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/