public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alistair Phipps" <aphipps@thenorth.org>
To: <linux-kernel@vger.kernel.org>
Subject: RE: [GOLDMINE!!!] Athlon optimisation bug (was Re: Duron kernel crash)
Date: Thu, 13 Sep 2001 11:20:10 +0100	[thread overview]
Message-ID: <000e01c13c3d$ac011bf0$0200000a@alistair> (raw)
In-Reply-To: <20010912214430.A2866@zed.dlitz.net>

> >Today I updated the BIOS of my motherboard, a ABIT KT7A (VIA Apollo
KT133A
> >chipset). The kernel I had (2.4.9) started crashing on boot with an
> >invalid page fault, usually right after starting init. I tryed a i686
> >kernel and noticed it works OK, so I recompiled my crashy kernel only
> >switching the processor type and it also worked. changed it back to
> >Athlon/K7/Duron and it starts crashing.
> >
> >Anyone else experiencing this?
>
> BINGO!
>
> This problem is known about, but this is the first report we've had
> of it on a Duron (as opposed to Athlon), and you've successfully
> tracked it down to the updated BIOS.
>
> We need the versions of your old and new BIOSes, as accurately as you
> can make it.

I don't know if this is relevant, but on the Abit KT7 w/Duron 700 I'm using
right now, I upgraded from the -ZT BIOS to the -3R BIOS, and immediately had
problems booting.  I ran memtest86 (www.memtest86.com) and found that on
test 5 I was getting many errors at a particular address range (there had
been no errors with the previous BIOS).  I tried turning down the RAM speed
settings in the BIOS, but none helped - then I tried setting the "MD driving
strength" to "Lo" instead of "Hi" (Hi had been the default) and suddenly got
complete stability and no memory errors with memtest86, even at the high
performance RAM settings.

I can't test if this is related to the i686 vs Athlon "kernel" bug as I'm
not running Linux right now (long story - this isn't my own machine) but it
might be something worth checking.  The crashing occuring may actually be
caused by memory problems - I suggest everyone experiencing this test their
system with memtest86 - particularly tests 5 and 6.  It takes a long time
but may be worth it to rule out problematic RAM / BIOS settings for RAM.

- Alistair Phipps


  reply	other threads:[~2001-09-13 10:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-11 11:21 [GOLDMINE!!!] Athlon optimisation bug (was Re: Duron kernel crash) Jonathan Morton
2001-09-11 11:27 ` Gergely Tamas
2001-09-11 11:32   ` Gergely Tamas
2001-09-11 11:53     ` Jonathan Morton
2001-09-11 14:59       ` Roberto Jung Drebes
2001-09-12 14:00   ` VDA
2001-09-12 17:59     ` Janne Pänkälä
2001-09-11 12:59 ` Nicholas Knight
2001-09-11 14:30   ` J.Brown (Ender/Amigo)
2001-09-11 16:21   ` Luigi Genoni
2001-09-13  2:30     ` Jonathan Morton
2001-09-13  3:44 ` Dwayne C. Litzenberger
2001-09-13 10:20   ` Alistair Phipps [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-12  4:29 Dmitry Volkoff
2001-09-12  6:28 ` Peter Horton
2001-09-12  7:24   ` J.Brown (Ender/Amigo)
2001-09-12 10:06 ` Alan Cox

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='000e01c13c3d$ac011bf0$0200000a@alistair' \
    --to=aphipps@thenorth.org \
    --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