Arch Linux

Big Scorpio

Member

Registered: 2024-12-15

Posts: 58

5+ minutes long boot time (firmware, kernel + network?)

Imagine solving my previous long boot time from here https://bbs.archlinux.org/viewtopic.php?id=303665 ... only to encounter an even longer booting time just 1-2 days after /!\

Today my system has booted up for a whopping 5 minutes and 50 seconds! And before that, i tried booting it up and i only saw my POST image taking too long to boot up, so i power cycled my machine only to find it still takes a long time to get past the POST image - just to confirm the long boot time is not a random one time coincidence.

What have i done since i solved my initial long boot time, that caused the boot time to take up almost 6 minutes? Not much, really. I attempted to use XFCE (used KDE before that), so i installed XFCE after I ran "sudo pacman -Syu". And my VPN connection (wireguard) stopped connecting a few hours later (it still doesn't work today. I suppose i am to renew my license today).

Here's some system printouts

[motherfucker_big_scorpio@Nexus ~]$ sudo 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 @37.796s
└─sddm.service @37.795s
  └─plymouth-quit.service @37.766s +27ms
    └─systemd-user-sessions.service @37.749s +14ms
      └─network.target @37.746s
        └─NetworkManager.service @37.354s +392ms
          └─network-pre.target @37.352s
[motherfucker_big_scorpio@Nexus ~]$ 
[motherfucker_big_scorpio@Nexus ~]$ sudo systemd-analyze
Startup finished in 3min 23.206s (firmware) + 17.965s (loader) + 1min 29.595s (kernel) + 37.799s (userspace) = 5min 48.567s 
graphical.target reached after 37.796s in userspace.
[motherfucker_big_scorpio@Nexus ~]$ 
[motherfucker_big_scorpio@Nexus ~]$ sudo systemd-analyze blame
36.562s systemd-journald.service
  857ms systemd-binfmt.service
  771ms lvm2-monitor.service
  392ms NetworkManager.service
  266ms dev-mapper-SystemVolume\x2droot.device
  249ms user@1000.service
  201ms systemd-udev-trigger.service
  187ms home.mount
  181ms udisks2.service
  158ms nftables.service
  126ms upower.service
  123ms ufw.service
   98ms systemd-tmpfiles-setup.service
   75ms systemd-journal-flush.service
   70ms systemd-tmpfiles-setup-dev-early.service
   62ms accounts-daemon.service
   51ms systemd-udevd.service
   50ms polkit.service
   49ms systemd-logind.service
   47ms systemd-fsck@dev-disk-by\x2duuid-D87B\x2dAFAA.service
   46ms systemd-hostnamed.service
   46ms proc-sys-fs-binfmt_misc.mount
   45ms dbus-broker.service
   45ms systemd-zram-setup@zram0.service
   42ms plymouth-start.service
   38ms dev-zram0.swap
   37ms systemd-tmpfiles-setup-dev.service
   34ms systemd-vconsole-setup.service
   30ms systemd-userdbd.service
   29ms dev-disk-by\x2duuid-826ae0ac\x2d254c\x2d4146\x2dadec\x2d1972158dbf9e.swap
   29ms boot.mount
   28ms plymouth-quit-wait.service
   27ms plymouth-quit.service
   27ms plymouth-read-write.service
   27ms systemd-cryptsetup@systemdrive.service
   27ms systemd-update-utmp.service
   26ms systemd-fsck@dev-disk-by\x2duuid-91EB\x2d4A5D.service
   25ms systemd-fsck@dev-disk-by\x2duuid-2f00a55b\x2d4388\x2d42be\x2db77f\x2de4bfa6676b00.service
   18ms systemd-random-seed.service
   18ms user-runtime-dir@1000.service
   17ms systemd-modules-load.service
   17ms boot-efi.mount
   16ms dev-hugepages.mount
   16ms dev-mqueue.mount
   16ms sys-fs-fuse-connections.mount
   16ms modprobe@configfs.service
   16ms sys-kernel-debug.mount
   15ms sys-kernel-config.mount
   15ms kmod-static-nodes.service
   15ms sys-kernel-tracing.mount
   15ms tmp.mount
   14ms systemd-user-sessions.service
   14ms modprobe@dm_mod.service
   14ms modprobe@drm.service
   13ms modprobe@loop.service
   13ms systemd-sysctl.service
   10ms systemd-remount-fs.service
    9ms systemd-udev-load-credentials.service
    8ms rtkit-daemon.service
    7ms modprobe@fuse.service
[motherfucker_big_scorpio@Nexus ~]$ 

And the journalctl -> http://0x0.st/8Sck.txt

I noticed, that Network-pre.target takes up 37 seconds to complete. It looks to me like it attempts to automatically connect to the VPN server, that is no longer having any connectivity. This is what's been residual from my routinely automatically establishing the VPN connection. For now I can try to disable it and see if it helps to some degree if it does not completely solve the problem but in the meantime a helping hand from you Arch Friends will be appreciated.

-thc

Member

Registered: 2017-03-15

Posts: 805

Re: 5+ minutes long boot time (firmware, kernel + network?)

The problem with your xHCI USB controller that takes 36 seconds to initialize is still present. NetworkManager seems to take a few seconds (~6) only.

The huge "firmware" time is your mainboard all by itself.