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: K7/Athlon optimizations and Sacrifices to the Great Ones.
Date: Thu, 6 Sep 2001 12:51:36 -0700	[thread overview]
Message-ID: <01090612513601.00171@c779218-a> (raw)

I'm upset, and angry, and could go into more detail but a future employer 
might read this.

133Mhz FSB + KT133A chipset theory has been officially shot to hell.
Not only that, but 6-4-4 (family/model/stepping) processors don't seem to 
be the culprit. I've now had reports of 6-4-2 experiencing problems, and 
6-4-4 NOT experiencing problems, even on KT133A @ 133Mhz.
At this point, I can't even isolate a MOTHERBOARD that could be the 
culprit, and I don't think it's the power supply.

The *only* other theory I have left in my arsenal is cooling. 
Unfortunately this data is more difficult to obtain from users, and thus 
wouldn't gather as many responses and in the end it'd probably be 
useless. It would be best tested in controlled conditions, but 
unfortunately I don't have the money to purchase the neccisary hardware 
to test these issues. Any companies want to sponsor tests? I'm serious, 
if someone wanted to, I'd be willing to test this possibility.
There is another remote possibility, and that's the fab plant that the 
processors came from. I didn't ask for CPU serial numbers, so I can't 
speak to that effect.
It's also possible that this is related to a specific batch or batches of 
KT133A chipsets, however I currently have one report of a guy seeing this 
problem on the SAME physical board, just two different processors. Both 
6-4-2, the only difference is that one is 1.13Ghz and doesn't have the 
problem, and the other is 1.2Ghz and DOES have the problem. This of 
course leads me back to the clock speed theory, but again it doesn't make 
any SENSE because the FSB on both of them is 133Mhz and I've got at least 
two reports of 1.33Ghz chips running FINE! ARG!
At this point, I'm giving up on collecting data, as I just don't see a 
definitive pattern, all I can say for sure is that the "majority" 
KT133A-based motherboards seem to have problems, but not ALL. I don't 
know of a single report outside of the KT133A chipset of these problems.

If anyone wants to keep collecting data, I'd be happy to send all the 
information I have so far to that person, and any that filters in over 
the next couple days.

Now for the Sacrifices.

At this point, I'd like to sacrifice a Red Hat Linux 6.2 CD to Alan Cox.

I would also like to sacrifice Minix 1.3(?) installation diskettes to 
Linus Torvalds.

I perform these sacrifices in the hope that enlightenment comes to me.

             reply	other threads:[~2001-09-06 19:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 19:51 Nicholas Knight [this message]
2001-09-06 20:21 ` K7/Athlon optimizations and Sacrifices to the Great Ones Alan Cox
2001-09-06 20:32   ` Dan Hollis
2001-09-06 23:24     ` David Hollister
2001-09-07 17:03     ` Heinz Deinhart
2001-09-07 20:52       ` Alan Cox
2001-09-07  8:30 ` VDA
2001-09-07 16:25 ` Jussi Laako

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=01090612513601.00171@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