CPU Governor not working at boot

  • I've been staring at my boot log and found another catch:

    Code
    Wed Dec 10 20:19:20 2014: CPUFreq Utilities: Setting conservative CPUFreq governor...disabled, governor not available...done.


    Proof that modules are not being used:

    Code
    root@demeter:~# lsmod | grep cpufreq
    cpufreq_userspace      12576  0
    cpufreq_stats          12866  0
    cpufreq_conservative    13147  0
    cpufreq_powersave      12454  0


    Did some searching and found that the location the init.d script is searching for the governor does not exist:

    Code
    # Which governor to use. Must be one of the governors listed in:
    #   cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors


    I have found anything related to cpu frequency in the following directory:


    How should the /etc/init.d/cpufrequtils script be changed?

    OMV 1.5 (Kralizec) VM on ESXi | HP Microserver | Snapraid

  • Code
    root@demeter:~# cat /etc/default/cpufrequtils
    ENABLE="true"
    GOVERNOR="conservative"
    MAX_SPEED="0"
    MIN_SPEED="0"


    By the way, congratulations with your 1,000th post!

    OMV 1.5 (Kralizec) VM on ESXi | HP Microserver | Snapraid

  • Seems no driver is loaded somehow:

    Code
    root@demeter:~# cpufreq-info
    cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
    Report errors and bugs to cpufreq@vger.kernel.org, please.
    analyzing CPU 0:
      no or unknown cpufreq driver is active on this CPU
      maximum transition latency: 4294.55 ms.
    analyzing CPU 1:
      no or unknown cpufreq driver is active on this CPU
      maximum transition latency: 4294.55 ms.

    OMV 1.5 (Kralizec) VM on ESXi | HP Microserver | Snapraid

  • I get twice the message:

    Code
    root@demeter:~# update-rc.d cpufrequtils disable
    update-rc.d: using dependency based boot sequencing
    insserv: warning: current start runlevel(s) (empty) of script `cpufrequtils' overrides LSB defaults (2 3 4 5).
    insserv: warning: current stop runlevel(s) (2 3 4 5) of script `cpufrequtils' overrides LSB defaults (empty).


    The governor warning during boot is gone.
    cpufreq info still the same:

    Code
    root@demeter:~# cpufreq-info
    cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
    Report errors and bugs to cpufreq@vger.kernel.org, please.
    analyzing CPU 0:
      no or unknown cpufreq driver is active on this CPU
      maximum transition latency: 4294.55 ms.
    analyzing CPU 1:
      no or unknown cpufreq driver is active on this CPU
      maximum transition latency: 4294.55 ms.

    OMV 1.5 (Kralizec) VM on ESXi | HP Microserver | Snapraid

  • Correct


    I'm off now. Will check in tomorrow. I want this boot to be as slick as possible. 8)

    OMV 1.5 (Kralizec) VM on ESXi | HP Microserver | Snapraid

  • I have enabled both at boot again. I can see the 'governor' message durng boot appear again.
    I just read this article about vmware passing on static/dynamic frequency data to clients, http://techhead.co/saving-powe…d-frequency-scaling-dvfs/
    This advanced setting value 'Power.CpuPolicy' is not available on ESXi 5.1.


    Even if this data is not passed on to OMV virtual machine, wouldn't the data in

    Code
    # Which governor to use. Must be one of the governors listed in:
    #   cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors

    be available in OMV?

    OMV 1.5 (Kralizec) VM on ESXi | HP Microserver | Snapraid

    Einmal editiert, zuletzt von bakman ()

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!