public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
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 21:06:40 +0000	[thread overview]
Message-ID: <bug-220715-137361-LId4ImNRfc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220715-137361@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220715

--- Comment #20 from Chris Harris (chris.harris79@gmail.com) ---
SUCCESS on kernel v6.17 with Gautham's patch combined with Mario's most recent
patch:

1. arch/x86/kernel/acpi/cppc.c (amd_detect_prefcore):
   for_each_present_cpu → for_each_online_cpu

2. drivers/acpi/cppc_acpi.c (acpi_cpc_valid):
   for_each_present_cpu → for_each_online_cpu

- Driver: amd-pstate (working correctly)
- Message: "AMD CPPC MSR based functionality is supported"
- nosmt=force active, SMT disabled (1 thread/core)

Full dmesg attached: dmesg-6.17-SUCCESS-online-cpu.txt

I imagine this fix will be included in the kernel in the future (that would be
very nice).  Please let me know if you'd like anything further from my side.  

Thanks again for all your efforts!

-- 
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:[~2025-11-04 21:06 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
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 [this message]
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-LId4ImNRfc@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