Bug#824947: After suspend and subsequent wake-up the contents of scaling_max_freq is disregarded

[Mark <Mark.McGregor@gmx.de>]

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!