** Description changed: steps to reproduce: 1) use cpufreq-applet to set cpu freqency to a fixed value (userspace governor) that is not maximum (e.g. 800mhz on a 1.7ghz cpu) 2) suspend 3) resume 4) see that cpu freqency governor is still userspace but frequency is maximum (e.g. 1.7ghz, userspace) i use the cpufreq-applet for all monitoring and manipulating cpu frequency scaling, but i don't think this is a bug of the applet itself. i didn't select any package because i don't know which one. ubuntu version is 9.04. please tell me which further information i should provide. + + + EDIT: i'm an idiot, i've been getting these messages for days when + resuming from standby, i just didn't take notice: + + cpufreq: suspend failed to assert current frequency is what timing core thinks it is + cpufreq: resume failed to assert current frequency is what timing core thinks it is
-- cpu frequency is reset to maximum after resume from suspend if governor is userspace https://bugs.launchpad.net/bugs/364514 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
