The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Doug Thompson <norsk5@yahoo.com>
To: linux-kernel@vger.kernel.org, Jeff Roberson <jroberson@jroberson.net>
Cc: bluesmoke-devel@lists.sourceforge.net
Subject: Re: Bugs in intel 5400 EDAC driver
Date: Fri, 7 Aug 2009 17:42:44 -0700 (PDT)	[thread overview]
Message-ID: <678970.61399.qm@web50105.mail.re2.yahoo.com> (raw)
In-Reply-To: <alpine.BSF.2.00.0908071312030.19226@desktop>



--- On Fri, 8/7/09, Jeff Roberson <jroberson@jroberson.net> wrote:

> From: Jeff Roberson <jroberson@jroberson.net>
> Subject: Bugs in intel 5400 EDAC driver
> To: linux-kernel@vger.kernel.org
> Date: Friday, August 7, 2009, 5:23 PM
> Hello,
> 
> The i5400 EDAC driver has several bugs with chip-select row
> computation which most likely lead to bugs in detailed error
> reporting.  Attempts to contact the authors have gone
> mostly unanswered so I am presenting my diff here.  I
> do not subscribe to lkml and would appreciate being kept in
> the cc.

Will do

Can you generate a patch, which will provide better closure than just text?

doug t

CC to the bluesmoke mailing list where most edac developers read

> 
> The most egregious problem was miscalculating the addresses
> of MTR registers after register 0 by assuming they are 32bit
> rather than 16. This caused the driver to miss half of the
> memories.  Most motherboards tend to have only 8 dimm
> slots and not 16, so this may not have been noticed before.
> 
> Further, the row calculations multiplied the number of
> dimms several times, ultimately ending up with a maximum row
> of 32.  The chipset only supports 4 dimms in each of 4
> channels, so csrow could not be higher than 4 unless you use
> a row per-rank with dual-rank dimms.  I opted to
> eliminate this behavior as it is confusing to the user and
> the error reporting works by slot and not rank.  This
> gives a much clearer view of memory by slot and channel in
> /sys.
> 
> Thanks,
> Jeff

      reply	other threads:[~2009-08-08  0:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 23:23 Bugs in intel 5400 EDAC driver Jeff Roberson
2009-08-08  0:42 ` Doug Thompson [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=678970.61399.qm@web50105.mail.re2.yahoo.com \
    --to=norsk5@yahoo.com \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=jroberson@jroberson.net \
    --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