#1050602 linux: kernel 6.4.11-1 does not recognize TPM on lenovo 14IAU7 (Flex 7i)

Package:
src:linux
Source:
src:linux
Submitter:
Justin King-Lacroix
Date:
2023-09-07 18:00:04 UTC
Severity:
normal
Tags:
#1050602#5
Date:
2023-08-26 21:20:42 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I use clevis-tpm2 to automatically unlock my harddisk on a 14IAU7 (Flex 7i),
and have been successfully using it for several months.


   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Update from linux-image-6.4.0-2-amd64 to linux-image-6.4.0-3-amd64

   * What was the outcome of this action?

Machine boots successfully, but TPM-based auto-unlock no longer works. In fact,
the following shows up in `dmesg`:

```
$ sudo dmesg |grep -i tpm
[    0.000000] efi: ACPI=0x1ef60000 ACPI 2.0=0x1ef60014 TPMFinalLog=0x1ee34000
SMBIOS=0x21489000 SMBIOS 3.0=0x2147c000 MEMATTR=0x5398d018 ESRT=0x55328118
MOKvar=0x21478000 RNG=0x1ef5f018 TPMEventLog=0x1d82b018
[    0.004648] ACPI: SSDT 0x000000002148B000 00060E (v02 LENOVO Tpm2Tabl
00001000 INTL 20200717)
[    0.004651] ACPI: TPM2 0x000000002148A000 00004C (v04 LENOVO CB-01
00000002 LENO 00000001)
[    0.004709] ACPI: Reserving TPM2 table memory at [mem 0x2148a000-0x2148a04b]
[    1.217243] tpm_crb: probe of INTC6001:00 failed with error 378
[    1.256600] ima: No TPM chip found, activating TPM-bypass!
[    9.117870] systemd[1]: systemd 254.1-2 running in system mode (+PAM +AUDIT
+SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID
+CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2
-PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK
-XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[    9.270983] systemd[1]: systemd-pcrmachine.service - TPM2 PCR Machine ID
Measurement was skipped because of an unmet condition check
(ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
$
```

(Note the line that says "No TPM chip found".)

TPM-related stuff is also gone from /sys/kernel/security.

   * What outcome did you expect instead?

TPM continues to be recognized and used by linux.


*** End of the template - remove these template lines ***

#1050602#10
Date:
2023-08-26 21:26:51 UTC
From:
To:
Looks like this is an upstream bug that affects all Alder Lake (and maybe
newer) systems.

https://bugzilla.kernel.org/show_bug.cgi?id=217804

https://github.com/NixOS/nixpkgs/issues/250166

#1050602#15
Date:
2023-08-28 23:27:52 UTC
From:
To:
Obviously, NEWS.Debian.gz is not an upstream file. :)
#1050602#20
Date:
2023-08-29 11:29:50 UTC
From:
To:
Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=217804 https://lore.kernel.org/stable/20230822231510.2263255-1-jarkko@kernel.org/
Control: tag -1 upstream
submission which will hopefully fix that issue.

The issue is also on Thorsten Leemhuis' radar:
https://lore.kernel.org/stable/fcf2f600-d1f0-de14-956b-4d4f3f0cb3fa@leemhuis.info/

#1050602#29
Date:
2023-09-02 03:32:34 UTC
From:
To:
Thanks.

FYI bug is still present in 6.4.13-1

J


On Tue, Aug 29, 2023 at 7:30 AM Diederik de Haas <didi.debian@cknow.org> wrote:

#1050602#36
Date:
2023-09-07 17:57:23 UTC
From:
To:
It has been fixed in Linus' tree with 8f7f35e5aa6f2182eabcfa3abef4d898a48e9aa8
And a backport of that is currently available in the stable queue for 6.5, 6.4
and 6.1, so it should make it into 6.5.3, 6.4.16 and 6.1.53 respectively.