[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c39cc02da9f60412a0f7f7772ef3d89e4a081d38.camel@HansenPartnership.com>
Date: Wed, 28 Dec 2022 18:07:25 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Vlastimil Babka <vbabka@...e.cz>, Peter Huewe <peterhuewe@....de>,
Jarkko Sakkinen <jarkko@...nel.org>,
Jason Gunthorpe <jgg@...pe.ca>, Jan Dabros <jsd@...ihalf.com>
Cc: regressions@...ts.linux.dev, LKML <linux-kernel@...r.kernel.org>,
linux-integrity@...r.kernel.org,
Dominik Brodowski <linux@...inikbrodowski.net>,
"Jason A. Donenfeld" <Jason@...c4.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [REGRESSION] suspend to ram fails in 6.2-rc1 due to tpm errors
On Wed, 2022-12-28 at 21:22 +0100, Vlastimil Babka wrote:
> Ugh, while the problem [1] was fixed in 6.1, it's now happening again
> on the T460 with 6.2-rc1. Except I didn't see any oops message or
> "tpm_try_transmit" error this time. The first indication of a problem
> is this during a resume from suspend to ram:
>
> tpm tpm0: A TPM error (28) occurred continue selftest
>
> and then periodically
>
> tpm tpm0: A TPM error (28) occurred attempting get random
That's a TPM 1.2 error which means the TPM failed the selftest. The
original problem was reported against TPM 2.0 because of a missing
try_get_ops(). The tpm 1.2 command path was never changed to require
this (and in fact hasn't changed for ages, TPM 1.2 being a bit
obsolete). So this looks like a new problem with TPM 1.2 and
suspend/resume, likely in the BIOS of your system.
James
Powered by blists - more mailing lists