[Bug 215938] New: amd-pstate ignoring scaling_max_freq after waking from suspend

[bugzilla-daemon@kernel.org]

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

            Bug ID: 215938
           Summary: amd-pstate ignoring scaling_max_freq after waking from
                    suspend
           Product: Power Management
           Version: 2.5
    Kernel Version: 5.17.5
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: alexmaras@gmail.com
        Regression: No

Using the amd-pstate driver for cpu scaling, I'm only able to enforce a maximum
clock speed when my laptop has not slept. I do the following:

echo 'ondemand' | sudo tee
/sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

echo '1400000' | sudo tee
/sys/devices/system/cpu/cpufreq/policy*/scaling_max_freq

cat /sys/devices/system/cpu/cpufreq/policy*/scaling_cur_freq

At this point, all reported frequencies for all cores are below 1.4ghz. If I
then suspend the laptop, then wake it up, then checking the core frequencies
again will show that it is behaving as if the ondemand governor was not set.
This behavior will persist until a reboot, even if the governor is switched to
another mode and then back, or if the scaling_max_freq value is changed. All
settings will be ignored. 

I have replicated this behavior on another identical model of laptop (Lenovo
IdeaPad 5 14ARE05), 

cpupower frequency-info also reports that the current CPU frequency is set to
1.4GHZ and that the governor is set to ondemand.

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

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