public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Kosin <jkosin@intcomgrp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: EDAC: Is it possible to calculate which piece of memory is bad?
Date: Mon, 29 Mar 2010 10:08:50 -0400	[thread overview]
Message-ID: <4BB0B472.7060705@intcomgrp.com> (raw)
In-Reply-To: <etnvQ-1Mn-3@gated-at.bofh.it>

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

       reply	other threads:[~2010-03-29 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <etnvQ-1Mn-3@gated-at.bofh.it>
2010-03-29 14:08 ` James Kosin [this message]
2010-03-29 13:40 EDAC: Is it possible to calculate which piece of memory is bad? Justin Piszcz
2010-03-30  7:05 ` Borislav Petkov
2010-03-30  8:00   ` Justin Piszcz
2010-03-30  9:51     ` Borislav Petkov

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=4BB0B472.7060705@intcomgrp.com \
    --to=jkosin@intcomgrp.com \
    --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