From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 220715] [REGRESSION] AMD P-State fails with "_CPC object is not present" on AMD Zen 4 between 6.10 and 6.11
Date: Tue, 04 Nov 2025 06:46:49 +0000 [thread overview]
Message-ID: <bug-220715-137361-twwOxYHByn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220715-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220715
Gautham R. Shenoy (gautham.shenoy@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gautham.shenoy@gmail.com
--- Comment #16 from Gautham R. Shenoy (gautham.shenoy@gmail.com) ---
I think Mario is on the right track in that the issue is because of failure to
detect something on a CPU that is present but not online.
My hunch is that it is in amd_detect_prefcore() which checks if the number of
distinct highest_perf values in the system is greater than 1, but uses
for_each_present_cpu() which fails when the system is booted with
`nosmt=force`. The commit that introduces this code is 279f838a61f9 ("x86/amd:
Detect preferred cores in amd_get_boost_ratio_numerator()") which got merged in
the upstream kernel 6.12.
@Chris, if you don't mind, can you please try the following patch:
diff --git a/arch/x86/kernel/acpi/cppc.c b/arch/x86/kernel/acpi/cppc.c
index 7047124490f6..d7c8ef1e354d 100644
--- a/arch/x86/kernel/acpi/cppc.c
+++ b/arch/x86/kernel/acpi/cppc.c
@@ -196,7 +196,7 @@ int amd_detect_prefcore(bool *detected)
break;
}
- for_each_present_cpu(cpu) {
+ for_each_online_cpu(cpu) {
u32 tmp;
int ret;
--
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:[~2025-11-04 6:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 23:37 [Bug 220715] New: [REGRESSION] AMD P-State fails with "_CPC object is not present" on AMD Zen 4 between 6.10 and 6.11 bugzilla-daemon
2025-10-31 3:55 ` [Bug 220715] " bugzilla-daemon
2025-10-31 4:01 ` bugzilla-daemon
2025-11-01 20:19 ` bugzilla-daemon
2025-11-01 20:20 ` bugzilla-daemon
2025-11-01 20:22 ` bugzilla-daemon
2025-11-01 20:24 ` bugzilla-daemon
2025-11-02 5:22 ` bugzilla-daemon
2025-11-02 5:27 ` bugzilla-daemon
2025-11-02 6:55 ` bugzilla-daemon
2025-11-02 14:53 ` bugzilla-daemon
2025-11-02 15:06 ` bugzilla-daemon
2025-11-02 18:53 ` bugzilla-daemon
2025-11-03 19:25 ` bugzilla-daemon
2025-11-04 2:53 ` bugzilla-daemon
2025-11-04 2:55 ` bugzilla-daemon
2025-11-04 2:59 ` bugzilla-daemon
2025-11-04 6:46 ` bugzilla-daemon [this message]
2025-11-04 8:19 ` bugzilla-daemon
2025-11-04 8:20 ` bugzilla-daemon
2025-11-04 13:56 ` bugzilla-daemon
2025-11-04 21:06 ` bugzilla-daemon
2025-11-04 21:09 ` bugzilla-daemon
2025-11-05 15:39 ` bugzilla-daemon
2025-11-05 19:01 ` bugzilla-daemon
2025-11-05 21:20 ` 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-220715-137361-twwOxYHByn@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).