From: Greg Norris <haphazard@kc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6.0-test3] Hyperthreading gone
Date: Sat, 9 Aug 2003 17:17:06 -0500 [thread overview]
Message-ID: <20030809221706.GA2106@glitch.localdomain> (raw)
In-Reply-To: <87llu2bvxg.fsf@deneb.enyo.de>
Did you select CPU Enumeration Only, or "normal" ACPI? If the former,
did you specify the "acpismp=force" parameter at bootup?
On Sat, Aug 09, 2003 at 07:08:43PM +0200, Florian Weimer wrote:
> ACPI with CPU enumeration is enabled, but the sibling CPUs aren't
> activated.
>
> This is all what I have of the boot message (standard buffer size is
> too small, apparently):
>
> CPU: After all inits, caps: 3febfbff 00000000 00000000 00000080
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#3.
> CPU#3: Intel P4/Xeon Extended MCE MSRs (12) available
> CPU#3: Thermal monitoring enabled
> CPU3: Intel(R) Xeon(TM) CPU 1.40GHz stepping 01
> Total of 4 processors activated (11034.62 BogoMIPS).
> WARNING: No sibling found for CPU 0.
> WARNING: No sibling found for CPU 1.
> WARNING: No sibling found for CPU 2.
> WARNING: No sibling found for CPU 3.
>
> Recent 2.4.x kernels (starting with 2.4.20 IIRC) support
> Hyperthreading on this machine (Siemens Primergy H450).
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-08-09 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-09 17:08 Florian Weimer
2003-08-09 21:10 ` Gabor MICSKO
2003-08-09 22:17 ` Greg Norris [this message]
2003-08-10 7:03 ` Florian Weimer
2003-08-10 12:00 ` Greg Norris
2003-08-11 7:13 ` Florian Weimer
2003-08-11 16:52 ` Hugh Dickins
2003-08-11 18:12 ` Florian Weimer
2003-08-11 18:35 ` Hugh Dickins
2003-08-12 16:05 Brown, Len
2003-08-12 17:02 ` Marcelo Tosatti
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=20030809221706.GA2106@glitch.localdomain \
--to=haphazard@kc.rr.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®