From: Paul Bolle <pebolle@tiscali.nl>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: cpufreq v3.17-rc7 error: "cpufreq: cpufreq_resume: Failed to start governor for policy: f6909a00"
Date: Thu, 02 Oct 2014 23:47:35 +0200 [thread overview]
Message-ID: <1412286455.2877.2.camel@x41> (raw)
In-Reply-To: <6111663.iIs1ITIHKP@vostro.rjw.lan>
Rafael J. Wysocki schreef op do 02-10-2014 om 19:34 [+0200]:
> On Thursday, October 02, 2014 06:33:28 PM Paul Bolle wrote:
> > On Thu, 2014-10-02 at 18:38 +0200, Rafael J. Wysocki wrote:
> > > Can you please try linux-pm.git/linux-next? There's a commit from Viresh in
> > > there with a chance to fix this and which I'm going to push to Linus shortly?
> >
> > Do you mean b1b12babe3b72cfb08b875245e5a5d7c2747c772 ("cpufreq: update
> > 'cpufreq_suspended' after stopping governors")? Does that require
> > anything else from that tree? It doesn't matter much, but if possible I
> > would prefer to add as few patches as I can get away with.
>
> Yes, that's the commit. It should work alone too.
Applies and builds cleanly on top of v3.17-rc7. Light testing (two
suspend and resume cycles and one hibernate and thaw cycle) doesn't
trigger the error.
So that commit works for this ThinkPad X41 too, it seems.
Paul Bolle
prev parent reply other threads:[~2014-10-02 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 11:45 cpufreq v3.17-rc7 error: "cpufreq: cpufreq_resume: Failed to start governor for policy: f6909a00" Paul Bolle
2014-10-02 11:55 ` Paul Bolle
2014-10-02 16:38 ` Rafael J. Wysocki
2014-10-02 16:33 ` Paul Bolle
2014-10-02 17:34 ` Rafael J. Wysocki
2014-10-02 21:47 ` Paul Bolle [this message]
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=1412286455.2877.2.camel@x41 \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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).