public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Olson <ejolson@math.uci.edu>
To: heinz@auto.tuwien.ac.at
Cc: linux-kernel@vger.kernel.org
Subject: Some experiences with the Athlon optimisation problem
Date: Fri, 7 Sep 2001 10:18:28 -0700 (PDT)	[thread overview]
Message-ID: <200109071718.KAA03472@math.uci.edu> (raw)

Dear Heinz Deinhart,

>The old Athlon reads: 
>        A1133AMS3C 
>        AVIA 0115TPAW 
>        95262550081 
>
>The new (non working) one: 
>        A1200AMS3C 
>        AXIA 0121RPDW 
>        95987660990 

The first line can be decoded using AMDs documentation at

    http://www.amd.com/products/cpg/athlon/techdocs/index.html

In particular

       A 1133 A M S 3 C
       |   |  | | | | |
       |   |  | | | |  \___ FSB (B=200, C=266)
       |   |  | | |  \_____ Size of L2 Cache (3=256K)
       |   |  | |  \_______ Case Temperature (S=95C, T=90C)
       |   |  |  \_________ Operating Voltage (M=1.75V, P=1.7V)
       |   |   \___________ Package Type (A=PGA)
       |    \______________ Speed in MHz
        \__________________ A for Athlon

Anyone know what the second line means?  It is quite mysterious 
that the word VIA appears on the chip that works with VIA KT133A 
and not on the other :-)

Have you tried Robert Redelmeier's new program burnMMX2 which has 
the 3DNow streaming cache bypass load/store instructions that seem 
to be causing all the trouble?

Does it run indefinitely or terminate with the 1133MHz processor 
configuration?  What about for the 1200MHz processor with kernel 
optimization turned off?

--Eric

             reply	other threads:[~2001-09-07 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-07 17:18 Eric Olson [this message]
2001-09-07 18:09 ` Some experiences with the Athlon optimisation problem Stefan Smietanowski
  -- strict thread matches above, loose matches on Subject: below --
2001-09-07 17:23 Eric Olson
2001-09-04  9:02 Heinz Deinhart

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=200109071718.KAA03472@math.uci.edu \
    --to=ejolson@math.uci.edu \
    --cc=heinz@auto.tuwien.ac.at \
    --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