public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <borislav.petkov@amd.com>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: radeon KMS causes GART Table Walk Errors (was: K8 ECC error with linux-2.6.32)
Date: Fri, 18 Dec 2009 12:56:39 +0100	[thread overview]
Message-ID: <20091218115639.GA28439@aftab> (raw)
In-Reply-To: <200912172003.30023.johannes.hirte@fem.tu-ilmenau.de>

On Thu, Dec 17, 2009 at 08:03:29PM +0100, Johannes Hirte wrote:
> GART Error Reporting was disabled. Here is the output after enabling it:
>
> datengrab ~ # lsmsr MC4 -V3
> MC4_CTL              = 0x0000000000003bff
>   CorrEccEn=0x1
>   UnCorrEccEn=0x1
>   CrcErr0En=0x1
>   CrcErr1En=0x1
>   CrcErr2En=0x1
>   SyncPkt0En=0x1
>   SyncPkt1En=0x1
>   SyncPkt2En=0x1
>   MstrAbrtEn=0x1
>   TgtAbrtEn=0x1
>   GartTblWkEn=0
>   AtomicRMWEn=0x1
>   WchDogTmrEn=0x1
>   DramParEn=0

[.. ]

> MC4_CTL_MASK         = 0x0000000000000000
>   CorrEccEn=0
>   UnCorrEccEn=0
>   CrcErr0En=0
>   CrcErr1En=0
>   CrcErr2En=0
>   SyncPkt0En=0
>   SyncPkt1En=0
>   SyncPkt2En=0
>   MstrAbrtEn=0
>   TgtAbrtEn=0
>   GartTblWkEn=0

Ok, thanks for testing. It looks like your BIOS is applying the wrong
workaround when the option is enabled. It clears MC4_CTL[GartTblWkEn],
which means, it disables reporting of GART table walk errors while
they're still being logged by the hw. What it should do is to set
MC4_CTL_MASK[GartTblWkEn] to 1 so that logging gets disabled, as it is
recommended in the K8 BKDG.

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


  reply	other threads:[~2009-12-18 11:56 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 [this message]
2009-12-16 18:41                     ` Jerome Glisse
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=20091218115639.GA28439@aftab \
    --to=borislav.petkov@amd.com \
    --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