[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2550705.C9YWxWdtP6@vostro.rjw.lan>
Date: Thu, 02 Oct 2014 18:38:15 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Paul Bolle <pebolle@...cali.nl>
Cc: Viresh Kumar <viresh.kumar@...aro.org>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: cpufreq v3.17-rc7 error: "cpufreq: cpufreq_resume: Failed to start governor for policy: f6909a00"
On Thursday, October 02, 2014 01:55:11 PM Paul Bolle wrote:
> Paul Bolle schreef op do 02-10-2014 om 13:45 [+0200]:
> > Running v3.17-rc7 I see a new (for me) error, apparently during each
> > resume (from suspend) or thaw (from hibernate):
> > cpufreq: cpufreq_resume: Failed to start governor for policy: f6909a00
>
> So there are only two recent commits:
> 7106e02baed4 ("cpufreq: release policy->rwsem on error")
> 8e30444e1530 ("cpufreq: fix cpufreq suspend/resume for
> intel_pstate")
>
> Would it be useful to test whether reverting the oldest commit,
> 8e30444e1530 ("cpufreq: fix cpufreq suspend/resume for intel_pstate"),
> changes anything?
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?
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists