This patch will fix it. Cpus that share cpufreq settings have their cpufreq settings symlinked together. What is happening is that we are saving several conflicting cpufreq settings (depending on the number of cores that share the same settings). The first time settings are saved for a given cpu group the correct ones are saved, the ones after that are all userspace. If the order in which the settings are restored are not the exact opposite, we will get the settings wrong.
The easiest way to avoid the whole situation is to skip any cores that are symlinked when saving settings. Their settings will be restored correctly when we restore the settings for whatever non-symlinked core they are grouped with. ** Attachment added: "fix saving incorrect cpufreq settings." http://launchpadlibrarian.net/12827304/fix-94cpufreq-in-pm-utils.patch -- pm-utils changes default cpu policy after resuming from suspend-to-ram https://bugs.launchpad.net/bugs/162652 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
