Comment 33 for bug 1188647

Revision history for this message
Doug Smythies (dsmythies) wrote :

@mike:

> if you don't think this is the right bug I can open another one or something,

This is not the right bug report, and we need to get off it before others start to complain.
However, it isn't time to open a new one yet, in my opinion, because we don't yet know what to file it against.

> but unless you can suggest a patch to try or a setting to change I am
> probably just going to disable pstate on the GRUB command line and be done with it

Well, a lot of people do just that, but then also wonder why issues don't get solved. Issues don't get solved if people don't investigate.

Myself, and without any proof, I suspect thermald is your root issue. Have a look at this bug: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1656528

By the way, a cool trick for some of the stuff you were listing above is to do this instead:

root@s15:/sys/devices/system/cpu/cpu0/cpufreq# grep . *
affected_cpus:0
cpuinfo_cur_freq:1599768
cpuinfo_max_freq:3800000
cpuinfo_min_freq:1600000
cpuinfo_transition_latency:4294967295
related_cpus:0
scaling_available_governors:performance powersave
scaling_cur_freq:1599768
scaling_driver:intel_pstate
scaling_governor:powersave
scaling_max_freq:3800000
scaling_min_freq:1600000
scaling_setspeed:<unsupported>