From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Frank van Maarseveen <frankvm@frankvm.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc4: no hyperthreading and idr_remove() stack traces
Date: Fri, 29 Jul 2005 17:41:38 -0700 [thread overview]
Message-ID: <20050729174138.A20681@unix-os.sc.intel.com> (raw)
In-Reply-To: <m17jf9gn1k.fsf@ebiederm.dsl.xmission.com>; from ebiederm@xmission.com on Fri, Jul 29, 2005 at 06:22:47PM -0600
On Fri, Jul 29, 2005 at 06:22:47PM -0600, Eric W. Biederman wrote:
> Andrew Morton <akpm@osdl.org> writes:
>
> > Frank van Maarseveen <frankvm@frankvm.com> wrote:
> >>
> >> 2.6.13-rc4 does not recognize the second CPU of a 3GHz HT P4:
> >
> > OK, we seem to have broken your APIC code.
>
> There is a big difference here in that one kernel is using
> the ACPI MADT tables and the other kernel is using the MP table.
>
> I suspect the MP table on your system is incomplete while
> your ACPI MADT does specify both logical cpus.
MPS tables will list only physical packages. ACPI MADT tables will list
all the logical CPUs.
Frank, Please enable ACPI in your config and check if it helps.
thanks,
suresh
next prev parent reply other threads:[~2005-07-30 0:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 16:20 2.6.13-rc4: no hyperthreading and idr_remove() stack traces 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 [this message]
2005-08-01 10:01 ` Frank van Maarseveen
2005-07-30 19:27 ` Hugh Dickins
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=20050729174138.A20681@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=frankvm@frankvm.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