udev taking 11-16 seconds on boot

coriolanus31415 · 2026-01-01 18:38:30

I'm looking into optimising my boot time and initrd is taking up a significant portion of the time

output of systemd-analyze:

$ systemd-analyze
Startup finished in 19.308s (firmware) + 402ms (loader) + 906ms (kernel) + 11.794s (initrd) + 2.073s (userspace) = 34.484s 
graphical.target reached after 2.067s in userspace.

(I'll optimise my firmware time later, ignore that part)

Initrd time varies between 11 seconds and 16 seconds.
On boot, I get a message that delays my boot by about 7-10 seconds which I assume is causing most of my initrd delay

A stop job is running for Rule Based Manager for Device Events and Files

If I run `journalctl -xb` I get a similar 7-10 second gap in events, as well as a message saying udev took 11-16s of cpu time

Jan 01 11:54:37 archlinux systemd[1]: initrd-cleanup.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit initrd-cleanup.service has successfully entered the 'dead' state.
Jan 01 11:54:37 archlinux systemd[1]: Finished Cleaning Up and Shutting Down Daemons.
░░ Subject: A start job for unit initrd-cleanup.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit initrd-cleanup.service has finished successfully.
░░ 
░░ The job identifier is 50.
Jan 01 11:54:46 archlinux kernel: [drm] amdgpu kernel modesetting enabled.
Jan 01 11:54:46 archlinux kernel: amdgpu: Virtual CRAT table created for CPU
Jan 01 11:54:46 archlinux kernel: amdgpu: Topology: Add CPU node
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x103C:0x8266 0xE4).
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: register mmio base: 0xF0C00000
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: register mmio size: 262144
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: detected ip block number 0 <common_v1_0_0> (vi_common)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: detected ip block number 1 <gmc_v8_0_0> (gmc_v8_0)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: detected ip block number 2 <ih_v3_0_0> (cz_ih)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: detected ip block number 3 <gfx_v8_0_0> (gfx_v8_0)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: detected ip block number 4 <sdma_v3_0_0> (sdma_v3_0)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: detected ip block number 5 <smu_v1_0_0> (powerplay)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: detected ip block number 6 <dce_v1_0_0> (dm)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: detected ip block number 7 <uvd_v6_0_0> (uvd_v6_0)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: detected ip block number 8 <vce_v3_1_0> (vce_v3_0)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: detected ip block number 9 <acp_v2_2_0> (acp_ip)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: Fetched VBIOS from VFCT
Jan 01 11:54:46 archlinux kernel: amdgpu: ATOM BIOS: BR46715.002
Jan 01 11:54:46 archlinux kernel: [drm] UVD is enabled in physical mode
Jan 01 11:54:46 archlinux kernel: [drm] VCE enabled in physical mode
Jan 01 11:54:46 archlinux kernel: Console: switching to colour dummy device 80x25
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: vgaarb: deactivate vga console
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: VRAM: 1024M 0x000000F400000000 - 0x000000F43FFFFFFF (1024M used)
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF
Jan 01 11:54:46 archlinux kernel: [drm] Detected VRAM RAM=1024M, BAR=1024M
Jan 01 11:54:46 archlinux kernel: [drm] RAM width 128bits UNKNOWN
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: amdgpu: 1024M of VRAM memory ready
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: amdgpu: 7454M of GTT memory ready.
Jan 01 11:54:46 archlinux kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144
Jan 01 11:54:46 archlinux kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F400E00000).
Jan 01 11:54:46 archlinux kernel: amdgpu: hwmgr_sw_init smu backed is smu8_smu
Jan 01 11:54:46 archlinux kernel: [drm] Found UVD firmware Version: 1.91 Family ID: 11
Jan 01 11:54:46 archlinux kernel: [drm] UVD ENC is disabled
Jan 01 11:54:46 archlinux kernel: [drm] Found VCE firmware Version: 52.4 Binary ID: 3
Jan 01 11:54:46 archlinux kernel: amdgpu: smu version 27.22.00
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB: values for Engine clock
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         300000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         400000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         464520
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         600000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         654550
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         720000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         800000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB: Validation clocks:
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:    engine_max_clock: 80000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:    memory_max_clock: 120000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:    level           : 8
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB: values for Display clock
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         300000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         400000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         496560
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         626090
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         685720
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         757900
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         800000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB: Validation clocks:
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:    engine_max_clock: 80000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:    memory_max_clock: 120000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:    level           : 8
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB: values for Memory clock
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         667000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:         1200000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB: Validation clocks:
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:    engine_max_clock: 80000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:    memory_max_clock: 120000
Jan 01 11:54:46 archlinux kernel: [drm] DM_PPLIB:    level           : 8
Jan 01 11:54:46 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: [drm] Display Core v3.2.351 initialized on DCE 11.0
Jan 01 11:54:46 archlinux kernel: [drm] UVD initialized successfully.
Jan 01 11:54:47 archlinux kernel: [drm] VCE initialized successfully.
Jan 01 11:54:47 archlinux kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Jan 01 11:54:47 archlinux kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
Jan 01 11:54:47 archlinux kernel: amdgpu: Virtual CRAT table created for GPU
Jan 01 11:54:47 archlinux kernel: amdgpu: Topology: Add dGPU node [0x9874:0x1002]
Jan 01 11:54:47 archlinux kernel: kfd kfd: amdgpu: added device 1002:9874
Jan 01 11:54:47 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: SE 1, SH per SE 1, CU per SH 8, active_cu_number 6
Jan 01 11:54:47 archlinux kernel: amdgpu: pp_dpm_get_sclk_od was not implemented.
Jan 01 11:54:47 archlinux kernel: amdgpu: pp_dpm_get_mclk_od was not implemented.
Jan 01 11:54:47 archlinux kernel: amdgpu 0000:00:01.0: amdgpu: Runtime PM not available
Jan 01 11:54:47 archlinux kernel: amdgpu 0000:00:01.0: [drm] Registered 3 planes with drm panic
Jan 01 11:54:47 archlinux kernel: [drm] Initialized amdgpu 3.64.0 for 0000:00:01.0 on minor 1
Jan 01 11:54:47 archlinux kernel: fbcon: amdgpudrmfb (fb0) is primary device
Jan 01 11:54:47 archlinux kernel: Console: switching to colour frame buffer device 240x67
Jan 01 11:54:47 archlinux kernel: amdgpu 0000:00:01.0: [drm] fb0: amdgpudrmfb frame buffer device
Jan 01 11:54:47 archlinux systemd[1]: systemd-udevd.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-udevd.service has successfully entered the 'dead' state.
Jan 01 11:54:47 archlinux systemd[1]: Stopped Rule-based Manager for Device Events and Files.
░░ Subject: A stop job for unit systemd-udevd.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A stop job for unit systemd-udevd.service has finished.
░░ 
░░ The job identifier is 64 and the job result is done.
Jan 01 11:54:47 archlinux systemd[1]: systemd-udevd.service: Consumed 11.302s CPU time over 11.263s wall clock time, 19.2M memory peak.

similarly, if I run `systemd-analyze blame` I get a whole bunch of devices taking up a similar amount of time

12.420s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
12.420s dev-ttyS1.device
12.401s dev-ttyS0.device
12.401s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
12.395s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
12.395s dev-ttyS3.device
12.371s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
12.371s dev-ttyS2.device
12.353s sys-module-configfs.device
12.351s sys-module-fuse.device
12.292s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-c6f38db2\x2d36de\x2d4a3b\x2d9fd8\x2db1022c4f0a44.device
12.292s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b415f1e6d\x2dpart1.device
12.292s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart1.device
12.292s dev-disk-by\x2did-nvme\x2dWDC_WDS250G2B0C_21302W804755\x2dpart1.device
12.292s sys-devices-pci0000:00-0000:00:02.3-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
12.292s dev-disk-by\x2did-nvme\x2dWDC_WDS250G2B0C_21302W804755_1\x2dpart1.device
12.292s dev-disk-by\x2duuid-6D9A\x2d63B5.device
12.292s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-6D9A\x2d63B5.device
12.292s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
12.292s dev-nvme0n1p1.device
12.292s dev-disk-by\x2ddiskseq-1\x2dpart1.device
12.292s dev-disk-by\x2dpartuuid-c6f38db2\x2d36de\x2d4a3b\x2d9fd8\x2db1022c4f0a44.device
12.291s sys-devices-pci0000:00-0000:00:02.3-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
12.289s dev-disk-by\x2did-nvme\x2dWDC_WDS250G2B0C_21302W804755\x2dpart2.device
12.289s dev-disk-by\x2duuid-b4f536a9\x2db6eb\x2d4b97\x2d996d\x2d721ee215ff33.device
12.289s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b415f1e6d\x2dpart2.device
12.289s dev-disk-by\x2did-nvme\x2dWDC_WDS250G2B0C_21302W804755_1\x2dpart2.device
12.289s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart2.device
12.289s dev-nvme0n1p2.device
12.289s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-53e1910d\x2d3b6d\x2d410f\x2d93d1\x2db582fc4299b4.device
12.289s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
12.289s dev-disk-by\x2ddiskseq-1\x2dpart2.device
12.289s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-b4f536a9\x2db6eb\x2d4b97\x2d996d\x2d721ee215ff33.device
12.289s dev-disk-by\x2dpartuuid-53e1910d\x2d3b6d\x2d410f\x2d93d1\x2db582fc4299b4.device
12.245s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart3.device
12.245s dev-disk-by\x2duuid-5f0e6bd0\x2dddbd\x2d48f2\x2d9eea\x2dbe68aaeafeb5.device
12.245s dev-nvme0n1p3.device
12.245s dev-disk-by\x2ddiskseq-1\x2dpart3.device
12.245s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-1122234d\x2d1684\x2d4de3\x2d9212\x2d9d398e4cc8e6.device
12.245s sys-devices-pci0000:00-0000:00:02.3-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
12.245s dev-disk-by\x2did-nvme\x2dWDC_WDS250G2B0C_21302W804755_1\x2dpart3.device
12.245s dev-disk-by\x2did-nvme\x2dWDC_WDS250G2B0C_21302W804755\x2dpart3.device
12.245s dev-disk-by\x2dpartuuid-1122234d\x2d1684\x2d4de3\x2d9212\x2d9d398e4cc8e6.device
12.245s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-5f0e6bd0\x2dddbd\x2d48f2\x2d9eea\x2dbe68aaeafeb5.device
12.245s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b415f1e6d\x2dpart3.device
12.245s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
12.226s dev-disk-by\x2did-nvme\x2dWDC_WDS250G2B0C_21302W804755_1.device
12.226s dev-disk-by\x2did-nvme\x2dWDC_WDS250G2B0C_21302W804755.device
12.226s sys-devices-pci0000:00-0000:00:02.3-0000:02:00.0-nvme-nvme0-nvme0n1.device
12.226s dev-nvme0n1.device
12.226s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.device
12.226s dev-disk-by\x2ddiskseq-1.device
12.226s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b415f1e6d.device
  712ms initrd-switch-root.service
  290ms systemd-networkd.service
  274ms systemd-udev-trigger.service
  235ms user@1000.service
  193ms systemd-journal-flush.service
  174ms upower.service
  147ms boot.mount
  134ms systemd-fsck-root.service
  133ms systemd-tmpfiles-setup.service
  127ms systemd-vconsole-setup.service
  126ms systemd-tmpfiles-setup-dev-early.service
  116ms systemd-journald.service
  113ms systemd-resolved.service
  106ms ldconfig.service
  105ms systemd-tmpfiles-clean.service
   89ms udisks2.service
   87ms polkit.service
   83ms systemd-hostnamed.service
   78ms systemd-udevd.service
   77ms systemd-tmpfiles-setup-dev.service
   69ms systemd-logind.service
   64ms dev-mqueue.mount
   63ms sys-kernel-debug.mount
   62ms dev-hugepages.mount
   60ms initrd-cleanup.service
   60ms sys-kernel-tracing.mount
   54ms kmod-static-nodes.service
   54ms sys-kernel-config.mount
   53ms dev-disk-by\x2duuid-b4f536a9\x2db6eb\x2d4b97\x2d996d\x2d721ee215ff33.swap
   52ms sys-fs-fuse-connections.mount
   50ms systemd-remount-fs.service
   48ms systemd-networkd-persistent-storage.service
   46ms dbus-broker.service
   42ms systemd-userdbd.service
   42ms systemd-udev-load-credentials.service
   38ms systemd-modules-load.service
   35ms systemd-journal-catalog-update.service
   34ms tmp.mount
   34ms systemd-network-generator.service
   32ms systemd-sysusers.service
   31ms systemd-random-seed.service
   31ms systemd-userdb-load-credentials.service
   25ms rtkit-daemon.service
   24ms user-runtime-dir@1000.service
   24ms systemd-sysctl.service
   23ms initrd-udevadm-cleanup-db.service
   22ms systemd-update-done.service
   18ms systemd-update-utmp.service
   18ms systemd-hibernate-resume.service
   17ms systemd-user-sessions.service
   12ms initrd-parse-etc.service
    3ms systemd-mute-console.socket
    2ms polkit-agent-helper.socket
    1ms systemd-ask-password.socket
    1ms systemd-coredump.socket
    1ms systemd-bootctl.socket
    1ms systemd-factory-reset.socket
    1ms systemd-sysext.socket
    1ms systemd-repart.socket
  989us systemd-creds.socket
  182us gpg-agent@etc-pacman.d-gnupg.socket
  158us gpg-agent-ssh@etc-pacman.d-gnupg.socket
  151us keyboxd@etc-pacman.d-gnupg.socket
  144us gpg-agent-extra@etc-pacman.d-gnupg.socket
  143us dbus.socket
  140us dirmngr@etc-pacman.d-gnupg.socket
  135us gpg-agent-browser@etc-pacman.d-gnupg.socket
  114us systemd-journald-dev-log.socket
  105us systemd-userdbd.socket
  105us systemd-machined.socket
   87us systemd-resolved-monitor.socket
   82us systemd-importd.socket
   81us systemd-udevd-varlink.socket
   79us systemd-hostnamed.socket
   77us systemd-resolved-varlink.socket
   71us systemd-logind-varlink.socket
   69us systemd-udevd-control.socket
   56us dm-event.socket
   54us systemd-journald.socket
   52us systemd-networkd-resolve-hook.socket
   43us systemd-networkd.socket
   37us systemd-rfkill.socket
   35us systemd-networkd-varlink.socket
   18us systemd-udevd-kernel.socket

not sure whats going on with all these devices, I found a few forum posts elsewhere with similar 'systemd-analyze blame' outputs, but they either never solved the problem, or it was mysteriously fixed with no real solution published online.
Any help would be appreciated!

P.S as a sidenote, the kms hook seems to take the longest (by far) when building the initramfs, is it worth looking into optimising this?

seth · 2026-01-01 19:55:15

Please never use -x w/ journalctl, it's just spam.
Then please post your complete system journal for the boot:

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

The problem seems to be your nvme, but it deosn't show up in that snippet at all (where it's not even clear whether this is in the initramfs or afterwards)

coriolanus31415 · 2026-01-01 20:48:27

I ran the command and here is the link it provided:
http://0x0.st/P-w3.txt

hopefully thats what you were looking for.
(Sorry I'm new on the forum)

seth · 2026-01-01 20:55:26

Not the nvme

Jan 01 14:29:57 archlinux kernel: usb 1-3: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=11.00
Jan 01 14:29:57 archlinux kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 01 14:29:57 archlinux kernel: usb 1-3: Product: Flash Disk
Jan 01 14:29:57 archlinux kernel: usb 1-3: Manufacturer: USB
Jan 01 14:29:57 archlinux kernel: usb 1-3: SerialNumber: SCY0000000118842
Jan 01 14:30:10 archlinux kernel: [drm] amdgpu kernel modesetting enabled.
Jan 01 14:30:10 archlinux kernel: amdgpu: Virtual CRAT table created for CPU
Jan 01 14:30:10 archlinux kernel: amdgpu: Topology: Add CPU node

There's a 4GB USB key - try to remove that…

coriolanus31415 · 2026-01-02 02:31:32

It doesn't make a difference, boots the same with or without. Heres the system logs again if you want: http://0x0.st/P-YU.txt

seth · 2026-01-02 10:01:48

Jan 01 20:27:42 arch systemd-fstab-generator[378]: Failed to create unit file '/run/systemd/generator/-.mount', as it already exists. Duplicate entry in '/etc/fstab'?
Jan 01 20:27:42 arch systemd-fstab-generator[378]: Failed to create unit file '/run/systemd/generator/boot.mount', as it already exists. Duplicate entry in '/etc/fstab'?
Jan 01 20:27:42 arch systemd-fstab-generator[378]: Failed to create unit file '/run/systemd/generator/dev-disk-by\x2duuid-b4f536a9\x2db6eb\x2d4b97\x2d996d\x2d721ee215ff33.swap', as it already exists. Duplicate entry in '/etc/fstab'?
Jan 01 20:27:42 arch (generato[372]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.

Clean up the fstab

cat /etc/fstab

Other than that it stalls before the AMD gpu - not sure what makes it take so long, there're no errors.
You could try to move it out of the initramfs (the kms hook) to delay its loading and see whether that prevents the stall…

coriolanus31415 · 2026-01-02 14:16:20

Fixed the fstab, though it didn't make a difference. Thats my bad for botching it up since my last post.

Removing the kms hook swapped the initrd time and userspace time howerever, with initrd now taking roughly one second and userspace taking 15.
System logs: http://0x0.st/P-U8.txt

Running systemd-analyze blame, it looks like alsa-restore.service is the only thing slowing me down now with a 13s delay
I will do some looking online.

seth · 2026-01-02 15:34:21

Jan 02 08:10:06 arch systemd[1]: Manage Sound Card State (restore and store) was skipped because of an unmet condition check (ConditionPathExists=/etc/alsa/state-daemon.conf).
Jan 02 08:10:10 arch kernel: tg3 0000:01:00.0 enp1s0: Link is up at 1000 Mbps, full duplex
Jan 02 08:10:10 arch kernel: tg3 0000:01:00.0 enp1s0: Flow control is on for TX and on for RX
Jan 02 08:10:10 arch systemd-networkd[402]: enp1s0: Gained carrier
Jan 02 08:10:10 arch kernel: tg3 0000:01:00.0 enp1s0: EEE is enabled
Jan 02 08:10:20 arch systemd[1]: Starting User Login Management...
Jan 02 08:10:20 arch systemd[1]: TPM PCR Barrier (User) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
Jan 02 08:10:20 arch systemd-networkd[402]: enp1s0: Gained IPv6LL
Jan 02 08:10:20 arch systemd[1]: Starting Permit User Sessions...
Jan 02 08:10:20 arch kernel: [drm] amdgpu kernel modesetting enabled.
Jan 02 08:10:20 arch systemd[1]: Finished Save/Restore Sound Card State.

The boot really just pauses - for a suspiciously consistent 10s…

Jan 02 08:10:06 arch kernel: snd_hda_intel 0000:00:01.1: Force to non-snoop mode
Jan 02 08:10:06 arch kernel: snd_hda_codec_alc269 hdaudioC1D0: ALC221: picked fixup  for PCI SSID 103c:0000
Jan 02 08:10:06 arch kernel: snd_hda_codec_alc269 hdaudioC1D0: autoconfig for ALC221: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Jan 02 08:10:06 arch kernel: snd_hda_codec_alc269 hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Jan 02 08:10:06 arch kernel: snd_hda_codec_alc269 hdaudioC1D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Jan 02 08:10:06 arch kernel: snd_hda_codec_alc269 hdaudioC1D0:    mono: mono_out=0x0
Jan 02 08:10:06 arch kernel: snd_hda_codec_alc269 hdaudioC1D0:    inputs:
Jan 02 08:10:06 arch kernel: snd_hda_codec_alc269 hdaudioC1D0:      Mic=0x1a
Jan 02 08:10:20 arch kernel: snd_hda_intel 0000:00:01.1: bound 0000:00:01.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])

the (only?) sound chip is on the GPU so if that stalls for whatever reason, restoring the volumes will just with it.

Do you boot w/o delay (and accelerated graphics…) if you add

module_blacklist=amdgpu

to the https://wiki.archlinux.org/title/Kernel_parameters ?

coriolanus31415 · 2026-01-02 18:14:19

There is zero delay with the module blacklisted. System boots up before I can hardly blink.

Is there a way to keep accelerated graphics without taking an extra 10s to boot?

seth · 2026-01-02 20:36:23

We'll have to figure why amdgpu is taking so long - are the LTS kernel or 6.17.9 affected?

coriolanus31415 · 2026-01-03 17:26:28

Not sure if I'm doing it wrong, but installing the LTS kernel broke my system.
Reverting all packages using the archives to November 30 also broke my system.
Until I accidentally booted with that kernel argument to blacklist the amdgpu module again and somehow it worked?

I have never downgraded a package before, I apologise for my fumbling.

seth · 2026-01-03 19:49:14

Please post your complete system journal for the boot w/ the broken kernel

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

coriolanus31415 · 2026-01-04 05:26:24

I can't access a shell after the boot process fails, which is why i didn't do that earlier.
However i realised I can use the arch installation medium to chroot into the system and access the logs from there.

Journal after installing linux-lts and linux-lts-headers: http://0x0.st/Pocf.txt

I used the following wiki page to downgrade all my packages to November 30, about a week after 6.17.9 was released: https://wiki.archlinux.org/title/Arch_L … cific_date

The system seems to boot successfully about MOST the time with the downgraded packages.
When it crashes, there is a long start job on 2 devices. Logs: http://0x0.st/Poc6.txt

When it works, there is still a long delay, but the start job message is different every time now, as though its incorrectly diagnosing what is causing the delay.
Journal: http://0x0.st/PoT-.txt

It's weird to me that this behaviour occurs seemingly randomly.

seth · 2026-01-04 09:00:46

The journal from the archiso boot will not be helpful.
https://wiki.archlinux.org/title/System … al_to_view
Or you'll have to pick t he previous journal (… -b -1 …) and do not reboot w/ the power button but https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB

http://0x0.st/PoT-.txt is actually from the installed system, you're booting kernel 6.17.9-arch1-1, the gap is

Jan 03 23:14:46 arch kernel: tg3 0000:01:00.0 enp1s0: Flow control is on for TX and on for RX
Jan 03 23:14:46 arch systemd-networkd[252]: enp1s0: Gained carrier
Jan 03 23:14:46 arch kernel: tg3 0000:01:00.0 enp1s0: EEE is enabled
Jan 03 23:14:56 arch systemd-networkd[252]: enp1s0: Gained IPv6LL
Jan 03 23:14:56 arch systemd-logind[339]: Watching system buttons on /dev/input/event1 (Power Button)

for your ethernet connection.

sddm will probably depend on the network but the multi-user.target should™ not and that also doesn't explain the amdgpu relation.
What happens when you boot w/o the network cable being plugged?

I can't access a shell after the boot process fails, which is why i didn't do that earlier.

You cannot boot when adding "systemd.unit=multi-user.target" to the kernel parameters??

Arch Linux

#1 2026-01-01 18:38:30

udev taking 11-16 seconds on boot

#2 2026-01-01 19:55:15

Re: udev taking 11-16 seconds on boot

#3 2026-01-01 20:48:27

Re: udev taking 11-16 seconds on boot

#4 2026-01-01 20:55:26

Re: udev taking 11-16 seconds on boot

#5 2026-01-02 02:31:32

Re: udev taking 11-16 seconds on boot

#6 2026-01-02 10:01:48

Re: udev taking 11-16 seconds on boot

#7 2026-01-02 14:16:20

Re: udev taking 11-16 seconds on boot

#8 2026-01-02 15:34:21

Re: udev taking 11-16 seconds on boot

#9 2026-01-02 18:14:19

Re: udev taking 11-16 seconds on boot

#10 2026-01-02 20:36:23

Re: udev taking 11-16 seconds on boot

#11 2026-01-03 17:26:28

Re: udev taking 11-16 seconds on boot

#12 2026-01-03 19:49:14

Re: udev taking 11-16 seconds on boot

#13 2026-01-04 05:26:24

Re: udev taking 11-16 seconds on boot

#14 2026-01-04 09:00:46

Re: udev taking 11-16 seconds on boot

Board footer