Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754353AbZLROrx (ORCPT ); Fri, 18 Dec 2009 09:47:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753804AbZLROrw (ORCPT ); Fri, 18 Dec 2009 09:47:52 -0500 Received: from nox.protox.org ([88.191.38.29]:44579 "EHLO nox.protox.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753857AbZLROru (ORCPT ); Fri, 18 Dec 2009 09:47:50 -0500 Date: Fri, 18 Dec 2009 15:44:35 +0100 From: Jerome Glisse To: Johannes Hirte Cc: 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) Message-ID: <20091218144435.GH22703@localhost.localdomain> References: <200912112202.48173.johannes.hirte@fem.tu-ilmenau.de> <20091216184148.GB22703@localhost.localdomain> <200912162031.48983.johannes.hirte@fem.tu-ilmenau.de> <200912181447.00498.johannes.hirte@fem.tu-ilmenau.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200912181447.00498.johannes.hirte@fem.tu-ilmenau.de> User-Agent: Mutt/1.5.20 (2009-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2976 Lines: 70 On Fri, Dec 18, 2009 at 02:47:00PM +0100, Johannes Hirte wrote: > Am Mittwoch 16 Dezember 2009 20:31:48 schrieb Johannes Hirte: > > Am Mittwoch 16 Dezember 2009 19:41:48 schrieb Jerome Glisse: > > > 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 ? > > > > Yes I'm using KMS when this error occours. > > Hardware: > > - Tyan Tiger K8W S8875 (AMD8151 Northbridge) > > - Radeon HD3650 AGP (RV635) > > > > Software: > > - linux-2.6.32 > > - libdrm-2.4.16 > > - mesa-7.7_rc2 > > - xf86-video-ati-9999 (latest git everytime) > > - KDE-4.3.4 with compositing enabled (OpenGL) > > > > The errors occours after a while of normal desktop work. I haven't tested > > without KMS or compisiting. Will do this as well. > > It's KMS related but not to compositing. Without KMS the errors don't occur. I > found at least two log entries where the error occurred on initializing KMS. > It happens reliable after a while working with X. > > regards, > Johannes > Can you give me the full reference of your motherboard ? Cheers, Jerome -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/