From: Jonathan Morton <chromi@cyberspace.org>
To: Moses McKnight <m_mcknight@surfbest.net>, linux-kernel@vger.kernel.org
Subject: Re: DISCOVERED! Cause of Athlon/VIA KX133 Instability
Date: Wed, 2 May 2001 16:47:51 +0100 [thread overview]
Message-ID: <l0313030eb715db09b49f@[192.168.239.105]> (raw)
In-Reply-To: <3AEFB8BE.5050007@surfbest.net>
In-Reply-To: <Pine.LNX.4.10.10105012333400.18414-100000@coffee.psychology.mcmaster.ca>
>> the only general issue is that kx133 systems seem to be difficult
>> to configure for stability. ugly things like tweaking Vio.
>> there's no implication that has anything to do with Linux, though.
>
>
>When I reported my problem a couple weeks back another fellow
>said he and several others on the list had the same problem,
>and as far as I can tell it is *only* with the IWILL boards.
>When I compiled with k7 optimizations I'd get all kinds of oopses
>and panics and never fully boot. They were different every time.
>When any of the lesser optimizations are used I have no problems.
>My memory is one 256MB Corsair PC150 dimm, CPU is a Thunderbird 850,
>and mobo is an IWILL KK266 (KT133A). The CPU runs between 35°C
>and 40°C.
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).
Out of interest, what FSB are you using for your machine? I understand the
difference between the KT133 and the KT133A is that the latter supports a
266MHz FSB for the Athlon rather than 200MHz. Since your CPU is running
cool, I doubt you've managed to accidentally o/c it, but nevertheless this
is a possibility...
The 266MHz FSB does require considerably higher standards in board
construction though, so it could be that IWILL have managed to do a shoddy
job on that end.
--------------------------------------------------------------
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-02 15:53 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 [this message]
2001-05-03 10:41 ` Seth Goldberg
2001-05-03 12:25 ` Jonathan Morton
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='l0313030eb715db09b49f@[192.168.239.105]' \
--to=chromi@cyberspace.org \
--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®