From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219431] New: [6.12] amd-pstate / Ryzen 5xxx (Zen 3, Vermeer): Could not retrieve highest performance (-19)
Date: Sun, 27 Oct 2024 18:43:10 +0000 [thread overview]
Message-ID: <bug-219431-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219431
Bug ID: 219431
Summary: [6.12] amd-pstate / Ryzen 5xxx (Zen 3, Vermeer): Could
not retrieve highest performance (-19)
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: intelfx@intelfx.name
Regression: No
Created attachment 307075
--> https://bugzilla.kernel.org/attachment.cgi?id=307075&action=edit
dmesg
With https://lore.kernel.org/lkml/20240905163007.1350840-1-superm1@kernel.org/
applied (or on 6.12-rc3+), booting on a Ryzen 9 5950X CPU (Zen 3, Vermeer)
yields the newly-promoted warning:
```
[ 0.623843] Could not retrieve highest performance (-19)
```
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-10-27 18:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 18:43 bugzilla-daemon [this message]
2024-10-27 18:43 ` [Bug 219431] [6.12] amd-pstate / Ryzen 5xxx (Zen 3, Vermeer): Could not retrieve highest performance (-19) bugzilla-daemon
2024-10-27 18:44 ` bugzilla-daemon
2024-10-27 21:50 ` bugzilla-daemon
2024-10-28 14:20 ` bugzilla-daemon
2024-10-28 15:41 ` bugzilla-daemon
2024-10-28 15:56 ` bugzilla-daemon
2024-10-28 15:57 ` bugzilla-daemon
2024-10-28 16:32 ` bugzilla-daemon
2024-10-28 17:19 ` bugzilla-daemon
2024-10-28 19:22 ` bugzilla-daemon
2024-10-28 19:39 ` bugzilla-daemon
2024-10-28 20:31 ` bugzilla-daemon
2024-10-28 21:22 ` bugzilla-daemon
2024-10-29 1:50 ` bugzilla-daemon
2024-10-29 7:35 ` bugzilla-daemon
2024-10-29 9:00 ` bugzilla-daemon
2024-10-29 13:59 ` bugzilla-daemon
2024-10-29 14:10 ` bugzilla-daemon
2024-10-29 17:53 ` 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-219431-137361@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;
as well as URLs for NNTP newsgroup(s).