Much longer boot time after updating to Fedora 41

Ask Fedora
, , ,
1

Hello!
I updated to Fedora 41 earlier today and noticed that my boot time had increased massively.

Been looking around a bit for a solution but not found anything really useful so far.
Probably me not knowing what I am really looking for to solve this.

Tested with both kernel version 6.11.0-63 and 6.10.11-200. Both giving the same result.

I have some output from systemd-analyze below.

rach@fedora ~ $ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @47.252s
└─multi-user.target @47.251s
  └─virtqemud.service @47.174s +76ms
    └─remote-fs.target @47.171s
      └─remote-fs-pre.target @47.170s
        └─nfs-client.target @47.170s
          └─gssproxy.service @47.102s +67ms
            └─network.target @47.098s
              └─NetworkManager.service @46.972s +124ms
                └─network-pre.target @46.969s
                  └─firewalld.service @46.314s +654ms
                    └─polkit.service @46.150s +151ms
                      └─basic.target @46.110s
                        └─dbus-broker.service @46.024s +82ms
                          └─dbus.socket @46.000s
                            └─sysinit.target @45.990s
                              └─tpm2.target @45.990s

rach@fedora ~ $ systemd-analyze blame
46.411s sys-module-fuse.device
46.363s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2\x2dpart1.device
46.363s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.0\x2dpart-by\x2dpartnum-1.device
46.363s dev-sda1.device
46.363s dev-disk-by\x2dpartuuid-bee3f864\x2d1bbb\x2d4f61\x2dafca\x2da668b157d485.device
46.363s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.0\x2dpart-by\x2dpartuuid-bee3f864\x2d1bbb\x2d4f61\x2dafca\x2da668b157d485.device
46.363s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.0\x2dpart1.device
46.363s dev-disk-by\x2did-ata\x2dSamsung_SSD_840_EVO_250GB_S1DBNSBDB29660A\x2dpart1.device
46.363s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
46.363s dev-disk-by\x2did-wwn\x2d0x50025388a0115ea2\x2dpart1.device
46.363s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.0\x2dpart-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
46.363s dev-disk-by\x2ddiskseq-1\x2dpart1.device
46.363s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda1.device
46.337s dev-disk-by\x2did-wwn\x2d0x5002538e40055e0b\x2dpart3.device
46.337s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata5-host4-target4:0:0-4:0:0:0-block-sdb-sdb3.device
46.337s dev-disk-by\x2dpartuuid-69ac539b\x2d7370\x2d45a5\x2da449\x2d147502a81957.device
46.337s dev-sdb3.device
46.337s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5\x2dpart3.device
46.337s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart3.device
46.337s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart-by\x2dpartnum-3.device
46.337s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart-by\x2dpartuuid-69ac539b\x2d7370\x2d45a5\x2da449\x2d147502a81957.device
46.337s dev-disk-by\x2ddiskseq-2\x2dpart3.device
46.337s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_500GB_S3Z2NB0K120980B\x2dpart3.device
46.312s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata2-host1-target1:0:0-1:0:0:0-block-sda.device
46.312s dev-disk-by\x2did-wwn\x2d0x50025388a0115ea2.device
46.312s dev-disk-by\x2did-ata\x2dSamsung_SSD_840_EVO_250GB_S1DBNSBDB29660A.device
46.312s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.device
46.312s dev-sda.device
46.312s dev-disk-by\x2ddiskseq-1.device
46.312s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.0.device
46.312s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5\x2dpart1.device
46.312s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
46.312s dev-disk-by\x2dpartuuid-58b80098\x2d8d48\x2d45e5\x2db121\x2de0777ea9c50b.device
46.312s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart1.device
46.312s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_500GB_S3Z2NB0K120980B\x2dpart1.device
46.312s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
46.312s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart-by\x2dpartuuid-58b80098\x2d8d48\x2d45e5\x2db121\x2de0777ea9c50b.device
46.312s dev-disk-by\x2duuid-797D\x2dBD87.device
46.312s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata5-host4-target4:0:0-4:0:0:0-block-sdb-sdb1.device
46.312s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart-by\x2duuid-797D\x2dBD87.device
46.312s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart-by\x2dpartnum-1.device
46.311s dev-disk-by\x2did-wwn\x2d0x5002538e40055e0b\x2dpart1.device
46.311s dev-disk-by\x2ddiskseq-2\x2dpart1.device
46.311s dev-sdb1.device
46.303s dev-disk-by\x2did-wwn\x2d0x5002538e40055e0b.device
46.303s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0.device
46.303s dev-disk-by\x2ddiskseq-2.device
46.303s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_500GB_S3Z2NB0K120980B.device
46.303s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.device
46.303s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata5-host4-target4:0:0-4:0:0:0-block-sdb.device
46.303s dev-sdb.device
46.266s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.0\x2dpart2.device
46.266s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.0\x2dpart-by\x2dpartnum-2.device
46.266s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
46.266s dev-disk-by\x2duuid-B88ED4F98ED4B0DC.device
46.266s dev-sda2.device
46.266s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda2.device
46.266s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.0\x2dpart-by\x2duuid-B88ED4F98ED4B0DC.device
46.266s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2\x2dpart2.device
46.266s dev-disk-by\x2ddiskseq-1\x2dpart2.device
46.266s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.0\x2dpart-by\x2dpartuuid-27ab6991\x2dd353\x2d44f8\x2d8525\x2d0bf7e4944c5b.device
46.266s dev-disk-by\x2dpartuuid-27ab6991\x2dd353\x2d44f8\x2d8525\x2d0bf7e4944c5b.device
46.266s dev-disk-by\x2did-ata\x2dSamsung_SSD_840_EVO_250GB_S1DBNSBDB29660A\x2dpart2.device
46.266s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d2.0\x2dpart-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
46.266s dev-disk-by\x2did-wwn\x2d0x50025388a0115ea2\x2dpart2.device
46.244s dev-sdb2.device
46.244s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart-by\x2dpartuuid-a86fc80a\x2d0ca9\x2d4bf6\x2d9ec8\x2df8d41f378b94.device
46.244s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_500GB_S3Z2NB0K120980B\x2dpart2.device
46.244s dev-disk-by\x2did-wwn\x2d0x5002538e40055e0b\x2dpart2.device
46.244s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata5-host4-target4:0:0-4:0:0:0-block-sdb-sdb2.device
46.244s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5\x2dpart2.device
46.244s dev-disk-by\x2dpartuuid-a86fc80a\x2d0ca9\x2d4bf6\x2d9ec8\x2df8d41f378b94.device
46.244s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart-by\x2duuid-7b31ae3a\x2d0f33\x2d40a7\x2dac7f\x2d4e369e55f441.device
46.244s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart-by\x2dpartnum-2.device
46.244s dev-disk-by\x2duuid-7b31ae3a\x2d0f33\x2d40a7\x2dac7f\x2d4e369e55f441.device
46.244s dev-disk-by\x2ddiskseq-2\x2dpart2.device
46.244s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d5.0\x2dpart2.device
46.243s dev-ttyS2.device
46.243s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
46.242s sys-devices-pnp0-00:03-00:03:0-00:03:0.0-tty-ttyS0.device
46.242s dev-ttyS0.device
46.237s dev-ttyS1.device
46.237s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
46.235s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
46.235s dev-ttyS3.device
46.219s sys-module-configfs.device
46.193s dev-disk-by\x2did-ata\x2dWDC_WD4003FZEX\x2d00Z4SA0_WD\x2dWCC5D0021101.device
46.193s dev-sdc.device
46.193s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6.device
46.193s dev-disk-by\x2ddiskseq-3.device
46.193s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sdc.device
46.193s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6.0.device
46.193s dev-disk-by\x2did-wwn\x2d0x50014ee2b425f1c9.device
46.051s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0TA15320J\x2dpart1.device
46.051s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0TA15320J_1\x2dpart1.device
46.051s dev-disk-by\x2did-nvme\x2deui.002538da21a03bf9\x2dpart1.device
46.051s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
46.051s dev-disk-by\x2dpartuuid-de1fdc2f\x2dd358\x2d4689\x2dbff4\x2d731f5b060cff.device
46.051s dev-disk-by\x2ddiskseq-4\x2dpart1.device
46.051s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-de1fdc2f\x2dd358\x2d4689\x2dbff4\x2d731f5b060cff.device
46.051s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart1.device
46.051s dev-nvme0n1p1.device
46.051s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
46.041s dev-disk-by\x2ddiskseq-5\x2dpart1.device
46.041s dev-nvme1n1p1.device
46.041s dev-disk-by\x2dpath-pci\x2d0000:1b:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
46.041s dev-disk-by\x2dpath-pci\x2d0000:1b:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-977882bb\x2dedb5\x2d43f8\x2d8e7a\x2d320bfd9bb8c5.device
46.041s dev-disk-by\x2did-nvme\x2deui.002538da21a03c18\x2dpart1.device
46.041s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0TA15351K_1\x2dpart1.device
46.041s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0TA15351K\x2dpart1.device
46.041s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.2-0000:16:04.0-0000:1b:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
46.041s dev-disk-by\x2dpath-pci\x2d0000:1b:00.0\x2dnvme\x2d1\x2dpart1.device
46.041s dev-disk-by\x2dpartuuid-977882bb\x2dedb5\x2d43f8\x2d8e7a\x2d320bfd9bb8c5.device
46.018s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0TA15320J.device
46.018s dev-disk-by\x2ddiskseq-4.device
46.018s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0TA15320J_1.device
46.018s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1.device
46.018s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1.device
46.018s dev-nvme0n1.device
46.018s dev-disk-by\x2did-nvme\x2deui.002538da21a03bf9.device
46.007s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.2-0000:16:04.0-0000:1b:00.0-nvme-nvme1-nvme1n1.device
46.007s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0TA15351K_1.device
46.007s dev-disk-by\x2dpath-pci\x2d0000:1b:00.0\x2dnvme\x2d1.device
46.007s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0TA15351K.device
46.007s dev-disk-by\x2did-nvme\x2deui.002538da21a03c18.device
46.007s dev-disk-by\x2ddiskseq-5.device
46.007s dev-nvme1n1.device
12.059s NetworkManager-wait-online.service
 4.392s dracut-initqueue.service
  909ms initrd-switch-root.service
  654ms firewalld.service
  451ms systemd-tmpfiles-setup.service
  387ms abrtd.service
  299ms user@1000.service
  248ms upower.service
  233ms udisks2.service
  225ms systemd-udev-trigger.service
  205ms smartd.service
  161ms power-profiles-daemon.service
  153ms accounts-daemon.service
  151ms polkit.service
  142ms chronyd.service
  138ms bluetooth.service
  124ms NetworkManager.service
  121ms rsyslog.service
  113ms systemd-journal-flush.service
  112ms systemd-logind.service
  108ms systemd-resolved.service
  106ms systemd-tmpfiles-setup-dev-early.service
  105ms systemd-fsck@dev-disk-by\x2duuid-7b31ae3a\x2d0f33\x2d40a7\x2dac7f\x2d4e369e55f441.service
  103ms packagekit.service
   95ms var-lib-nfs-rpc_pipefs.mount
   95ms systemd-udevd.service
   94ms ModemManager.service
   88ms switcheroo-control.service
   87ms lvm2-monitor.service
   86ms systemd-localed.service
   82ms dbus-broker.service
   77ms systemd-vconsole-setup.service
   77ms home.mount
   76ms virtqemud.service
   75ms systemd-journald.service
   74ms avahi-daemon.service
   70ms systemd-hostnamed.service
   69ms systemd-fsck@dev-disk-by\x2duuid-797D\x2dBD87.service
   68ms dev-zram0.swap
   67ms gssproxy.service
   65ms systemd-binfmt.service
   64ms cups.service
   59ms systemd-oomd.service
   59ms systemd-tmpfiles-setup-dev.service
   56ms dracut-cmdline.service
   56ms audit-rules.service
   54ms systemd-fsck@dev-disk-by\x2duuid-b1c70642\x2d234b\x2d451a\x2d8afa\x2d8461db79bc2f.service
   48ms auditd.service
   43ms rtkit-daemon.service
   43ms dracut-shutdown.service
   42ms plymouth-read-write.service
   42ms systemd-rfkill.service
   41ms boot.mount
   41ms systemd-homed.service
   38ms dracut-pre-pivot.service
   37ms systemd-network-generator.service
   37ms plymouth-switch-root.service
   36ms systemd-remount-fs.service
   36ms systemd-sysctl.service
   36ms systemd-udev-load-credentials.service
   35ms dracut-pre-udev.service
   34ms systemd-userdbd.service
   32ms initrd-udevadm-cleanup-db.service
   32ms initrd-parse-etc.service
   30ms plymouth-quit-wait.service
   30ms systemd-zram-setup@zram0.service
   30ms plymouth-quit.service
   29ms systemd-update-utmp.service
   28ms systemd-user-sessions.service
   28ms initrd-cleanup.service
   27ms dev-hugepages.mount
   27ms systemd-fsck-root.service
   26ms dev-mqueue.mount
   26ms tmp.mount
   25ms modprobe@dm_mod.service
   25ms sys-kernel-debug.mount
   25ms user-runtime-dir@1000.service
   24ms sys-kernel-tracing.mount
   24ms modprobe@configfs.service
   24ms modprobe@dm_multipath.service
   23ms modprobe@fuse.service
   23ms uresourced.service
   23ms kmod-static-nodes.service
   22ms plymouth-start.service
   22ms sys-fs-fuse-connections.mount
   22ms systemd-machined.service
   21ms modprobe@drm.service
   19ms boot-efi.mount
   19ms rpc-statd-notify.service
   18ms thermald.service
   16ms systemd-modules-load.service
   15ms proc-sys-fs-binfmt_misc.mount
   14ms systemd-random-seed.service
   10ms systemd-sysusers.service
    9ms systemd-update-utmp-runlevel.service
    8ms modprobe@efi_pstore.service
    7ms modprobe@loop.service
  114us systemd-homed-activate.service
2

What is on nvme1n1 partition? Please show output of lsblk -f.

3

I have a LVM partition over 3 SSDs which is what’s on nvme1n1.

Here is the output:

rach@fedora ~ $ lsblk -f
NAME                 FSTYPE      FSVER    LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                   
├─sda1                                                                                                
└─sda2               ntfs                       B88ED4F98ED4B0DC                                      
sdb                                                                                                   
├─sdb1               vfat        FAT32          797D-BD87                               591,3M     1% /boot/efi
├─sdb2               ext4        1.0            7b31ae3a-0f33-40a7-ac7f-4e369e55f441    495,4M    42% /boot
└─sdb3               LVM2_member LVM2 001       465jVX-c0Oe-eo3v-zB2k-ufip-h4H9-CKVA4j                
  ├─fedora_data-root ext4        1.0            572ccbdc-ee1b-42e4-bb24-7b74798a46ce     52,8G    41% /
  └─fedora_data-home ext4        1.0            b1c70642-234b-451a-8afa-8461db79bc2f    334,5G    80% /home
sdc                                                                                                   
zram0                                                                                                 [SWAP]
nvme0n1                                                                                               
└─nvme0n1p1          LVM2_member LVM2 001       KHliy9-ZmTv-eRrs-371B-sfLK-Bspx-vKiBXk                
  └─fedora_data-home ext4        1.0            b1c70642-234b-451a-8afa-8461db79bc2f    334,5G    80% /home
nvme1n1                                                                                               
└─nvme1n1p1          LVM2_member LVM2 001       lUIAdE-voRK-mQlW-edpV-CDud-Ixdt-OfeVWl                
  ├─fedora_data-root ext4        1.0            572ccbdc-ee1b-42e4-bb24-7b74798a46ce     52,8G    41% /
  └─fedora_data-home ext4        1.0            b1c70642-234b-451a-8afa-8461db79bc2f    334,5G    80% /home

There is 2 more drives that is currently not used (old windows drive and a empty HDD)

4

I am not seeing anything stand out as strange yet.

What is in your /etc/fstab?

5

I haven’t seen anything stand out either while I was looking.

This is fstab:

UUID=572ccbdc-ee1b-42e4-bb24-7b74798a46ce /                       ext4    defaults        1 1
UUID=7b31ae3a-0f33-40a7-ac7f-4e369e55f441 /boot                   ext4    defaults        1 2
UUID=797D-BD87          /boot/efi               vfat    umask=0077,shortname=winnt 0 2
UUID=b1c70642-234b-451a-8afa-8461db79bc2f /home                   ext4    defaults        1 2

Same one that I have had since I installed Fedora back in January

6

I think I have found something.
It seems to timeout while waiting for dev-tpmrm0.device

okt 01 19:00:47 fedora systemd[1]: Reached target initrd-fs.target - Initrd File Systems.
okt 01 19:00:47 fedora systemd[1]: dracut-mount.service - dracut mount hook was skipped because no trigger condition checks were met.
okt 01 19:01:27 fedora systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start timed out.
okt 01 19:01:27 fedora systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
okt 01 19:01:27 fedora systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start failed with result 'timeout'.
okt 01 19:01:27 fedora systemd[1]: Reached target tpm2.target - Trusted Platform Module.
okt 01 19:01:27 fedora systemd[1]: systemd-pcrphase-initrd.service - TPM PCR Barrier (initrd) was skipped because of an unmet condition check (Cond>
okt 01 19:01:27 fedora systemd[1]: Reached target sysinit.target - System Initialization.
okt 01 19:01:27 fedora systemd[1]: Reached target basic.target - Basic System.

So somehow my tpm module isn’t recognized?

7

Added boot, dracut, networkmanager

8

I read those logs from 0->1 am I wrong here?

So networkmanager waited a loong time until it was online. The break between it and the NVME thing.

Dracut was also kinda long so tagged that too. Might be normal.

9

I just tried turning my fTPM off and it booted as normal in 15ish seconds.
Seems something changed between 40 and 41 that does not really play well with AMDs fTPM system on my motherboard.

10

NM took 12s to come on line, likely device coming on line and then DHCP.
Then 30+s to get the disk mounted.

11

Okay so the status message appears once a process is ready? Then yes, networkmanager took long but the disk is the issue

12

Is there anything additional in journalctl -b -k -g "tpm"

13

Just got home, here is the output:

rach@fedora ~ $ journalctl -b -k -g "tpm"
okt 02 19:39:53 fedora kernel: efi: TPMFinalLog=0xdd990000 ACPI 2.0=0xdd926000 ACPI=0xdd926000 SMBIOS=0xde473000 ESRT=0xdae56998 MEMATTR=0xd8ba1698 MOKvar=0xde47c000 RNG=0xdd484018 TPMEventLog=0xca1c8018 
okt 02 19:39:53 fedora kernel: ACPI: TPM2 0x00000000DD93C5C8 000034 (v04 ALASKA A M I    00000001 AMI  00000000)
okt 02 19:39:53 fedora kernel: ACPI: Reserving TPM2 table memory at [mem 0xdd93c5c8-0xdd93c5fb]
okt 02 19:39:53 fedora kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xdd9c0000-0xdd9c0fff flags 0x200] vs dd9c0000 4000
okt 02 19:39:53 fedora kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0xdd9c0000-0xdd9c0fff]
okt 02 19:39:53 fedora kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
okt 02 19:39:53 fedora kernel: ima: No TPM chip found, activating TPM-bypass!
okt 02 19:39:53 fedora systemd[1]: systemd 256.6-1.fc41 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>
okt 02 19:39:53 fedora systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0...
okt 02 17:40:39 fedora systemd[1]: systemd 256.6-1.fc41 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>
okt 02 17:40:39 fedora systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0...
14

I believe there is a systemd startup service that is waiting for tpm to generate some random key, i’m not sure for what purpose. I’ve noticed on my system before that it appears to keep some runlevel target waiting as long as it’s not finished. Might be interesting to look into further.

Here it is on my F40 boot chart:

image
image1657×1338 588 KB