linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bug 220715] New: [REGRESSION] AMD P-State fails with "_CPC object is not present" on AMD Zen 4 between 6.10 and 6.11
@ 2025-10-28 23:37 bugzilla-daemon
  2025-10-31  3:55 ` [Bug 220715] " bugzilla-daemon
                   ` (24 more replies)
  0 siblings, 25 replies; 26+ messages in thread
From: bugzilla-daemon @ 2025-10-28 23:37 UTC (permalink / raw)
  To: linux-pm

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

            Bug ID: 220715
           Summary: [REGRESSION] AMD P-State fails with "_CPC object is
                    not present" on AMD Zen 4 between 6.10 and 6.11
           Product: Power Management
           Version: 2.5
    Kernel Version: 6.17.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: chris.harris79@gmail.com
                CC: mario.limonciello@amd.com
        Regression: Yes

Created attachment 308864
  --> https://bugzilla.kernel.org/attachment.cgi?id=308864&action=edit
acpidump, dmesg with current kernel (6.17), dmesg with a last working kernel

This bug was initially reported to linux-pm@vger.kernel.org and I was asked
by Mario Limonciello to open this bugzilla and provide additional debug data.

SUMMARY
-------
The AMD P-State driver fails to initialize on AMD Zen 4 processors starting
with kernel 6.11.0, returning "_CPC object is not present in SBIOS or ACPI
disabled"
error. The same hardware works correctly with kernel 6.10.0 and earlier.

The regression was introduced between 6.10.0 and 6.11.0.

REGRESSION INFORMATION
----------------------
- Regression: Yes
- Last working kernel: 6.10.14
- First broken kernel: 6.11.0
- Still broken in: 6.17.5, 6.18.0-rc3

ATTACHMENTS PROVIDED
--------------------
1. acpidump.txt - ACPI table dump (same across all kernels)
2. dmesg-6.10.14-061014-generic.txt - dmesg from WORKING kernel
3. dmesg-6.17.5-061705-generic.txt - dmesg from BROKEN kernel
4. system-info-6.10.14.txt - Additional system info from working kernel
5. system-info-6.17.5.txt - Additional system info from broken kernel
tarball: amd-pstate-debug-all.tar.gz

HARDWARE TESTED
---------------
Reproduced on multiple AMD Zen 4 systems:

System 1 (primary testing - multiple identical units tested):
- CPU: AMD EPYC 4484PX 12-Core Processor
- Motherboard: Supermicro H13SRE-F (Version 1.01)
- System: Supermicro AS-3015MR-H10TNR
- BIOS: American Megatrends International, LLC. v2.4 (04/29/2025, Revision
5.35)

System 2 (additional confirmation):
- CPU: AMD Ryzen 9 7950X 16-Core Processor
- Motherboard: Supermicro H13SRD-F (Version 1.00)
- System: Supermicro AS-3015MR-H8TNR
- BIOS: American Megatrends International, LLC. v1.2a (07/10/2024, Revision
5.32)

Both systems exhibit identical behavior with the regression.
CPPC confirmed enabled in BIOS by vendor.

Note: This issue likely affects all AMD Zen 4 processors and possibly other AMD
generations with CPPC support.

REGRESSION TEST RESULTS
-----------------------
Working (amd-pstate loads successfully):
- 6.8.0-84-generic (Ubuntu 24.04)
- 6.8.0-86-generic (Ubuntu 24.04)
- 6.9.0-060900-generic (Ubuntu mainline)
- 6.10.0-061000-generic (Ubuntu mainline)
- 6.10.14-061014-generic (Ubuntu mainline) <- LAST WORKING (latest 6.10.x)

Broken (falls back to acpi-cpufreq with _CPC error):
- 6.11.0-061100-generic (Ubuntu mainline) <- FIRST BROKEN
- 6.12.0-061200-generic (Ubuntu mainline)
- 6.13.0-061300-generic (Ubuntu mainline)
- 6.14.0-061400-generic (Ubuntu mainline)
- 6.16.7-061607-generic (Ubuntu mainline)
- 6.17.1-061701-generic (Ubuntu mainline)
- 6.17.5-061705-generic (Ubuntu mainline)
- 6.18.0-061800rc3-generic (Ubuntu mainline RC)
- 6.17.1-1-cachyos-server-lto (Arch Linux)

ERROR MESSAGE
-------------
[    4.508125] amd_pstate: the _CPC object is not present in SBIOS or ACPI
disabled

STEPS TO REPRODUCE
------------------
1. Boot with kernel parameter: amd_pstate=passive
2. Check driver: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
   Expected: amd-pstate
   Actual: acpi-cpufreq
3. Check dmesg: dmesg | grep "_CPC"
   Shows: "the _CPC object is not present in SBIOS or ACPI disabled"

KERNEL CONFIGURATION
--------------------
All tested kernels have identical AMD P-State configuration:
CONFIG_ACPI_CPPC_LIB=y
CONFIG_X86_AMD_PSTATE=y
CONFIG_X86_AMD_PSTATE_DEFAULT_MODE=3
CONFIG_X86_AMD_PSTATE_UT=m

TESTING ENVIRONMENT
-------------------
- Tested with vanilla kernels from Ubuntu mainline PPA
- No additional modules or patches
- Kernel not tainted
- Reproduced on both Ubuntu 24.04 and Arch Linux distributions

IMPACT
------
This regression prevents affected AMD systems from using the optimized AMD
P-State
driver, forcing fallback to generic acpi-cpufreq with approximately 5-10%
performance loss for server and desktop workloads. Confirmed on both AMD EPYC
4484PX
and Ryzen 9 7950X (Zen 4), likely affecting all Zen 4 processors and possibly
other
AMD generations that support CPPC/ACPI P-States.

BISECTION RESULTS
-----------------
Through systematic testing of Ubuntu mainline kernels, I've identified the
exact
regression window:

- Last working version: 6.10.14-061014-generic (all 6.10.x versions work)
- First broken version: 6.11.0-061100-generic

The regression was introduced during the 6.11 merge window. All 6.10.x versions
work correctly (tested 6.10.0 through 6.10.14), while all 6.11+ versions fail.
The issue persists through all subsequent versions tested up to 6.18.0-rc3.

The regression appears to be in ACPI _CPC object detection/parsing, as the same
BIOS/hardware combination works with the entire 6.10.x series but fails with
6.11+.

ADDITIONAL INFORMATION
----------------------
The same ACPI tables and BIOS work correctly with 6.8, 6.9, and 6.10 kernels,
confirming
this is not a firmware issue but a kernel regression in CPPC/ACPI handling.

From working system (6.10.14):
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
amd-pstate
- No error messages, driver loads successfully

From broken system (6.17.5):
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
acpi-cpufreq
$ dmesg | grep amd_pstate
[    0.714133] amd_pstate: the _CPC object is not present in SBIOS or ACPI
disabled

I've tested on multiple systems with identical results. I'm available
for testing patches or providing additional debugging information as needed.

I can perform git bisect between 6.10 and 6.11 if required to identify
the specific commit that introduced this regression.

Thank you for your attention to this regression.

Chris Harris


Keywords:
amd-pstate
cpufreq
ACPI
_CPC
Zen4

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 26+ messages in thread

end of thread, other threads:[~2025-11-05 21:20 UTC | newest]

Thread overview: 26+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

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).