From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "James Bottomley" <James.Bottomley@HansenPartnership.com>,
"Christoph Anton Mitterer" <calestyo@scientia.org>,
<linux-integrity@vger.kernel.org>
Subject: Re: regression: kernel log "flooded" with tpm tpm0: A TPM error (2306) occurred attempting to create NULL primary
Date: Thu, 14 Nov 2024 06:56:08 +0200 [thread overview]
Message-ID: <D5LMUO2NNWFK.390DHBIZ06SMD@kernel.org> (raw)
In-Reply-To: <05f511502a5918fe81d69201ec3df01b25803bcd.camel@HansenPartnership.com>
On Thu Nov 14, 2024 at 4:06 AM EET, James Bottomley wrote:
> Getting the TPM messages to quiet by disabling the chip fixes the
> message spew, but it doesn't get you a working TPM chip back on resume.
> I'll take a look at the hibernation path and see if I can see a hook we
> can use to bring the TPM back.
Fixing hibernate issue could not be done in the same patch as it is
a different bug logically that I fixed. The hibernate bug pre-existed
in your original code.
So my fix was not about at all masking a bug, it was about fixing a
bug in my own previous fix. I.e. even you had a fix for hibernate, this
patch would have been needed separately.
BR, Jarkko
next prev parent reply other threads:[~2024-11-14 4:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 14:44 regression: kernel log "flooded" with tpm tpm0: A TPM error (2306) occurred attempting to create NULL primary Christoph Anton Mitterer
2024-11-13 15:47 ` James Bottomley
2024-11-13 18:12 ` James Bottomley
2024-11-13 22:34 ` Jarkko Sakkinen
2024-11-13 22:43 ` Jarkko Sakkinen
2024-11-13 23:56 ` Christoph Anton Mitterer
2024-11-14 2:06 ` James Bottomley
2024-11-14 2:17 ` Christoph Anton Mitterer
2024-11-14 4:57 ` Jarkko Sakkinen
2024-11-25 13:49 ` Christoph Anton Mitterer
2024-11-30 2:37 ` Jarkko Sakkinen
2024-11-14 4:56 ` Jarkko Sakkinen [this message]
2024-11-13 18:49 ` Jarkko Sakkinen
2024-11-13 18:59 ` Jarkko Sakkinen
2024-11-14 0:04 ` Christoph Anton Mitterer
2024-11-14 4:52 ` Jarkko Sakkinen
2024-11-14 23:57 ` Christoph Anton Mitterer
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=D5LMUO2NNWFK.390DHBIZ06SMD@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=calestyo@scientia.org \
--cc=linux-integrity@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