From: Frederik Himpe <frederik@frehi.be>
To: Mario Limonciello <mario.limonciello@amd.com>,
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
Subject: Re: [Bug 221019] After s2idle: amd-pmf AMDI0107:00: TEE enact cmd failed. err: ffff000e, ret:0
Date: Fri, 05 Jun 2026 13:57:50 +0200 [thread overview]
Message-ID: <8fdf8d6b80ac1ef9064518d557698673a59df07d.camel@frehi.be> (raw)
In-Reply-To: <c536f60d-2741-427a-9b46-7fb8cc1a2a4e@amd.com>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On Wed, 2026-01-28 at 09:56 -0600, Mario Limonciello wrote:
> > >
https://bugzilla.kernel.org/show_bug.cgi?id=221019
> > > 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/
I experienced this bug again with kernel 7.0.9. Every second I get:
amd-pmf AMDI0107:00: TEE enact cmd failed. err: ffff000e, ret:0
Attached an amd-s2idle report.
--
Frederik Himpe <frederik@frehi.be>
[-- Attachment #2: amd-s2idle-report-2026-06-05.html --]
[-- Type: text/html, Size: 125766 bytes --]
prev parent reply other threads:[~2026-06-05 12:06 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 ` Borislav Petkov
2026-01-28 15:56 ` Mario Limonciello
2026-06-05 11:57 ` Frederik Himpe [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=8fdf8d6b80ac1ef9064518d557698673a59df07d.camel@frehi.be \
--to=frederik@frehi.be \
--cc=Shyam-sundar.S-k@amd.com \
--cc=bp@alien8.de \
--cc=bugzilla-daemon@kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--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
all inboxes | Powered by JetHome®