[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.99.0710100133590.5040@localhost.localdomain>
Date: Wed, 10 Oct 2007 01:35:31 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Linus Torvalds <torvalds@...ux-foundation.org>
cc: Greg KH <greg@...ah.com>, Olof Johansson <olof@...om.net>,
Greg KH <gregkh@...e.de>, "Rafael J. Wysocki" <rjw@...k.pl>,
"Theodore Ts'o" <tytso@....edu>,
Zwane Mwaikambo <zwane@....linux.org.uk>,
Justin Forbes <jmforbes@...uxtx.org>,
linux-kernel@...r.kernel.org,
Chris Wedgwood <reviews@...cw.f00f.org>,
Domenico Andreoli <cavokz@...il.com>,
Mark Lord <mlord@...ox.com>,
Randy Dunlap <rdunlap@...otime.net>,
Michael Krufky <mkrufky@...uxtv.org>,
Chuck Ebbert <cebbert@...hat.com>,
Dave Jones <davej@...hat.com>, akpm@...ux-foundation.org,
Chuck Wolber <chuckw@...ntumlinux.com>, stable@...nel.org,
alan@...rguk.ukuu.org.uk
Subject: Re: [stable] [patch 09/12] Fix SMP poweroff hangs
On Tue, 9 Oct 2007, Linus Torvalds wrote:
>
>
> On Wed, 10 Oct 2007, Thomas Gleixner wrote:
> >
> > Wrapping it into a #ifdef CONFIG_X86 would be sufficient.
>
> Well, the ppc oops seems to be a ppc bug regardless.
>
> If CPU_HOTPLUG isn't defined, the thing does nothing. And if it is
> defined, I don't see why/how ppc can validly oops. So I think the first
> thing to do is to try to figure out why it oopses, not to disable it for
> ppc.
Fair enough. OTOH for the affected PPC users it's a regression and that's
what I'm concerned of.
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/
Powered by blists - more mailing lists