> 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.
@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 . * cur_freq: 1599768 max_freq: 3800000 min_freq: 1600000 transition_ latency: 4294967295 available_ governors: performance powersave cur_freq: 1599768 driver: intel_pstate governor: powersave max_freq: 3800000 min_freq: 1600000 setspeed: <unsupported>
affected_cpus:0
cpuinfo_
cpuinfo_
cpuinfo_
cpuinfo_
related_cpus:0
scaling_
scaling_
scaling_
scaling_
scaling_
scaling_
scaling_