linux-kernel - Re: 2.6.27rc1 cannot boot more than 8CPUs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 Aug 2008 21:54:21 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeff Chua <jeff.chua.linux@...il.com>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	David Miller <davem@...emloft.net>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.27rc1 cannot boot more than 8CPUs


* Jeff Chua <jeff.chua.linux@...il.com> wrote:

>
> On Wed, Aug 6, 2008 at 5:42 PM, Jeff Chua <jeff.chua.linux@...il.com>  
> wrote:
>>>> CONFIG_X86_GENERICARCH=y
>>>> CONFIG_X86_BIGSMP=y
>>>> 8 more cpu need bigsmp mode.
>
>> Just found it under " Subarchitecture Type (Generic architecture)",
>> and then it shows the CONFIG_X86_BIGSMP option.
>
> It works. Booted with 16CPUs. 32GB RAM.
>
> CPU0 L7345 1.86GHz  0C
> CPU1 L7345 1.86GHz  0C
> CPU2 L7345 1.86GHz  0C
> CPU3 L7345 1.86GHz  0C
> CPU4 L7345 1.86GHz  0C
> CPU5 L7345 1.86GHz  0C
> CPU6 L7345 1.86GHz  0C
> CPU7 L7345 1.86GHz  0C
> CPU8 L7345 1.86GHz  0C
> CPU9 L7345 1.86GHz  0C
> CPU10 L7345 1.86GHz  0C
> CPU11 L7345 1.86GHz  0C
> CPU12 L7345 1.86GHz  0C
> CPU13 L7345 1.86GHz  0C
> CPU14 L7345 1.86GHz  0C
> CPU15 L7345 1.86GHz  0C
>
>
> So, but setting the config not obvious. And should CONFIG_X86_PC be  
> considered as well as CONFIG_X86_GENERICARCH?
>
> With CONFIG_X86_PC, I can set CONFIG_SPARSEMEM=y.
>
> With CONFIG_X86_GENERICARCH, CONFIG_SPARSEMEM depends on CONFIG_NUMA.
>
> I'm using the patch below to enable sparsemem instead of flatmem, but  
> don't know what impact it has. System booted and running.
>
> It would be nice to automatically default CONFIG_X86_BIGSMP with CPUs 
> > 8. But I don't know to do that.

thanks, applied.

i'm wondering, does with that patch applied a working 2.6.26 .config if 
put through 'make oldconfig' boot fine on your box now? Any make 
oldconfig breakage is a regression we want to fix. We want upgrades 
between kernel versions to be seemless and complete.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/