From: Ashok Raj <ashok.raj@intel.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: Dave Jones <davej@redhat.com>, "Raj, Ashok" <ashok.raj@intel.com>,
Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.16rc5 'found' an extra CPU.
Date: Thu, 2 Mar 2006 08:30:38 -0800 [thread overview]
Message-ID: <20060302083038.A11407@unix-os.sc.intel.com> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B30063BFB95@hdsmsx401.amr.corp.intel.com>; from len.brown@intel.com on Wed, Mar 01, 2006 at 09:49:53PM -0800
On Wed, Mar 01, 2006 at 09:49:53PM -0800, Brown, Len wrote:
>
> >sysfs gets it right.
> >
> >(23:11:01:davej@nemesis:~)$ ls /sys/devices/system/cpu/
> >cpu0/ cpu1/
> >(23:11:07:davej@nemesis:~)$ ls /proc/acpi/processor/
> >CPU1/ CPU2/ CPU3/
>
> This is because the BIOS has three "Processor" objects in the DSDT.
>
I have a dual core + HT platform. I disabled HT to have the same situation
as Dave.
ACPI DSDT dump shows 4 objects in \_PR scope as below.
Scope (\_PR)
{
Processor (CPU0, 0x01, 0x00000410, 0x06) {}
Processor (CPU1, 0x02, 0x00000410, 0x06) {}
Processor (CPU2, 0x03, 0x00000410, 0x06) {}
Processor (CPU3, 0x04, 0x00000410, 0x06) {}
}
Only 2 are marked enabled in the ACPI MADT..
>From boot log
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
Processor #2 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled)
But proc/acpi/processor also lists just 2 entries.
[root@araj-sfield-2 tmp]# ls /proc/acpi/processor/
CPU0 CPU2
I suspect that the BIOS is goofy and sending a valid acpiid when we try
to evaluate the processor object.
Could you see what comes out of the /proc/acpi/processor/CPUx/info for all the
3 listed in your system?
Also if you can send DSDT dump just to look over.
Cheers,
ashok
next prev parent reply other threads:[~2006-03-02 16:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 5:49 2.6.16rc5 'found' an extra CPU 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-03-02 19:37 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:18 Brown, Len
2006-03-02 19:16 Brown, Len
2006-03-02 17:34 Brown, Len
2006-03-02 17:30 Brown, Len
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-01 23:01 Moore, Robert
2006-03-01 22:46 Dave Jones
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
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=20060302083038.A11407@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=ak@suse.de \
--cc=davej@redhat.com \
--cc=len.brown@intel.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;
as well as URLs for NNTP newsgroup(s).