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]

Message-ID: <489A057E.8090405@qualcomm.com>
Date:	Wed, 06 Aug 2008 13:11:42 -0700
From:	Max Krasnyansky <maxk@...lcomm.com>
To:	Li Zefan <lizf@...fujitsu.com>
CC:	Jeff Chua <jeff.chua.linux@...il.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.27rc1 cannot boot more than 8CPUs

Li Zefan wrote:
> Max Krasnyansky wrote:
>> Jeff Chua wrote:
>>> On Wed, Aug 6, 2008 at 11:54 AM, Max Krasnyansky <maxk@...lcomm.com>
>>> wrote:
>>>
>>>> Are you running 32-bit kernel ?
>>> Yes. But, does it matter?
>> It used to. 64-bit kernel used to handle maxcpus option as documented in
>> the Documentation/cpu-hotplug.txt and 32-bit one was broken.
>> I just looked at the latest code and realized that both are now broken.
>> They ignore cpu id > maxcpus instead of not-booting them.
>>
> 
> Yes. I have an x86_64 box with 4 cpus, but yesterday when I booted up with maxcpus=2,
> I didn't see the other 2 cpus.
> 
>> I'll send a patch that fixes that tomorrow.
>>
> 
> greate :)

I just sent it and CC'ed both of you guys.
	[PATCH] Resurect proper handling of maxcpus= kernel option

Jeff, maybe you can try again booting with maxcpus=8 and then bringing 
them online one by one to see where/what fails.

Max


--
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/