Re: the maxcpus= boot parameter broke somewhere along the line

[Sasha Levin]

On Tue, Mar 6, 2012 at 6:48 PM, Nick Bowler <nbowler@xxxxxxxxxxxxxxxx> wrote:
> On 2012-03-06 17:17 +0200, Sasha Levin wrote:
>> On Tue, Mar 6, 2012 at 4:59 PM, Jeff Moyer <jmoyer@xxxxxxxxxx> wrote:
>> > When booting my machine with maxcpus=1, it seems to be ignored with
>> > 3.3.0-rc3.  I know that 3.1.0-rc3 works fine, but I haven't had time to
>> > track it down any further than that.  I've attached the dmesg from my
>> > machine.  Let me know if there is any other information that would help
>> > in solving this.
>>
>> [snip]
>>
>> > Brought up 1 CPUs
>> > Total of 1 processors activated (4256.06 BogoMIPS).
>>
>> Looks like it indeed brings up only one CPU, what's the problem there?
>
> If you scroll further down it seems that the remaining CPUs are brought
> online near the end of the boot?
>
>  [...]
>  udev: starting version 147
>  SMP alternatives: switching to SMP code
>  WARNING! power/level is deprecated; use power/control instead
>  EDAC MC: Ver: 2.1.0
>  Booting Node 0 Processor 3 APIC 0x3
>  smpboot cpu 3: start_ip = 9a000
>  EDAC MC0: Giving out device to 'i3200_edac' 'i3200': DEV 0000:00:00.0
>  NMI watchdog enabled, takes one hw-pmu counter.
>  Booting Node 0 Processor 2 APIC 0x1
>  smpboot cpu 2: start_ip = 9a000
>  NMI watchdog enabled, takes one hw-pmu counter.
>  Booting Node 0 Processor 1 APIC 0x2
>  smpboot cpu 1: start_ip = 9a000
>  NMI watchdog enabled, takes one hw-pmu counter.

I can't reproduce it locally with a 3.3-rc5 kernel.
--
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/