From: Hugh Dickins <hugh@veritas.com>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: Andrew Morton <akpm@osdl.org>, Len Brown <len.brown@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc4: no hyperthreading and idr_remove() stack traces
Date: Sat, 30 Jul 2005 20:27:24 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0507302017400.3459@goblin.wat.veritas.com> (raw)
In-Reply-To: <20050729162006.GA18866@janus>
On Fri, 29 Jul 2005, Frank van Maarseveen wrote:
> 2.6.13-rc4 does not recognize the second CPU of a 3GHz HT P4:
I think your problem is this: HT has depended on CONFIG_ACPI for
some while, and now in 2.6.13-rc CONFIG_ACPI depends on CONFIG_PM.
You don't have CONFIG_PM set in your .config (nor had I), so you
don't get ACPI, so you don't get HT.
I don't know why CONFIG_ACPI now depends on CONFIG_PM: it seemed
gratuitous when it first hit me, looked like someone just felt it
was a nice arrangement. But seems particularly unhelpful for HT.
On the other hand, I can well understand Len wanting to simplify
the ACPI config interdependencies, which have caused breakage
after breakage after breakage.
Hugh
next prev parent reply other threads:[~2005-07-30 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 16:20 Frank van Maarseveen
2005-07-29 16:44 ` 2.6.13-rc4: no hyperthreading and idr_remove() stack traces (2) Frank van Maarseveen
2005-07-29 19:26 ` 2.6.13-rc4: no hyperthreading and idr_remove() stack traces (3) Frank van Maarseveen
2005-07-30 0:03 ` 2.6.13-rc4: no hyperthreading and idr_remove() stack traces Andrew Morton
2005-07-30 0:22 ` Eric W. Biederman
2005-07-30 0:41 ` Siddha, Suresh B
2005-08-01 10:01 ` Frank van Maarseveen
2005-07-30 19:27 ` Hugh Dickins [this message]
2005-08-01 9:56 ` Frank van Maarseveen
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=Pine.LNX.4.61.0507302017400.3459@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=frankvm@frankvm.com \
--cc=len.brown@intel.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®