maxcpus=1 fails to boot

When trying to boot with the maxcpus=1 option, the -rt kernel seems to hang 
somewhere in acpi_processor_init().

I tested mainline 2.6.21 and it does boot with maxcpus=1.  2.6.20-rt8, 
2.6.21-rt1, 2, and 4 all hang at:

Calling initcall 0xffffffff817a41df: acpi_processor_init+0x0/0xdf()

when booted with initcall_debug and maxcpus=1.  I traced this only as far as 
the call to acpi_bus_register_driver.  So this seems to have been introduced 
by the -rt patch.  I'm not sure if I should try and see when it was 
introduced (as 2.6.16-rt22 does not fail) or if I should head "down the acpi 
rabbit hole"...

Thanks,

-- 
Darren Hart
IBM Linux Technology Center
Realtime Linux Team
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: maxcpus=1 fails to boot
    • From: Thomas Gleixner <[email protected]>

• Prev by Date: Re: [2.6.22-rc1-mm1] vaio laptop (SZ72B) immediately resumes after STR
• Next by Date: Re: signals logged / [RFC] log out-of-virtual-memory events
• Previous by thread: [PATCH/WIP] Remove 'irq' argument from all IRQ handlers
• Next by thread: Re: maxcpus=1 fails to boot
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]