Your message dated Wed, 22 Jun 2016 18:35:35 +0200
with message-id <[email protected]>
and subject line
has caused the Debian Bug report #824947,
regarding After suspend and subsequent wake-up the contents of scaling_max_freq
is disregarded
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
824947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824947
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-4.5.0-2-amd64
Version: 4.5.3-2
Before suspend and after suspend we had
# for i in `seq 0 7`; do cat
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_min_freq; done
1200000
1200000
1200000
1200000
1200000
1200000
1200000
1200000
# for i in `seq 0 7`; do cat
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq; done
1200000
1200000
1200000
1200000
1200000
1200000
1200000
1200000
Before suspend, we had around 1200000 in cpuinfo_cur_freq, but after
suspend we have:
# for i in `seq 0 7`; do cat
/sys/devices/system/cpu/cpu$i/cpufreq/cpuinfo_cur_freq; done
2599898
2599898
2599898
2599898
2599898
2600000
2599898
2600000
We constantly have
# for i in `seq 0 7`; do cat
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_governor; done
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
The cooling is noisy, so it's not just a wrong printf. Plz repair!
--- End Message ---
--- Begin Message ---
close 824947
thanks
--- End Message ---
