View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000440 | AlmaLinux-9 | kernel | public | 2023-11-14 08:30 | 2024-04-16 10:56 |
Reporter | ccto32 | Assigned To | alukoshko | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | assigned | Resolution | open | ||
OS | AlmaLinux | OS Version | 9.3 | ||
Summary | 0000440: No TPM2 chip detected in AlmaLinux 9.3 , but TPM2 chip detected in AlmaLinux 9.2 in the same machine | ||||
Description | CPU: Intel i7-13700 Motherboard: ASUS PRIME B760-PLUS D4, with Platform TPM 2 enabled in BIOS SecureBoot UEFI enabled SELinux enabled We have been using TPM2 + Clevis + LUKS to boot up and unlock the LUKS partitions automatically. You have released AlmaLinux 9.3 today (2023-11-14). We tried to use a development machine, upgrade it (yum -y update) from AlmaLinux 9.2 to 9.3 . Reboot it, during the boot process, it waits me to enter passphrase. Entering passphrase, it can boot up as usual. (However, it shall not ask me passphrase) After checking (dmesg | grep -i tpm) , no TPM detected in AlmaLinux 9.3 kernel (kernel-5.14.0-362.8.1.el9_3.x86_64) If I reboot, and use AlmaLinux 9.2 kernel (5.14.0-284.30.1.el9_2.x86_64) to boot , it is normal to boot (i.e. automatically unlock the LUKS partitions) ------------------------------------- I tried to compare the dmesg messages between 2 kernels, and found the following inside AlmaLinux 9.3 - [ 0.391191] tpm_crb: probe of MSFT0101:00 failed with error 378 [ 0.761961] ima: No TPM chip found, activating TPM-bypass! ------------------------------------- [root@xxxxxxx /]# grep -i tpm /dmesg.al92 [ 0.000000] efi: ACPI=0x764fd000 ACPI 2.0=0x764fd014 TPMFinalLog=0x7666c000 SMBIOS=0x77a72000 SMBIOS 3.0=0x77a71000 MEMATTR=0x6d8f8018 ESRT=0x6f871618 MOKvar=0x77aec000 RNG=0x77a9e918 TPMEventLog=0x5ea91018 [ 0.005219] ACPI: TPM2 0x0000000076363000 00004C (v04 ALASKA A M I 00000001 AMI 00000000) [ 0.005234] ACPI: Reserving TPM2 table memory at [mem 0x76363000-0x7636304b] [ 0.913706] systemd[1]: systemd 252-18.el9 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) [ 12.902476] systemd[1]: systemd 252-18.el9 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) [root@xxxxxxx /]# ------------------------------------- [root@xxxxxxx /]# grep -i tpm /dmesg.al93 [ 0.000000] efi: ACPI=0x764fd000 ACPI 2.0=0x764fd014 TPMFinalLog=0x7666c000 SMBIOS=0x77a72000 SMBIOS 3.0=0x77a71000 MEMATTR=0x6d8f8018 ESRT=0x6f871618 MOKvar=0x77aec000 RNG=0x77a9e918 TPMEventLog=0x5ea91018 [ 0.005100] ACPI: TPM2 0x0000000076363000 00004C (v04 ALASKA A M I 00000001 AMI 00000000) [ 0.005116] ACPI: Reserving TPM2 table memory at [mem 0x76363000-0x7636304b] [ 0.391191] tpm_crb: probe of MSFT0101:00 failed with error 378 [ 0.761961] ima: No TPM chip found, activating TPM-bypass! [ 0.866226] systemd[1]: systemd 252-18.el9 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) [ 55.854214] systemd[1]: systemd 252-18.el9 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) [root@xxxxxxx /]# [root@xxxxxxx /]# | ||||
Steps To Reproduce | Simply reboot with latest kernel kernel-5.14.0-362.8.1.el9_3.x86_64 | ||||
Additional Information | Other information related to "tpm_crb: probe of MSFT0101:00 failed with error 378" https://github.com/NixOS/nixpkgs/issues/250166 https://github.com/NixOS/nixpkgs/issues/251967 | ||||
Tags | No tags attached. | ||||
|
F.Y.I. - For another machine (ASUS Prime B660 D4), it was booting with AlmaLinux 9.3 with TPM 2 successfully in the past. Then, 2 days ago, I updated its BIOS from 2212 to 3010. Then, it raised the same error - "[ 0.391191] tpm_crb: probe of MSFT0101:00 failed with error 378", and need me to input the LUKS passphrase to boot it up. If I fall back to AlmaLinux 9.2 kernel, it is working fine. Thank you for your kind attention. |
|
This appears to be flagged here by Red Hat https://access.redhat.com/solutions/7057168 with a note that their bug report is private. They list the patches which need to be pulled into the 9.3 kernel to make it work with these TPMs. |
|
The 9.4 beta release has working TPM2 support for me. I've only tested a clean install, but as this is only a driver issue I don't think it would be any different if upgraded from 9.3. |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-11-14 08:30 | ccto32 | New Issue | |
2023-11-20 22:19 | alukoshko | Assigned To | => alukoshko |
2023-11-20 22:19 | alukoshko | Status | new => assigned |
2024-01-08 05:51 | ccto32 | Note Added: 0001006 | |
2024-03-25 12:21 | bsr-gb | Note Added: 0001022 | |
2024-04-16 10:56 | bsr-gb | Note Added: 0001026 |