From: Moses McKnight <m_mcknight@surfbest.net>
To: linux-kernel@vger.kernel.org
Subject: Re: DISCOVERED! Cause of Athlon/VIA KX133 Instability
Date: Wed, 02 May 2001 02:35:26 -0500 [thread overview]
Message-ID: <3AEFB8BE.5050007@surfbest.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10105012333400.18414-100000@coffee.psychology.mcmaster.ca>
Mark Hahn wrote:
>> Actually, I think there are 2 problems that have been discussed -- the
>>disk corruption and a general instability resulting in oops'es at
>>various points shortly after boot up.
>>
>
> I don't see this. specifically, there were scattered reports
> of a via-ide problem a few months ago; this is the issue that's
> gotten some press, and for which Alan has a fix. and there are reports
> of via-smp problems at boot (which go away with noapic). I see no reports
> of the kind of general instability you're talking about. and all the
> via-users I've heard of have no such stability problems -
> me included (kt133/duron).
>
> 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.
>> My memory system jas been set up very conservitavely and has been
>>rock solid in my other board (ka7), so I doubt it's that, but I
>>sure am happy to try a few more cominations of bios settings. Anything
>>I should look for in particular?
>>
>
> how many dimms do you have? interleave settings? Vio jumper?
> already checked on cooling issues? and that you're not overclocking...
next prev parent reply other threads:[~2001-05-02 12:49 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 ` DISCOVERED! Cause of Athlon/VIA KX133 Instability Seth Goldberg
2001-05-01 20:02 ` Mark Hahn
2001-05-02 2:22 ` Seth Goldberg
2001-05-02 3:38 ` Wayne Whitney
2001-05-02 3:43 ` Mark Hahn
2001-05-02 7:35 ` Moses McKnight [this message]
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
2001-05-02 11:17 ` Alan Cox
2001-05-02 17:36 ` Dan Hollis
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=3AEFB8BE.5050007@surfbest.net \
--to=m_mcknight@surfbest.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.