From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219431] [6.12] amd-pstate / Ryzen 5xxx (Zen 3, Vermeer): Could not retrieve highest performance (-19)
Date: Mon, 28 Oct 2024 17:19:22 +0000 [thread overview]
Message-ID: <bug-219431-137361-vCoUg7BPmP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219431-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219431
--- Comment #9 from Ivan Shapovalov (intelfx@intelfx.name) ---
Created attachment 307082
--> https://bugzilla.kernel.org/attachment.cgi?id=307082&action=edit
`acpidump -b`, 5950X, ASRock X570M-Pro4, BIOS P3.60
Attaching `acpidump -b` output for my system, which is a 5950X on an ASRock
X570M-Pro4 motherboard. The BIOS is also quite old here.
I'm not observing any specific functional limitations *that I can track to this
issue*.
However, there is this thing that basically nothing I do to the EPP knobs or
the cpufreq governor has any effect on the CPU frequency management behavior.
Also, sometimes under ~75% load (cgroup limited) some cores get stuck at <4GHz
while others boost to expected ~4.7-ish, but I've no idea how to reproduce this
one reliably.
--
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:[~2024-10-28 17:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 18:43 [Bug 219431] New: [6.12] amd-pstate / Ryzen 5xxx (Zen 3, Vermeer): Could not retrieve highest performance (-19) bugzilla-daemon
2024-10-27 18:43 ` [Bug 219431] " 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 [this message]
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-vCoUg7BPmP@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.