Linux Power Management development
 help / color / mirror / Atom feed
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: Fri, 29 May 2026 11:31:47 +0000	[thread overview]
Message-ID: <bug-221505-137361-56oIsgxsi5@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 #25 from Sergey (sergeyluashkov@gmail.com) ---
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from
comment #24)
> (In reply to Mario Limonciello (AMD) from comment #22)
> > If I understood the root cause I would have a better answer for you.
> 
> One more question then, if I may: does a bisection make sense, or are things
> just to messy/complicated due to the other fixes in this area (or if, how to
> best approach one given those fixes? apply them at each step without
> committing them?)?
> 
> Side note: Alex, Sergey, you both seems to have Asus laptops, wondering if
> that's part of the problem here.

I can't say for sure, but I can test the 7.1-rc5 kernel on a mini PC with an
AMD Ryzen 9 7945HX this weekend and report back here if there are any issues.

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

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

  parent reply	other threads:[~2026-05-29 11:31 UTC|newest]

Thread overview: 27+ 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
2026-05-13 18:44 ` bugzilla-daemon
2026-05-13 19:14 ` bugzilla-daemon
2026-05-14  7:30 ` bugzilla-daemon
2026-05-26  6:40 ` bugzilla-daemon
2026-05-26  9:20 ` bugzilla-daemon
2026-05-26  9:22 ` bugzilla-daemon
2026-05-26 11:23 ` bugzilla-daemon
2026-05-27 17:41 ` bugzilla-daemon
2026-05-29  9:41 ` bugzilla-daemon
2026-05-29  9:43 ` bugzilla-daemon
2026-05-29  9:51 ` bugzilla-daemon
2026-05-29  9:56 ` bugzilla-daemon
2026-05-29 10:00 ` bugzilla-daemon
2026-05-29 10:02 ` bugzilla-daemon
2026-05-29 10:10 ` bugzilla-daemon
2026-05-29 11:18 ` bugzilla-daemon
2026-05-29 11:31 ` bugzilla-daemon [this message]
2026-05-29 11:50 ` 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-56oIsgxsi5@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