CachyOS/linux-cachyos

[AMD] PState Zen 2 not working

Closed this issue · 8 comments

Hi @superm1

as discussed in the E-Mail, ill just create a issue here to have better tracking.

Current State:

  1. 6.9 Kernel without amd-pstate patches --> working

  2. 6.9 Kernel with latest amd-pstate cpb boost & amd-pstate fixes and enhancements v12 --> not working https://paste.cachyos.org/p/b6dddae --> Patches: https://github.com/CachyOS/linux/commits/6.9/amd-pstate/

  3. Kernel with v10 amd-pstate fixes and enhancements --> not working (due wrongly reported freq issue) --> https://paste.cachyos.org/p/c480247 , this was also reported here: #236 and fixed with newer versions

We will attach the dynamic debug as soon as possible from a clean v12 build and from a non patched kernel.

@superm1

Sorry for the noise. It seems its not this patchset, which is affected.
the latest cpb-boost and amd-pstate-fixes v12 are fine.

We have additional commits in, which where picked from the "linux-pf" kernel (https://codeberg.org/pf-kernel/linux)

Following commits:
CachyOS/linux@de0fc04 - (probably not the breaker)
CachyOS/linux@829b315 - (probably not the breaker)
CachyOS/linux@b870a22 - (probably the breaker)
CachyOS/linux@8fd0d0a - (probably the breaker)

So, its just questionable, why this issue was not visible on Zen3 or Zen4.

CachyOS/linux@de0fc04 - (probably not the breaker)
CachyOS/linux@829b315 - (probably not the breaker)

Agree; probably not the cause, those are headed to 6.10 as well.

CachyOS/linux@b870a22 - (probably the breaker)

This was never merged and so it's not getting good testing coverage, I think you should drop it.
https://lore.kernel.org/linux-pm/20240227071133.3405003-1-li.meng@amd.com/

CachyOS/linux@8fd0d0a - (probably the breaker)

This is the wrong fix for this problem, please drop it. The correct fix should be submitted soon ™.

This is the wrong fix for this problem, please drop it. The correct fix should be submitted soon ™.

This would be very important to some of our users, since several people reported issues with it and this was also the reason, why we have pulled it in the past.

This was never merged and so it's not getting good testing coverage, I think you should drop it.
Thanks, we will drop it and keep the patches from amd-pstate (next).

Sorry for the noise again and thanks for helping.

FYI @pfactum ,

You should consider to drop the above 2 patches from your tree, it breaks amd-pstate on some CPUs.

These:

$ git log --oneline amd-pstate-6.8~2..amd-pstate-6.8
2031648ce0d3f Revert "amd_pstate: fix erroneous highest_perf value on some CPUs"
8deec09d7de89 Revert "cpufreq/amd-pstate: fix setting policy current frequency value"

?

These:

$ git log --oneline amd-pstate-6.8~2..amd-pstate-6.8
2031648ce0d3f Revert "amd_pstate: fix erroneous highest_perf value on some CPUs"
8deec09d7de89 Revert "cpufreq/amd-pstate: fix setting policy current frequency value"

?

Yes, these reverts you should apply to your branch.

Done then, thanks.