From: Mario Limonciello <mario.limonciello@amd.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Gautham Ranjal Shenoy <gautham.shenoy@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, linux-pm@vger.kernel.org,
linux-acpi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
it+linux-dell@molgen.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)
Date: Mon, 17 Mar 2025 20:29:50 -0500 [thread overview]
Message-ID: <35c99e60-c44d-433f-8988-62aa94dd924f@amd.com> (raw)
In-Reply-To: <73da51ef-a7cc-4c38-8289-09c9cbd0c65d@molgen.mpg.de>
<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
prev parent reply other threads:[~2025-03-18 1:29 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 ` 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 [this message]
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=35c99e60-c44d-433f-8988-62aa94dd924f@amd.com \
--to=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=it+linux-dell@molgen.mpg.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--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