linux-kernel - maxcpus=1 fails to boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200705190015.53518.dvhltc@us.ibm.com>
Date:	Sat, 19 May 2007 00:15:52 -0700
From:	Darren Hart <dvhltc@...ibm.com>
To:	linux-rt-users@...r.kernel.org
Cc:	"lkml, " <linux-kernel@...r.kernel.org>
Subject: 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/