mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Sell <msell@ontimesupport.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Athlon /proc/cpuinfo anomaly [minor]
Date: Wed, 21 Nov 2001 09:41:47 -0600	[thread overview]
Message-ID: <5.1.0.14.0.20011121093412.00a92e78@127.0.0.1> (raw)
In-Reply-To: <Pine.LNX.4.33.0111211316220.4080-100000@Appserv.suse.de>
In-Reply-To: <20011121130838.D9978@suse.de>


The results of "dmesg" on my dual-Athlon show a (rather comical) 
discrepancy, it's not a big deal - just funny (to me)....

I was just wondering if this was a similar behavior to the earlier posts on 
this topic:


Intel MultiProcessor Specification v1.4
     Virtual Wire compatibility mode.
OEM ID: TYAN     Product ID: GUINNESS     APIC at: 0xFEE00000
Processor #1 Pentium(tm) Pro APIC version 16
Processor #0 Pentium(tm) Pro APIC version 16
I/O APIC #2 Version 17 at 0xFEC00000.
Processors: 2


Intel machine check reporting enabled on CPU#0.
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After vendor init, caps: 0183fbff c1c7fbff 00000000 00000000
CPU:     After generic, caps: 0183fbff c1c7fbff 00000000 00000000
CPU:             Common caps: 0183fbff c1c7fbff 00000000 00000000
CPU0: AMD Athlon(tm) Processor stepping 04
per-CPU timeslice cutoff: 731.77 usecs.


Intel machine check reporting enabled on CPU#1.
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After vendor init, caps: 0183fbff c1c7fbff 00000000 00000000
CPU:     After generic, caps: 0183fbff c1c7fbff 00000000 00000000
CPU:             Common caps: 0183fbff c1c7fbff 00000000 00000000
CPU1: AMD Athlon(tm) Processor stepping 04
Total of 2 processors activated (5564.00 BogoMIPS).


         - Matt



At 01:19 PM 11/21/2001 +0100, Dave Jones wrote:
>On Wed, 21 Nov 2001, Jens Axboe wrote:
>
> > Strange, I was pretty sure that earlier 2.4.x got it right. Oh well.
>
>*shrug* As we don't do any setting of this string, all I can guess
>at is that the new seqfile based /proc/cpuinfo code is stricter
>about getting the info from the right CPU than the older code was.
>
>Though I'm not sure why, as the older code just read from the
>per-CPU structs anyway.  Most odd.
>
>regards,
>Dave.
>
>--
>| Dave Jones.        http://www.codemonkey.org.uk
>| SuSE Labs
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/



Matthew Sell
Programmer
On Time Support, Inc.
www.ontimesupport.com
(281) 296-6066

Join the Metrology Software discussion group METLIST!
http://www.ontimesupport.com/cgi-bin/mojo/mojo.cgi


"One World, One Web, One Program" - Microsoft Promotional Ad
"Ein Volk, Ein Reich, Ein Fuhrer" - Adolf Hitler

Many thanks for this tagline to a fellow RGVAC'er...


  parent reply	other threads:[~2001-11-21 15:42 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 [this message]
2001-11-21 11:49     ` Stefan Smietanowski
2001-11-21 11:40   ` Dave Jones
2001-11-21 23:44   ` Stuart Young
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.20011121093412.00a92e78@127.0.0.1 \
    --to=msell@ontimesupport.com \
    --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®