linux-kernel - Re: cpufreq v3.17-rc7 error: "cpufreq: cpufreq_resume: Failed to start governor for policy: f6909a00"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 02 Oct 2014 13:55:11 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	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"

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?


Paul Bolle

--
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/