From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Christoph Anton Mitterer" <calestyo@scientia.org>,
"James Bottomley" <James.Bottomley@HansenPartnership.com>,
<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:57:46 +0200 [thread overview]
Message-ID: <D5LMVWUBX2FK.205ZHBLQKY7SB@kernel.org> (raw)
In-Reply-To: <6b66684616408e2f9576bd5eca5ab58254a69438.camel@scientia.org>
On Thu Nov 14, 2024 at 4:17 AM EET, Christoph Anton Mitterer wrote:
> On Wed, 2024-11-13 at 18:06 -0800, 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.
>
> Sure, but actually I don't use TPM anyway so for me the main point was
> really just the nuisance of the repetitive log messages O:-)
>
> Still, it would of course be nice if you get it properly running after
> hibernation.
Yeah, my point and fix was about denoting that there was actually
*logically* not one but two bugs, you can blame for the noise bug
:-)
Rare occasion but in this case it was for better that I caused the
noise bug so that we noticed hibernate having issue....
>
> Thanks,
> Chris
BR, Jarkko
next prev parent reply other threads:[~2024-11-14 4:57 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 [this message]
2024-11-25 13:49 ` Christoph Anton Mitterer
2024-11-30 2:37 ` Jarkko Sakkinen
2024-11-14 4:56 ` Jarkko Sakkinen
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=D5LMVWUBX2FK.205ZHBLQKY7SB@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.