Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764630AbYHFJgt (ORCPT ); Wed, 6 Aug 2008 05:36:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758393AbYHFJgi (ORCPT ); Wed, 6 Aug 2008 05:36:38 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:57676 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1758216AbYHFJgh (ORCPT ); Wed, 6 Aug 2008 05:36:37 -0400 Date: Wed, 06 Aug 2008 02:36:38 -0700 (PDT) Message-Id: <20080806.023638.98202277.davem@davemloft.net> To: jeff.chua.linux@gmail.com Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.27rc1 cannot boot more than 8CPUs From: David Miller In-Reply-To: References: <20080806.001836.135194365.davem@davemloft.net> X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1068 Lines: 29 From: "Jeff Chua" Date: Wed, 6 Aug 2008 17:33:07 +0800 > On Wed, Aug 6, 2008 at 3:18 PM, David Miller wrote: > > > You have to turn off CONFIG_PROVE_LOCKING, in fact just turn off > > everything in the lock debugging section: > > > > # CONFIG_DEBUG_RT_MUTEXES is not set > > # CONFIG_RT_MUTEX_TESTER is not set > > # CONFIG_DEBUG_SPINLOCK is not set > > # CONFIG_DEBUG_MUTEXES is not set > > # CONFIG_DEBUG_LOCK_ALLOC is not set > > # CONFIG_PROVE_LOCKING is not set > > # CONFIG_LOCK_STAT is not set > > # CONFIG_DEBUG_SPINLOCK_SLEEP is not set > > # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set > > > > I don't any option to turn these off. Still searching. Maybe edit the ".config" file at the top level of the kernel sources and then type "make oldconfig" ?!?!?! -- 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/