linux-kernel - Re: [stable] [PATCH] Ignore bogus ACPI info for offline CPUs

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <200705211058.34108.dvhltc@us.ibm.com>
Date:	Mon, 21 May 2007 10:58:32 -0700
From:	Darren Hart <dvhltc@...ibm.com>
To:	Chris Wright <chrisw@...s-sol.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...l.org>, Stable Team <stable@...nel.org>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>, Len Brown <lenb@...nel.org>
Subject: Re: [stable] [PATCH] Ignore bogus ACPI info for offline CPUs

On Monday 21 May 2007 10:08:15 Chris Wright wrote:
> * Darren Hart (dvhltc@...ibm.com) wrote:
> > On Saturday 19 May 2007 07:22:50 Thomas Gleixner wrote:
> > > Booting a SMP kernel with maxcpus=1 on a SMP system leads to a hard
> > > hang, because ACPI ignores the maxcpus setting and sends timer
> > > broadcast info for the offline CPUs. This results in a stuck for ever
> > > call to smp_call_function_single() on an offline CPU.
> > >
> > > Ignore the bogus information and print a kernel error to remind ACPI
> > > folks to fix it.
> > >
> > > Affects 2.6.21 / 2.6.22-rc
> > >
> > > Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
> >
> > When I first booted with this patch I received the following in a loop:
> >
> > irq 9: nobody cared (try booting with the "irqpoll" option)
>
> What happens when booting w/out this patch?  Don't want to add known
> regression to -stable.

The system will boot w/o acpi=noirq with and without this patch if maxcpus is 
not specified.  If maxcpus is specified without the patch, the system locks 
up as Thomas described.  If maxcpus is specified with the patch, then 
acpi=noirq is required to boot - but it will boot.  This does not introduce a 
regression IMO.

--Darren

>
> thanks,
> -chris



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