Today I tried to gather further information and found: before s2ram:
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq 1600000 1600000 1600000 1600000 cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq 3800000 3800000 3800000 3800000 after resume from s2ram: cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq 1600000 3800000 3800000 3800000 cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq 3800000 3800000 3800000 3800000 which clearly indicates there is some data altered during s2ram cycle. Also fan regulation indicates increased speed/power consumpition after s2ram. FYI (because not reported automatically): I got a quad-core Ivy Bridge processor, here the info for 1st core: cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz stepping : 9 microcode : 0x12 cpu MHz : 1734.000 cache size : 6144 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 6800.74 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: If more information is required, please let me know. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
