The cpufreq indicator doesn't work with intel_pstate

Bug #1376838 reported by Marcus Sundman on 2014-10-02
This bug affects 7 people
Affects Status Importance Assigned to Milestone
indicator-cpufreq (Ubuntu)

Bug Description

After upgrading from 3.13 (trusty) to 3.16 (utopic) most cpufreq stuff have vanished.
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
performance powersave
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
$ sudo cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

I suppose this is because of the transition to intel_pstate. However, the frequencies seem to be wrong. I'm pretty sure the max freq used to be less than 2000000, and when entering performance mode the cpu ran at something like 1,8 GHz.

However, both /proc/cpuinfo and /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq report something (wrong as it seems), but the cpufreq indicator always shows the cpu to run at lowest possible speed.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-cpufreq 0.2.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Oct 2 19:47:58 2014
InstallationDate: Installed on 2013-11-27 (309 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
SourcePackage: indicator-cpufreq
UpgradeStatus: No upgrade log present (probably fresh install)

Marcus Sundman (sundman) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-cpufreq (Ubuntu):
status: New → Confirmed
Changed in indicator-cpufreq (Ubuntu):
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers