From: Nicholas Knight <tegeran@home.com>
To: "Simen Thoresen" <simentt@dolphinics.no>,
"alan" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Status of the VIA KT133a and 2.4.x debacle?
Date: Sat, 1 Sep 2001 10:11:14 -0700 [thread overview]
Message-ID: <01090110111400.00171@c779218-a> (raw)
In-Reply-To: <200109011619480531.23AA844A@scispor.dolphinics.no>
In-Reply-To: <200109011619480531.23AA844A@scispor.dolphinics.no>
On Saturday 01 September 2001 07:19 am, Simen Thoresen wrote:
> Alan, list, et all,
>
> I've picked up a KT133a board (EpoX 8KTA/3) and a 1.2GHz Thunderbird
> processor (133MHz FSB), and have seen the same problems that have been
> reported previously with the KT133a. Random oops'es, both fatal and non
> fatal, when running the system on a 2.4 kernel with CONFIG_MK7.
>
> The bord seems rock solid with 2.2.x kernels, and also with 2.4.x
> kernels with CONFIG_M686 set for basic i686 + MMX. I've also run the
> board with a 100MHz FSB, but that has not improved anything. Also
> turning off /some/ optimizations in bios have not helped.
Just out of curiosity, can you drop that to 100Mhz FSB and a multiplier
of 8? I don't know about the manual clocking support on EpoX boards, but
if you can, it might be good to give it a shot. Most likely it has
nothing to do with clock speed whatsoever, but I'm really beginning to
wonder. I don't think I've seen a single reported case under 900-1000Mhz,
and thunderbirds were made below 900Mhz.
(reason I chose 800MHz is my non-tbird Athlon is 800 and is rock solid)
next prev parent reply other threads:[~2001-09-01 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-01 14:19 Status of the VIA KT133a and 2.4.x debacle? Simen Thoresen
2001-09-01 17:05 ` Simen Thoresen
2001-09-01 17:11 ` Nicholas Knight [this message]
2001-09-02 22:53 ` Gerbrand van der Zouw
-- strict thread matches above, loose matches on Subject: below --
2001-09-03 4:58 Patrick Chase
2001-09-04 22:14 ` Gerbrand van der Zouw
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=01090110111400.00171@c779218-a \
--to=tegeran@home.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=simentt@dolphinics.no \
/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