Re: 2.6.23-rc4: maxcpus still broken

[Hugh Dickins <hugh@veritas.com>]

On Wed, 29 Aug 2007, Alexey Dobriyan wrote:
> On Wed, Aug 29, 2007 at 01:35:57AM +0200, Michal Piotrowski wrote:
> > On 28/08/07, Alexey Dobriyan <adobriyan@sw.ru> wrote:
> > > Every time I try to boot with maxcpus=1 it dies show_stat():
> > 
> > Is this a regression?
> 
> yep

A regression since when, I wonder?  Please do NOT waste any time
bisecting, but I'd be interested to know which release or -rc you
previously found it worked on.

When I gave the code a quick look, it appeared to be something
which has long been wrong; but I didn't investigate whether per-cpu
allocation has changed recently.  My _suspicion_, no more than that,
is that it might be a regression to you because you're now forced
to have CONFIG_HOTPLUG_CPU=y where you didn't need it before.

Anyway, it doesn't matter too much what it's a regression since:
it's a bug that needs fixing whatever, and should be simple.
My x86_64 was running other tests yesterday which I didn't want
to interrupt, but I'll take a look later on today.

> 
> > Hugh fixed some issues on x86-64 commit 813409771731d80e6fa94199adf99f2269a4afc0
> 
> This is 2.6.23-rc4, which has this fix, yes.
> 
> And I have second box with exactly same behaviour: x86_64 E6400, it also has ACPI=n
> Turning on ACPI doesn't make it any better, though.

Hugh