Bug#880203: After suspend, cpufreq/scaling_max_freq is ignored - (wild hack) shell script

2017-11-01 Thread Ben Hutchings
On Wed, 2017-11-01 at 13:02 +0100, Leon Meier wrote: > On 31.10.2017 13:25, Leon Meier wrote: > > On 31.10.2017 11:39, Debian Bug Tracking System wrote: > > > Yes, but that doesn't mean we can do anything about it. > > > > Why not simply re-issue the request setting the performance-level after >

Bug#880203: After suspend, cpufreq/scaling_max_freq is ignored - (wild hack) shell script

2017-11-01 Thread Leon Meier
On 31.10.2017 13:25, Leon Meier wrote: On 31.10.2017 11:39, Debian Bug Tracking System wrote: Yes, but that doesn't mean we can do anything about it. Why not simply re-issue the request setting the performance-level after resume? You could at least suggest a script similar to the following