Closed ghost closed 6 years ago
Indeed, I've got the same issue with Linux 4.14.12-3-ck-sandybridge. This is related to kernel, due to it is working with LTS kernel (Linux 4.9).
Actually, the frequency is provided by libcpuid cpu_clock()
(see here), and this function calls cpu_clock_by_os()
: on Linux, it reads the /proc/cpuinfo
file.
Some kernel patches related to this issue: v4.13-rc1: torvalds/linux@51204e0639c49ada02fd823782ad673b6326d748 v4.14-rc8: torvalds/linux@890da9cf098364b11a7f7f5c22fa652531624d03 v4.15-rc1: torvalds/linux@7d5905dc14a87805a59f3c5bf70173aac2bb18f8 The last patch will be backported in Linux 4.14.13.
Just wait and see...
Workaround in e6b199a: you can set CPUX_FORCE_FREQ_FALLBACK=1
environment variable to use /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq
.
Just updated to Linux 4.14.13: problem fixed. 😉
CPU frequency is locked at 4000MHz in CPU-X. I believe this is due to this: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1727158
I suggest grabbing the CPU frequency from _*/sys/devices/system/cpu/cpu/cpufreq/scaling_curfreq** instead.
lscpu shows the wrong frequency: CPU MHz: 4000.000 CPU max MHz: 4500.0000 CPU min MHz: 800.0000
While scaling_cur_freq shows the right frequency: cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq 800024 800029 800118 800211 800189 800118 800007 800046
Operating system name and version: Arch (4.14.12-1-ARCH)
CPU-X installation type: e.g. package/portable version/built from source Package
cpu-x --issue-fmt
command output (as root):