linux-kernel - Re: 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-prev] [day] [month] [year] [list]

Message-Id: <1179565350.12981.107.camel@chaos>
Date:	Sat, 19 May 2007 11:02:30 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Darren Hart <dvhltc@...ibm.com>
Cc:	linux-rt-users@...r.kernel.org,
	"lkml," <linux-kernel@...r.kernel.org>
Subject: Re: maxcpus=1 fails to boot

On Sat, 2007-05-19 at 00:15 -0700, Darren Hart wrote:
> 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"...

Be careful, when sticking your head into this hole !

I try to nail it down. 

	tglx


-
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/