From: Jonathan Morton <chromi@cyberspace.org>
To: Seth Goldberg <bergsoft@home.com>
Cc: Moses McKnight <m_mcknight@surfbest.net>, linux-kernel@vger.kernel.org
Subject: Re: DISCOVERED! Cause of Athlon/VIA KX133 Instability
Date: Thu, 3 May 2001 13:25:33 +0100 [thread overview]
Message-ID: <l03130313b716fd8bf5d6@[192.168.239.105]> (raw)
In-Reply-To: <3AF135F0.6ED58AB3@home.com>
In-Reply-To: <Pine.LNX.4.10.10105012333400.18414-100000@coffee.psychology.mcmaster.ca> <l0313030eb715db09b49f@[192.168.239.105]>
>> I'm using an Abit KT7 board (KT133) and my new 1GHz T'bird (running 50-60°C
>> in a warm room) is giving me no trouble. This is with the board and RAM
>> pushed as fast as it will go without actually overclocking anything... and
>> yes, I do have Athlon/K7 optimisations turned on in my kernel (2.4.3).
>>
>
> I wonder if the KT133A (which is what the IWILL KK266 is based on)
>differences
>a could be a source of the problem. My FSB is at plain old 100 MHz
>since I
>have regular PC100 SDRAM. Overclocked, or not, I get the same results.
>I,
>too, had an ABIT KA7[-RAID] and it was rock solid. So much for "if it's
>not broke, don't fix it" -- I should have listened to my gf, but that's
>the life of an upgrader ;)... In general the IWILL got great reviews at
>a
>number of reliable hardware review sites, and hey, it doesn't lock up in
>windows ;) (ok don't flame me for that ;)).
Maybe, but the IWILL board is the only one we've heard about problems with.
The Abit KT7A (which also has the KT133A chipset and is otherwise identical
to the KT7) would appear to run smoothly, although I don't actually *have*
one of those. Probably the Windows drivers turn off some feature of the
IWILL board which is known to be flaky.
I suggest setting *everything* in the BIOS to the "most conservative"
settings and seeing if the problem persists. If so, then it can't be a
hardware-speed-limitation problem, and there's clearly something we have to
turn off "manually". Also, try running memtest86 and see if that is
capable of triggering the problem.
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: chromi@cyberspace.org (not for attachments)
big-mail: chromatix@penguinpowered.com
uni-mail: j.d.morton@lancaster.ac.uk
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----
next prev parent reply other threads:[~2001-05-03 12:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010501085939.A40276@shell.aros.net>
2001-05-01 19:40 ` Seth Goldberg
2001-05-01 20:02 ` Mark Hahn
2001-05-02 2:22 ` Seth Goldberg
2001-05-02 3:43 ` Mark Hahn
2001-05-02 7:35 ` Moses McKnight
2001-05-03 10:34 ` Seth Goldberg
2001-05-02 15:47 ` Jonathan Morton
2001-05-03 10:41 ` Seth Goldberg
2001-05-03 12:25 ` Jonathan Morton [this message]
2001-05-02 11:17 ` Alan Cox
2001-05-02 17:36 ` Dan Hollis
2001-05-02 3:38 ` Wayne Whitney
2001-05-06 14:41 Ray Shaw
-- strict thread matches above, loose matches on Subject: below --
2001-05-06 9:12 Christian Bornträger
2001-05-06 10:10 ` Dan Podeanu
2001-05-06 10:51 ` Christian Bornträger
2001-05-01 17:03 Will Newton
2001-05-01 18:54 ` Seth Goldberg
2001-05-01 19:33 ` Dan Hollis
2001-05-01 19:41 ` Seth Goldberg
2001-05-01 10:48 Seth Goldberg
2001-05-01 12:57 ` 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='l03130313b716fd8bf5d6@[192.168.239.105]' \
--to=chromi@cyberspace.org \
--cc=bergsoft@home.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m_mcknight@surfbest.net \
/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®