From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: preeti <preeti@linux.vnet.ibm.com>
Cc: Linux PM mailing list <linux-pm@vger.kernel.org>,
Dave Hansen <dave@linux.vnet.ibm.com>,
linux-acpi@vger.kernel.org,
"Srivatsa.S.Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH] Cpuidle drivers, Suspend : Fix suspend/resume hang with intel_idle driver
Date: Sat, 30 Jun 2012 00:13:42 +0200 [thread overview]
Message-ID: <201206300013.42974.rjw@sisk.pl> (raw)
In-Reply-To: <4FED6CED.2060908@linux.vnet.ibm.com>
On Friday, June 29, 2012, preeti wrote:
>
> From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
>
> Dave Hansen reported problems with suspend/resume when used
> with intel_idle driver.More such problems were noticed.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/674075.
>
> The reason for this could not be suspected till he reported
> resume hang issue when used with acpi idle driver on his Lenovo-S10-3
> Atom netbook.
>
> The patch-[PM / ACPI: Fix suspend/resume regression caused by cpuidle
> cleanup],fixed this issue by ensuring that acpi idle drivers prevent
> cpus from going into deeper sleep states during suspend to prevent
> resume hang on certain bios.
> http://marc.info/?l=linux-pm&m=133958534231884&w=2
>
> Commit b04e7bdb984e3b7f62fb7f44146a529f88cc7639
> (ACPI: disable lower idle C-states across suspend/resume) throws
> light on the resume hang issue on certain specific bios.
>
> Also the following lines in drivers/idle/intel_idle.c suggest intel_idle
> drivers should also ensure cpus are prevented from entering idle states
> during suspend to avoid a resume hang.
>
> /*
> * Known limitations
> * [..]
> *
> * ACPI has a .suspend hack to turn off deep c-states during suspend
> * to avoid complications with the lapic timer workaround.
> * Have not seen issues with suspend, but may need same workaround here.
> *
> */
> This patch aims at having this fix in a place common to both the idle
> drivers.
>
> Suspend is enabled only if ACPI is active on x86.Thus the setting of
> acpi_idle_suspend during suspend is moved up to ACPI specific code with
> both acpi and intel idle drivers checking if it is valid to enter deeper
> idle states.The setting of acpi_idle_suspend is done via PM_SUSPEND_PREPARE
> notifiers to avoid race conditions between processors entering idle states
> and the ongoing process of suspend.
>
> The check on acpi_idle_suspend is included in the most appropriate header
> so as to be visible to both the idle drivers irrespective of the
> different configurations.Even if ACPI is disabled intel idle drivers can
> still carry out the acpi_idle_suspend check.
>
> Reported-by: Dave Hansen <dave@linux.vnet.ibm.com>
> Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
> Reviewed-by: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
> Signed-off-by: Preeti U Murthy <preeti@linux.vnet.ibm.com>
The patch didn't get any better as a result of modifying the changelog.
Please consider it as rejected.
Thanks,
Rafael
next prev parent reply other threads:[~2012-06-29 22:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 9:16 Cpuidle drivers,Suspend : Fix suspend/resume hang with intel_idle driver preeti
2012-06-28 9:53 ` Rafael J. Wysocki
2012-06-28 16:21 ` preeti
2012-06-28 19:11 ` Cpuidle drivers, Suspend " Rafael J. Wysocki
2012-06-29 4:11 ` Cpuidle drivers,Suspend " preeti
2012-06-29 5:26 ` preeti
2012-06-29 8:53 ` [PATCH] " preeti
2012-06-29 22:13 ` Rafael J. Wysocki [this message]
2012-06-29 22:11 ` Rafael J. Wysocki
2012-07-02 4:37 ` preeti
2012-07-02 5:04 ` Cpuidle drivers, Suspend " Srivatsa S. Bhat
2012-07-02 5:27 ` Cpuidle drivers,Suspend " preeti
2012-07-02 5:28 ` Srivatsa S. Bhat
2012-06-29 22:07 ` Rafael J. Wysocki
2012-06-30 13:11 ` Rafael J. Wysocki
2012-07-02 10:21 ` preeti
2012-07-02 5:36 ` preeti
2012-07-02 5:33 ` Srivatsa S. Bhat
2012-07-02 19:43 ` Rafael J. Wysocki
2012-07-06 3:11 ` [PATCH V2] Suspend,cpuidle:resume_hang fix with cpuidle preeti
2012-07-06 3:07 ` Dave Hansen
2012-07-06 7:36 ` preeti
2012-07-06 7:42 ` preeti
2012-07-06 17:20 ` Srivatsa S. Bhat
2012-07-06 17:23 ` Rafael J. Wysocki
2012-07-06 17:21 ` Dave Hansen
2012-07-06 17:30 ` Rafael J. Wysocki
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=201206300013.42974.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-acpi@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 \
/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).