Announcement

Collapse
No announcement yet.

cpupower - cpu frequency stuck at lowest 400mhz on UX305 ultrabook pc

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    cpupower - cpu frequency stuck at lowest 400mhz on UX305 ultrabook pc

    Kubuntu 16.10 Yakkety Yak

    there seemed to be some problems with cpupower binaries installed from apt-get

    based on the guide found at https://blog.sleeplessbeastie.eu/201...ernor-at-boot/

    i installed cpupower sudo apt-get install linux-tools-common linux-tools-$(uname -r)u (note uname -r is 4.8.0-27-generic) then running it

    > sudo cpupower -c all frequency-info

    analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0
    CPUs which need to have their frequency coordinated by software: 0
    maximum transition latency: Cannot determine or is not supported.
    hardware limits: 400 MHz - 2.20 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 2.20 GHz. The governor "powersave" may decide which speed to use within this range.
    current CPU frequency: 400 MHz (asserted by call to hardware)
    boost state support: Supported: yes
    Active: yes ...
    then i run a heavy compute job but the above command shows that the cpu frequency is stuck at 400 mhz regardless

    then i tried setting the frequency governor to "performance"

    >sudo cpupower -c all frequency-set -g performance
    >sudo cpupower -c all frequency-info
    analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0
    maximum transition latency: Cannot determine or is not supported.
    hardware limits: 400 MHz - 2.20 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 2.20 GHz. The governor "powersave" may decide which speed to use within this range.
    current CPU frequency: 400ha
    Active: yes
    the governer didn't get changed using cpupower then as root

    > cd /sys/devices/system/cpu/cpu0/cpufreq
    > echo performance > scaling_governor
    > cpupower -c all frequency-info
    analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0
    CPUs which need to have their frequency coordinated by software: 0
    maximum transition latency: Cannot determine or is not supported.
    hardware limits: 400 MHz - 2.20 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 2.20 GHz. The governor "performance" may decide which speed to use within this range.
    current CPU frequency: 400 MHz (asserted by call to hardware)
    boost state support: Supported: yes
    Active: yes ...
    the cpupower command did not change the scaling governor, it takes updating it directly in /sys filesystem

    and changing the frequency using

    >cpupower -c all frequency-set -f 2.2ghz
    >cpupower -c all frequency-info
    analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0
    CPUs which need to have their frequency coordinated by software: 0
    maximum transition latency: Cannot determine or is not supported.
    hardware limits: 400 MHz - 2.20 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 2.20 GHz. The governor "performance" may decide which speed to use within this range.
    current CPU frequency: 400 MHz (asserted by call to hardware)
    boost state support: Supported: yes
    Active: yes ...
    didn't helped at all (it doesn't matter what frequency steps is requested 2ghz, 1ghz, 800mhz etc)

    anyone eise run into the same issue? the Intel processor is m3-6y30

    #2
    I think this is the result of this kernel bug -

    https://bugzilla.kernel.org/show_bug.cgi?id=90041

    Spent quite a bit of time with someone on Reddit with the same issue - he found this bug, which appears to have been patched. No idea when the patch will make it into mainstream distros, though.
    we see things not as they are, but as we are.
    -- anais nin

    Comment


      #3
      hi all, an update, due to too little data points when i shutldown and restart my laptop and re-did *different* load tests again, this time round, the cpu frequency become dynamic varying with the loads

      analyzing CPU 0:
      driver: intel_pstate
      CPUs which run at the same hardware frequency: 0
      CPUs which need to have their frequency coordinated by software: 0
      maximum transition latency: Cannot determine or is not supported.
      hardware limits: 400 MHz - 2.20 GHz
      available cpufreq governors: performance powersave
      current policy: frequency should be within 400 MHz and 2.20 GHz.
      The governor "powersave" may decide which speed to use
      within this range.
      current CPU frequency: Unable to call hardware
      current CPU frequency: 1.40 GHz (asserted by call to kernel)
      boost state support:
      Supported: yes
      Active: yes

      analyzing CPU 1:
      driver: intel_pstate
      CPUs which run at the same hardware frequency: 1
      CPUs which need to have their frequency coordinated by software: 1
      maximum transition latency: Cannot determine or is not supported.
      hardware limits: 400 MHz - 2.20 GHz
      available cpufreq governors: performance powersave
      current policy: frequency should be within 400 MHz and 2.20 GHz.
      The governor "powersave" may decide which speed to use
      within this range.
      current CPU frequency: Unable to call hardware
      current CPU frequency: 1.40 GHz (asserted by call to kernel)
      boost state support:
      Supported: yes
      Active: yes

      analyzing CPU 2:
      driver: intel_pstate
      CPUs which run at the same hardware frequency: 2
      CPUs which need to have their frequency coordinated by software: 2
      maximum transition latency: Cannot determine or is not supported.
      hardware limits: 400 MHz - 2.20 GHz
      available cpufreq governors: performance powersave
      current policy: frequency should be within 400 MHz and 2.20 GHz.
      The governor "powersave" may decide which speed to use
      within this range.
      current CPU frequency: Unable to call hardware
      current CPU frequency: 1.40 GHz (asserted by call to kernel)
      boost state support:
      Supported: yes
      Active: yes

      analyzing CPU 3:
      driver: intel_pstate
      CPUs which run at the same hardware frequency: 3
      CPUs which need to have their frequency coordinated by software: 3
      maximum transition latency: Cannot determine or is not supported.
      hardware limits: 400 MHz - 2.20 GHz
      available cpufreq governors: performance powersave
      current policy: frequency should be within 400 MHz and 2.20 GHz.
      The governor "powersave" may decide which speed to use
      within this range.
      current CPU frequency: Unable to call hardware
      current CPU frequency: 1.40 GHz (asserted by call to kernel)
      boost state support:
      Supported: yes
      Active: yes
      sometimes too few data points, cases would trigger the problem, other times it seemed normal
      need to continue monitoring as it seem erratic and application related

      Comment


        #4
        That looks a lot better
        we see things not as they are, but as we are.
        -- anais nin

        Comment

        Working...
        X