From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Adam Alves" <adamoa@gmail.com>
Cc: "Peter Huewe" <peterhuewe@gmx.de>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
<linux-integrity@vger.kernel.org>
Subject: Re: [PATCH v2] tpm: Fix suspend/shutdown on some boards by preserving chip Locality
Date: Tue, 19 Mar 2024 22:07:26 +0200 [thread overview]
Message-ID: <CZXZXNPX9VUP.1VOSQNSGQYX7A@kernel.org> (raw)
In-Reply-To: <CAHwaaX-j37rq4+DCNSRAgPmeQmrYZiX2sLv4ugBjPJSj9LPxcg@mail.gmail.com>
On Thu Mar 14, 2024 at 6:31 PM EET, Adam Alves wrote:
> Hi Jarkko,
>
> I have an update here. I would like you to check if it makes sense
> before I submit a patch.
>
> The problem might be related to the chip itself which leaves the idle
> state whenever the locality is relinquished.
There's no real discrete chip. It is a TPM living in the firmware,
namely management engine.
So first thing to check would be to update the BIOS entirely.
> I probed the chip while operating and noted that the
> TPM_CRB_CTRL_STS_0.tpmIdle bit (located at `regs_t->ctrl_sts` on
> `crb_priv` structure in tpm_crb.c) is always cleared whenever the
> locality is relinquished.
>
> The result is that this chip never becomes idle since after going idle
> the locality is relinquished (`tpm_chip_stop` function in tpm-chip.c).
This can be verified as tpm_crb does print "goIdle timed out" if it does
not go to idle. Should be visible in klog.
BR, Jarkko
next prev parent reply other threads:[~2024-03-19 20:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 0:03 [PATCH 0/1] Fix TPM chip hanging system before suspend/shutdown Adam Alves
2024-03-07 0:03 ` [PATCH 1/1] " Adam Alves
2024-03-07 19:54 ` Jarkko Sakkinen
2024-03-07 22:17 ` Adam Alves
2024-03-07 22:49 ` [PATCH v2] tpm: Fix suspend/shutdown on some boards by preserving chip Locality Adam Alves
2024-03-08 9:33 ` Paul Menzel
2024-03-08 14:22 ` Adam Alves
2024-03-08 14:53 ` [PATCH v3] " Adam Alves
2024-03-11 20:04 ` [PATCH v2] " Jarkko Sakkinen
2024-03-13 17:02 ` Adam Alves
2024-03-14 16:31 ` Adam Alves
2024-03-14 16:32 ` Adam Alves
2024-03-19 20:07 ` Jarkko Sakkinen [this message]
2024-03-19 19:57 ` Jarkko Sakkinen
2024-03-19 21:38 ` Jarkko Sakkinen
2024-03-19 21:41 ` Jarkko Sakkinen
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=CZXZXNPX9VUP.1VOSQNSGQYX7A@kernel.org \
--to=jarkko@kernel.org \
--cc=adamoa@gmail.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).