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>] [day] [month] [year] [list]

Message-ID: <4BB0B472.7060705@intcomgrp.com>
Date:	Mon, 29 Mar 2010 10:08:50 -0400
From:	James Kosin <jkosin@...comgrp.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: EDAC: Is it possible to calculate which piece of memory is bad?

On 3/29/2010 9:50 AM, Justin Piszcz wrote:
> Hello,
> 
> I see the following errors:
> 
> EDAC MC0: CE page 0x8abba, offset 0xa10, grain 8, syndrome 0x4758, row
> 0, channel 0, label "": k8_edac
> 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?
> 
> Justin.
> 

Theoretically, YES.

However, you would have to have some important information:
1)  The number and size of each memory stick in the machine.
2)  The physical location accessed.  With virtual memory being the norm
there isn't always a 1-1 mapping here.  But, this should be attainable.

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