Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764163AbYHFEtz (ORCPT ); Wed, 6 Aug 2008 00:49:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753465AbYHFEs4 (ORCPT ); Wed, 6 Aug 2008 00:48:56 -0400 Received: from wolverine02.qualcomm.com ([199.106.114.251]:48731 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753451AbYHFEs4 (ORCPT ); Wed, 6 Aug 2008 00:48:56 -0400 X-IronPort-AV: E=McAfee;i="5200,2160,5354"; a="5181603" Message-ID: <48992D35.9020005@qualcomm.com> Date: Tue, 05 Aug 2008 21:48:53 -0700 From: Max Krasnyansky User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Jeff Chua CC: lkml Subject: Re: 2.6.27rc1 cannot boot more than 8CPUs References: <48991B07.3050500@qualcomm.com> <48992085.3050203@qualcomm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 726 Lines: 20 Jeff Chua wrote: > On Wed, Aug 6, 2008 at 11:54 AM, Max Krasnyansky 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. I'll send a patch that fixes that tomorrow. Max -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/