From: Stuart Young <sgy@amc.com.au>
To: <linux-kernel@vger.kernel.org>
Cc: Alastair Stevens <alastair.stevens@mrc-bsu.cam.ac.uk>
Subject: Re: Athlon /proc/cpuinfo anomaly [minor]
Date: Thu, 22 Nov 2001 10:44:23 +1100 [thread overview]
Message-ID: <5.1.0.14.0.20011122104119.026ebdc0@mail.amc.localnet> (raw)
In-Reply-To: <Pine.GSO.4.33.0111211116130.795-100000@gurney>
In-Reply-To: <E166VOz-0004kH-00@the-village.bc.nu>
At 11:19 AM 21/11/01 +0000, Alastair Stevens wrote:
> > > CPU0 is labelled as an "AMD Athlon(tm) MP Processor 1800+".
> > > CPU1 is instead labelled just "AMD Athlon(tm) Processor".
> >
> > Those strings are read directly out of the CPU.
>
>Hmmm, case of a suspicious CPU then? I haven't physically looked at it,
>but all the correct XP flags (such as "sse") are reported, so it must be
>the real thing.
>
>Perhaps one is a certified MP processor, and the other (ahem) isn't...?
Tried swapping the processors around?
If it's processor dependent, that'll show it. If it's code, it'll be the same.
AMC Enterprises P/L - Stuart Young
First Floor - Network and Systems Admin
3 Chesterville Rd - sgy@amc.com.au
Cheltenham Vic 3192 - Ph: (03) 9584-2700
http://www.amc.com.au/ - Fax: (03) 9584-2755
next prev parent reply other threads:[~2001-11-21 23:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 9:53 Alastair Stevens
2001-11-21 11:18 ` Alan Cox
2001-11-21 11:19 ` Alastair Stevens
2001-11-21 11:20 ` Jens Axboe
2001-11-21 11:42 ` Dave Jones
2001-11-21 11:47 ` Jens Axboe
2001-11-21 11:55 ` Dave Jones
2001-11-21 12:08 ` Jens Axboe
2001-11-21 12:19 ` Dave Jones
2001-11-21 15:41 ` Matthew Sell
2001-11-21 11:49 ` Stefan Smietanowski
2001-11-21 11:40 ` Dave Jones
2001-11-21 23:44 ` Stuart Young [this message]
2001-11-22 14:57 Zwane Mwaikambo
2001-11-22 14:53 ` Dave Jones
2001-11-25 21:36 ` H. Peter Anvin
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=5.1.0.14.0.20011122104119.026ebdc0@mail.amc.localnet \
--to=sgy@amc.com.au \
--cc=alastair.stevens@mrc-bsu.cam.ac.uk \
--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
all inboxes | Powered by JetHome®