From: Mario Limonciello <mario.limonciello@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Sean Rhodes <sean@starlabs.systems>,
x86@kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@kernel.org>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/pm: Save AMD CPUID leaf 7 across S3
Date: Tue, 11 Aug 2026 13:45:43 -0500 [thread overview]
Message-ID: <1192083d-62f9-4cfc-bee5-251d9dabe011@amd.com> (raw)
In-Reply-To: <20260811184044.GAantsrA_ApoUksCiu@fat_crate.local>
On 8/11/26 13:40, Borislav Petkov wrote:
> On Tue, Aug 11, 2026 at 01:25:27PM -0500, Mario Limonciello wrote:
>> Well the fact that they could also reproduce it on the CRB with UEFI and the
>> latest firmware tells me it's most likely any system with this SoC and using
>> S3 for suspend is affected.
>
> So S3 is the problem...
>
>> I guess the same thing might be doable in coreboot ASL handlers for S3, but
>> I don't know how well that would go over with coreboot folks.
>>
>> They might say "It should be fixed in FSP" or "It's the kernel's problem".
>
> Definitely not the kernel's problem. The kernel gets to fix all the shit all
> the others broke.
>
Sean - Can you move your system to s0i3? If not, I suggest you draft a
coreboot ASL change for S3 handlers, and see how it looks.
next prev parent reply other threads:[~2026-08-11 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 10:13 [PATCH] x86/pm: Save AMD CPUID leaf 7 across S3 Sean Rhodes
2026-08-04 18:49 ` Borislav Petkov
2026-08-04 19:22 ` Sean Rhodes
2026-08-06 1:29 ` Borislav Petkov
2026-08-10 18:31 ` Mario Limonciello
2026-08-10 19:42 ` Sean Rhodes
2026-08-10 20:07 ` Mario Limonciello
2026-08-10 21:33 ` Borislav Petkov
2026-08-11 18:25 ` Mario Limonciello
2026-08-11 18:40 ` Borislav Petkov
2026-08-11 18:45 ` Mario Limonciello [this message]
2026-08-12 7:42 ` David Laight
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=1192083d-62f9-4cfc-bee5-251d9dabe011@amd.com \
--to=mario.limonciello@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=sean@starlabs.systems \
--cc=tglx@kernel.org \
--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