cpu frequency is reset to maximum after resume from suspend if governor is userspace

I'm also hitting this in Lucid, though without the messages reported by Andreas. I originally reported it as bug 512686.

I also see this in Karmic

I had this problem on Jaunty and still have it on Lucid. I have a System 76 Pangolin Performance running Ubuntu 64-bit.

This continues to be a problem for me in Lucid. Is there any chance whatsoever of this long-standing bug getting looked at? As I said in my original comment on this issue in the now-duplicate bug report (see: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/445186/comments/3) I am willing to provide whatever additional information is needed to track this down.

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
If yes please attach these files:
/var/log/syslog
/var/log/dmesg
and, if possible,open a terminal, type top and take a screenshot when the maximum request of cpu resources is showed.

Tanks in advance.

Thank you for looking into this. I'm uploading two sets of the requested files (in a single archive) One set after a fresh boot, and the second after a suspend/resume cycle. I'm currently using the 2.6.34-020634-generic kernel from Ubuntu mainline. The official kernel shows the same symptoms.

Again, any further assistance I can provide shall be yours on request.

@Fabio: I'm sorry... I didn't mention that I'm using a fully up-to-date Lucid install. Also, in my case, CPU frequency is set to the minimum on my system after a suspend/resume with the default "ondemand" governor. Interestingly, I can switch to "Performance," "Conservative," "Powersave," and any of the "Userspace" settings with expected results. But when I switch back to "Ondemand" it is again stuck at the minimum frequency (800 MHZ on my Intel Core 2 Duo P8700). Again, thank you for looking into this annoying bug.

Can you run in a terminal
apport-collect -p cpufreq-applet (or the righ name of the applet you use)364514

Hi Fabio, I have the same bug so I will run the apport-collect command and try to attach it to my response. Thank you for looking into this!

@PGScooter: you have to subscribe the bug in order to attach apport collect files
look on the right side of the page and click on subscribe.

And please run in a terminal
apport-collect -p cpufrequtils 364514
Thanks in advance

Architecture: amd64
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
NonfreeKernelModules: nvidia
Package: cpufrequtils 006-2
PackageArchitecture: amd64
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.34-020634-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

apport information

Architecture: amd64
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
NonfreeKernelModules: nvidia
Package: cpufrequtils 006-2
PackageArchitecture: amd64
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-23-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

apport information

thanks for the instructions Fabio.

Note that the first apport-collect command,
apport-collect -p cpufreq-applet 364514
did not work for me. I received an "no additional information added" window or something like that. And in the terminal I had the message "apport-collect -p cpufreq-applet 364514Package cpufreq-applet not installed and no hook available, ignoring"

And regarding the second,
apport-collect -p cpufrequtils 364514
This worked and is now attached. But I had to install cpufrequtils. That is, I have had this problem long before this was installed.

Thanks!

@Fabio: We did what you asked months ago, and yet another release (10.10) has come and gone with this bug still a problem. Although "confirmed," its importance remains "undecided" and it has not yet been assigned to anybody. I wish I were a competent coder, but the only way I have to contribute to the Ubuntu community is to give feedback to developers by way of bug reports. Is there any other information that can be provided by me that will speed the process along?

I've just installed Ubuntu 11.10 on an Optiplex 990 Desktop w/ i7-2600 chip. I noticed that, after waking from sleep, all my processor cores were maxed out at 3.4GHz.

I ran this:

sudo cpufreq-set -u 1.6GHz

That seems to fix everything at 1.6GHz. If I set it back to 3.4GHz again with the same command, everything seems to be ok--it goes back to 'ondemand' with 3.4GHz maximum. I guess I can write a little script to do this.

i've had performance issues post-suspend on my System 76 Pangolin Performance for some time, and now believe it is related to this bug. On a fresh start, my cpu frequency seems to be 2401MHz on AC power or 1600MHz on DC power, but after resuming from suspend, it seems stuck at 800MHz. If my system suspends, i basically need to reboot to make things viable again. Would love some progress on this, and can submit logs or whatever to assist.

smcoll: that sounds like this bug indeed. Did you add yourself to the "This bug affects me" list? I think that's the only way to get attention.

PGScooter: thanks for pointing that out. i just added myself.

This seems to have been fixed for me on 13.10. I just did a quick test. I don't actually use suspend anymore (I got out of the habit because of this bug). smcoll can you confirm that this is fixed on 13.10?

Never mind. It's definitely still there. I thought it was fixed because in the cpufreq selector it stayed the same after suspend (it stayed on ondemand) but comp ran super slow so I had to manually select 2.40.

This bug seems to affect 15.10, without even using userspace. It appears that only CPU1 is set to 'powersave' resuming from suspend.

---Before Suspend (on battery power)---
thejas@thejas-Aspire-E5-573:~$ cpufreq-info |egrep 'The governor'\|'current CPU'
                  The governor "powersave" may decide which speed to use
  current CPU frequency is 1.79 GHz.
                  The governor "powersave" may decide which speed to use
  current CPU frequency is 923 MHz.
                  The governor "powersave" may decide which speed to use
  current CPU frequency is 1.75 GHz.
                  The governor "powersave" may decide which speed to use
  current CPU frequency is 1.80 GHz.

---After Suspend (on battery power)---
thejas@thejas-Aspire-E5-573:~$ cpufreq-info |egrep 'The governor'\|'current CPU'
                  The governor "powersave" may decide which speed to use
  current CPU frequency is 1.99 GHz.
                  The governor "performance" may decide which speed to use
  current CPU frequency is 2.00 GHz.
                  The governor "performance" may decide which speed to use
  current CPU frequency is 2.00 GHz.
                  The governor "performance" may decide which speed to use
  current CPU frequency is 1.99 GHz.

On a dual-boot laptop this bug causes Ubuntu battery backup time to be worse than windows.

For laptop, workaround is to monitor "/sys/class/power_supply/ACAD/online" using incrond and execute a script to set governor according to its value.