Linux Integrity Measurement development
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jarkko Sakkinen" <jarkko@kernel.org>,
	"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: Wed, 13 Nov 2024 20:59:52 +0200	[thread overview]
Message-ID: <D5LA64STJRU1.1V6GQCO7Y95K9@kernel.org> (raw)
In-Reply-To: <D5L9XVNXYQR1.2EBNEZRV0QVUI@kernel.org>

On Wed Nov 13, 2024 at 8:49 PM EET, Jarkko Sakkinen wrote:
> On Wed Nov 13, 2024 at 4:44 PM EET, Christoph Anton Mitterer wrote:
> > Hey.
> >
> > Forwarding myself from:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087331
> >
> > Since 6.11.7 (might have also happened with .6, which I've skipped, but
> > wasn't the case at least in 6.11.5).
> >
> > I get:
> > Nov 11 17:50:20 heisenberg kernel: tpm tpm0: A TPM error (2306) occurred attempting to create NULL primary
>
> Yep, I found the reason. My fix causes this. I sent a fix.
>
> The problem still persists related to TPM bus encryption not working
> with hibernate in 6.11.5 but the message was shown only once in the
> log (and thus you did not notice it).
>
> That can be worked around e.g. with kernel command-line flag that
> would disable TPM bus encryption but it is out-of-scope as far as
> I'm concerned.
>
> Please test my fix and I can take it to PR.

https://lore.kernel.org/linux-integrity/20241113184449.477731-1-jarkko@kernel.org/T/#u

BR, Jarkko

  reply	other threads:[~2024-11-13 18:59 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
2024-11-13 18:49 ` Jarkko Sakkinen
2024-11-13 18:59   ` Jarkko Sakkinen [this message]
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=D5LA64STJRU1.1V6GQCO7Y95K9@kernel.org \
    --to=jarkko@kernel.org \
    --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