kernel-packages team mailing list archive

[Rafael David Tinoco <inaddy@xxxxxxxxxx>]

I found the following commit:

commit 2ed99e39cb9392312c100d9da591c20641c64d12 
Author: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> 
Date: Wed Mar 12 21:49:33 2014 +0100 

cpufreq: Skip current frequency initialization for ->setpolicy drivers

After commit da60ce9f2fac (cpufreq: call cpufreq_driver->get() after 
calling ->init()) __cpufreq_add_dev() sometimes fails for CPUs handled 
by intel_pstate, because that driver may return 0 from its ->get() 
callback if it has not run long enough to collect enough samples on the 
given CPU. That didn't happen before commit da60ce9f2fac which added 
policy->cur initialization to __cpufreq_add_dev() to help reduce code 
duplication in other cpufreq drivers. 
... 

Already backported to 3.13 since 3.13.0-20. 
Will investigate why we are suffering from the same problem for their kernel (3.13.0-43).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1447763

Title:
  HP Proliant Servers suffer from cpufreq initialization failure for
  some cpu cores

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It was brought to my attention the following:

  Ubuntu Trusty Kernel 3.13 is suffering from cpufreq initialization
  failure for some cpu cores on Proliant Servers.

  /sys/devices/system/cpu# for cpu in `ls -1d cpu[0-9]*`; do ls -ld $cpu/cpufreq; done 
  drwxr-xr-x 2 root root 0 Apr 2 16:15 cpu0/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu1/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu10/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu11/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu12/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu13/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu14/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu15/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu16/cpufreq 
  ls: cannot access cpu17/cpufreq: No such file or directory 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu18/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu19/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu2/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu20/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu21/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu22/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu23/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu24/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu25/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu26/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu27/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu28/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu29/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu3/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu30/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu31/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu4/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu5/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu6/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu7/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu8/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu9/cpufreq 

  With the following message:

  [ 2.465616] pcc-cpufreq: (v1.10.00) driver loaded with frequency limits: 1200 MHz, 2200 MHz 
  [ 2.474810] cpufreq: __cpufreq_add_dev: ->get() failed 

  Disabling Collaborative Power Control into firmware setup mitigates
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447763/+subscriptions