From: Dave Jones <davej@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-acpi@vger.kernel.org
Subject: 2.6.16rc5 'found' an extra CPU.
Date: Wed, 1 Mar 2006 17:46:47 -0500 [thread overview]
Message-ID: <20060301224647.GD1440@redhat.com> (raw)
This amused me.
(17:43:34:davej@nemesis:~)$ ll /proc/acpi/processor/
total 0
dr-xr-xr-x 2 root root 0 Mar 1 17:43 CPU1/
dr-xr-xr-x 2 root root 0 Mar 1 17:43 CPU2/
dr-xr-xr-x 2 root root 0 Mar 1 17:43 CPU3/
(17:43:36:davej@nemesis:~)$
As cool as a 3-way x86-64 sounds, it's really only got 2.
Two of these..
vendor_id : AuthenticAMD
cpu family : 15
model : 5
model name : AMD Opteron(tm) Processor 244
stepping : 8
cpu MHz : 1789.412
cache size : 1024 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow
bogomips : 3578.59
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts ttp
(17:45:21:davej@nemesis:~)$ cat /proc/acpi/processor/CPU*/info
processor id: 0
acpi id: 1
bus mastering control: no
power management: no
throttling control: yes
limit interface: yes
processor id: 1
acpi id: 2
bus mastering control: no
power management: no
throttling control: no
limit interface: no
processor id: 255
acpi id: 3
bus mastering control: no
power management: no
throttling control: no
limit interface: no
I guess the '255' has confused something.
This made my 'bug of the day' :)
Dave
next reply other threads:[~2006-03-01 22:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 22:46 Dave Jones [this message]
2006-03-01 23:03 ` Dave Jones
2006-03-02 0:55 ` Andi Kleen
2006-03-02 1:19 ` Dave Jones
2006-03-02 1:38 ` Andi Kleen
2006-03-02 3:13 ` Dave Jones
2006-03-02 3:24 ` Andi Kleen
2006-03-02 3:45 ` Dave Jones
2006-03-02 3:52 ` Ashok Raj
2006-03-02 4:11 ` Dave Jones
2006-03-01 23:01 Moore, Robert
2006-03-02 0:55 Chuck Ebbert
2006-03-02 1:09 ` Dave Jones
2006-03-05 0:42 ` Andrew Morton
2006-03-05 2:26 ` Dave Jones
2006-03-02 5:49 Brown, Len
2006-03-02 9:33 ` Romano Giannetti
2006-03-02 15:53 ` Zwane Mwaikambo
2006-03-02 15:58 ` Romano Giannetti
2006-03-02 12:14 ` Andi Kleen
2006-03-02 16:30 ` Ashok Raj
2006-03-02 18:44 ` Dave Jones
2006-03-02 19:21 ` Ashok Raj
2006-03-03 7:14 ` Andrew Morton
2006-03-03 17:41 ` Ashok Raj
2006-03-02 17:30 Brown, Len
2006-03-02 17:34 Brown, Len
2006-03-02 19:16 Brown, Len
2006-03-02 19:18 Brown, Len
2006-03-02 19:26 Brown, Len
2006-03-02 19:31 ` Dave Jones
2006-03-02 19:33 ` Andi Kleen
2006-03-02 19:37 Brown, Len
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=20060301224647.GD1440@redhat.com \
--to=davej@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--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
Powered by JetHome