mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Len Brown <len.brown@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>
Subject: Re: HT not working by default since 2.4.22
Date: Mon, 29 Sep 2003 07:29:09 +0200	[thread overview]
Message-ID: <20030929052909.GA18126@louise.pinerecords.com> (raw)
In-Reply-To: <1064799717.2532.8.camel@dhcppc4>

> [len.brown@intel.com]
> 
> > CONFIG_NR_CPUS=4
> 
> See if cranking this up to 8 helps.
> It looks like your BIOS defines empty processor slots
> as processors that are present but disabled.
> 
> if this doesn't do it, please drop the output from
> from dmidecode and acpidmp in a bugzilla and point me to it.

Indeed, raising CONFIG_NR_CPUS to 8 solved the problem
even for the CONFIG_ACPI_HT_ONLY case (which wouldn't
work in 2.4.22-ac*).

Do you need any more info on this system or will this do?

-- 
Tomas Szepe <szepe@pinerecords.com>

  reply	other threads:[~2003-09-29  5:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BF1FE1855350A0479097B3A0D2A80EE0CC870C@hdsmsx402.hd.intel.com>
2003-09-28 10:43 ` Tomas Szepe
2003-09-28 10:46   ` Tomas Szepe
2003-09-29  1:41     ` Len Brown
2003-09-29  5:29       ` Tomas Szepe [this message]
2003-09-26  4:54 Brown, Len
2003-09-26  7:44 ` Jan Evert van Grootheest
2003-09-26 17:38   ` Len Brown
2003-09-30  5:27   ` Len Brown
  -- strict thread matches above, loose matches on Subject: below --
2003-09-26  1:13 Nakajima, Jun
2003-09-24 21:56 Brown, Len
2003-09-24 23:12 ` Tomas Szepe
2003-09-25 13:33 ` marcelo
2003-09-26  0:04   ` Jeff Garzik
2003-09-26  3:37     ` Len Brown
2003-09-26  3:49       ` Jeff Garzik
2003-09-27 15:26         ` Herbert Poetzl
2003-09-22 17:28 Brown, Len
2003-09-22 17:55 ` Jeff Garzik
2003-09-22 14:41 Nakajima, Jun
2003-09-22  9:00 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=20030929052909.GA18126@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com.br \
    /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

Powered by JetHome