[Bug 215800] amd-pstate does not allow to set arbitrary maximum CPU frequency above 2200MHz for a desktop Zen 3 CPU

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=215800

--- Comment #22 from perry_yuan@outlook.com ---
(In reply to Artem S. Tashkinov from comment #21)
> /sys/devices/system/cpu/cpufreq/policy0
> 
> amd_pstate_highest_perf:166
> scaling_min_freq:550000
> scaling_available_governors:conservative ondemand userspace powersave
> performance schedutil 
> scaling_governor:ondemand
> cpuinfo_max_freq:4929000
> amd_pstate_lowest_nonlinear_freq:1752000
> amd_pstate_max_freq:4929000
> related_cpus:0
> scaling_cur_freq:1247422
> scaling_setspeed:<unsupported>
> affected_cpus:0
> scaling_max_freq:1600000
> cpuinfo_transition_latency:131072
> scaling_driver:amd-pstate
> cpuinfo_min_freq:550000
> 
> Why do I have two wildly different amd_pstate_highest_perf=166 and
> highest_perf=186?
> 
> What's the relationship between the two?
> 
> Anyways, the issue remains. As far as I can see
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/
> drivers/cpufreq/amd-pstate.c has seen near zero activity for the past three
> months.
 modprobe amd-pstate replace=1(In reply to Artem S. Tashkinov from comment #19)
> All the same with 5.18.3.
> 
> Steps to reproduce:
> 
> echo 3000000 | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq
> 
> Now all the CPU cores are stuck below 2.2GHz.
> 
> This is after `modprobe amd-pstate replace=1`
> 
> I really don't understand what else I can do. This is reproducible with a
> single command on my Ryzen 7 5800X CPU.

Please drop the replace parameter when loading driver, that patch is not merged
by upstream yet.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.