From: Adam Alves <adamoa@gmail.com>
To: Peter Huewe <peterhuewe@gmx.de>, Jarkko Sakkinen <jarkko@kernel.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
linux-integrity@vger.kernel.org, Adam Alves <adamoa@gmail.com>
Subject: [PATCH 0/1] Fix TPM chip hanging system before suspend/shutdown
Date: Wed, 6 Mar 2024 21:03:30 -0300 [thread overview]
Message-ID: <20240307000331.14848-1-adamoa@gmail.com> (raw)
Fix hanging before shutdown/suspend behaviour on some buggy
platform firmwares.
Adam Alves (1):
Some buggy firmwares might require the TPM device to be in default
locality (Locality 0) before suspend or shutdown. Failing to do so
would leave the system in a hanged state before sleep or power off
(after “reboot: Power down” message). Such is the case for the
ASUSTeK COMPUTER INC. TUF GAMING B460M-PLUS board, I believe this
might be the case for several other boards based on the bugs I have
found on the internet while trying to find out how to fix my
specific issue. Most forums suggest the user to disable the TPM
device on firmware BIOS in order to work around this specific issue,
which disables several nice security features provided by TPM, such
as secure boot attestation, automatic decryption and hardware random
generator.
drivers/char/tpm/tpm-chip.c | 9 ++++++++
drivers/char/tpm/tpm-interface.c | 36 +++++++++++++++++++++++++++++++-
drivers/char/tpm/tpm.h | 1 +
include/linux/tpm.h | 1 +
4 files changed, 46 insertions(+), 1 deletion(-)
--
2.44.0
next reply other threads:[~2024-03-07 0:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 0:03 Adam Alves [this message]
2024-03-07 0:03 ` [PATCH 1/1] Fix TPM chip hanging system before suspend/shutdown 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
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=20240307000331.14848-1-adamoa@gmail.com \
--to=adamoa@gmail.com \
--cc=jarkko@kernel.org \
--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).