From: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>,
Linux PM mailing list <linux-pm@vger.kernel.org>
Cc: Kevin Hilman <khilman@ti.com>, Len Brown <len.brown@intel.com>,
Arnd Bergmann <arnd@arndb.de>, "Tomas M." <tmezzadra@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
preeti@linux.vnet.ibm.com, linux-pm@lists.linux-foundation.org,
Ferenc Wagner <wferi@niif.hu>,
Arjan van de Ven <arjan@linux.intel.com>,
Jean Pihet <j-pihet@ti.com>
Subject: Re: Suspend/resume regressions on Lenovo S10-3
Date: Wed, 06 Jun 2012 18:21:21 +0530 [thread overview]
Message-ID: <4FCF5249.2070600@linux.vnet.ibm.com> (raw)
In-Reply-To: <4FC2DA8C.7050401@linux.vnet.ibm.com>
On 05/28/2012 07:23 AM, Dave Hansen wrote:
> I have a Lenovo S10-3 Atom netbook. It's always had some amount of
> trouble working with the intel_idle driver, so I usually compile that
> out an use the acpi one. However, just after 3.1, suspend/resume broke.
> 'echo mem > /sys/power/state' would hang before suspending. I bisected
> it down to the commits around:
>
> e978aa7d7d57d04eb5f88a7507c4fb98577def77 / v3.1-1-ge978aa7
>
> by Deepthi. But, current mainline (v3.4-07644-g07acfc2) hangs with a
> different symptom: it suspends, but hangs on resume from suspend. I
> think _that_ delta in the behavior was caused by:
>
> 3439a8da16bcad6b0982ece938c9f8299bb53584
>
> ACPI / cpuidle: Remove acpi_idle_suspend (to fix suspend
> regression)
>
> It's a bit of a pain to bisect these two different things in parallel.
> I was trying to tell git bisect 'good' on working suspend/resume, 'bad'
> on the hang during resume, and 'skip' on the hangs _during_ suspend. 83
> kernels in, I'm not sure that's working very well. :)
>
> Deepthi, do you have any idea why your patches broke me in the first
> place? Perhaps we should fix that regression first before we go on and
> try to figure out what changed to let it suspend again, but break later.
Hi Dave,
Sorry about my patches breaking your suspend-resume.
I, basically tried out building and booting 3.1 kernel with
my patch set to reproduce the failure. I could clearly
see suspend not happening. It turns out to be
a bug with my first patch in global registration
series submitted earlier.
e978aa7d7d57d04eb5f88a7507c4fb98577def77 / v3.1-1-ge978aa7
The following patch, fixes the suspend issues
seen on my laptop due to earlier cpuidle cleanup
(Lenevo T420 booting with acpi_idle enabled).
Can you please give this a try
on top of my patch set (without Rafael's fix)
and see if it fixes the problem for you.
I am not reverting acpi_idle_suspend flag and
hopefully it should resume fine too.
---
This patch fixes suspend-resume issue seen in the kernel 3.1
series using acpi_idle_driver because of cpuidle global
registration cleanup.
Here, when acpi_idle_suspend flag was set ( during suspend)
the interrupts were not getting enabled in acpi_idle_enter_bm()
routine which was causing the system to hang.
Signed-off-by: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
---
drivers/acpi/processor_idle.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
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;
}
Cheers,
Deepthi
next parent reply other threads:[~2012-06-06 12:51 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 ` Deepthi Dharwar [this message]
2012-06-06 13:43 ` Suspend/resume regressions on Lenovo S10-3 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
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=4FCF5249.2070600@linux.vnet.ibm.com \
--to=deepthi@linux.vnet.ibm.com \
--cc=arjan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=dave@linux.vnet.ibm.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=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).