From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 221505] REGRESSION][amd_pstate] "EPP cannot be set under performance policy" (EBUSY) when switching to performance profile via PPD on 7.1
Date: Wed, 13 May 2026 18:41:35 +0000 [thread overview]
Message-ID: <bug-221505-137361-vK2yX730fY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221505-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221505
--- Comment #8 from Sergey (sergeyluashkov@gmail.com) ---
(In reply to Mario Limonciello (AMD) from comment #7)
> Can you please pair that patch with the patches on this branch?
> https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git/log/?h=amd-
> pstate-fixes
>
> There are multiple bugs at play here.
I’ve tested the kernel from your amd-pstate-fixes branch (commit f9f16835d4dc),
but unfortunately, the issues persist, and I’ve discovered a new conflict with
the ASUS platform driver.
Current observations:
With amd_dynamic_epp=disable (or no parameter):
The behavior remains identical to the initial report. powerprofilesctl still
fails with the error described in the original report (Description).
With amd_dynamic_epp=enable:
It breaks the integration with asus-nb-wmi.
Specifically, the /sys/devices/platform/asus-nb-wmi/throttle_thermal_policy
(which controls ASUS thermal profiles) stops switching to value 2
(Silent/Power-save mode).
When I set "Power-saver" via PPD, it only toggles between 0 and 1.
The CPU TDP is not limited to its expected ~55W threshold unless I manually
write 2 to the throttle_thermal_policy file.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2026-05-13 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 17:45 [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
2026-05-11 20:15 ` [Bug 221505] " bugzilla-daemon
2026-05-13 6:17 ` bugzilla-daemon
2026-05-13 11:03 ` bugzilla-daemon
2026-05-13 15:39 ` bugzilla-daemon
2026-05-13 15:43 ` bugzilla-daemon
2026-05-13 16:57 ` bugzilla-daemon
2026-05-13 17:12 ` bugzilla-daemon
2026-05-13 18:41 ` bugzilla-daemon [this message]
2026-05-13 18:44 ` bugzilla-daemon
2026-05-13 19:14 ` bugzilla-daemon
2026-05-14 7:30 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-221505-137361-vK2yX730fY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox