From: "Niklas Söderlund" <niklas.soderlund@ericsson.com>
To: Tony Luck <tony.luck@intel.com>
Cc: Borislav Petkov <bp@amd64.org>,
"lucas.demarchi@profusion.mobi" <lucas.demarchi@profusion.mobi>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] edac: i5100 ack error detection register after each read
Date: Tue, 21 Feb 2012 11:26:44 +0100 [thread overview]
Message-ID: <4F437164.5020408@ericsson.com> (raw)
In-Reply-To: <20111209162254.GB14900@aftab>
Hi Tony,
Is there any interest in this patch?
On 12/09/2011 05:22 PM, Borislav Petkov wrote:
> Adding Tony.
>
> On Fri, Dec 09, 2011 at 05:12:15PM +0100, Niklas Söderlund wrote:
>> If I only ack the detection register after a error have been detected
>> I'm unable to reliably detect errors. I have verified this behavior
>> using both an error injection DIMM and software to inject errors.
>>
>> I can't find any documentation supporting this behavior in Intel 5100
>> Memory Controller Hub Chipset, see 1. So this is all based on
>> experimentation.
>>
>> [1] Intel® 5100 Memory Controller Hub Chipset
>> http://www.intel.com/content/dam/doc/datasheet/5100-
>> memory-controller-hub-chipset-datasheet.pdf
>>
>> Signed-off-by: Niklas Söderlund<niklas.soderlund@ericsson.com>
>> ---
>> drivers/edac/i5100_edac.c | 11 ++++-------
>> 1 files changed, 4 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/edac/i5100_edac.c b/drivers/edac/i5100_edac.c
>> index bcbdeec..ec728e9 100644
>> --- a/drivers/edac/i5100_edac.c
>> +++ b/drivers/edac/i5100_edac.c
>> @@ -535,23 +535,20 @@ static void i5100_read_log(struct mem_ctl_info *mci, int chan,
>> static void i5100_check_error(struct mem_ctl_info *mci)
>> {
>> struct i5100_priv *priv = mci->pvt_info;
>> - u32 dw;
>> -
>> + u32 dw, dw2;
>>
>> pci_read_config_dword(priv->mc, I5100_FERR_NF_MEM,&dw);
>> if (i5100_ferr_nf_mem_any(dw)) {
>> - u32 dw2;
>>
>> pci_read_config_dword(priv->mc, I5100_NERR_NF_MEM,&dw2);
>> - if (dw2)
>> - pci_write_config_dword(priv->mc, I5100_NERR_NF_MEM,
>> - dw2);
>> - pci_write_config_dword(priv->mc, I5100_FERR_NF_MEM, dw);
>>
>> i5100_read_log(mci, i5100_ferr_nf_mem_chan_indx(dw),
>> i5100_ferr_nf_mem_any(dw),
>> i5100_nerr_nf_mem_any(dw2));
>> +
>> + pci_write_config_dword(priv->mc, I5100_NERR_NF_MEM, dw2);
>> }
>> + pci_write_config_dword(priv->mc, I5100_FERR_NF_MEM, dw);
>> }
>>
>> /* The i5100 chipset will scrub the entire memory once, then
>> --
>> 1.7.7.3
>>
>>
>
next prev parent reply other threads:[~2012-02-21 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 16:12 [PATCH] edac: i5100 ack error detection register after each read Niklas Söderlund
2011-12-09 16:22 ` Borislav Petkov
2012-02-21 10:26 ` Niklas Söderlund [this message]
2012-02-22 0:58 ` Luck, Tony
2012-02-22 12:13 ` Mauro Carvalho Chehab
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=4F437164.5020408@ericsson.com \
--to=niklas.soderlund@ericsson.com \
--cc=bp@amd64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=tony.luck@intel.com \
/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