kernel-packages team mailing list archive

[Paolo Pisati <1457781@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

While cpufreq support on armhf is available for a while, if support is
compiled as a kernel module, the corresponding module doesn't autoload
by default, and thus frequency scaling is not active upon boot until a
user manually load it (or until /etc/modules is modified to forcibly
load it).

While in Trusty cpufreq was built-in on armhf, starting with Utopic we
made support available as a kernel module, making people think that
cpufreq was either broken or missing in their new kernels.

To fix it, revert back that decision and make cpufreq compiled-in again
on armhf - it affects Utopic and Vivid kernels.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: patch

-- 
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/1457781

Title:
  armhf: cpufreq doesn't autoload by default

Status in linux package in Ubuntu:
  New

Bug description:
  While cpufreq support on armhf is available for a while, if support is
  compiled as a kernel module, the corresponding module doesn't autoload
  by default, and thus frequency scaling is not active upon boot until a
  user manually load it (or until /etc/modules is modified to forcibly
  load it).

  While in Trusty cpufreq was built-in on armhf, starting with Utopic we
  made support available as a kernel module, making people think that
  cpufreq was either broken or missing in their new kernels.

  To fix it, revert back that decision and make cpufreq compiled-in
  again on armhf - it affects Utopic and Vivid kernels.

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