From: Mario Limonciello <mario.limonciello@amd.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
Huang Rui <ray.huang@amd.com>,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>
Cc: linux-pm@vger.kernel.org
Subject: Re: Warning `amd_pstate: the _CPC object is not present in SBIOS or ACPI disabled` (Dell PowerEdge R7625, AMD EPYC 9174F)
Date: Mon, 27 Jan 2025 09:43:20 -0600 [thread overview]
Message-ID: <5dff1719-c4e9-4ebf-ae0b-73b9de98df05@amd.com> (raw)
In-Reply-To: <2b811df7-5278-4cfc-b8a0-7d6d72d3358d@molgen.mpg.de>
On 1/27/2025 06:41, Paul Menzel wrote:
> Dear Linux folks,
>
>
> On a Dell PowerEdge R7625 with two 32x AMD EPYC 9174F Linux 6.12 logs
>
> $ dmesg | grep -e "DMI:" -e "Linux version" -e microcode
> [ 0.000000] Linux version 6.12.11.mx64.479
> (root@lucy.molgen.mpg.de) (gcc (GCC) 12.3.0, GNU ld (GNU Binutils) 2.41)
> #1 SMP PREEMPT_DYNAMIC Fri Jan 24 13:30:47 CET 2025
> [ 0.000000] DMI: Dell Inc. PowerEdge R7625/0M7YXP, BIOS 1.10.6
> 12/06/2024
> [ 0.000000] DMI: Memory slots populated: 4/24
> [ 9.487804] amd_pstate: the _CPC object is not present in SBIOS
> or ACPI disabled
> [ 9.733516] microcode: Current revision: 0x0a101148
>
> ACPI is enabled. What can I do about the warning?
You can look if the BIOS has any options for enabling it. They might be
called "CPPC".
next prev parent reply other threads:[~2025-01-27 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 12:41 Warning `amd_pstate: the _CPC object is not present in SBIOS or ACPI disabled` (Dell PowerEdge R7625, AMD EPYC 9174F) Paul Menzel
2025-01-27 15:43 ` Mario Limonciello [this message]
[not found] ` <DS7PR12MB82528A694056F1FBA20CE01E96EF2@DS7PR12MB8252.namprd12.prod.outlook.com>
2025-01-28 10:49 ` Paul Menzel
2025-01-28 15:08 ` Warnings `Could not retrieve perf counters (-19)` and " Paul Menzel
2025-02-11 16:12 ` Paul Menzel
2025-02-11 16:18 ` Mario Limonciello
2025-03-10 15:17 ` Paul Menzel
2025-03-18 1:29 ` Mario Limonciello
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=5dff1719-c4e9-4ebf-ae0b-73b9de98df05@amd.com \
--to=mario.limonciello@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-pm@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=ray.huang@amd.com \
/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