From: Jarkko Sakkinen <jarkko@kernel.org>
To: Sean Meadows <Hellfire@unspacy.com>
Cc: linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
rafael@kernel.org, lenb@kernel.org, linux-acpi@vger.kernel.org,
Adam Alves <adamoa@gmail.com>
Subject: Re: [BUG] tpm_crb/Intel PTT: Late S3/S5/Reboot ACPI power management deadlock
Date: Wed, 30 Sep 2026 01:25:23 +0300 [thread overview]
Message-ID: <arw609M6mDiqhQwJ@kernel.org> (raw)
In-Reply-To: <0e8f93d0-3da9-4af0-ac12-b3670acdcf79@unspacy.com>
On Tue, Sep 29, 2026 at 01:44:29PM -0400, Sean Meadows wrote:
>
> On 9/25/26 11:05, Jarkko Sakkinen wrote:
> >
> > Thanks for providing the information.
> >
> > Bugzilla bug under discussion: https://bugzilla.kernel.org/
> > show_bug.cgi? id=217890
> >
> > I also found fix attempt of which 3rd version somehow went past me:
> >
> > https://lore.kernel.org/all/20240308145313.40932-1-adamoa@gmail.com/
> >
> > Does this or disabling hwrng sort out the issue?
> >
> > I got one other idea too with no empirical basis (just hypothesis): perhaps
> > release memory mapping on suspend could help firmware.
> >
> >
> > Br, Jarkko
>
> Acknowledged.
>
> Disabling HWRNG via kernel cmdline failed, and since my research implied
> that path would require a custom kernel, I shifted my efforts toward
> forward-porting Mr. Alves's 2024 patch to 7.2.7. It took some work, but
> I have successfully compiled it and got it booting on my machine.
>
> The patch appears to sort out the issue so far, but I'm only 43 hours
> into the test. As we discussed previously, this bug can take days to
> manifest, so I will reply again once I cross a week of sleep cycles
> without a crash.
>
> I also have a USB3 debug cable on the way in hope of capturing the
> hardware state during the power transition. That said, if Mr. Alves's
> patch continues to work as well as it has so far, there may not be any
> need for that.
>
> Sean
There's a commit with title "tpm: Call cmd_ready/go_idle for each command
transmission", which is strongest contender to make a difference to this
long running issue.
I.e. I think it will improve firmware behavior given full release of
resources per TPM command.
I'm including it to v7.4 pull request.
Br, Jarkko
next prev parent reply other threads:[~2026-09-29 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 6:45 [BUG] tpm_crb/Intel PTT: Late S3/S5/Reboot ACPI power management deadlock Sean Meadows
2026-09-18 1:28 ` Jarkko Sakkinen
2026-09-22 8:42 ` Sean Meadows
2026-09-25 15:05 ` Jarkko Sakkinen
2026-09-29 17:44 ` Sean Meadows
2026-09-29 22:25 ` Jarkko Sakkinen [this message]
2026-10-07 16:27 ` Sean Meadows
2026-10-08 17:47 ` Jarkko Sakkinen
2026-10-08 20:00 ` Mario Limonciello
2026-10-08 21:56 ` Sean Meadows
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=arw609M6mDiqhQwJ@kernel.org \
--to=jarkko@kernel.org \
--cc=Hellfire@unspacy.com \
--cc=adamoa@gmail.com \
--cc=jgg@ziepe.ca \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=rafael@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