This is going to have to be fixed in userspace. The reason we lose the
cpufreq state is because on suspend, the kernel hot unplugs the CPU,
thus losing all referenced to it.
Userspace is going to need to respond to hot plug/unplug of cpu's and
restore things like governor and frequency. Probably can do this with
some udev rules, and remove the need for the init script all together.
Maybe the init/udev scripts could check of cpu hotplug is enabled, and
act accordingly (use init when it isn't supported and udev scripts when
it is).
** Changed in: powernowd (Ubuntu)
Sourcepackagename: linux-source-2.6.20 => powernowd
Assignee: Ben Collins => (unassigned)
Status: In Progress => Confirmed
--
cpufreq scaling_grovernor only saved for CPU0 on SMP following suspend/resume.
https://launchpad.net/bugs/78512
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
