https://bugs.kde.org/show_bug.cgi?id=382561
Fabian Vogt <fab...@ritter-vogt.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |https://commits.kde.org/ksy
| |sguard/cbaaf5f4ff54e20cb8ec
| |782737e04d540085e6af
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Fabian Vogt <fab...@ritter-vogt.de> ---
Git commit cbaaf5f4ff54e20cb8ec782737e04d540085e6af by Fabian Vogt.
Committed on 06/10/2017 at 12:47.
Pushed by fvogt into branch 'Plasma/5.8'.
Try to read CPU clock from cpufreq/scaling_cur_freq instead of /proc/cpuinfo
Summary:
>From kernel 4.13 on, /proc/cpuinfo always reports the static normative
CPU clock and not the current one. So try to read the frequency from
cpufreq and only fall back to cpuinfo it that fails.
Test Plan:
Started ksysguard, frequency now changes. If the file is not
readable, the frequency is read from cpuinfo as expected.
Reviewers: #plasma, sebas
Reviewed By: #plasma, sebas
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D8153
M +21 -1 ksysguardd/Linux/cpuinfo.c
https://commits.kde.org/ksysguard/cbaaf5f4ff54e20cb8ec782737e04d540085e6af
--
You are receiving this mail because:
You are watching all bug changes.
