All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:41:06 +0000	[thread overview]
Message-ID: <bug-219431-137361-46DCrSy4TL@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 #5 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
It looks like this message is being emitted specifically from the calls in
amd_set_max_freq_ratio().

You system is a shared memory design not a MSR design.
"[  +0.000016] amd_pstate: AMD CPPC shared memory based functionality is
supported"

This looks like the calltrace:
amd_set_max_freq_ratio
->amd_get_boost_ratio_numerator
->->amd_detect_prefcore
->->->amd_get_highest_perf
->->->->cppc_get_highest_perf
->->->->->cppc_get_perf

The first error you see is "No CPC descriptor for CPU:1" which comes from
cppc_get_perf().

Can you please share your acpidump?  It sure seems like a BIOS bug to me.

-- 
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:[~2024-10-28 15:41 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 [this message]
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-46DCrSy4TL@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.