From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Date: Sat, 13 Nov 2010 10:30:24 +0000 Subject: Re: [BUG 2.6.27-rc1] find_busiest_group() LOCKUP Message-Id: <1289644224.2084.521.camel@laptop> List-Id: References: <20101111100628.GA24728@localhost> <1289478978.2084.74.camel@laptop> <20101111124015.GA9706@localhost> <1289480656.2084.80.camel@laptop> <20101113084018.GA23098@localhost> In-Reply-To: <20101113084018.GA23098@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Wu Fengguang Cc: LKML , Ingo Molnar , Nikanth Karthikesan , Yinghai Lu , David Rientjes , "Zheng, Shaohui" , Andrew Morton , linux-hotplug@vger.kernel.org On Sat, 2010-11-13 at 16:40 +0800, Wu Fengguang wrote: > > Will try and figure out how the heck that's happening, Ingo any clue? > > It's back to normal on 2.6.37-rc1 when reverting commit 50f2d7f682f9 > ("x86, numa: Assign CPUs to nodes in round-robin manner on fake NUMA"). > > The interesting part is, the commit was introduced in > 2.6.36-rc7..2.6.36, however 2.6.36 boots OK, while 2.6.37-rc1 panics. Argh, that commit again.. Does this fix it: http://lkml.org/lkml/2010/11/12/8