Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758454AbZFISnV (ORCPT ); Tue, 9 Jun 2009 14:43:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756279AbZFISnK (ORCPT ); Tue, 9 Jun 2009 14:43:10 -0400 Received: from mx2.redhat.com ([66.187.237.31]:43278 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751742AbZFISnJ (ORCPT ); Tue, 9 Jun 2009 14:43:09 -0400 Message-ID: <4A2EAD2F.5010505@redhat.com> Date: Tue, 09 Jun 2009 21:42:55 +0300 From: Avi Kivity User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Stephen Hemminger CC: Dan Williams , Rusty Russell , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List Subject: Re: [Bug #13116] Can't boot with nosmp References: <20090608091544.53a94235@nehalam> <20090608170437.1c2386a5@nehalam> <4A2EAA53.7060006@redhat.com> <20090609113656.46ed6335@nehalam> In-Reply-To: <20090609113656.46ed6335@nehalam> 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: 913 Lines: 32 Stephen Hemminger wrote: >> This only affects reboots. But yes, the cpumask code has bugs. Does >> the .config involved select MAXSMP? >> >> > > Patch does not fix the problem. Not sure if it is KVM only problem. > Look like possible cpumask always equals what ACPI / SMP tables report. > So currently looking into alloc_percpu which may not handle the possible > but never used cpus. > > Right, it shouldn't have. > It is x86-64 config and does not have MAXSMP set. It does have NR_CPUS set. > So it's not cpumask. Dare I suggest a bisect? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. -- 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/