[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <7cbe96cf-e0b5-ba63-d1b4-f63d2e826efa@suse.cz>
Date: Wed, 28 Dec 2022 21:22:56 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: 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: [REGRESSION] suspend to ram fails in 6.2-rc1 due to tpm errors
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
and further suspend to ram attempts fail:
tpm tpm0: Error (28) sending savestate before suspend
tpm_tis 00:08: PM: __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x80 returns 28
tpm_tis 00:08: PM: dpm_run_callback(): pnp_bus_suspend+0x0/0x10 returns 28
tpm_tis 00:08: PM: failed to suspend: error 28
PM: Some devices failed to suspend, or early wake event detected
Unfortunately I doubt I would be able to bisect it as any "good" kernel might
be a false negative.
[1] https://lore.kernel.org/all/c5ba47ef-393f-1fba-30bd-1230d1b4b592@suse.cz/
#regzbot introduced: v6.1..v6.2-rc1
Powered by blists - more mailing lists