From: Dave Jones <davej@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Mark Lord <lkml@rtr.ca>,
akpm@linux-foundation.org, mlord@pobox.com, rjw@sisk.pl,
tglx@linutronix.de, torvalds@linux-foundation.org,
stable@kernel.org, stable-commits@vger.kernel.org
Subject: Re: patch revert-fix-smp-poweroff-hangs.patch queued to -stable tree
Date: Thu, 13 Dec 2007 12:30:41 -0500 [thread overview]
Message-ID: <20071213173041.GB28148@redhat.com> (raw)
In-Reply-To: <20071213164545.GA10593@suse.de>
On Thu, Dec 13, 2007 at 08:45:45AM -0800, Greg KH wrote:
> >> There still is a remaining shutdown problem in 2.6.22 with old APM based
> >> systems, but this fix is not the correct one
> > ..
> >
> > Eh? It may not fix APM systems, but it *does* fix several known examples
> > of ACPI systems.
>
> And I have a large number of real systems that this patch has caused
> problems with. So much so that we had to revert it from a shipping SuSE
> product already, so I figured it was safe to also revert this in
> mainline as it did cause regressions.
Cheesy, but why not something like..
+ if (acpi_enabled) // Or whatever the var name is these days
+ disable_nonboot_cpus();
until we find out more?
Dave
--
http://www.codemonkey.org.uk
next parent reply other threads:[~2007-12-13 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071213053020.E28AB1454450@imap.suse.de>
[not found] ` <4761601B.3030408@rtr.ca>
[not found] ` <20071213164545.GA10593@suse.de>
2007-12-13 17:30 ` Dave Jones [this message]
[not found] ` <47616C15.7030604@rtr.ca>
[not found] ` <47616F8C.9030803@rtr.ca>
2008-12-17 15:48 ` SMP poweroff hangs: it's baaaack! But on x86_64 this time Mark Lord
2008-12-19 11:59 ` Pavel Machek
2008-12-20 2:19 ` Mark Lord
2008-12-22 15:48 ` Mark Lord
2009-01-05 4:37 ` Mark Lord
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=20071213173041.GB28148@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mlord@pobox.com \
--cc=rjw@sisk.pl \
--cc=stable-commits@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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