mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Jeff Chua" <jeff.chua.linux@gmail.com>
Cc: "David Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.27rc1 cannot boot more than 8CPUs
Date: Wed, 6 Aug 2008 01:49:22 -0700	[thread overview]
Message-ID: <86802c440808060149s697fe9p43f0be72d464f75e@mail.gmail.com> (raw)
In-Reply-To: <b6a2187b0808052342w6fba9152m197d56aa9e88746a@mail.gmail.com>

On Tue, Aug 5, 2008 at 11:42 PM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> On Wed, Aug 6, 2008 at 1:19 PM, David Miller <davem@davemloft.net> wrote:
>> From: "Jeff Chua" <jeff.chua.linux@gmail.com>
>> Date: Wed, 6 Aug 2008 11:15:30 +0800
>> Do you have lockdep enabled?  If sure, try turning that off.
>
> It's enabled by default, and I can't seem to disable it even if I
> commented it out or delete it, it comes back after running "make".
>
> CONFIG_X86_32=y
> # CONFIG_X86_64 is not set
> CONFIG_X86=y
> CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
> # CONFIG_GENERIC_LOCKBREAK is not set
> CONFIG_GENERIC_TIME=y
> CONFIG_GENERIC_CMOS_UPDATE=y
> CONFIG_CLOCKSOURCE_WATCHDOG=y
> CONFIG_GENERIC_CLOCKEVENTS=y
> CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
> CONFIG_LOCKDEP_SUPPORT=y
> CONFIG_STACKTRACE_SUPPORT=y
> CONFIG_HAVE_LATENCYTOP_SUPPORT=y
> CONFIG_FAST_CMPXCHG_LOCAL=y
> CONFIG_MMU=y
> CONFIG_ZONE_DMA=y
> CONFIG_GENERIC_ISA_DMA=y
> CONFIG_GENERIC_IOMAP=y
> CONFIG_GENERIC_BUG=y
> CONFIG_GENERIC_HWEIGHT=y
>
>

do you have

CONFIG_X86_GENERICARCH=y
CONFIG_X86_BIGSMP=y

8 more cpu need bigsmp mode.

YH

  parent reply	other threads:[~2008-08-06  8:56 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06  3:15 Jeff Chua
2008-08-06  3:31 ` Max Krasnyansky
2008-08-06  3:50   ` Jeff Chua
2008-08-06  3:54     ` Max Krasnyansky
2008-08-06  4:06       ` Jeff Chua
2008-08-06  4:48         ` Max Krasnyansky
2008-08-06  4:53           ` Li Zefan
2008-08-06 20:11             ` Max Krasnyansky
     [not found] ` <86802c440808052050u489264beo30812523669ef4df@mail.gmail.com>
2008-08-06  4:05   ` Jeff Chua
2008-08-06  5:19 ` David Miller
2008-08-06  6:42   ` Jeff Chua
2008-08-06  7:18     ` David Miller
2008-08-06  9:33       ` Jeff Chua
2008-08-06  9:36         ` David Miller
2008-08-06  9:50           ` Jeff Chua
2008-08-06  8:49     ` Yinghai Lu [this message]
2008-08-06  9:35       ` Jeff Chua
2008-08-06  9:42         ` Jeff Chua
2008-08-06  6:01 ` Linus Torvalds
2008-08-06  6:42   ` Jeff Chua
2008-08-06 15:33     ` Jeff Chua
2008-08-11 19:59       ` Ingo Molnar
2008-08-11 20:03         ` Yinghai Lu
2008-08-11 20:08           ` Ingo Molnar
2008-08-11 20:12             ` Yinghai Lu
2008-08-11 20:36               ` Yinghai Lu
2008-08-11 20:44                 ` Ingo Molnar
2008-08-06 11:09 Jeff Chua
2008-08-06 16:13 ` Yinghai Lu
2008-08-06 16:34   ` Jeff Chua
2008-08-11 19:54 ` Ingo Molnar
2008-08-13 14:16 ` Ingo Molnar
2008-08-13 17:10   ` Jeff Chua
2008-08-13 17:33     ` Jeff Chua
2008-08-13 17:39       ` Ingo Molnar
2008-08-13 17:46         ` Yinghai Lu
2008-08-13 18:33           ` Yinghai Lu
2008-08-14  7:16             ` Jeff Chua
2008-08-14  8:59               ` Yinghai Lu
2008-08-14  9:07               ` Ingo Molnar
2008-08-15 10:34 Jeff Chua
2008-08-15 14:07 ` Ingo Molnar
2008-08-18  3:07   ` Jeff Chua
2008-08-18  8:00     ` Ingo Molnar

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=86802c440808060149s697fe9p43f0be72d464f75e@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jeff.chua.linux@gmail.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®