Long boot time since systemd 251

Since upgrading to systemd251 (actual: 251.2-3)
my boottime has raised unaceptably:
Using systemd250 / (downgrading) this does not occur.
inxi -Fazy

System:
  Kernel: 5.18.8-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.18-x86_64
    root=UUID=4d420b6c-d15f-4290-9634-80a32ba9e5d3 rw quiet apparmor=1
    security=apparmor
  Desktop: GNOME v: 42.2 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM v: 42.0
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING B550-PLUS v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 2803
    date: 04/27/2022
CPU:
  Info: model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 gen: 3
    built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x71 (113)
    stepping: 0 microcode: 0x8701021
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 2229 high: 2811 min/max: 2200/4426 boost: disabled
    scaling: driver: acpi-cpufreq governor: ondemand cores: 1: 2492 2: 2105
    3: 1920 4: 2109 5: 2153 6: 2196 7: 2371 8: 2150 9: 2811 10: 2066 11: 2437
    12: 2139 13: 2084 14: 2187 15: 2331 16: 2119 bogomips: 115036
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Retpolines, IBPB: conditional, STIBP: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 14 [Radeon RX 5500/5500M / Pro 5500M]
    vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA 1
    process: TSMC n7 (7nm) built: 2019-20 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: DP-3 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 09:00.0
    chip-ID: 1002:7340 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2
    compositor: gnome-shell driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa gpu: amdgpu
    display-ID: 0
  Monitor-1: DP-3 model: Samsung LU28R55 serial: <filter> built: 2047
    res: 3840x2160 dpi: 154 gamma: 1.2 size: 632x360mm (24.88x14.17")
    diag: 727mm (28.6") ratio: 16:9 modes: max: 3840x2160 min: 720x400
  OpenGL: renderer: AMD Radeon RX 5500 XT (navi14 LLVM 13.0.1 DRM 3.46
  5.18.8-1-MANJARO)
    v: 4.6 Mesa 22.1.2 direct render: Yes
Audio:
  Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 09:00.1 chip-ID: 1002:ab38
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
  Sound Server-1: ALSA v: k5.18.8-1-MANJARO running: yes
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.52 running: yes
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 2.51 TiB used: 389.03 GiB (15.2%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 5B2QGXA7 temp: 33.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 PRO 256GB
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 2B6Q scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD10EFRX-68FYTN0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0A82 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Toshiba model: HDWD110
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: A8R0 scheme: GPT
Partition:
  ID-1: / raw-size: 230 GiB size: 225.33 GiB (97.97%) used: 23.25 GiB (10.3%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 400 MiB size: 399.2 MiB (99.80%)
    used: 296 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 925 GiB size: 909.41 GiB (98.31%)
    used: 365.79 GiB (40.2%) fs: ext4 dev: /dev/sdc1 maj-min: 8:33
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2
    file: /home/swapfile
Sensors:
  System Temperatures: cpu: 36.6 C mobo: N/A gpu: amdgpu temp: 34.0 C
    mem: 0.0 C
  Fan Speeds (RPM): cpu: 695 fan-5: 0 fan-6: 0 fan-7: 0 gpu: amdgpu
    fan: 1308
Info:
  Processes: 332 Uptime: 12m wakeups: 0 Memory: 31.26 GiB
  used: 2.62 GiB (8.4%) Init: systemd v: 251 default: graphical
  tool: systemctl Compilers: gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 1546
  lib: 402 flatpak: 0 Shell: Zsh v: 5.9 running-in: gnome-terminal
  inxi: 3.3.19

systemd251-2-3

systemd-analyze                                                                                                                                                           
Startup finished in 20.589s (firmware) + 2.310s (loader) + 3.066s (kernel) + 783ms (initrd) + 1.492s (userspace) = 28.243s 
graphical.target reached after 1.492s in userspace.

systemd250.5-1:

systemd-analyze                                                                                                                                                           
Startup finished in 20.562s (firmware) + 2.117s (loader) + 3.066s (kernel) + 763ms (initrd) + 1.553s (userspace) = 28.063s 
graphical.target reached after 1.553s in userspace

Looks similar - BUT:
systemd251.2-3
systemd-analyze blame tells:

> systemd-analyze blame                                                                                                                                                     
1.146s sys-module-configfs.device
1.022s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d1.0\x2dpart5.device
1.022s dev-disk-by\x2did-wwn\x2d0x5002538e4019b21c\x2dpart5.device
1.022s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda5.device
1.022s dev-sda5.device
1.022s dev-disk-by\x2duuid-32A0C5F2A0C5BD1B.device
1.022s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d1\x2dpart5.device
1.022s dev-disk-by\x2dpartuuid-2ff9a483\x2dfe07\x2d4823\x2d9715\x2df93ab211b064.device
1.022s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_PRO_256GB_S42VNF0K209268D\x2dpart5.device
1.010s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d1.0\x2dpart4.device
1.010s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d1\x2dpart4.device
1.010s dev-disk-by\x2did-wwn\x2d0x5002538e4019b21c\x2dpart4.device
1.010s dev-disk-by\x2dpartuuid-b2ca6f49\x2d77e9\x2d4e29\x2db74b\x2db027d022cbbc.device
1.010s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda4.device
1.010s dev-disk-by\x2duuid-86281B37281B25A9.device
1.010s dev-sda4.device
1.010s dev-disk-by\x2dlabel-Windoofs.device
1.010s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
1.010s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_PRO_256GB_S42VNF0K209268D\x2dpart4.device
1.009s dev-ttyS12.device
1.009s sys-devices-platform-serial8250-tty-ttyS12.device
1.008s sys-devices-platform-serial8250-tty-ttyS1.device
1.008s dev-ttyS1.device
".and so on"

Whereas using systemd250.5-1:

systemd-analyze blame                                                                                                                                                     
437ms ufw.service
248ms initrd-switch-root.service
245ms udisks2.service
214ms user@1000.service
126ms systemd-fsck@dev-disk-by\x2duuid-4c618674\x2d47d9\x2d48d5\x2d9bec\x2d7016368b14fc.service
116ms ldconfig.service
 97ms lm_sensors.service
 92ms apparmor.service
 75ms cups.service
 75ms home.mount
 70ms home-swapfile.swap
 63ms systemd-journal-flush.service
 58ms initrd-parse-etc.service
 53ms accounts-daemon.service
 50ms systemd-udev-trigger.service
 37ms systemd-modules-load.service
 30ms polkit.service
 29ms geoclue.service
 28ms systemd-udevd.service
 28ms systemd-sysusers.service
 28ms upower.service
 25ms systemd-localed.service
 24ms systemd-timesyncd.service
"and so on"

Some I-Net sources claims that for systemd251 there must be
“a differnet way / parameters to compile the kernel”

Most of the wait (20 seconds) happens before kernel gets even loaded. Something weird with your uefi loader.

But only with systemd251???

Yeah weird. :person_shrugging:

Looks like this bug:

sys-module-configfs.device has increased boot time · Issue #23850 · systemd/systemd · GitHub

2 Likes

It is not bug, but the performance is slowed down very little. I do not notice 2 sec difference.

Yes, “sys-module-configfs.device” too late

Ah, I mistakenly thought you are talking about those 20 seconds. Anyway, that doesn’t look normal either. :stuck_out_tongue:

Yeah, the 20 seconds are made by “Postboot-Time” in the ASUS-BIOS

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.