From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Phil Oester <kernel@linuxace.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12->2.6.13-rc6 SMT changes -- intentional?
Date: Tue, 09 Aug 2005 00:34:10 +0200 [thread overview]
Message-ID: <42F7DDE2.8020403@vc.cvut.cz> (raw)
In-Reply-To: <20050808222146.GA7123@linuxace.com>
Phil Oester wrote:
> Just booted a box on 2.6.13-rc6, and noticed that it now only reports
> a single processor, whereas on 2.6.12.4 it reports two. While there
> is only one physical processor, I wonder if this change was intentional,
> since I can't find anything in the changelog about SMT changes.
>
> Below is dmesg output from each kernel.
>
> Phil
>
> DMI 2.3 present.
> ACPI: RSDP (v000 DELL ) @ 0x000fec00
> ACPI: RSDT (v001 DELL GX280 0x00000007 ASL 0x00000061) @ 0x000fcc04
> ACPI: FADT (v001 DELL GX280 0x00000007 ASL 0x00000061) @ 0x000fcc44
> ACPI: SSDT (v001 DELL st_ex 0x00001000 MSFT 0x0100000d) @ 0xfffd3468
> ACPI: MADT (v001 DELL GX280 0x00000007 ASL 0x00000061) @ 0x000fccb8
> ACPI: BOOT (v001 DELL GX280 0x00000007 ASL 0x00000061) @ 0x000fcd2a
> ACPI: ASF! (v016 DELL GX280 0x00000007 ASL 0x00000061) @ 0x000fcd52
> ACPI: MCFG (v001 DELL GX280 0x00000007 ASL 0x00000061) @ 0x000fcdb9
> ACPI: HPET (v001 DELL GX280 0x00000007 ASL 0x00000061) @ 0x000fcdf7
> ACPI: DSDT (v001 DELL dt_ex 0x00001000 MSFT 0x0100000d) @ 0x00000000
> ********************************************
>
> DMI 2.3 present.
> Intel MultiProcessor Specification v1.4
> Virtual Wire compatibility mode.
It looks like that ACPI is gone... Can you recheck your .config that
you still have ACPI enabled?
Petr
next prev parent reply other threads:[~2005-08-08 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 22:21 2.6.12->2.6.13-rc6 SMT changes -- intentional? Phil Oester
2005-08-08 22:34 ` Petr Vandrovec [this message]
2005-08-08 22:56 ` Phil Oester
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=42F7DDE2.8020403@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=kernel@linuxace.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