linux-kernel - Re: EDAC: Is it possible to calculate which piece of memory is bad?

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: <20100330070544.GA19488@aftab>
Date:	Tue, 30 Mar 2010 09:05:44 +0200
From:	Borislav Petkov <bp@...64.org>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: EDAC: Is it possible to calculate which piece of memory is bad?

From: Justin Piszcz <jpiszcz@...idpixels.com>
Date: Mon, Mar 29, 2010 at 09:40:38AM -0400

> Hello,
> 
> I see the following errors:
> 
> EDAC MC0: CE page 0x8abba, offset 0xa10, grain 8, syndrome 0x4758, row 0, channel 0, label "": k8_edac

It looks like it is the first DIMM on your mainboard, i.e., whichever
gets mapped to channel 0 of the DCT.

Sigh, someday we'll have a better mapping, hopefully, ... :|

> EDAC MC0: CE - no information available: k8_edac Error Overflow set
> EDAC k8 MC0: extended error code: ECC chipkill x4 error
> EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
> 
> Is it possible to use the page or offset to calculate which DIMM is having a
> problem?

-- 
Regards/Gruss,
Boris.

--
Advanced Micro Devices, Inc.
Operating Systems Research Center
--
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/