[Bug 221505] New: REGRESSION][amd_pstate] "EPP cannot be set under performance policy" (EBUSY) when switching to performance profile via PPD on 7.1

[bugzilla-daemon@kernel.org]

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

            Bug ID: 221505
           Summary: REGRESSION][amd_pstate] "EPP cannot be set under
                    performance policy" (EBUSY) when switching to
                    performance profile via PPD on 7.1
           Product: Power Management
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: sergeyluashkov@gmail.com
        Regression: No

Created attachment 310089
  --> https://bugzilla.kernel.org/attachment.cgi?id=310089&action=edit
dmesg

Hardware: ASUS TUF Gaming A14 (2026) FA401EA
CPU: AMD Ryzen AI Max+ 932 (Strix Halo platform)
Kernel: 7.1.0-mainline (including patches for Bugzilla #221310)
Power Daemon: power-profiles-daemon 0.30

Description:
On kernel 7.1, power-profiles-daemon fails to activate the "performance"
profile. The D-Bus error returned is Code 26 (Device or resource busy).

After enabling dynamic debug for the amd_pstate module (echo 'module amd_pstate
+p' > /sys/kernel/debug/dynamic_debug/control), I captured the following reason
for the failure in dmesg:

[  299.585428] amd_pstate: EPP cannot be set under performance policy

Steps to Reproduce:

Use a system with amd_pstate in active mode on kernel 7.1.

Attempt to switch profile: powerprofilesctl set performance.

Failed to communicate with power-profiles-daemon: g-io-error-quark:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code26:
Failed to activate CPU driver 'amd_pstate': Error writing
'/sys/devices/system/cpu/cpufreq/policy11/energy_performance_preference':
Device or resource busy (26)


The command fails, and dmesg logs: amd_pstate: EPP cannot be set under
performance policy.

Expected Result:
The driver should allow setting the EPP value even if the policy is set to
performance, or handle the transition gracefully without returning EBUSY to
user-space daemons.

Additional Context:
This issue was observed on the new Strix Halo (Ryzen AI Max+) platform. The
conflict between PPD's profile orchestration and the driver's internal state
checks makes the "Performance" profile unusable via standard desktop tools
(KDE/GNOME power settings).

I can build and test custom patches on this hardware

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

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