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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200912152300.46325.johannes.hirte@fem.tu-ilmenau.de>
Date:	Tue, 15 Dec 2009 23:00:46 +0100
From:	Johannes Hirte <johannes.hirte@....tu-ilmenau.de>
To:	Borislav Petkov <borislav.petkov@....com>
Cc:	Borislav Petkov <petkovbb@...glemail.com>,
	linux-kernel@...r.kernel.org
Subject: Re: K8 ECC error with linux-2.6.32

Am Dienstag 15 Dezember 2009 16:30:26 schrieb Borislav Petkov:
> On Tue, Dec 15, 2009 at 08:08:04AM +0100, Johannes Hirte wrote:
> >  Northbridge Error, node 0, core: -1
> > amd_decode_nb_mce: NBSL: 0x0005001b, NBSL: 0xa4000000
> > K8 ECC error.
> 
> Yep, this is a benign GART TLB error which is not being reported but
> you're using the amd64_edac module and it trips since the error is still
> being logged and the module sees it. There are two fixes:
> 
> 1. If you have a BIOS option with a wording like:
> 
> "Gart Table Walk Error MC reporting: Disabled/Enabled."
> 
> which should disable it.

Yes, there is such an option that was enabled. I was shure I had disabled it, 
especially as the BIOS help says too that it's only for graphic driver 
developers. I've disabled it now, will test the patch later.

> 2. If no BIOS option, the patch below should fix it. Can you please
> test (against v2.6.32).

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.


regards,
  Johannes
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ