Date: Sun, 10 Aug 2003 15:07:52 +0200
From: Andi Kleen <ak@suse.de>
To: kwijibo@zianet.com
Cc: Andi Kleen <ak@suse.de>, Dave Jones <davej@redhat.com>,
       richard.brunner@amd.com, linux-kernel@vger.kernel.org
Subject: Re: Machine check expection panic
Message-ID: <20030810130752.GB586@wotan.suse.de>
References: <3F3182B5.3040301@zianet.com.suse.lists.linux.kernel> <20030807002722.GA3579@suse.de.suse.lists.linux.kernel> <p73ekzynuxt.fsf@oldwotan.suse.de> <3F35FE5B.7060003@zianet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F35FE5B.7060003@zianet.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1020
Lines: 28

> The CPU's aren't overclocked and have worked fine for
> me under much heavier loads than booting a kernel for

It could be corrected ECC errors in the cache. If that
happens I would consider it a hardware problem

(now hidden with the disabled bank).

> 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.

I maintain that such a magic hack needs at least a big fat comment.

I still find the change very suspicious, there isn't any errata that 
says that bank 0 is bad on Athlon.

Also disabling a whole bank just for some buggy CPUs is quite a sledgehammer,
it would be probably better to identify the bank 0 sub unit that causes it
and only turn that off.

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/