** Description changed:
While testing the current 3.7.0-0.5 kernel together with the Xen 4.2
package I noticed that "xenpm get-cpufreq-para 0" would weirdly report
only one available frequency. Booting back into kernel 3.5.0-18.29 with
the same userspace shows the expected output:
cpu id : 0
affected_cpus : 0
cpuinfo frequency : max [2000000] min [800000] cur [800000]
+ scaling_driver :
+ scaling_avail_gov : userspace performance powersave ondemand
+ current_governor : ondemand
+ ondemand specific :
+ sampling_rate : max [10000000] min [10000] cur [20000]
+ up_threshold : 80
+ scaling_avail_freq : 2000000 1500000 1200000 1000000 *800000
+ scaling frequency : max [2000000] min [800000] cur [800000]
+
+ Bad output on 3.7:
+
+ cpu id : 0
+ affected_cpus : 0
+ cpuinfo frequency : max [1600000] min [1600000] cur [1600000]
scaling_driver :
scaling_avail_gov : userspace performance powersave ondemand
current_governor : ondemand
ondemand specific :
sampling_rate : max [10000000] min [10000] cur [20000]
up_threshold : 80
- scaling_avail_freq : 2000000 1500000 1200000 1000000 *800000
- scaling frequency : max [2000000] min [800000] cur [800000]
+ scaling_avail_freq : *1600000 *1600000 *1600000 *1600000 *1600000
+ scaling frequency : max [1600000] min [1600000] cur [1600000]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078619
Title:
[raring] xen power managment (freq scaling) fails on linux 3.7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1078619/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
