Slow boot on Thinkpad T470

indianahorst · 2025-10-21 20:48:42

Hello everyone,

as the title says, my Thinkpad T470 (16 GB RAM, 500 GB SSD) is booting a little bit slow. Boot loader is systemd-boot, I'm using the default LTS kernel, LUKS-encrypted root and home partition, Display Manager is lxdm.

Here the relevant systemd-analyze logs:

$ systemd-analyze
Startup finished in 13.639s (firmware) + 4.723s (loader) + 940ms (kernel) + 11.685s (initrd) + 8.877s (userspace) = 39.865s 
graphical.target reached after 8.231s in userspace.

$ systemd-analyze blame
13.281s sys-devices-pci0000:00-0000:00:14.0-usb2-2\x2d3-2\x2d3:1.0-host0-target0:0:0-0:0:0:0-block-sda.device
13.281s dev-disk-by\x2dpath-pci\x2d0000:00:14.0\x2dusbv3\x2d0:3:1.0\x2dscsi\x2d0:0:0:0.device
13.281s dev-disk-by\x2dpath-pci\x2d0000:00:14.0\x2dusb\x2d0:3:1.0\x2dscsi\x2d0:0:0:0.device
13.281s dev-sda.device
13.281s dev-disk-by\x2ddiskseq-3.device
13.280s dev-disk-by\x2did-usb\x2dGeneric\x2d_SD_MMC_20120501030900000\x2d0:0.device
12.063s dev-ttyS3.device
12.063s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
12.046s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
12.046s dev-ttyS1.device
12.026s dev-ttyS0.device
12.026s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
12.024s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
12.024s dev-ttyS2.device
12.008s sys-module-fuse.device
12.006s sys-module-configfs.device
11.741s sys-devices-pci0000:00-0000:00:1f.6-ptp-ptp0.device
11.741s dev-ptp0.device
11.547s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-EFIBOOT.device
11.547s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart1.device
11.547s dev-disk-by\x2ddiskseq-1\x2dpart1.device
11.547s dev-disk-by\x2ddesignator-esp.device
11.547s dev-nvme0n1p1.device
11.547s sys-devices-pci0000:00-0000:00:1d.2-0000:3e:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
11.547s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-102C\x2dB6C6.device
11.547s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HAJQ\x2d000L7_S3TNNE0J914080\x2dpart1.device
11.547s dev-disk-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
11.547s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HAJQ\x2d000L7_S3TNNE0J914080_1\x2dpart1.device
11.547s dev-disk-by\x2did-nvme\x2deui.0025388971005f54\x2dpart1.device
11.547s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
11.547s dev-disk-by\x2duuid-102C\x2dB6C6.device
11.547s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
11.547s dev-disk-by\x2dpartuuid-9c3c3a83\x2d673a\x2d44b3\x2d9587\x2d324b9e80c812.device
11.547s dev-disk-by\x2dlabel-EFIBOOT.device
11.547s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-9c3c3a83\x2d673a\x2d44b3\x2d9587\x2d324b9e80c812.device
11.538s dev-nvme0n1p3.device
11.538s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-88922F31922F22E4.device
11.538s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
11.538s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HAJQ\x2d000L7_S3TNNE0J914080_1\x2dpart3.device
11.538s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
11.538s dev-disk-by\x2dpartuuid-ab192d60\x2d443d\x2d42e2\x2d90c2\x2d705bf49c9dd9.device
11.538s dev-disk-by\x2did-nvme\x2deui.0025388971005f54\x2dpart3.device
11.538s dev-disk-by\x2duuid-88922F31922F22E4.device
11.538s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-ab192d60\x2d443d\x2d42e2\x2d90c2\x2d705bf49c9dd9.device
11.538s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
11.538s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-Windows.device
11.538s dev-disk-by\x2ddiskseq-1\x2dpart3.device
11.538s sys-devices-pci0000:00-0000:00:1d.2-0000:3e:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
11.538s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HAJQ\x2d000L7_S3TNNE0J914080\x2dpart3.device
11.538s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart3.device
11.538s dev-disk-by\x2dlabel-Windows.device
11.535s sys-devices-pci0000:00-0000:00:1d.2-0000:3e:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
11.535s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart4.device
11.535s dev-disk-by\x2dpartuuid-9470f8da\x2d90e5\x2d49a7\x2d8f8b\x2d90d1a9ec7918.device
11.535s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-9470f8da\x2d90e5\x2d49a7\x2d8f8b\x2d90d1a9ec7918.device
11.535s dev-disk-by\x2ddiskseq-1\x2dpart4.device
11.535s dev-disk-by\x2dlabel-WinRE_DRV.device
11.535s dev-nvme0n1p4.device
11.534s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HAJQ\x2d000L7_S3TNNE0J914080_1\x2dpart4.device
11.534s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-WinRE_DRV.device
11.534s dev-disk-by\x2did-nvme\x2deui.0025388971005f54\x2dpart4.device
11.534s dev-disk-by\x2dpath-pci\x2d0000:3e:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-4.device
lines 1-62

$ 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 @8.231s
└─multi-user.target @8.231s
  └─sshd.service @8.170s +59ms
    └─network.target @8.163s
      └─wpa_supplicant.service @8.725s +42ms
        └─basic.target @7.286s
          └─dbus-broker.service @7.180s +65ms
            └─dbus.socket @7.173s +86us
              └─sysinit.target @7.168s
                └─systemd-update-utmp.service @7.114s +53ms
                  └─systemd-tmpfiles-setup.service @6.962s +147ms
                    └─local-fs.target @6.951s
                      └─home.mount @6.907s +43ms
                        └─systemd-fsck@dev-mapper-crypthome.service @6.831s +70ms
                          └─dev-mapper-crypthome.device @6.829s

If anyone wonders, sda.device is the integrated SD card reader (empty). I already tried to disable it in BIOS, but it didn't make a difference.

Here the bootloader file /boot/loader/entries/arch-lts.conf:

title Arch Linux LTS Kernel (sd-encrypt)
linux /vmlinuz-linux-lts
initrd /intel-ucode.img
initrd /initramfs-linux-lts.img
options rd.luks.name=<UUID>=cryptroot root=/dev/mapper/cryptroot rd.luks.options=discard quiet loglevel=3 systemd.show_status=auto rd.udev.log_level=3 rd.systemd.gpt_auto=0 rw

and the HOOKS line in /etc/mkinitcpio.conf:

HOOKS=(systemd keyboard autodetect microcode modconf sd-vconsole block sd-encrypt filesystems numlock fsck)

I'm wondering about the myriads of *.device paths in systemd-analyze blame, I don't have a clue where this comes from. The other thing I'm wondering about are the tty*.device entries.

Where do I have to change my configuration to release the brakes of my boot process?
Thank you for your attention!

seth · 2025-10-22 08:22:47

I'm wondering about the myriads of *.device paths in systemd-analyze blame

HOOKS=(systemd

?

If you're looking at a wall clock: how long does it take from entering the LUKS password until you see lxdm?

indianahorst · 2025-10-22 11:40:08

seth wrote:

I'm wondering about the myriads of *.device paths in systemd-analyze blame
HOOKS=(systemd
?

What are you wondering about here?

seth wrote:

If you're looking at a wall clock: how long does it take from entering the LUKS password until you see lxdm?

Last boot:

$ systemd-analyze 
Startup finished in 13.571s (firmware) + 9.720s (loader) + 949ms (kernel) + 14.709s (initrd) + 9.034s (userspace) = 47.985s 
graphical.target reached after 8.309s in userspace.

The timespan from hitting Enter after entering the LUKS password until LXDM starts was around 15s, so it is coherent with the initrd time from above.

seth · 2025-10-22 12:06:55

The "myriads of *.device paths in systemd-analyze blame" most likey come from using systemd instead of udev/busybox and are likely an artifact of how it configures the partitions.
You're spending 8-9s in the userspace but 2/3 of that are *before* dev-mapper-crypthome.device (the first entry in your blame)
Let's see what's actually going on: Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

indianahorst · 2025-10-22 19:15:00

Here it is:
https://0x0.st/Kenl.txt

seth · 2025-10-22 19:49:07

Oct 22 13:23:45 archlinux kernel: Linux version 6.12.53-1.1-lts (linux-lts@archlinux) (gcc (GCC) 15.2.1 20250813, GNU ld (GNU Binutils) 2.45.0) #1 SMP PREEMPT_DYNAMIC Fri, 17 Oct 2025 10:14:19 +0000
…
Oct 22 13:23:48 archlinux kernel: hid-generic 0003:05E3:0102.0004: hiddev97,hidraw3: USB HID v1.01 Device [USB_HID_DEVICE] on usb-0000:0a:00.0-1.3.3.4/input0
Oct 22 13:23:57 archlinux systemd-tty-ask-password-agent[169]: Password query on /dev/tty1 finished successfully.
Oct 22 13:23:57 archlinux systemd-cryptsetup[165]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/disk/by-uuid/ed3b5aee-0203-4a90-a6d4-fdffa2ce32ca.
Oct 22 13:23:59 archlinux kernel: Key type encrypted registered
Oct 22 13:23:59 archlinux systemd[1]: Found device /dev/mapper/cryptroot.
Oct 22 13:23:59 archlinux systemd[1]: Finished Cryptography Setup for cryptroot.
Oct 22 13:23:59 archlinux systemd[1]: Reached target Local Encrypted Volumes.
Oct 22 13:23:59 archlinux systemd[1]: Reached target Initrd Root Device.
Oct 22 13:23:59 archlinux systemd[1]: Reached target System Initialization.
…
Oct 22 13:24:08 zeus systemd[1]: Started LXDE Display Manager.
…
Oct 22 13:24:11 zeus root[1695]: ACPI group/action undefined: jack/videoout / VIDEOOUT
Oct 22 13:24:11 zeus NetworkManager[1251]: <info>  [1761132251.7585] manager: rfkill: Wi-Fi now enabled by radio killswitch
Oct 22 13:24:14 zeus NetworkManager[1251]: <info>  [1761132254.5754] manager: startup complete
Oct 22 13:24:19 zeus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 22 13:24:19 zeus dbus-broker-launch[1249]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Oct 22 13:24:19 zeus lxdm-session[1746]: gkr-pam: unable to locate daemon control file
Oct 22 13:24:19 zeus lxdm-session[1746]: gkr-pam: stashed password to try later in open session
Oct 22 13:24:19 zeus lxdm-session[1746]: pam_unix(lxdm:session): session opened for user jascha(uid=1000) by jascha(uid=0)
Oct 22 13:24:20 zeus systemd-logind[1257]: New session '1' of user 'jascha' with class 'user' and type 'x11'.

System boots normally fast until you reach tty-ask-password-agent and I guess the following gap is entirely down to you entering the password?
Then takes another 9s to start LXDM and I assume the following 12s are likewise dominated by you entering the password etc.

The most interesting part is between

Oct 22 13:23:59 archlinux systemd[1]: Reached target System Initialization.
…
Oct 22 13:24:08 zeus systemd[1]: Started LXDE Display Manager.

because there're no obvious stalls - the log just moves w/ glacial speed.

Oct 22 13:23:57 archlinux systemd-cryptsetup[165]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/disk/by-uuid/ed3b5aee-0203-4a90-a6d4-fdffa2ce32ca.
Oct 22 13:24:01 zeus systemd-cryptsetup[341]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/disk/by-uuid/2783fd2a-da36-45f3-a5db-d82618a34e04.

https://wiki.archlinux.org/title/Dm-cry … etup_usage
Check the benchmark.

I'd love to blame intel-undervolt (because it would be an easy explanation), but that starts only afterwards

Arch Linux

#1 2025-10-21 20:48:42

Slow boot on Thinkpad T470

#2 2025-10-22 08:22:47

Re: Slow boot on Thinkpad T470

#3 2025-10-22 11:40:08

Re: Slow boot on Thinkpad T470

#4 2025-10-22 12:06:55

Re: Slow boot on Thinkpad T470

#5 2025-10-22 19:15:00

Re: Slow boot on Thinkpad T470

#6 2025-10-22 19:49:07

Re: Slow boot on Thinkpad T470

Board footer