From: Stefan Smietanowski <stesmi@stesmi.com>
To: Jens Axboe <axboe@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Alastair Stevens <alastair.stevens@mrc-bsu.cam.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Athlon /proc/cpuinfo anomaly [minor]
Date: Wed, 21 Nov 2001 12:49:40 +0100 [thread overview]
Message-ID: <3BFB94D4.10201@stesmi.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0111210945590.795-100000@gurney> <E166VOz-0004kH-00@the-village.bc.nu> <20011121122034.B9978@suse.de>
Jens Axboe wrote:
> On Wed, Nov 21 2001, Alan Cox wrote:
>
>>>CPU0 is labelled as an "AMD Athlon(tm) MP Processor 1800+", as expected.
>>>CPU1 is instead labelled just "AMD Athlon(tm) Processor".
>>>
>>Those strings are read directly out of the CPU. Mine for example says
>>
>>cpu family : 6
>>model : 1
>>model name : AMD-K7(tm) Processor
>>stepping : 1
>>
>
> No there is a bug there, I can confirm that mine does the same (ie
> second athlon is not reported with correct model name)
Have you actually verified it by switching the cpu's around? That should
be the first to do.
// Stefan
next prev parent reply other threads:[~2001-11-21 11:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 9:53 Athlon /proc/cpuinfo anomaly [minor] 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 [this message]
2001-11-21 11:40 ` Dave Jones
2001-11-21 23:44 ` Stuart Young
-- strict thread matches above, loose matches on Subject: below --
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=3BFB94D4.10201@stesmi.com \
--to=stesmi@stesmi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alastair.stevens@mrc-bsu.cam.ac.uk \
--cc=axboe@suse.de \
--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.