Slow Boot Time

Za Fyuri · 2024-08-09 22:16:18

Machine : Lenovo Thinkpad x13 Gen 1
CPU : AMD Ryzen™ 3 PRO 4450U with Radeon™ Graphics × 8

Hi All, Apologies if this has been posted in here before I am facing an issue that I do not understand would like to learn how to fix. I've installed a fresh copy of Arch onto my thinkpad but for a reason I do not understand, the boot time is not very fast. In comparison my x270 booted far quicker into Arch that this laptop.
As per the systemd-analyze you can see that boot time is taking nearly a minute:

systemd-analyze
Startup finished in 13.767s (firmware) + 3.333s (loader) + 33.079s (kernel) + 3.511s (userspace) = 53.692s 
graphical.target reached after 3.510s in userspace.

I added the systemd-analyze critical-chain as well:

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 @3.510s
└─gdm.service @3.473s +36ms
  └─systemd-user-sessions.service @3.428s +38ms
    └─network.target @3.425s
      └─wpa_supplicant.service @3.363s +60ms
        └─basic.target @2.436s
          └─dbus-broker.service @2.391s +40ms
            └─dbus.socket @2.379s
              └─sysinit.target @2.373s
                └─systemd-timesyncd.service @2.312s +59ms
                  └─systemd-tmpfiles-setup.service @2.196s +110ms
                    └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @2.243s

I've pulled a log: http://0x0.st/XWPA.txt

I've read other comments to try and get and understanding/attempt fixes but I am at a loss. Barring stopping services, I am not sure what else I should be doing.
I would like to understand why the boot is taking so long, any help/guidance would be appreciated. Thank you.

seth · 2024-08-09 23:16:00

Define "boot" and "slow" - it takes ~3s until GDM starts, then ~17s until you login.
Most time of the boot is spent in firmware (UEFI, 14s) and the kernel (33s, which seems excessive and could point towards issues w/ your nvme)

At what point exactly does the boot stall for about how long by your concern?

Za Fyuri · 2024-08-10 11:40:34

seth wrote:

Define "boot" and "slow" - it takes ~3s until GDM starts, then ~17s until you login.
Most time of the boot is spent in firmware (UEFI, 14s) and the kernel (33s, which seems excessive and could point towards issues w/ your nvme)
At what point exactly does the boot stall for about how long by your concern?

Once the system boots, its display an warning:

Aug 10 11:35:51 archnomad kernel: amdgpu 0000:06:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
Aug 10 11:35:51 archnomad kernel: amdgpu 0000:06:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
Aug 10 11:35:51 archnomad kernel: amdgpu 0000:06:00.0: amdgpu: Secure display: Generic Failure.
Aug 10 11:35:51 archnomad kernel: amdgpu 0000:06:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0

After this message it will take roughly 20/30 seconds for the system to boot. From my understanding the warning above can be ignored.
It used to boot quicker, I am trying to understand if something has changed for it to boot slower.

If the NVME is on the way out, I will grab another one and install that but I want to confirm this before doing so.
Your help is appreciated and apologies if this question has annoyed you in anyway. I am trying to learn and understand things. Thank you.

seth · 2024-08-10 17:49:38

Try to boot the multi-user.target (2nd link below) - are there any delays?
GDM should™ be up after 4s-6s, but there's some wifi related delay before you log in.

Za Fyuri · 2024-08-10 21:43:11

seth wrote:

Try to boot the multi-user.target (2nd link below) - are there any delays?
GDM should™ be up after 4s-6s, but there's some wifi related delay before you log in.

After the warning message, similar delay before GDM pops up. Please let me know if you need me to pull any logs.

seth · 2024-08-10 21:51:05

GDM should not "pop up" at all when booting the multi-user.target, you're ending w/ an agetty login.

Za Fyuri · 2024-08-10 22:08:32

seth wrote:

GDM should not "pop up" at all when booting the multi-user.target, you're ending w/ an agetty login.

Apologies, it was agetty but I didn't know the correct terminology so I said GDM. It was agetty and it took 47 seconds.

Link: https://imgur.com/a/pdvxU1a

Sorry for the bad quality image.

Last edited by Za Fyuri (2024-08-11 20:34:50)

seth · 2024-08-11 08:28:46

Don't be sorry, but please replace the oversized image w/ a link and post the journal for that boot instead.
Eg.

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

for the previous ("-1") one.

Za Fyuri · 2024-08-11 20:40:22

seth wrote:

Don't be sorry, but please replace the oversized image w/ a link and post the journal for that boot instead.
Eg.
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st
for the previous ("-1") one.

Please find the journal as requested: https://0x0.st/XWf6.txt. Thank you for the guidance.

seth · 2024-08-11 22:25:25

Aug 11 22:36:05 archnomad kernel: Command line: initrd=\initramfs-linux.img root=PARTUUID=3ad8c5c1-e59d-42bc-90e2-da069b59b3d7 zswap.enabled=0 rw rootfstype=ext4
…
Aug 11 22:36:12 archnomad systemd-logind[500]: New session 1 of user nomad.

7 seconds, getty starts after 2 - if there's something slow it's the bootloader loading the kernel.
But that doesn't add up w/ the message suggested in #3 showing up *before* the delay.

Do you use a booltloader like grub or an UKI booted by the UEFI directly?

Za Fyuri · 2024-08-12 20:58:51

seth wrote:

Aug 11 22:36:05 archnomad kernel: Command line: initrd=\initramfs-linux.img root=PARTUUID=3ad8c5c1-e59d-42bc-90e2-da069b59b3d7 zswap.enabled=0 rw rootfstype=ext4
…
Aug 11 22:36:12 archnomad systemd-logind[500]: New session 1 of user nomad.
7 seconds, getty starts after 2 - if there's something slow it's the bootloader loading the kernel.
But that doesn't add up w/ the message suggested in #3 showing up *before* the delay.
Do you use a booltloader like grub or an UKI booted by the UEFI directly?

I use systemd and no other bootloader.

I ran efibootmgr and got the following information:

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0010,0011,0012,0013,0014,0017,0018,0019,001A,001B,001C,001D,0001
Boot0000* Linux Boot Manager	HD(1,GPT,c972a07f-993c-4699-9833-6865471547a2,0x800,0x200000)/\EFI\systemd\systemd-bootx64.efi
Boot0001* Linux-Firmware-Updater	HD(1,GPT,c972a07f-993c-4699-9833-6865471547a2,0x800,0x200000)/\EFI\arch\fwupdx64.efi
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics	FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  ThinkShield secure wipe	FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
Boot0015  Startup Interrupt Menu	FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0016  Rescue and Recovery	FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0017  USB CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018  USB FDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019* NVMe0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001A  ATA HDD0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001B* USB HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot001C  PXE BOOT	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot001D  Regulatory Information	FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
Boot001E* Boot Next Boot Option	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,a7ca6d35b2c2684783721826a7404894)

Let me me know if this is relevant.

Last edited by Za Fyuri (2024-08-12 21:07:48)

seth · 2024-08-12 21:46:27

I use systemd and no other bootloader.

systemd isn't a bootloader, but systemd-boot is (it's a completely different thing, only clogged up w/ the rest of systemd-stuff in the same package)
Please post its configurations, https://wiki.archlinux.org/title/System … figuration

Za Fyuri · 2024-08-13 07:18:51

seth wrote:

I use systemd and no other bootloader.
systemd isn't a bootloader, but systemd-boot is (it's a completely different thing, only clogged up w/ the rest of systemd-stuff in the same package)
Please post its configurations, https://wiki.archlinux.org/title/System … figuration

I found the loader.conf in the following path:

boot/loader/loader.conf

It contains the following information:

timeout 3
#console-mode keep

Please let me know if you need any other information.

seth · 2024-08-13 07:30:14

So you don't have entries for any actual boots?

Za Fyuri · 2024-08-13 07:53:57

seth wrote:

So you don't have entries for any actual boots?

I've checked my pc and this does seem to be the case. My main machine runs EndeavourOS and the loader.conf shows the following:

default e55dfafb06cf4d42b86f4f513b9bdcb0*
timeout 5
console-mode auto
reboot-for-bitlocker 1

Whereas what I provided you in my previous post looks to be missing the default. I am not sure how this has happened, I used archinstall and made sure I selected all the options as advised.

I've run bootctl list and got the following information:

         type: Boot Loader Specification Type #1 (.conf)
        title: Arch Linux (linux) (default) (selected)
           id: 2024-07-23_19-55-51_linux.conf
       source: /boot//loader/en
tries/2024-07-23_19-55-51_linux.conf
        linux: /boot//vmlinuz-linux
       initrd: /boot//initramfs-linux.img
      options: root=PARTUUID=3ad8c5c1-e59d-42bc-90e2-da069b59b3d7 zswap.enabled=0 rw rootfstype=ext4

         type: Boot Loader Specification Type #1 (.conf)
        title: Arch Linux (linux-fallback)
           id: 2024-07-23_19-55-51_linux-fallback.conf
       source: /boot//
loader/entries/2024-07-23_19-55-51_linux-fallback.conf
        linux: /boot//vmlinuz-linux
       initrd: /boot//initramfs-linux-fallback.img
      options: root=PARTUUID=3ad8c5c1-e59d-42bc-90e2-da069b59b3d7 zswap.enabled=0 rw rootfstype=ext4

         type: Automatic
        title: Reboot Into Firmware Interface
           id: auto-reboot-to-firmware-setup
       source: /sys/firmware/efi/efivars/LoaderEntries-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

seth · 2024-08-13 14:51:25

So "/boot//loader/entries/2024-07-23_19-55-51_linux.conf" actually does exist??
How long does the boot take for

systemctl reboot --boot-loader-entry=2024-07-23_19-55-51_linux.conf

Za Fyuri · 2024-08-13 15:23:34

Please find the information below:

systemd-analyze:

Startup finished in 8.369s (firmware) + 2.367s (loader) + 34.317s (kernel) + 2.449s (userspace) = 47.503s 
graphical.target reached after 2.445s in userspace.

systemd-analyze critical-chain:

graphical.target @2.445s
└─gdm.service @2.386s +56ms
  └─systemd-user-sessions.service @2.335s +44ms
    └─network.target @2.330s
      └─NetworkManager.service @1.987s +340ms
        └─basic.target @1.983s
          └─dbus-broker.service @1.902s +75ms
            └─dbus.socket @1.886s
              └─sysinit.target @1.877s
                └─systemd-timesyncd.service @1.780s +95ms
                  └─systemd-tmpfiles-setup.service @1.657s +118ms
                    └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @1.666s

Yes, the file does exist: https://imgur.com/a/2Oe1yBG

seth · 2024-08-13 19:11:14

"systemd-analyze critical-chain" won't tell us anything here, the problem happens before the system actually boots.

lsblk -f

What if you change the bootloader entry to use the UUID instead of the PARTUUID?
Do you have secure boot enabled?

Za Fyuri · 2024-08-13 21:22:38

Secure boot is not enabled and https://0x0.st/X4r6.txt

Do you think a new hard drive may solve the issue or is this a software issue? I apologise for killing so much of your time with this. I appreciate the help and guidance.

seth · 2024-08-13 22:11:52

Aug 13 23:05:03 archnomad kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

There's no indication of any IO errors in the journal, if it's not the corrupted filesystem, try to reference the partition via its UUID instead of the PARTUUID

Za Fyuri · 2024-08-14 18:20:21

seth wrote:

Aug 13 23:05:03 archnomad kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
There's no indication of any IO errors in the journal, if it's not the corrupted filesystem, try to reference the partition via its UUID instead of the PARTUUID

Sorry for the delayed response. I will do what you've advised and let you know what happens.

Za Fyuri · 2024-08-17 21:31:59

I wanted to provide an update regarding this issue where I am with it. I've managed to bring the boot times down to 25 seconds max. There is a minor fluctuation of about 10 seconds, Max is 25 seconds - Low is about 15 seconds, give or take depending on the boot:

Startup finished in 8.021s (firmware) + 163ms (loader) + 10.909s (kernel) + 2.537s (userspace) = 21.631s 
graphical.target reached after 2.535s in userspace.

Turns out that trying to fix the xhci controller error and added the following package to the system: https://aur.archlinux.org/packages/upd72020x-fw has helped to bring the boot times down.
I've got one more warning to understand and fix:

ug 17 23:17:21 archnomad kernel: xhci_hcd 0000:05:00.0: Timeout for Set DATAX step: 34
Aug 17 23:17:21 archnomad kernel: xhci_hcd 0000:05:00.0: ROM Download Step 34 failed at position 136 bytes with (-110)

I've found an old link where advice was given on how to fix it: https://bbs.archlinux.org/viewtopic.php?id=281751
I need to review and understand this, try to apply what has been advised and see if it fixes the issue.

Thank you for your help and sorry for the delayed response.

seth · 2024-08-17 23:06:30

https://bbs.archlinux.org/viewtopic.php … 5#p2190005 was apparently related to xhci issues, but caused longer delays and in userspace - maybe still worth a shot. Have you already updated to 6.10.5 ?

Za Fyuri · 2024-08-20 15:36:20

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 5#p2190005 was apparently related to xhci issues, but caused longer delays and in userspace - maybe still worth a shot. Have you already updated to 6.10.5 ?

Sorry for the delayed response, I've updated but the issue persists. Its not a showstopper but happy to dig deeper to resolve it.

seth · 2024-08-20 20:01:51

If you add more output, can you narrow down when it stalls?
https://wiki.archlinux.org/title/Genera … l_messages

Arch Linux

#1 2024-08-09 22:16:18

Slow Boot Time

#2 2024-08-09 23:16:00

Re: Slow Boot Time

#3 2024-08-10 11:40:34

Re: Slow Boot Time

#4 2024-08-10 17:49:38

Re: Slow Boot Time

#5 2024-08-10 21:43:11

Re: Slow Boot Time

#6 2024-08-10 21:51:05

Re: Slow Boot Time

#7 2024-08-10 22:08:32

Re: Slow Boot Time

#8 2024-08-11 08:28:46

Re: Slow Boot Time

#9 2024-08-11 20:40:22

Re: Slow Boot Time

#10 2024-08-11 22:25:25

Re: Slow Boot Time

#11 2024-08-12 20:58:51

Re: Slow Boot Time

#12 2024-08-12 21:46:27

Re: Slow Boot Time

#13 2024-08-13 07:18:51

Re: Slow Boot Time

#14 2024-08-13 07:30:14

Re: Slow Boot Time

#15 2024-08-13 07:53:57

Re: Slow Boot Time

#16 2024-08-13 14:51:25

Re: Slow Boot Time

#17 2024-08-13 15:23:34

Re: Slow Boot Time

#18 2024-08-13 19:11:14

Re: Slow Boot Time

#19 2024-08-13 21:22:38

Re: Slow Boot Time

#20 2024-08-13 22:11:52

Re: Slow Boot Time

#21 2024-08-14 18:20:21

Re: Slow Boot Time

#22 2024-08-17 21:31:59

Re: Slow Boot Time

#23 2024-08-17 23:06:30

Re: Slow Boot Time

#24 2024-08-20 15:36:20

Re: Slow Boot Time

#25 2024-08-20 20:01:51

Re: Slow Boot Time

Board footer