On 31 March 2013 17:40, Simon Kalteis <skalteis@xxxxxxxxxxxxxx> wrote: > cpufreq-info: > > cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 > Report errors and bugs to cpufreq@xxxxxxxxxxxxxxx, please. > analyzing CPU 0: > driver: acpi-cpufreq > CPUs which run at the same hardware frequency: 0 > CPUs which need to have their frequency coordinated by software: 0 > maximum transition latency: 10.0 us. > hardware limits: 600 MHz - 900 MHz > available frequency steps: 900 MHz, 600 MHz > available cpufreq governors: userspace, conservative, powersave, > ondemand, performance current policy: frequency should be within 600 > MHz and 900 MHz. The governor "ondemand" may decide which speed to use > within this range. > current CPU frequency is 900 MHz (asserted by call to hardware). > cpufreq stats: 900 MHz:49.48%, 600 MHz:50.52% (204) > analyzing CPU 1: > driver: acpi-cpufreq > CPUs which run at the same hardware frequency: 1 > CPUs which need to have their frequency coordinated by software: 1 > maximum transition latency: 10.0 us. > hardware limits: 600 MHz - 900 MHz > available frequency steps: 900 MHz, 600 MHz > available cpufreq governors: userspace, conservative, powersave, > ondemand, performance current policy: frequency should be within 600 > MHz and 900 MHz. The governor "ondemand" may decide which speed to use > within this range. > current CPU frequency is 900 MHz (asserted by call to hardware). > cpufreq stats: 900 MHz:22.56%, 600 MHz:77.44% (377) So your hardware has communicated only two frequencies to cpufreq-core: 600 and 900 MHz.. Don't know what that could be on a x86.. Lets see if others added in Cc can help you. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
