public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Knight <tegeran@home.com>
To: linux-kernel@vger.kernel.org
Subject: Early results and more information needed (K7/Athlon optimization problems)
Date: Thu, 6 Sep 2001 04:45:52 -0700	[thread overview]
Message-ID: <01090604455200.00176@c779218-a> (raw)

I've only had a half-dozen responses so far, please keep sending 
information as detailed in my last message!

I do have an early thought though.
Everyone who's reported the requested information to me and had problems 
has been using the VIA KT133A chipset, this isn't in itself surprising, 
it's been a pattern that's already been noted.
However, I do have one report of no-problems on a VIA KT133A chipset, and 
it differs in one major way from the rest, the FSB speed is 100Mhz(200), 
whereas all the others are running at 133Mhz(266). This partialy fits my 
suspicion that something, somewhere, is clock speed related, since, when 
running at rated speeds, nothing below a certain level (I think about 
1Ghz) is running with a 133Mhz FSB, and many chips above that level are 
running at 133Mhz.

I still need more reports, the information previously requested is this:

--previous request--
Motherboard + chipset
Front Side Bus speed
CPU speed + multiplier
out put of "cat /proc/cpuinfo"
if avalible, RAM type and speed (both clock and CAS latency)
if avalible, PSU wattage, and amperage on all outputs.
--end previous request--

Also, I need another peice of specific information, is anyone running a 
VIA KT133A chipset with a 133Mhz(266) FSB, and NOT experiencing problems? 
And if you're not, are you running a chip rated for 133Mhz FSB operation 
or not?

Thanks,
-NK

                 reply	other threads:[~2001-09-06 11:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=01090604455200.00176@c779218-a \
    --to=tegeran@home.com \
    --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