From: Mario Limonciello <mario.limonciello@amd.com>
To: Borislav Petkov <bp@alien8.de>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Cc: "Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, bugzilla-daemon@kernel.org,
frederik@frehi.be
Subject: Re: [Bug 221019] After s2idle: amd-pmf AMDI0107:00: TEE enact cmd failed. err: ffff000e, ret:0
Date: Wed, 28 Jan 2026 09:56:23 -0600 [thread overview]
Message-ID: <c536f60d-2741-427a-9b46-7fb8cc1a2a4e@amd.com> (raw)
In-Reply-To: <20260128122900.GAaXoBDDwHHyIkk6Wv@fat_crate.local>
On 1/28/26 6:29 AM, Borislav Petkov wrote:
> Switching to mail and adding people to Cc.
>
> On Wed, Jan 28, 2026 at 08:20:27AM +0000, bugzilla-daemon@kernel.org wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=221019
>>
>> frederik@frehi.be changed:
>>
>> What |Removed |Added
>> ----------------------------------------------------------------------------
>> Kernel Version| |6.18.5
>>
>> --- Comment #1 from frederik@frehi.be ---
>> I have an HP EliteBook 8 G1a 14 laptop. Sometimes when resuming the system
>> from s2idle, I get an endless loop of this kernel error message,
>> repeated every second:
>>
>> amd-pmf AMDI0107:00: TEE enact cmd failed. err: ffff000e, ret:0
>>
>> I'm using Linux 6.18.5 from Debian unstable.
>>
>> Complete kernel log attached.
This looks just like the issue we had with S4.
Try this series.
https://lore.kernel.org/platform-driver-x86/20260116041132.153674-1-superm1@kernel.org/
Thanks,
next prev parent reply other threads:[~2026-01-28 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-221019-6385@https.bugzilla.kernel.org/>
[not found] ` <bug-221019-6385-GcFBcW3deQ@https.bugzilla.kernel.org/>
2026-01-28 12:29 ` [Bug 221019] After s2idle: amd-pmf AMDI0107:00: TEE enact cmd failed. err: ffff000e, ret:0 Borislav Petkov
2026-01-28 15:56 ` Mario Limonciello [this message]
2026-06-05 11:57 ` Frederik Himpe
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=c536f60d-2741-427a-9b46-7fb8cc1a2a4e@amd.com \
--to=mario.limonciello@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=bp@alien8.de \
--cc=bugzilla-daemon@kernel.org \
--cc=frederik@frehi.be \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.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