mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Doug Thompson <norsk5@yahoo.com>
To: Andy Chittenden <andyc@bluearc.com>, linux-kernel@vger.kernel.org
Subject: RE: Linux 2.6.26 edac errors and ASUS P5W DH Deluxe motherboard
Date: Tue, 19 Aug 2008 10:41:01 -0700 (PDT)	[thread overview]
Message-ID: <472120.81746.qm@web50112.mail.re2.yahoo.com> (raw)
In-Reply-To: <0F10A59FDFFDFD4E9BEBD7365DE672550214F0B1@uk-email.terastack.bluearc.com>


--- Andy Chittenden <andyc@bluearc.com> wrote:

> 
> If you could let me know what I need to put in /etc/edac/labels.db, that
> would be appreciated too.
> 

This becomes a manual, one time, event, to discover the mapping of DIMMs to the silkscreen.

One command is the 'dmidecode' which is run as root and dumps the BIOS DMI Tables. Unfortunately,
many BIOSes do not correctly set these tables properly to the correct DIMM silk screen labels.
Because of this lack, EDAC and edac-utils was created to provide mechanism for end users.

If your system does provide correct DIMM Labels, you can create/correct the entry for your
motherboard in the database file for edac-utils.

If your system provides simple generic labels, then you will need to physically move DIMMs from
slot to slot and watching as the error "moves" with the DIMM. This will take a few iterations and
a state table.

Usually, a DIMM will have 2 Chip-Select Rows (csrow)

The first set of DIMMs form a 128-bit data path (called dual channel operation) and have csrows 0
and 1

The second set of DIMMs will have csrows 2 and 3.

Therefore, you need to examine which csrow and which channel the error is being reported in.

doug t


W1DUG

  reply	other threads:[~2008-08-19 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 14:17 Andy Chittenden
2008-08-18 19:45 ` Doug Thompson
2008-08-19  8:17   ` Andy Chittenden
2008-08-19 17:41     ` Doug Thompson [this message]
2008-08-18 19:49 ` Bernd Schubert

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=472120.81746.qm@web50112.mail.re2.yahoo.com \
    --to=norsk5@yahoo.com \
    --cc=andyc@bluearc.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

Powered by JetHome