When a user is using the intel_pstate driver in performance mode, then
yes, prior to Kernel 4.2RC1 the CPU frequency will be typically be stuck
after resume from suspend.
This is not a pm-ultils issue (which is how I stumbled across this bug
report).
To test that the issue is fixed on kernel 4.2, just use primitive
commands and not these higher level utilities (that I neither use or
know anything about). For example use:
grep MHz /proc/cpuinfo
to observe CPU frequencies.
The commit that, I think, fixes this issue is:
commit 6c1e45917dec5e7c99ba8125fd8cc50f6e482a21
Author: Doug Smythies <doug.smyth...@gmail.com>
Date: Mon Jun 1 21:12:34 2015 -0700
intel_pstate: Force setting target pstate when required
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1484587
Title:
CPU frequency management fails to re-engage on resume from suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
