LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: martin f krafft <madduck@madduck.net>
To: Borislav Petkov <bp@amd64.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Opteron ECC/ChipKill error
Date: Tue, 8 Feb 2011 18:09:16 +0100	[thread overview]
Message-ID: <20110208170916.GB26278@fishbowl.rw.madduck.net> (raw)
In-Reply-To: <20110208142442.GA30263@aftab>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

also sprach Borislav Petkov <bp@amd64.org> [2011.02.08.1524 +0100]:
> Yeah, well, keep your fingers crossed. Just to reiterate, getting ECCs
> is not a problem per se - they may appear even during normal operation
> and in this case get corrected just fine by the memory controller.

That's what I thought. Many thanks for confirming it.

> > Don't want to spam the list, so:
> > http://scratch.madduck.net/__tmp__dmesg.gz
> 
> Ah ok, this is a .32 kernel and it doesn't have the information I was
> looking for. I've changed that in later kernels so that EDAC dumps the
> DRAM chip selects placement on the memory controller.

Excellent to see you are working to improve this. If the problems
increase, then I shall either turn on CONFIG_EDAC_DEBUG or upgrade
to 2.6.38.

Thank you for your help!

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
wind catches lily,
scattering petals to the ground.
segmentation fault.
 
spamtraps: madduck.bogus@madduck.net

[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) --]
[-- Type: application/pgp-signature, Size: 1124 bytes --]

      reply	other threads:[~2011-02-08 17:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 13:30 martin f krafft
2011-02-08 13:49 ` Borislav Petkov
2011-02-08 13:59   ` martin f krafft
2011-02-08 14:24     ` Borislav Petkov
2011-02-08 17:09       ` martin f krafft [this message]

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=20110208170916.GB26278@fishbowl.rw.madduck.net \
    --to=madduck@madduck.net \
    --cc=bp@amd64.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Opteron ECC/ChipKill error' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).