From: Jens Axboe <axboe@suse.de>
To: Dave Jones <davej@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 13:08:38 +0100 [thread overview]
Message-ID: <20011121130838.D9978@suse.de> (raw)
In-Reply-To: <20011121124706.C9978@suse.de> <Pine.LNX.4.33.0111211252500.4080-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.33.0111211252500.4080-100000@Appserv.suse.de>
On Wed, Nov 21 2001, Dave Jones wrote:
> On Wed, 21 Nov 2001, Jens Axboe wrote:
>
> > [root@bart x86info-1.5]# ./x86info -a | grep "name string"
> > Processor name string: AMD Athlon(tm) MP Processor 1700+
> > Processor name string: AMD Athlon(tm) MP Processor 1700+
> > [root@bart x86info-1.5]# ./x86info -a | grep "name string"
> > Processor name string: AMD Athlon(tm) Processor
> > Processor name string: AMD Athlon(tm) Processor
>
> Thanks. Looks like I was right, your BIOS isn't doing
> the 'right thing' for CPU 2. Cest la vie.
Strange, I was pretty sure that earlier 2.4.x got it right. Oh well.
--
Jens Axboe
next prev parent reply other threads:[~2001-11-21 12:09 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 [this message]
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
-- 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=20011121130838.D9978@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alastair.stevens@mrc-bsu.cam.ac.uk \
--cc=davej@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox