Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#59234 - [linux] TPM fails on boot misinterpreting warning as error

Attached to Project: Arch Linux
Opened by Konstantin Gizdov (kgizdov) - Wednesday, 04 July 2018, 19:54 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 30 July 2018, 14:13 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Since kernel 4.14, I've not been able to use the TPM on my Dell XPS 13, this persists until 4.17+. It has to do with the kernel not waiting on the self-test running in the background and turns off the device as if it returned an error.

Additional info:
* package version(s): kernel 4.17.3
* config and/or log files etc.: n/a

Steps to reproduce:
1. Boot Arch on a machine with a TPM 2.0 compatible device
2. get the following error:
tpm tpm0: A TPM error (2314) occurred attempting the self test

Actually, 2314 == 0x090A == TPM2_RC_TESTING, which is the status returned while tests are running in the background and it's not an error. It's described more here -

Thus, I am wondering if we can include this patch in the current linux package. Thanks.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 30 July 2018, 14:13 GMT
Reason for closing:  Fixed
Comment by loqs (loqs) - Wednesday, 04 July 2018, 20:28 GMT
The referenced patch does not apply cleanly to 4.17.3 and 4.17.3 already has 2be8ffed093b91536d52b5cd2c99b52f605c9ba6 and e2fb992d82c626c43ed0566e07c410e56a087af3 which were applied with 4.17.
Do you have a patch that applies to 4.17.3 that you have tested and resolves the issue? Does the issue still occur with 4.18-rc3?
Edit: e2fb992d82c626c43ed0566e07c410e56a087af3 instead of second 2be8ffed093b91536d52b5cd2c99b52f605c9ba6
Comment by Konstantin Gizdov (kgizdov) - Monday, 30 July 2018, 09:28 GMT
Seems like it was fixed in the kernel. Now, I can use my TPM and I don't see he error in `dmesg`.