Bug ID 1234619
Summary CPU reporting and using incorrect max freq
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.6
Hardware x86-64
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-bugs@opensuse.org
Reporter ez2blost@yahoo.com
QA Contact qa-bugs@suse.de
Target Milestone ---
Found By ---
Blocker ---

On an Intel i9-13900HX, /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq
reports the same frequency as base_frequency.

E.g.,
cat /sys/devices/system/cpu/cpu0/cpufreq/{base_frequency,cpuinfo_max_freq}
2200000
2200000

By default the maximum scaling frequency for performance is set to the
cpuinfo_max_freq
cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
2200000

However the maximum frequency for cpu1 is 5400000 as can be seen if a higher
valuer is written to scaling_max_freq:


echo 10000000 >| /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq ; cat
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
5400000

By default the cpu frequency never exceeds 2.2Ghz resulting in poor
performance.

A workaround is to set the maximum scaling frequency in the TLP configuration
file (if tlp is used), e.g.

Echo "CPU_SCALING_MAX_FREQ_ON_AC=5400000" >> /etc/tlp.d/50.local.conf

This is partial fix because other software, such as NVIDIA power management
features, can reset the scaling_max_frequency to cpuinfo_max_frequency, and
cannot be enabled easily without a performance hit.


You are receiving this mail because: