From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
Cc: Linux PM mailing list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Tomas M." <tmezzadra@gmail.com>, Ferenc Wagner <wferi@niif.hu>,
Arnd Bergmann <arnd@arndb.de>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Len Brown <len.brown@intel.com>, Kevin Hilman <khilman@ti.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Jean Pihet <j-pihet@ti.com>, Trinabh Gupta <g.trinabh@gmail.com>,
linux-pm@lists.linux-foundation.org,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
preeti@linux.vnet.ibm.com
Subject: Re: Suspend/resume regressions on Lenovo S10-3
Date: Wed, 06 Jun 2012 07:48:52 -0700 [thread overview]
Message-ID: <4FCF6DD4.4090608@linux.vnet.ibm.com> (raw)
In-Reply-To: <4FCF5249.2070600@linux.vnet.ibm.com>
On 06/06/2012 05:51 AM, Deepthi Dharwar wrote:
> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
> index 24fe3af..6e35293 100644
> --- a/drivers/acpi/processor_idle.c
> +++ b/drivers/acpi/processor_idle.c
> @@ -895,8 +895,9 @@ static int acpi_idle_enter_bm(struct cpuidle_device *dev,
> if (unlikely(!pr))
> return -EINVAL;
>
> -
> if (acpi_idle_suspend) {
> + local_irq_disable();
> + local_irq_enable();
> cpu_relax();
> return -EINVAL;
> }
Heh, that is quite the hack. :)
However, it does at least work around my problem: I can suspend again
with 46bcfad + your patch.
next prev parent reply other threads:[~2012-06-06 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FC2DA8C.7050401@linux.vnet.ibm.com>
2012-06-06 12:51 ` Suspend/resume regressions on Lenovo S10-3 Deepthi Dharwar
2012-06-06 13:43 ` Rafael J. Wysocki
2012-06-06 15:09 ` [linux-pm] " Alan Stern
2012-06-06 16:45 ` Deepthi Dharwar
2012-06-08 6:30 ` Rafael J. Wysocki
2012-06-08 6:41 ` Srivatsa S. Bhat
2012-06-06 14:48 ` Dave Hansen [this message]
2012-06-11 13:31 ` Srivatsa S. Bhat
2012-06-11 14:57 ` Dave Hansen
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=4FCF6DD4.4090608@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=arjan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=deepthi@linux.vnet.ibm.com \
--cc=g.trinabh@gmail.com \
--cc=j-pihet@ti.com \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-pm@vger.kernel.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tmezzadra@gmail.com \
--cc=wferi@niif.hu \
/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;
as well as URLs for NNTP newsgroup(s).