From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: Dan Merillat <harik@chaos.ao.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Wierd /proc/cpuinfo with 2.4.11-pre4
Date: Fri, 05 Oct 2001 23:45:03 +0200 [thread overview]
Message-ID: <3BBE29DF.A5DECF12@oracle.com> (raw)
In-Reply-To: <200110051816.f95IGRW2008474@vulpine.ao.net>
Dan Merillat wrote:
>
> From dmesg:
> CPU: Before vendor init, caps: 000001bf 00000000 00000000, vendor = 0
> Intel Pentium with F0 0F bug - workaround enabled.
> Intel old style machine check architecture supported.
> Intel old style machine check reporting enabled on CPU#0.
> CPU: After vendor init, caps: 000001bf 00000000 00000000 00000000
> CPU: After generic, caps: 000001bf 00000000 00000000 00000000
> CPU: Common caps: 000001bf 00000000 00000000 00000000
> CPU: Intel Pentium 75 - 200 stepping 0b
> Checking 'hlt' instruction... OK.
>
> Looks normal. Let's see /proc/cpuinfo...
>
> processor : 0
[snip]
> processor : 7
> vendor_id : unknown
> cpu family : 0
> model : 0
> model name : unknown
> stepping : 0
> cache size : 515 KB
> fdiv_bug : no
> hlt_bug : yes
> f00f_bug : yes
> coma_bug : yes
> fpu : no
> fpu_exception : no
> cpuid level : 0
> wp : no
> flags :
> bogomips : 644464.70
>
> Wow! That's pretty impressive, a new kernel build gives me an
> additional _7_ CPUs!
>
> Interesting bits of .config:
>
> CONFIG_M586TSC=y
> CONFIG_X86_MSR=y
> CONFIG_X86_CPUID=y
> CONFIG_NOHIGHMEM=y
> # CONFIG_HIGHMEM4G is not set
> # CONFIG_HIGHMEM64G is not set
> # CONFIG_MATH_EMULATION is not set
> CONFIG_MTRR=y
> # CONFIG_SMP is not set
> # CONFIG_X86_UP_APIC is not set
> # CONFIG_X86_UP_IOAPIC is not set
>
> Won't compile with UP APIC turned on, as others have noted.
>
> Aside from /bin/ps getting confused about the system capabilities, it
> seems stable.
Same 8-processor incorrect info on my PIII Dell laptop -
redirecting '/usr/bin/top' stderr gets this:
[asuardi@dolphin linux]$ cat x
fscanf failed on /proc/stat for cpu 1
fscanf failed on /proc/stat for cpu 2
fscanf failed on /proc/stat for cpu 3
fscanf failed on /proc/stat for cpu 4
fscanf failed on /proc/stat for cpu 5
fscanf failed on /proc/stat for cpu 6
fscanf failed on /proc/stat for cpu 7
fscanf failed on /proc/stat for cpu 1
So I'd assume anything touching /proc/cpuinfo is hosed.
--alessandro
"this is no time to get cute, it's a mad dog's promenade
so walk tall, or baby don't walk at all"
(Bruce Springsteen, 'New York City Serenade')
next prev parent reply other threads:[~2001-10-05 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 18:16 Wierd /proc/cpuinfo with 2.4.11-pre4 Dan Merillat
2001-10-05 21:45 ` Alessandro Suardi [this message]
2001-10-05 21:58 ` Martin J. Bligh
2001-10-05 23:10 ` Alessandro Suardi
2001-10-05 23:07 ` Martin J. Bligh
2001-10-06 0:37 ` Alessandro Suardi
2001-10-05 23:18 ` Andreas Dilger
2001-10-05 23:20 ` Martin J. Bligh
2001-10-05 23:17 ` Brian Gerst
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=3BBE29DF.A5DECF12@oracle.com \
--to=alessandro.suardi@oracle.com \
--cc=harik@chaos.ao.net \
--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.