From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 221795] amd-pstate: max_perf stuck at nominal_perf after boot on Ryzen AI 9 HX 370
Date: Mon, 27 Jul 2026 15:00:42 +0000 [thread overview]
Message-ID: <bug-221795-137361-sYSG6dXV5y@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221795-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221795
Mario Limonciello (AMD) (mario.limonciello@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #2 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
CachyOS carries patches (mostly backports). So, they could have backported
from a bad place potentially.
Can you please reproduce on 7.2-rc5?
--
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-07-27 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 11:34 [Bug 221795] New: amd-pstate: max_perf stuck at nominal_perf after boot on Ryzen AI 9 HX 370 bugzilla-daemon
2026-07-26 11:37 ` [Bug 221795] " bugzilla-daemon
2026-07-27 15:00 ` bugzilla-daemon [this message]
2026-08-03 8:49 ` 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-221795-137361-sYSG6dXV5y@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.