CPU: AḾD Ryzen 9 7940 HS
Amd_pstate set to passive mode
Kernel: cachyos-znver4 6.11.0-5
Though min/max Cpu Frequency is set to 2500 Mhz some cores run about 400 Mhz higher.
Frequency is set correctly when using Kernel 6.10 or when using Kernel 6.11 on my Manjaro System.
So this seems to be an CachyOS Kernel issue.
Not a great issue to fill an extra bug report.
Was just wondering why its working with Kernel 6.11 in Manjaro and with 6.10 in Cachy.
Meanwhile I set amd_pstate to active. Thought I could only set a fixed Cpu freq when I set amd_pstate to passive.
Why you dont use the disable boost function, e.g via power-profiles-daemon put to powersave and then it will disable the boost. That will help you more then using the passive driver and switching their manually things around.
We had a lot of discussion, testing together with AMD.
Question is not about boost. It’s why Cachy Kernel 6.11 does not keep a fixed set CPU Freq, while Cachy Kernel 6.10 does, and while Manjaro Kernel 6.11 does.
At least on my system.
The issue is the same with boost disabled, and with amd_pstate set to active.
Can you run the command with passive driver and you setting the min-max freqs? From this log, it’s using the active driver and there are no apparent log messages that help figure out what the issue is.
Tested with linux 6.11.arch1-1.
Working, no such issue.
On my Manjaro System I tested with Kernel 6.12. rc0.
The issue is the same.
So it’s definetly the amd_pstate patch from 6.12 causing this issue on my CPU.
I don’t know if I’ve asked before but can you please share log sudo cachyos-bugreport.sh after you tried to reproduce the bug. We can forward to our contact at AMD after.
Do you know how to bisect?
We have sent to AMD the report, but they dont see what the issue would be. So, we need to go through every commit and compile a kernel.
You would need to revert every commit per build. If you need help, let us know.
Oh, sorry, that’s too complicated and too much action for the issue for me.
I guess maybe other users will come up with the issue and it gets fixed until final 6.12 release.
For now I use the 6.11 zen-kernel.