linux-kernel - 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)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <35c99e60-c44d-433f-8988-62aa94dd924f@amd.com>
Date: Mon, 17 Mar 2025 20:29:50 -0500
From: Mario Limonciello <mario.limonciello@....com>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: Gautham Ranjal Shenoy <gautham.shenoy@....com>,
 Ray Huang <Ray.Huang@....com>, Thomas Gleixner <tglx@...utronix.de>,
 Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
 Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
 linux-pm@...r.kernel.org, linux-acpi@...r.kernel.org,
 LKML <linux-kernel@...r.kernel.org>, it+linux-dell@...gen.mpg.de
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)

<snip>
> 
> I made the service request 205423744 on February 12th, 2025, and after 
> collecting the details until February 14th, 2025, Dell replied on March 
> 4th, 2025, that there L3 support and engineering team was able to 
> reproduce the issue, and they are going to provide a firmware update, 
> currently estimated for June.
> 
> I am still surprised, that Dell’s QA overlooked this. Does AMD provide 
> them test suites (does FWTS check for this). `dmesg --level=warning` is 
> unfortunately not empty, so maybe they ignore it.
> 

IIRC FWTS doesn't test for this.  Perhaps you can add check to klog.json 
for the message you saw?  There is an existing pattern for a CPPC 
related error message:

https://github.com/fwts/fwts/blob/ec33c8ee1d99211a9cb2081324ec909a325e93d8/data/klog.json#L56

A similar pattern could be added for your case.

> Would it make sense to make the warning an error, so it’s less likely 
> overlooked?
> 

If they don't run dmesg --level=warning, why would dmesg --level=error 
would be more likely to be run?

FWIW For 6.15 we're introducing another warning for BIOS failures.

https://web.git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git/commit/?h=linux-next&id=a9ba0fd452d82ca0da170eb6291aac01075a17d5