linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <1412250350.3060.9.camel@x41>
Date:	Thu, 02 Oct 2014 13:45:50 +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: cpufreq v3.17-rc7 error: "cpufreq: cpufreq_resume: Failed to start
 governor for policy: f6909a00"

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

The logs on this laptop go back over nine months (ie, the oldest kernels
I see in there are rc's for v3.13). It has basically booted every rc in
between and never printed this error before. It is an (outdated!)
ThinkPad X41 (single core i686).

Note that I did not actually notice anything odd before checking the
logs. But this laptop is getting rather painful to use, so I'll probably
only notice _major_ regressions.

Feel free to prod me for further details.

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/