From: Harry Ciao <qingtao.cao@windriver.com>
To: akpm@linux-foundation.org, bluesmoke-devel@lists.sourceforge.net
Cc: norsk5@yahoo.com, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] EDAC: CPC925 MC check fixup
Date: Tue, 5 May 2009 11:45:48 +0800 [thread overview]
Message-ID: <1241495148-15166-2-git-send-email-qingtao.cao@windriver.com> (raw)
In-Reply-To: <1241495148-15166-1-git-send-email-qingtao.cao@windriver.com>
Fix an obvious bug in CPC925 Memory Controller's check routine -
edac_mc_handle_ue() should have been called for UECC errors and
edac_mc_handle_ce() for CECC errors.
Signed-off-by: Harry Ciao <qingtao.cao@windriver.com>
---
drivers/edac/cpc925_edac.c | 11 +++++------
1 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/edac/cpc925_edac.c b/drivers/edac/cpc925_edac.c
index 2ad6465..8c54196 100644
--- a/drivers/edac/cpc925_edac.c
+++ b/drivers/edac/cpc925_edac.c
@@ -544,17 +544,16 @@ static void cpc925_mc_check(struct mem_ctl_info *mci)
/* Revert column/row addresses into page frame number, etc */
cpc925_mc_get_pfn(mci, mear, &pfn, &offset, &csrow);
- if (apiexcp & UECC_EXCP_DETECTED) {
- cpc925_mc_printk(mci, KERN_INFO, "DRAM UECC Fault\n");
+ if (apiexcp & CECC_EXCP_DETECTED) {
+ cpc925_mc_printk(mci, KERN_INFO, "DRAM CECC Fault\n");
channel = cpc925_mc_find_channel(mci, syndrome);
edac_mc_handle_ce(mci, pfn, offset, syndrome,
csrow, channel, mci->ctl_name);
}
- if (apiexcp & CECC_EXCP_DETECTED) {
- cpc925_mc_printk(mci, KERN_INFO, "DRAM CECC Fault\n");
- edac_mc_handle_ue(mci, pfn, offset,
- csrow, mci->ctl_name);
+ if (apiexcp & UECC_EXCP_DETECTED) {
+ cpc925_mc_printk(mci, KERN_INFO, "DRAM UECC Fault\n");
+ edac_mc_handle_ue(mci, pfn, offset, csrow, mci->ctl_name);
}
cpc925_mc_printk(mci, KERN_INFO, "Dump registers:\n");
--
1.5.6.2
prev parent reply other threads:[~2009-05-05 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 3:45 [v0 PATCH 0/1] EDAC: CPC925 MC check routine fixup Harry Ciao
2009-05-05 3:45 ` Harry Ciao [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=1241495148-15166-2-git-send-email-qingtao.cao@windriver.com \
--to=qingtao.cao@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=norsk5@yahoo.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
all inboxes | Powered by JetHome®