Re: [Bug #13116] Can't boot with nosmp

[Stephen Hemminger]

On Tue, 09 Jun 2009 21:42:55 +0300
Avi Kivity <avi@xxxxxxxxxx> 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


Given that it is fixed in 2.6.30, at this point there really is no urgency
to spend more time investigating the issue. There are certainly bigger problems
to deal with.

-- 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/