You are not logged in.

#1 2024-06-12 12:07:25

FwuffFox
Member
Registered: 2024-06-12
Posts: 2

[SOLVED] Boot process slowdown because of /dev/tpmrm0 start job.

Hello! After recent update of the system I started getting this problem. Because of this job starting, I gave to wait extra minute during boot before it times out. It persisted for a few days already, and I never had problems with that thing before. I think that systemd tries to use my tpm module, but as I understand I don't even have one in my machine. (Using `cat /sys/class/tpm/tpm*/tpm_version_major` from ArchWiki yields no result.)

I guess I just need to disable it, but I didn't find any configs related to this.

journalctl -b --grep=tpm

Jun 12 14:49:08 ArchFwuff kernel: efi: TPMFinalLog=0xcd961000 ESRT=0xce606218 ACPI=0xcd0f0000 ACPI 2.0=0xcd0f0000 SMBIOS=0xce54e000 SMBIOS 3.0=0xce54d000 RNG=0xcca8af98 INITRD=0xc6551e18 TPMEventLog=0xc4993018 
Jun 12 14:49:08 ArchFwuff kernel: ACPI: TPM2 0x00000000CD10F870 000034 (v03        Tpm2Tabl 00000001 AMI  00000000)
Jun 12 14:49:08 ArchFwuff kernel: ACPI: Reserving TPM2 table memory at [mem 0xcd10f870-0xcd10f8a3]
Jun 12 14:49:08 ArchFwuff kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xcd958000-0xcd958fff flags 0x200] vs cd958000 4000
Jun 12 14:49:08 ArchFwuff kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xcd958000-0xcd958fff]
Jun 12 14:49:08 ArchFwuff kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
Jun 12 14:49:29 ArchFwuff systemd[1]: systemd 256-1-arch-g5c79cde^ running in system mode (+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP -SYSVINIT +LIBARCHIVE)
Jun 12 14:49:36 ArchFwuff systemd[1]: Expecting device /dev/tpmrm0...
Jun 12 14:51:06 ArchFwuff systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start timed out.
Jun 12 14:51:06 ArchFwuff systemd[1]: Timed out waiting for device /dev/tpmrm0.
Jun 12 14:51:06 ArchFwuff systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start failed with result 'timeout'.
Jun 12 14:51:06 ArchFwuff systemd[1]: Listening on TPM PCR Measurements.
Jun 12 14:51:06 ArchFwuff systemd[1]: Listening on Make TPM PCR Policy.
Jun 12 14:51:06 ArchFwuff systemd[1]: Starting TPM PCR Machine ID Measurement...
Jun 12 14:51:06 ArchFwuff systemd[1]: Starting Early TPM SRK Setup...
Jun 12 14:51:06 ArchFwuff systemd-pcrextend[783]: No complete TPM2 support detected, exiting gracefully.
Jun 12 14:51:06 ArchFwuff systemd[1]: Finished TPM PCR Machine ID Measurement.
Jun 12 14:51:06 ArchFwuff systemd-tpm2-setup[784]: No complete TPM2 support detected, exiting gracefully.
Jun 12 14:51:06 ArchFwuff systemd[1]: Finished Early TPM SRK Setup.
Jun 12 14:51:06 ArchFwuff systemd[1]: Starting TPM SRK Setup...
Jun 12 14:51:06 ArchFwuff systemd-tpm2-setup[787]: No complete TPM2 support detected, exiting gracefully.
Jun 12 14:51:06 ArchFwuff systemd[1]: Finished TPM SRK Setup.
Jun 12 14:51:06 ArchFwuff systemd[1]: Starting TPM PCR Barrier (Initialization)...
Jun 12 14:51:06 ArchFwuff systemd-pcrextend[790]: No complete TPM2 support detected, exiting gracefully.
Jun 12 14:51:06 ArchFwuff systemd[1]: Finished TPM PCR Barrier (Initialization).
Jun 12 14:51:07 ArchFwuff systemd[1]: Starting TPM PCR Barrier (User)...
Jun 12 14:51:07 ArchFwuff systemd-pcrextend[798]: No complete TPM2 support detected, exiting gracefully.
Jun 12 14:51:07 ArchFwuff systemd[1]: Finished TPM PCR Barrier (User).
sudo dmesg -k | grep tpm

[    0.490436] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xcd958000-0xcd958fff flags 0x200] vs cd958000 4000
[    0.490455] tpm_crb MSFT0101:00: can't request region for resource [mem 0xcd958000-0xcd958fff]
[    0.490462] tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16

Any help appreciated smile

Last edited by FwuffFox (2024-06-17 13:29:57)

Offline

#2 2024-06-17 13:29:40

FwuffFox
Member
Registered: 2024-06-12
Posts: 2

Re: [SOLVED] Boot process slowdown because of /dev/tpmrm0 start job.

Solved by masking tmp2.target.

Offline

#3 2024-06-18 19:09:01

redqueen
Member
Registered: 2024-06-18
Posts: 2

Re: [SOLVED] Boot process slowdown because of /dev/tpmrm0 start job.

hi! i'm having the same issue, what command did you run to fix? i have no idea what i'm doing when it comes to systemd

Offline

#4 2024-06-18 19:24:59

redqueen
Member
Registered: 2024-06-18
Posts: 2

Re: [SOLVED] Boot process slowdown because of /dev/tpmrm0 start job.

nvm, fixed with

systemctl mask dev-tpmrm0.device

Offline

#5 2024-06-18 22:13:51

SoundOfE
Member
Registered: 2024-05-11
Posts: 11

Re: [SOLVED] Boot process slowdown because of /dev/tpmrm0 start job.

FwuffFox wrote:

Solved by masking tmp2.target.

Typo: tpm2, not tmp2 smile

I'm very thankful for your comment, this did the trick for me!

Offline

#6 2024-06-24 17:42:16

thorrrr
Member
From: UK
Registered: 2023-05-30
Posts: 2

Re: [SOLVED] Boot process slowdown because of /dev/tpmrm0 start job.

Sorry for the noob follow-up question is this really a fix or are we masking the error (excuse the pun)?

>>> sudo dmesg -k | grep tpm                                                                                                                                   19:03.56 Mon Jun 24 2024 >>>
[sudo] password for xxxx:
[    1.204257] tpm_tis MSFT0101:00: probe with driver tpm_tis failed with error -1

Last edited by thorrrr (2024-06-24 18:05:11)

Offline

#7 2024-06-25 02:45:25

014
Member
Registered: 2015-11-11
Posts: 7

Re: [SOLVED] Boot process slowdown because of /dev/tpmrm0 start job.

I also ran into this big drag of a boot time after some updates on one of my machines. I looked at the systemctl manual and searched for "mask" to find the answer to above question:

>Completely disabled, so any start operation on it fails (permanently in /etc/systemd/system/ or transiently in /run/systemd/systemd/).

In short, it's similar to disabling a systemd service, but "disable" does not work in this case.

Offline

Board footer

Powered by FluxBB