From: Kronos <kronos@kronoz.cjb.net>
To: davej@codemonkey.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Fix Athlon MCA
Date: Sun, 21 Sep 2003 16:39:34 +0200 [thread overview]
Message-ID: <20030921143934.GA1867@dreamland.darkstar.lan> (raw)
Hi,
on boot I'm seeing a lot of messages like this:
MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
Bank 0: d47fa0000000bfee
This messages go away if I revert cset 1.1119.9.1. AFAIK you were trying
to decrease the logging level. After reading IA32 Architecture Software
Developers Manual, vol3 - chapter 14.5 "Machine-Check Initialization" I
think that the right way to do it is this:
--- linux-2.6/arch/i386/kernel/cpu/mcheck/k7.c~ Sat Aug 9 06:37:27 2003
+++ linux-2.6/arch/i386/kernel/cpu/mcheck/k7.c Sun Sep 21 00:36:39 2003
@@ -81,8 +81,9 @@
wrmsr (MSR_IA32_MCG_CTL, 0xffffffff, 0xffffffff);
nr_mce_banks = l & 0xff;
- for (i=1; i<nr_mce_banks; i++) {
- wrmsr (MSR_IA32_MC0_CTL+4*i, 0xffffffff, 0xffffffff);
+ for (i=0; i<nr_mce_banks; i++) {
+ if (i)
+ wrmsr (MSR_IA32_MC0_CTL+4*i, 0xffffffff, 0xffffffff);
wrmsr (MSR_IA32_MC0_STATUS+4*i, 0x0, 0x0);
}
We really want to clean all MC*_STATUS. I'm currently running linux 2.6.0-t5
+ this patch and I don't see the MCE messages on boot anymore.
Luca
--
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
"L'abilita` politica e` l'abilita` di prevedere quello che
accadra` domani, la prossima settimana, il prossimo mese e
l'anno prossimo. E di essere cosi` abili, piu` tardi,
da spiegare perche' non e` accaduto."
next reply other threads:[~2003-09-21 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 14:39 Kronos [this message]
2003-09-21 14:47 ` Dave Jones
2003-09-21 17:39 ` Linus Torvalds
2003-09-21 17:47 ` Dave Jones
2003-09-22 14:20 ` CaT
2003-09-22 14:43 ` Dave Jones
2003-09-22 15:06 ` CaT
2003-09-22 16:02 ` Dave Jones
2003-09-22 16:07 ` CaT
2003-09-22 16:20 ` Dave Jones
2003-09-22 13:32 ` venom
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=20030921143934.GA1867@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=davej@codemonkey.org.uk \
--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
all inboxes | Powered by JetHome®