[Bug 1234619] New: CPU reporting and using incorrect max freq
https://bugzilla.suse.com/show_bug.cgi?id=1234619 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: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234619 https://bugzilla.suse.com/show_bug.cgi?id=1234619#c2 --- Comment #2 from E Z <ez2blost@yahoo.com> --- Created attachment 879395 --> https://bugzilla.suse.com/attachment.cgi?id=879395&action=edit top lines from dmesg -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234619 https://bugzilla.suse.com/show_bug.cgi?id=1234619#c3 --- Comment #3 from E Z <ez2blost@yahoo.com> --- Created attachment 879396 --> https://bugzilla.suse.com/attachment.cgi?id=879396&action=edit output from hwinfo --cpu -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234619 https://bugzilla.suse.com/show_bug.cgi?id=1234619#c4 --- Comment #4 from E Z <ez2blost@yahoo.com> --- I have attached some of the output from hwinfo and the initial dmesg - I can send more information if you let me know what specifically you are after. Note that the problem does not appear with kernels from other distributions -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234619 E Z <ez2blost@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ez2blost@yahoo.co | |m) | -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com