From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-integrity <linux-integrity@vger.kernel.org>
Subject: TPM selftest failure in 4.15
Date: Thu, 01 Feb 2018 12:16:11 +0000 [thread overview]
Message-ID: <1517487371.3251.9.camel@HansenPartnership.com> (raw)
Embarrassingly enough, I'm just on my way to do a TPM talk at FOSDEM.
I installed my shiny new 4.15 kernel on the 'plane and this is what I
got after I arrived this morning:
jejb@jarvis:~> dmesg | grep -i tpm
[ 0.000000] ACPI: TPM2 0x0000000079446CC0 000034
(v03 Tpm2Tabl 00000001 AMI 00000000)
[ 1.598059] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 2)
[ 1.608863] tpm tpm0: A TPM error (2314) occurred continue selftest
[ 1.640052] tpm tpm0: A TPM error (2314) occurred continue selftest
[ 1.691215] tpm tpm0: A TPM error (2314) occurred continue selftest
[ 1.782377] tpm tpm0: A TPM error (2314) occurred continue selftest
[ 1.953539] tpm tpm0: A TPM error (2314) occurred continue selftest
[ 2.284701] tpm tpm0: A TPM error (2314) occurred continue selftest
[ 2.935743] tpm tpm0: A TPM error (2314) occurred continue selftest
[ 4.216236] tpm tpm0: TPM self test failed
[ 4.236829] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
The error is TPM_RC_TESTING, which means it looks like we don't wait
long enough for the selftests to complete. I get this all the time
booting with 4.15. Fortunately I have a 4.13 backup kernel which is
fine (otherwise I'd be a bit hosed since all my keys now require a
TPM).
I'll debug on the train; my current suspicion is that the TPM_LONG
duration might be a bit short for this chip (A nuvoton 6xx in a dell
XPS-13).
James
next reply other threads:[~2018-02-01 12:16 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 12:16 James Bottomley [this message]
2018-02-01 12:21 ` TPM selftest failure in 4.15 Paul Menzel
2018-02-01 12:42 ` James Bottomley
2018-02-01 15:24 ` James Bottomley
2018-02-01 17:40 ` Jason Gunthorpe
2018-02-01 18:46 ` James Bottomley
2018-02-01 18:59 ` Jason Gunthorpe
2018-02-01 20:00 ` James Bottomley
2018-02-01 20:35 ` Jason Gunthorpe
2018-02-01 21:06 ` James Bottomley
2018-02-08 13:10 ` Jarkko Sakkinen
2018-02-08 17:02 ` James Bottomley
2018-02-09 10:02 ` Jarkko Sakkinen
2018-02-09 10:30 ` Nayna Jain
2018-02-15 12:00 ` Jarkko Sakkinen
2018-02-09 11:47 ` Alexander Steffen
2018-02-15 12:12 ` Jarkko Sakkinen
2018-02-15 15:13 ` Mimi Zohar
2018-02-16 18:30 ` Alexander Steffen
2018-02-19 9:15 ` Nayna Jain
2018-02-19 22:26 ` Jason Gunthorpe
2018-02-16 18:27 ` Alexander Steffen
2018-02-20 13:05 ` Jarkko Sakkinen
2018-02-09 12:26 ` Mimi Zohar
2018-02-09 16:23 ` James Bottomley
2018-02-09 21:23 ` Mimi Zohar
2018-04-08 18:27 ` Ken Goldman
2018-02-09 16:18 ` James Bottomley
2018-02-08 17:27 ` Ken Goldman
2018-02-01 19:16 ` TPM selftest failure in 4.15 (Dell XPS 13, Nuvoton 6xx) Paul Menzel
2018-02-01 19:17 ` Paul Menzel
2018-02-01 20:12 ` Mario.Limonciello
2018-02-01 21:06 ` Mario.Limonciello
2018-02-01 22:22 ` Jason Gunthorpe
2018-02-02 5:46 ` James Bottomley
2018-02-02 5:46 ` James Bottomley
2018-02-08 16:53 ` Ken Goldman
2018-02-08 13:18 ` Jarkko Sakkinen
2018-02-08 13:05 ` TPM selftest failure in 4.15 Jarkko Sakkinen
2018-02-08 13:03 ` Jarkko Sakkinen
2018-02-08 12:49 ` Jarkko Sakkinen
2018-02-08 18:45 ` Ken Goldman
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=1517487371.3251.9.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--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