public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 15:04:01 -0600	[thread overview]
Message-ID: <3F36B341.7@zianet.com> (raw)
In-Reply-To: <20030810130752.GB586@wotan.suse.de>

Out of curiosity I decided to try this on some other Athlon
systems I have.  I tried it on a dual Athlon MP 2400(2GHz)
system with a Tyan 2462 motherboard.  Also I tried it on a
single Athlon XP 1800 with a Asus A7V motherboard.  They
both booted fine with the 2.6.0-test2 kernel and the machine
exception code in it.  So I am thinking either it is something
with the older CPU's or the CPU is actually borked.  Like I said
though I have been using those 1.2GHz processors for a long time
with no problems.

Steve

Andi Kleen wrote:

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



  reply	other threads:[~2003-08-10 21:05 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
2003-08-10 13:07       ` Andi Kleen
2003-08-10 21:04         ` kwijibo [this message]
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=3F36B341.7@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