[Bug 217618] New: Changing maximum frequency and boost state does not work with amd-pstate in passive mode plus the schedutil governor

[bugzilla-daemon@kernel.org]

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

            Bug ID: 217618
           Summary: Changing maximum frequency and boost state does not
                    work with amd-pstate in passive mode plus the
                    schedutil governor
           Product: Power Management
           Version: 2.5
    Kernel Version: 6.4.0
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: putr4.s@gmail.com
                CC: ray.huang@amd.com
        Regression: No

I have a HP Omen 16-n0000 laptop with a Ryzen 7 6800H, and if I have amd-pstate
set to passive mode (either by booting with `amd_pstate=passive` kernel cmdline
or by running `echo "passive" | sudo tee
/sys/devices/system/cpu/amd_pstate/status` on runtime) and the governor left to
the default schedutil then changing the maximum allowed frequency (via `sudo
cpupower frequency-set -g 3200MHz` for example) does nothing, the CPU
frequencies (and temperatures along with it) still goes up high. Disabling
boost via `echo 0 | sudo tee /sys/devices/system/cpu/cpufreq/boost` also does
not work with the schedutil governor.

However, if I switch to the ondemand governor then both the boost and maximum
frequency settings work as expected.

The distro I am using is Arch Linux, with kernel 6.4.0 from the testing repo,
although this issue has been present since at least kernel 6.2.x when I first
got this laptop. I can recompile the kernel myself to test patches if there are
any.

Also, for what it's worth amd-pstate in guided mode also ignores both the
maximum frequency and boost knobs, but it does that with both the schedutil and
ondemand governors so I guess that's expected(?).

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

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