mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jonathan McDowell <noodles@earth.li>,
	linux-integrity@vger.kernel.org,
	 Jarkko Sakkinen <jarkko@kernel.org>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
	 linux-kernel@vger.kernel.org
Subject: Re: Problems with TPM timeouts
Date: Wed, 02 Oct 2024 10:31:34 -0700	[thread overview]
Message-ID: <a9b94fad8f0d8023ce2459fa11494ff8e83d0b65.camel@HansenPartnership.com> (raw)
In-Reply-To: <Zv1810ZfEBEhybmg@earth.li>

On Wed, 2024-10-02 at 18:03 +0100, Jonathan McDowell wrote:
[...]
> First, I've seen James' post extending the TPM timeouts back in 2018
> (
> https://lore.kernel.org/linux-integrity/1531329074.3260.9.camel@Hansen
> Partnership.com/), which doesn't seem to have been picked up. Was an
> alternative resolution found, or are you still using this, James?

No, because I've got a newer laptop.  The problem was seen on a 2015
XPS-13 with a Nuvoton TPM that was software upgraded to 2.0 (and had
several other problems because of this).  I assumed, based on the lack
of reports from others, that this was a problem specific to my TPM and
so didn't push it.

The annoying thing for me was that the TPM didn't seem to recover. 
Once it started giving timeouts it carried on timing out until machine
reset, which really caused problems because all my keys are TPM
resident.

Is yours a permanent problem like mine, or is it transient (TPM
recovers and comes back)?

Regards,

James


  parent reply	other threads:[~2024-10-02 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 17:03 Jonathan McDowell
2024-10-02 17:04 ` [RFC PATCH] tpm: Workaround failed command reception on Infineon devices Jonathan McDowell
2024-10-03 21:59   ` Stefan Berger
2024-10-03 22:25     ` Stefan Berger
2024-10-04 14:47       ` Jonathan McDowell
2024-10-02 17:31 ` James Bottomley [this message]
2024-10-02 19:26   ` Problems with TPM timeouts Jonathan McDowell

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=a9b94fad8f0d8023ce2459fa11494ff8e83d0b65.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noodles@earth.li \
    --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

all inboxes | Powered by JetHome®