Subject : Can't boot with "nosmp" Submitter : Stephen Hemminger <shemminger@vyatta.com> Date : 2009-04-15 4:18 References : http://marc.info/?l=linux-kernel&m=123976917817920&w=4 Handled-By : Dan Williams <dan.j.williams@intel.com> This entry is being used for tracking a regression from 2.6.29. Please don't close it until the problem is fixed in the mainline.
References : http://lkml.org/lkml/2009/6/8/301
On Tuesday 09 June 2009, Stephen Hemminger wrote: > On Tue, 09 Jun 2009 21:42:55 +0300 > Avi Kivity <avi@redhat.com> wrote: > > > 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 did some testing of different versions. > > * Problem does not exist with 2.6.30-rc8 (so regression should be closed). > > * Problem does exist with 2.6.29.4 > > * Happens with both nosmp and maxcpus=1