From: kwijibo@zianet.com
To: Andi Kleen <ak@suse.de>
Cc: Dave Jones <davej@redhat.com>,
richard.brunner@amd.com, linux-kernel@vger.kernel.org
Subject: Re: Machine check expection panic
Date: Sun, 10 Aug 2003 02:12:11 -0600 [thread overview]
Message-ID: <3F35FE5B.7060003@zianet.com> (raw)
In-Reply-To: <p73ekzynuxt.fsf@oldwotan.suse.de>
Andi Kleen wrote:
>Dave Jones <davej@redhat.com> writes:
>
>
>>#
>>diff -Nru a/arch/i386/kernel/cpu/mcheck/k7.c b/arch/i386/kernel/cpu/mcheck/k7.c
>>--- a/arch/i386/kernel/cpu/mcheck/k7.c Wed Aug 6 23:33:40 2003
>>+++ b/arch/i386/kernel/cpu/mcheck/k7.c Wed Aug 6 23:33:40 2003
>>@@ -81,7 +81,7 @@
>> wrmsr (MSR_IA32_MCG_CTL, 0xffffffff, 0xffffffff);
>> nr_mce_banks = l & 0xff;
>>
>>- for (i=0; i<nr_mce_banks; i++) {
>>+ for (i=1; i<nr_mce_banks; i++) {
>>
>>
>
>The change looks rather suspicious to me.
>
>Bank 0 is the data cache unit (DC)
>
>Do you have an errata that says that the DC bank is bad on all Athlons?
>
>Normally BIOS or microcode are supposed to turn off bad MCEs by
>masking them in another register. Maybe the person's CPU has a
>real problem that is just masked now, e.g. it could be overclocked
>and stress the cache too much.
>
The CPU's aren't overclocked and have worked fine for
me under much heavier loads than booting a kernel for
at least a year. Using the 2.4 kernel that is. Once
I remove the exception code from the kernel it boots
fine and runs fine under any load I put it under.
>
>The original MCE was:
>
>Status: (4) Machine Check in progress.
>Restart IP invalid.
>parsebank(0): f606200000000833 @ 4040
> External tag parity error
> Uncorrectable ECC error
> CPU state corrupt. Restart not possible
> Address in addr register valid
> Error enabled in control register
> Error not corrected.
> Error overflow
> Bus and interconnect error
> Participation: Local processor originated request
> Timeout: Request did not timeout
> Request: Generic error
> Transaction type : Instruction
> Memory/IO : Other
>
>Tyan 2466 motherboard
>2 Athon MP 1200 processors (1200?)
>
>
Should say 1.2 GHz processor I imagine. AMD and their
wacky naming schemes. This is before they had they
wacky number scheme.
Steve
next prev parent reply other threads:[~2003-08-10 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F3182B5.3040301@zianet.com.suse.lists.linux.kernel>
[not found] ` <20030807002722.GA3579@suse.de.suse.lists.linux.kernel>
2003-08-07 1:00 ` Machine check expection panic Andi Kleen
2003-08-07 1:34 ` Dave Jones
2003-08-10 8:12 ` kwijibo [this message]
2003-08-10 13:07 ` Andi Kleen
2003-08-10 21:04 ` kwijibo
2003-08-11 10:15 ` Petr Vandrovec
2003-08-11 11:34 ` Bartlomiej Zolnierkiewicz
2003-08-06 22:35 kwijibo
2003-08-06 23:05 ` Matt Mackall
2003-08-07 0:27 ` Dave Jones
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=3F35FE5B.7060003@zianet.com \
--to=kwijibo@zianet.com \
--cc=ak@suse.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.brunner@amd.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