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: <48992E5A.3050303@cn.fujitsu.com>
Date:	Wed, 06 Aug 2008 12:53:46 +0800
From:	Li Zefan <lizf@...fujitsu.com>
To:	Max Krasnyansky <maxk@...lcomm.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

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 :)

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