From: Dave Jones <davej@codemonkey.org.uk>
To: erich@uruk.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [CFT] Athlon testers needed.
Date: Thu, 21 Nov 2002 15:13:44 +0000 [thread overview]
Message-ID: <20021121151344.GA12660@suse.de> (raw)
In-Reply-To: <E18EbCB-0003Z9-00@trillium-hollow.org>
On Wed, Nov 20, 2002 at 12:11:35PM -0800, erich@uruk.org wrote:
> In any case, here's the result from my recently acquired Athlon
> XP 2600+:
>
> 31 23 15 7
> MSR: 0x0000002a=0x00000000 : 00000000 00000000 00000000 00000000
> MSR: 0xc0000080=0x00000000 : 00000000 00000000 00000000 00000000
> MSR: 0xc0010010=0x00160604 : 00000000 00010110 00000110 00000100
> MSR: 0xc0010015=0x080b9008 : 00001000 00001011 10010000 00001000
> MSR: 0xc001001b=0x6003d22f : 01100000 00000011 11010010 00101111
>
> Family: 6 Model: 8 Stepping: 1
> CPU Model : Athlon XP (Thoroughbred)[B0]
Bingo, this has the bug.
> For comparison, here is the output from an Athlon XP 1800+:
>
> 31 23 15 7
> MSR: 0x0000002a=0x00000000 : 00000000 00000000 00000000 00000000
> MSR: 0xc0000080=0x00000000 : 00000000 00000000 00000000 00000000
> MSR: 0xc0010010=0x00168604 : 00000000 00010110 10000110 00000100
> MSR: 0xc0010015=0x01001008 : 00000001 00000000 00010000 00001000
> MSR: 0xc001001b=0x6003d22f : 01100000 00000011 11010010 00101111
>
> Family: 6 Model: 6 Stepping: 2
> CPU Model : Athlon MP (palomino)
This one is ok.
The bug is that c001001b are being programmed the same way.
They need different programming on newer models, which older
BIOSes are unaware of.
I'll cook up a patch and send a complete description after a quick
compile test. Thanks for the report.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-11-21 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 18:53 [CFT] Athlon testers needed Dave Jones
2002-11-20 20:11 ` erich
2002-11-21 15:13 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-20 20:07 Petr Vandrovec
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=20021121151344.GA12660@suse.de \
--to=davej@codemonkey.org.uk \
--cc=erich@uruk.org \
--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.