From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
cpufreq@vger.kernel.org,
"Linux PM list" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: Fix cpufreq regression after suspend/resume
Date: Mon, 15 Jul 2013 11:43:40 +0530 [thread overview]
Message-ID: <51E39314.6060808@linux.vnet.ibm.com> (raw)
In-Reply-To: <1373719972.1359.8.camel@x61.thuisdomein>
On 07/13/2013 06:22 PM, Paul Bolle wrote:
> On Sat, 2013-07-13 at 12:16 +0200, Paul Bolle wrote:
>> I suspect that the stuck frequency is a regression introduced in v3.10.0.
>
> The culprit apparently is commit a66b2e503f ("cpufreq: Preserve sysfs
> files across suspend/resume"). Srivatsa submitted a patch to revert that
> commit (see https://lkml.org/lkml/2013/7/11/661 ). That revert seems to
> fix this issue too.
>
>
Thanks a lot for your tests and for confirming that the complete revert
fixes your cpufreq issue.
Regards,
Srivatsa S. Bhat
next prev parent reply other threads:[~2013-07-15 6:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51C08370.4050906@gmx.de>
[not found] ` <1778593.ufLkNuJuaY@vostro.rjw.lan>
[not found] ` <51CB34A2.7090404@gmx.de>
2013-06-26 19:12 ` 3.10-rcX: cpu governor ondemand doesn't scale well after s2ram Rafael J. Wysocki
2013-06-27 4:10 ` Viresh Kumar
2013-06-27 18:00 ` Toralf Förster
2013-06-28 3:44 ` Viresh Kumar
2013-06-28 15:25 ` Toralf Förster
2013-06-29 13:30 ` Viresh Kumar
2013-06-29 17:50 ` Toralf Förster
2013-06-30 14:22 ` Rafael J. Wysocki
2013-06-30 15:15 ` Viresh Kumar
2013-06-30 16:20 ` Toralf Förster
2013-06-30 16:21 ` Toralf Förster
2013-06-30 16:33 ` Srivatsa S. Bhat
2013-06-30 17:05 ` Toralf Förster
2013-06-30 18:52 ` [PATCH] cpufreq: Fix cpufreq regression after suspend/resume Srivatsa S. Bhat
2013-06-30 22:46 ` Rafael J. Wysocki
2013-07-10 20:50 ` Toralf Förster
2013-07-10 22:29 ` Srivatsa S. Bhat
2013-07-11 5:40 ` Lan Tianyu
2013-07-11 6:23 ` Srivatsa S. Bhat
2013-07-11 14:03 ` Lan Tianyu
2013-07-11 14:24 ` Srivatsa S. Bhat
2013-07-11 14:23 ` Alan Stern
2013-07-11 14:38 ` Srivatsa S. Bhat
2013-07-13 10:16 ` Paul Bolle
2013-07-13 12:52 ` Paul Bolle
2013-07-15 6:13 ` Srivatsa S. Bhat [this message]
2013-07-03 19:46 ` 3.10-rcX: cpu governor ondemand doesn't scale well after s2ram Toralf Förster
2013-07-04 6:55 ` Srivatsa S. Bhat
2013-07-04 7:01 ` Viresh Kumar
2013-07-04 7:08 ` Srivatsa S. Bhat
2013-07-04 7:58 ` Viresh Kumar
2013-07-10 19:31 ` Toralf Förster
2013-07-04 8:04 ` Viresh Kumar
2013-07-04 8:23 ` Viresh Kumar
2013-07-04 16:42 ` Toralf Förster
2013-07-05 4:35 ` Viresh Kumar
2013-07-05 14:06 ` Toralf Förster
2013-06-28 17:17 ` Toralf Förster
2013-06-28 18:56 ` Rafael J. Wysocki
2013-06-28 18:51 ` Toralf Förster
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=51E39314.6060808@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rjw@sisk.pl \
--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;
as well as URLs for NNTP newsgroup(s).