From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Bug #13116] Can't boot with nosmp Date: Tue, 09 Jun 2009 21:42:55 +0300 Message-ID: <4A2EAD2F.5010505@redhat.com> References: <20090608091544.53a94235@nehalam> <20090608170437.1c2386a5@nehalam> <4A2EAA53.7060006@redhat.com> <20090609113656.46ed6335@nehalam> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090609113656.46ed6335@nehalam> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Stephen Hemminger Cc: Dan Williams , Rusty Russell , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List 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.