From: Darren Hart <dvhltc@us.ibm.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@osdl.org>, Stable Team <stable@kernel.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [stable] [PATCH] Ignore bogus ACPI info for offline CPUs
Date: Mon, 21 May 2007 10:58:32 -0700 [thread overview]
Message-ID: <200705211058.34108.dvhltc@us.ibm.com> (raw)
In-Reply-To: <20070521170815.GE3429@sequoia.sous-sol.org>
On Monday 21 May 2007 10:08:15 Chris Wright wrote:
> * Darren Hart (dvhltc@us.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@linutronix.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
prev parent reply other threads:[~2007-05-21 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 14:22 [PATCH] Ignore bogus ACPI info for offline CPUs Thomas Gleixner
2007-05-21 16:47 ` Darren Hart
2007-05-21 17:08 ` [stable] " Chris Wright
2007-05-21 17:32 ` Thomas Gleixner
2007-05-21 17:57 ` Chris Wright
2007-05-21 17:58 ` Darren Hart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200705211058.34108.dvhltc@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox