Linux Power Management development
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Gautham Ranjal Shenoy <gautham.shenoy@amd.com>,
	Mario Limonciello <Mario.Limonciello@amd.com>,
	Ray Huang <Ray.Huang@amd.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org
Cc: linux-pm@vger.kernel.org, linux-acpi@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Warnings `Could not retrieve perf counters (-19)` and `amd_pstate: the _CPC object is not present in SBIOS or ACPI disabled` (Dell PowerEdge R7625, AMD EPYC 9174F)
Date: Tue, 28 Jan 2025 16:08:43 +0100	[thread overview]
Message-ID: <e26bc00f-1675-4aac-bd02-60774ff5901a@molgen.mpg.de> (raw)
In-Reply-To: <d09f52d8-e084-4875-9608-5b3db2554f3d@molgen.mpg.de>

[Cc: +x86 maintainers and ACPI list]

Dear Linux folks,


Am 28.01.25 um 11:49 schrieb Paul Menzel:

> Thank you for your quick replies. Gautham, messages with HTML are 
> rejected by Linux kernel lists.
> 
> 
> Am 28.01.25 um 04:51 schrieb Shenoy, Gautham Ranjal:
> 
>> As Mario mentioned, you need to enable the CPPC option. Looking for 
>> some of the Dell PowerEdge documentation, there is an option called 
>> "Collaborative CPU Performance Control" (https://www.dell.com/support/manuals/en-in/poweredge-r730/r730_ompublication/system-profile-settings-details?guid=guid-2e9b46a1-71e3-4072-9d86-db648757f0e6&lang=en-us).
>>
>> [cid:fe57df8f-3d99-4ea0-8f6e-b0daae49bb0e]
>> Can you please try enabling it ?
> 
> You quoted the Dell PowerEdge R730. I couldn’t find it in the *Dell 
> PowerEdge R7625 Installation and Service Manual* [1], and also it’s not 
> listed in the iDRAC9 Web site (attached with added `.txt` extension to 
> trick the Linux list).

The amd_pstate warning seems to be related to the perf counters warning 
Linux prints earlier:

     $ dmesg --level alert,crit,err,warn
     [    2.666393] Spectre V2 : WARNING: Unprivileged eBPF is enabled 
with eIBRS on, data leaks possible via Spectre v2 BHB attacks!
     [    8.109446] Could not retrieve perf counters (-19)
     [    9.386551] scsi 0:0:4:0: set ignore_delay_remove for handle(0x0012)
     [    9.487804] amd_pstate: the _CPC object is not present in SBIOS 
or ACPI disabled
     [   14.726193] wmi_bus wmi_bus-PNP0C14:00: [Firmware Bug]: WQBC 
data block query control method not found

x86 maintainers, the original report with the Linux logs attached is in 
the archive [3].

It looks like, there is something missing in the Dell firmware to enable 
the feature.

The perf counters warning is from `amd_set_max_freq_ratio()` in 
`arch/x86/kernel/acpi/cppc.c`:

```
static void amd_set_max_freq_ratio(void)
{
         struct cppc_perf_caps perf_caps;
         u64 numerator, nominal_perf;
         u64 perf_ratio;
         int rc;

         rc = cppc_get_perf_caps(0, &perf_caps);
         if (rc) {
                 pr_warn("Could not retrieve perf counters (%d)\n", rc);
                 return;
         }
         […]
}
```

With

     include/uapi/asm-generic/errno-base.h:#define	ENODEV		19	/* No such 
device */

this is returned by in `drivers/acpi/cppc_acpi.c`:

```
/**
  * cppc_get_perf_caps - Get a CPU's performance capabilities.
  * @cpunum: CPU from which to get capabilities info.
  * @perf_caps: ptr to cppc_perf_caps. See cppc_acpi.h
  *
  * Return: 0 for success with perf_caps populated else -ERRNO.
  */
int cppc_get_perf_caps(int cpunum, struct cppc_perf_caps *perf_caps)
{
         struct cpc_desc *cpc_desc = per_cpu(cpc_desc_ptr, cpunum);
         […]
         if (!cpc_desc) {
                 pr_debug("No CPC descriptor for CPU:%d\n", cpunum);
                 return -ENODEV;
         }
         […]
}
```

Just for your information.


Kind regards,

Paul


> PS:
> 
>> -- 
>>
>> Thanks and Regards
>>
>> Gautham.
> 
> Only if you care: Your signature delimiter misses a space at the end [2].
> 
> 
> [1]: https://www.dell.com/support/manuals/de-de/poweredge-r7625/per7625_ism_pub/system-profile-settings?guid=guid-9f6b6652-4079-45e7-90f5-1c8feee08ec0&lang=en-us
> [2]: https://en.wikipedia.org/wiki/Signature_block#Standard_delimiter
[3]: 
https://lore.kernel.org/linux-pm/d09f52d8-e084-4875-9608-5b3db2554f3d@molgen.mpg.de/T/#t

  reply	other threads:[~2025-01-28 15:09 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
     [not found]   ` <DS7PR12MB82528A694056F1FBA20CE01E96EF2@DS7PR12MB8252.namprd12.prod.outlook.com>
2025-01-28 10:49     ` Paul Menzel
2025-01-28 15:08       ` Paul Menzel [this message]
2025-02-11 16:12         ` Warnings `Could not retrieve perf counters (-19)` and " 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=e26bc00f-1675-4aac-bd02-60774ff5901a@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=Mario.Limonciello@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gautham.shenoy@amd.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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