From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: viresh.kumar@linaro.org,
"Toralf Förster" <toralf.foerster@gmx.de>,
robert.jarzmik@intel.com, durgadoss.r@intel.com,
tianyu.lan@intel.com, lantianyu1986@gmail.com,
dirk.brandewie@gmail.com, stern@rowland.harvard.edu,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] Cpufreq, cpu hotplug, suspend/resume related fixes
Date: Sun, 21 Jul 2013 14:59:26 +0200 [thread overview]
Message-ID: <1534467.dElB1LkqvC@vostro.rjw.lan> (raw)
In-Reply-To: <51EB9F3E.70608@linux.vnet.ibm.com>
On Sunday, July 21, 2013 02:13:42 PM Srivatsa S. Bhat wrote:
> On 07/17/2013 09:19 PM, Srivatsa S. Bhat wrote:
> > On 07/17/2013 08:57 PM, Toralf Förster wrote:
> >> On 07/16/2013 11:32 PM, Rafael J. Wysocki wrote:
> >>> On Tuesday, July 16, 2013 05:15:14 PM Toralf Förster wrote:
> [...]
> >>>> sry - here again with full quote of the email :
> >>>>
> >>>> I applied patch [1/8] on top of v3.11-rc1-8-g47188d3 passes two s2ram/wakeup
> >>>> cycles fine and crashed the system at the 3rd attempt / one times just at
> >>>> the 4th (blinking power led, no sysrq, ...).
> >>>>
> >>>> Applying patch 1-8 on top of that tree differs in that way that it
> >>>> crashes now the system even at the 1st attempt or at least at the 2nd
> >>>>
> >>>> My hardware is a ThinkPad T420 with latest BIOS and a 32 bit stable
> >>>> Gentoo Linux - FWIW .config attached.
> >>>
> >>> I think you'll need the fixes first, basically [1/8] from this series and
> >>> this: https://patchwork.kernel.org/patch/2827512/ .
> >>>
> >>> Please try to run with these two things applied only and see how that goes.
> >>>
> >>> Thanks,
> >>> Rafael
> >>>
> >>>
> >> That was it.
> >>
> >> Applying https://patchwork.kernel.org/patch/2827512/ and then patch
> >> [1/8] on top of v3.11-rc1-8-g47188d3 works fine and solved the reported
> >> issue.
> >>
> >> Furthermore applying patches 2-8 works too - suspend/wakeup works fine
> >> and frequencies are scaled right after wakeup at the T420.
> >>
> >
> > Phew! Finally :-)
> >
> > Thank you for all your testing efforts!
> >
>
> Rafael, Viresh, any thoughts on picking up patches 2-8 from this series
> for 3.12?
>
> From the discussions on this thread so far, there are no pending issues:
> Toralf verified that these patches work fine on his system, as he mentioned
> above, and Tianyu Lan independently tested this patchset and found no
> issues with them. Also, Viresh analyzed the refcounting used in the patches
> and we came to the conclusion that there is no problem with them either.
Yes, I'm going to queue up that series for 3.12.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-07-21 12:49 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 22:15 Srivatsa S. Bhat
2013-07-11 22:15 ` [PATCH 1/8] cpufreq: Revert commit a66b2e to fix cpufreq regression during suspend/resume Srivatsa S. Bhat
2013-07-12 7:18 ` Viresh Kumar
2013-07-13 12:46 ` Paul Bolle
2013-07-15 6:18 ` Srivatsa S. Bhat
2013-07-11 22:15 ` [PATCH 2/8] cpufreq: Fix misplaced call to cpufreq_update_policy() Srivatsa S. Bhat
2013-07-12 7:06 ` Viresh Kumar
2013-07-15 6:20 ` Srivatsa S. Bhat
2013-07-15 11:37 ` Rafael J. Wysocki
2013-07-11 22:16 ` [PATCH 3/8] cpufreq: Add helper to perform alloc/free of policy structure Srivatsa S. Bhat
2013-07-12 7:09 ` Viresh Kumar
2013-07-15 6:24 ` Srivatsa S. Bhat
2013-07-11 22:16 ` [PATCH 4/8] cpufreq: Extract non-interface related stuff from cpufreq_add_dev_interface Srivatsa S. Bhat
2013-07-12 7:17 ` Viresh Kumar
2013-07-11 22:16 ` [PATCH 5/8] cpufreq: Extract the handover of policy cpu to a helper function Srivatsa S. Bhat
2013-07-12 7:19 ` Viresh Kumar
2013-07-11 22:16 ` [PATCH 6/8] cpufreq: Introduce a flag ('frozen') to separate full vs temporary init/teardown Srivatsa S. Bhat
2013-07-12 7:31 ` Viresh Kumar
2013-07-11 22:17 ` [PATCH 7/8] cpufreq: Preserve policy structure across suspend/resume Srivatsa S. Bhat
2013-07-15 9:55 ` Viresh Kumar
2013-07-15 10:05 ` Srivatsa S. Bhat
2013-07-15 10:21 ` Viresh Kumar
2013-07-15 11:52 ` Srivatsa S. Bhat
2013-07-15 11:35 ` Rafael J. Wysocki
2013-07-15 11:53 ` Srivatsa S. Bhat
2013-07-16 6:15 ` Viresh Kumar
2013-07-16 8:56 ` Srivatsa S. Bhat
2013-07-16 9:10 ` Viresh Kumar
2013-07-16 9:29 ` Srivatsa S. Bhat
2013-07-16 9:35 ` Viresh Kumar
2013-07-16 9:54 ` Srivatsa S. Bhat
2013-07-11 22:17 ` [PATCH 8/8] cpufreq: Perform light-weight init/teardown during suspend/resume Srivatsa S. Bhat
2013-07-11 22:25 ` [PATCH 0/8] Cpufreq, cpu hotplug, suspend/resume related fixes Jarzmik, Robert
2013-07-11 22:33 ` Rafael J. Wysocki
2013-07-11 22:23 ` Srivatsa S. Bhat
2013-07-16 15:15 ` Toralf Förster
2013-07-16 21:32 ` Rafael J. Wysocki
2013-07-17 5:03 ` Srivatsa S. Bhat
2013-07-17 15:27 ` Toralf Förster
2013-07-17 15:49 ` Srivatsa S. Bhat
2013-07-21 8:43 ` Srivatsa S. Bhat
2013-07-21 9:40 ` Toralf Förster
2013-07-21 10:38 ` Srivatsa S. Bhat
2013-07-21 12:59 ` Rafael J. Wysocki [this message]
2013-07-15 17:38 ` Toralf Förster
2013-07-15 23:25 ` Rafael J. Wysocki
2013-07-13 9:23 ` Toralf Förster
2013-07-13 13:50 ` Toralf Förster
2013-07-15 6:40 ` Srivatsa S. Bhat
2013-07-15 8:27 ` Lan Tianyu
2013-07-15 8:43 ` Srivatsa S. Bhat
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=1534467.dElB1LkqvC@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=dirk.brandewie@gmail.com \
--cc=durgadoss.r@intel.com \
--cc=lantianyu1986@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robert.jarzmik@intel.com \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=tianyu.lan@intel.com \
--cc=toralf.foerster@gmx.de \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®