Weirdly long loader times using silent-GRUB and weird systemd-analyze blame results

Support
, ,
1

Something is causing my loader times to skyrocket, and systemd-analyze prints out this weird list of devices, I don’t understand what’s going wrong.

3.117s dev-ttyS1.device
3.117s sys-devices-platform-serial8250-tty-ttyS1.device
3.117s dev-ttyS12.device
3.117s sys-devices-platform-serial8250-tty-ttyS12.device
3.117s dev-ttyS10.device
3.117s sys-devices-platform-serial8250-tty-ttyS10.device
3.116s sys-devices-platform-serial8250-tty-ttyS13.device
3.116s dev-ttyS13.device
3.116s dev-ttyS11.device
3.116s sys-devices-platform-serial8250-tty-ttyS11.device
3.116s sys-devices-platform-serial8250-tty-ttyS15.device
3.116s dev-ttyS15.device
3.115s sys-devices-platform-serial8250-tty-ttyS16.device
3.115s dev-ttyS16.device
3.115s dev-ttyS14.device
3.115s sys-devices-platform-serial8250-tty-ttyS14.device
3.115s dev-ttyS2.device
3.115s sys-devices-platform-serial8250-tty-ttyS2.device
3.114s dev-ttyS20.device
3.114s sys-devices-platform-serial8250-tty-ttyS20.device
3.114s sys-devices-platform-serial8250-tty-ttyS21.device
3.114s dev-ttyS21.device
3.113s dev-ttyS17.device
3.113s sys-devices-platform-serial8250-tty-ttyS17.device
3.113s dev-ttyS19.device
3.113s sys-devices-platform-serial8250-tty-ttyS19.device
3.112s dev-ttyS18.device
3.112s sys-devices-platform-serial8250-tty-ttyS18.device
3.112s dev-ttyS22.device
3.112s sys-devices-platform-serial8250-tty-ttyS22.device
3.112s sys-devices-platform-serial8250-tty-ttyS23.device
3.112s dev-ttyS23.device
3.111s sys-devices-platform-serial8250-tty-ttyS24.device
3.111s dev-ttyS24.device
3.111s dev-ttyS25.device
3.111s sys-devices-platform-serial8250-tty-ttyS25.device
3.110s sys-devices-platform-serial8250-tty-ttyS26.device
3.110s dev-ttyS26.device
3.110s dev-ttyS27.device
3.110s sys-devices-platform-serial8250-tty-ttyS27.device
3.110s dev-sda3.device
3.110s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
3.110s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6.0\x2dpart3.device
3.110s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sda-sda3.device
3.110s dev-disk-by\x2ddiskseq-1\x2dpart3.device
3.110s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6\x2dpart3.device
3.110s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_500GB_S4FNNE0M605797J\x2dpart3.device
3.110s dev-disk-by\x2dpartuuid-95295a0d\x2dbe80\x2d48f0\x2d976f\x2db049cbb9531c.device
3.110s dev-disk-by\x2did-wwn\x2d0x5002538e09627063\x2dpart3.device
3.110s dev-ttyS28.device
3.110s sys-devices-platform-serial8250-tty-ttyS28.device
3.109s dev-ttyS29.device
3.109s sys-devices-platform-serial8250-tty-ttyS29.device
3.109s dev-ttyS3.device
3.109s sys-devices-platform-serial8250-tty-ttyS3.device
3.109s dev-ttyS31.device
3.109s sys-devices-platform-serial8250-tty-ttyS31.device
3.108s sys-devices-platform-serial8250-tty-ttyS30.device
3.108s dev-ttyS30.device
3.108s dev-ttyS4.device
3.108s sys-devices-platform-serial8250-tty-ttyS4.device
3.108s sys-devices-platform-serial8250-tty-ttyS8.device
3.108s dev-ttyS8.device
3.107s dev-ttyS7.device
3.107s sys-devices-platform-serial8250-tty-ttyS7.device
3.107s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_500GB_S4FNNE0M605797J.device
3.107s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sda.device
3.107s dev-disk-by\x2ddiskseq-1.device
3.107s dev-sda.device
3.107s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6.device
3.107s dev-disk-by\x2did-wwn\x2d0x5002538e09627063.device
3.107s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6.0.device
3.107s sys-devices-platform-serial8250-tty-ttyS9.device
3.107s dev-ttyS9.device
3.106s dev-ttyS5.device
3.106s sys-devices-platform-serial8250-tty-ttyS5.device
3.106s dev-ttyS6.device
3.106s sys-devices-platform-serial8250-tty-ttyS6.device
3.106s dev-ttyS0.device
3.106s sys-devices-pnp0-00:04-tty-ttyS0.device
3.103s dev-sda2.device
3.103s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6.0\x2dpart2.device
3.103s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6\x2dpart2.device
3.103s dev-disk-by\x2duuid-F00D\x2d6BA8.device
3.103s dev-disk-by\x2dpartuuid-3a62d5bf\x2d1aef\x2d4635\x2db77c\x2def3d1c73849d.device
3.103s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sda-sda2.device
3.103s dev-disk-by\x2did-wwn\x2d0x5002538e09627063\x2dpart2.device
3.103s dev-disk-by\x2ddiskseq-1\x2dpart2.device
3.103s dev-disk-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
3.103s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_500GB_S4FNNE0M605797J\x2dpart2.device
3.102s dev-disk-by\x2dlabel-Recovery.device
3.102s dev-sda1.device
3.102s dev-disk-by\x2duuid-647C0D647C0D327A.device
3.102s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_500GB_S4FNNE0M605797J\x2dpart1.device
3.102s dev-disk-by\x2ddiskseq-1\x2dpart1.device
3.102s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6.0\x2dpart1.device
3.102s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
3.102s dev-disk-by\x2did-wwn\x2d0x5002538e09627063\x2dpart1.device
3.102s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6\x2dpart1.device
3.102s dev-disk-by\x2dpartuuid-73b9f90e\x2d5c50\x2d4193\x2db305\x2dfc2ceab0d3c3.device
3.102s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sda-sda1.device
3.099s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.0-usb2-2\x2d2-2\x2d2:1.0-host8-target8:0:0-8:0:0:0-block-sdb-sdb1.device
3.099s dev-disk-by\x2did-wwn\x2d0x5002538e00000000\x2dpart1.device
3.099s dev-disk-by\x2did-usb\x2dSamsung_Portable_SSD_T5_12345686D380\x2d0:0\x2dpart1.device
3.099s dev-disk-by\x2dlabel-Samsung_T5.device
3.099s dev-disk-by\x2duuid-AE71\x2d3943.device
3.099s dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dusb\x2d0:2:1.0\x2dscsi\x2d0:0:0:0\x2dpart1.device
3.099s dev-disk-by\x2dpartuuid-be51f84b\x2d01.device
3.099s dev-disk-by\x2ddiskseq-3\x2dpart1.device
3.099s dev-disk-by\x2did-ata\x2dSamsung_Portable_SSD_T5_S4B1NR0NC39904A\x2dpart1.device
3.099s dev-sdb1.device
3.098s dev-sdb.device
3.098s dev-disk-by\x2did-ata\x2dSamsung_Portable_SSD_T5_S4B1NR0NC39904A.device
3.098s dev-disk-by\x2ddiskseq-3.device
3.098s dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dusb\x2d0:2:1.0\x2dscsi\x2d0:0:0:0.device
3.098s dev-disk-by\x2did-usb\x2dSamsung_Portable_SSD_T5_12345686D380\x2d0:0.device
3.098s dev-disk-by\x2did-wwn\x2d0x5002538e00000000.device
3.098s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.0-usb2-2\x2d2-2\x2d2:1.0-host8-target8:0:0-8:0:0:0-block-sdb.device
3.096s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6\x2dpart4.device
3.096s dev-disk-by\x2duuid-4CD61975D619610E.device
3.096s dev-disk-by\x2dlabel-Samsung\x2devo\x2d870\x2d512gb.device
3.096s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_500GB_S4FNNE0M605797J\x2dpart4.device
3.096s dev-disk-by\x2dpartlabel-Main\x5cx20windows\x5cx20drive.device
3.096s dev-disk-by\x2ddiskseq-1\x2dpart4.device
3.096s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6.0\x2dpart4.device
3.096s dev-disk-by\x2dpartuuid-f8a37e19\x2d820f\x2d40ef\x2db9c7\x2d3117907f7a4b.device
3.096s dev-sda4.device
3.096s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sda-sda4.device
3.096s dev-disk-by\x2did-wwn\x2d0x5002538e09627063\x2dpart4.device
3.090s dev-sda5.device
3.090s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6.0\x2dpart5.device
3.090s dev-disk-by\x2dpartuuid-8990c1d9\x2d75e4\x2d4e19\x2daf40\x2dfcaf6d955d52.device
3.090s dev-disk-by\x2did-wwn\x2d0x5002538e09627063\x2dpart5.device
3.090s dev-disk-by\x2ddiskseq-1\x2dpart5.device
3.090s dev-disk-by\x2duuid-9CB8772DB87704D4.device
3.090s sys-devices-pci0000:00-0000:00:01.3-0000:03:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sda-sda5.device
3.090s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_500GB_S4FNNE0M605797J\x2dpart5.device
3.090s dev-disk-by\x2dpath-pci\x2d0000:03:00.1\x2data\x2d6\x2dpart5.device
3.009s sys-module-configfs.device
2.780s dev-disk-by\x2ddiskseq-2.device
2.780s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1.device
2.780s dev-nvme0n1.device
2.780s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1.device
2.780s dev-disk-by\x2did-nvme\x2deui.0026b7684465aa25.device
2.780s dev-disk-by\x2did-nvme\x2dKINGSTON_SA2000M81000G_50026B7684465AA2_1.device
2.780s dev-disk-by\x2did-nvme\x2dKINGSTON_SA2000M81000G_50026B7684465AA2.device
2.777s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart1.device
2.777s dev-disk-by\x2dlabel-Game\x2dStorage\x2dVids.device
2.777s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
2.777s dev-disk-by\x2ddiskseq-2\x2dpart1.device
2.777s dev-nvme0n1p1.device
2.777s dev-disk-by\x2duuid-2EECD6A5ECD6669D.device
2.777s dev-disk-by\x2dpartuuid-0d52f862\x2dd654\x2d354e\x2daa26\x2d388b87a6dec2.device
2.777s dev-disk-by\x2did-nvme\x2deui.0026b7684465aa25\x2dpart1.device
2.777s dev-disk-by\x2did-nvme\x2dKINGSTON_SA2000M81000G_50026B7684465AA2_1\x2dpart1.device
2.777s dev-disk-by\x2did-nvme\x2dKINGSTON_SA2000M81000G_50026B7684465AA2\x2dpart1.device
2.773s dev-disk-by\x2dpartlabel-Manjaro\x5cx20Partition.device
2.773s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
2.773s dev-disk-by\x2ddiskseq-2\x2dpart2.device
2.773s dev-disk-by\x2did-nvme\x2dKINGSTON_SA2000M81000G_50026B7684465AA2_1\x2dpart2.device
2.773s dev-nvme0n1p2.device
2.773s dev-disk-by\x2did-nvme\x2deui.0026b7684465aa25\x2dpart2.device
2.773s dev-disk-by\x2did-nvme\x2dKINGSTON_SA2000M81000G_50026B7684465AA2\x2dpart2.device
2.773s dev-disk-by\x2dpartuuid-fe61cbaa\x2da0a7\x2d0f4f\x2da81c\x2dcbc856a6176e.device
2.773s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart2.device
2.773s dev-disk-by\x2duuid-aacb61fe\x2da7a0\x2d4f0f\x2da81c\x2dcbc856a6176e.device
 722ms initrd-switch-root.service
 502ms tlp.service
 348ms systemd-udev-trigger.service
 319ms systemd-remount-fs.service
 299ms systemd-modules-load.service
 266ms run-media-cone-Orico\x2dnvme\x2denclosure.mount
 201ms modprobe@fuse.service
 172ms modprobe@drm.service
 163ms systemd-fsck@dev-disk-by\x2duuid-F00D\x2d6BA8.service
 144ms avahi-daemon.service
 143ms lvm2-monitor.service
 140ms polkit.service
 138ms user@1000.service
 102ms systemd-journal-flush.service
  98ms apparmor.service
  90ms systemd-tmpfiles-setup.service
  89ms systemd-tmpfiles-setup-dev.service
  77ms boot-efi.mount
  72ms ModemManager.service
  65ms set-cfs-tweaks.service
  63ms cups.service
  60ms kmod-static-nodes.service
  60ms systemd-sysctl.service
  56ms systemd-zram-setup@zram0.service
  51ms systemd-user-sessions.service
  49ms upower.service
  47ms systemd-binfmt.service
  46ms user-runtime-dir@1000.service
  46ms systemd-udevd.service
  44ms packagekit.service
  42ms NetworkManager-wait-online.service
  42ms udisks2.service
  41ms accounts-daemon.service
  37ms systemd-timesyncd.service
  37ms modprobe@configfs.service
  36ms dev-zram0.swap
  32ms modprobe@loop.service
  30ms systemd-random-seed.service
  29ms alsa-restore.service
  29ms systemd-update-utmp.service
  28ms linux-module-cleanup.service
  27ms dbus.service
  25ms systemd-logind.service
  20ms NetworkManager.service
  10ms systemd-journald.service
   9ms systemd-fsck-root.service
   8ms dev-hugepages.mount
   8ms dev-mqueue.mount
   8ms sys-kernel-debug.mount
   7ms sys-kernel-tracing.mount
   7ms wpa_supplicant.service
   6ms initrd-parse-etc.service
   5ms initrd-cleanup.service
   3ms sys-fs-fuse-connections.mount
   3ms initrd-udevadm-cleanup-db.service
   3ms systemd-rfkill.service
   3ms sys-kernel-config.mount
   2ms rtkit-daemon.service
   1ms modprobe@dm_mod.service
   1ms proc-sys-fs-binfmt_misc.mount
   1ms tmp.mount

my inxi output:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = "",
        LC_ALL = (unset),
        LC_ADDRESS = "el_GR.UTF-8",
        LC_IDENTIFICATION = "el_GR.UTF-8",
        LC_MEASUREMENT = "el_GR.UTF-8",
        LC_MONETARY = "el_GR.UTF-8",
        LC_NAME = "el_GR.UTF-8",
        LC_NUMERIC = "en_US.UTF-8",
        LC_PAPER = "el_GR.UTF-8",
        LC_TELEPHONE = "el_GR.UTF-8",
        LC_TIME = "en_JE.UTF-8",
        LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
System:
  Kernel: 6.1.36-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=aacb61fe-a7a0-4f0f-a81c-cbc856a6176e rw nvidia-drm.modeset=1
    quiet loglevel=3 apparmor=1 security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 info: latte-dock
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: B450 TOMAHAWK MAX (MS-7C02) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 3.F0
    date: 07/23/2022
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: available: 15.54 GiB used: 5.45 GiB (35.1%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 gen: 3
    level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 32 MiB
    desc: 2x16 MiB
  Speed (MHz): avg: 2410 high: 3601 min/max: 2200/4208 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2200 2: 2200
    3: 2200 4: 2058 5: 3600 6: 2056 7: 2200 8: 2208 9: 2200 10: 2200 11: 3601
    12: 2200 bogomips: 86444
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs
    irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
    msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae
    pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
    pfthreshold pge pni popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a
    rdtscp rep_good sep sev sev_es sha_ni skinit smap smca smep ssbd sse sse2
    sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext
    tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme vmmcall
    wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt
  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: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  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:
    always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660] vendor: Micro-Star MSI
    driver: nvidia v: 535.54.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
    status: current (as of 2023-05) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: DP-3 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 26:00.0
    chip-ID: 10de:2184 class-ID: 0300
  Device-2: Microdia USB 2.0 Camera driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:3 chip-ID: 0c45:636d
    class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.2
    compositor: kwin_wayland driver: X: loaded: nvidia gpu: nvidia display-ID: 0
  Monitor-1: DP-3 res: 1920x1080 size: N/A modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 535.54.03 renderer: NVIDIA GeForce GTX
    1660/PCIe/SSE2 direct-render: Yes
Audio:
  Device-1: NVIDIA TU116 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 26:00.1 chip-ID: 10de:1aeb class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 28:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Microdia USB 2.0 Camera driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:3 chip-ID: 0c45:636d
    class-ID: 0102 serial: <filter>
  API: ALSA v: k6.1.36-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: qjackctl
  Server-3: PipeWire v: 0.3.71 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 21:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp34s0 state: down mac: <filter>
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 3.18 TiB used: 2.44 TiB (76.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SA2000M81000G
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: S5Z42105 temp: 38.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 3B6Q scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: Portable SSD T5
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 3.1 spd: 10 Gb/s lanes: 1 mode: 3.2 gen-2x1 tech: SSD serial: <filter>
    scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 vendor: Realtek model: RTL9210B-CG
    size: 931.51 GiB block-size: physical: 2048 B logical: 512 B type: USB
    rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: 1.00 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 216.1 GiB size: 212.53 GiB (98.35%) used: 165.9 GiB (78.1%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A
    uuid: aacb61fe-a7a0-4f0f-a81c-cbc856a6176e
  ID-2: /boot/efi raw-size: 99 MiB size: 95 MiB (95.96%)
    used: 25.5 MiB (26.9%) fs: vfat dev: /dev/sda2 maj-min: 8:2 label: N/A
    uuid: F00D-6BA8
  ID-3: /run/media/cone/Game-Storage-Vids raw-size: 715.4 GiB
    size: 715.4 GiB (100.00%) used: 691.61 GiB (96.7%) fs: ntfs
    dev: /dev/nvme0n1p1 maj-min: 259:1 label: Game-Storage-Vids
    uuid: 2EECD6A5ECD6669D
  ID-4: /run/media/cone/Orico-nvme-enclosure raw-size: 931.51 GiB
    size: 931.51 GiB (100.00%) used: 876.49 GiB (94.1%) fs: btrfs dev: /dev/sdc1
    maj-min: 8:33 label: Orico-nvme-enclosure
    uuid: d1bd3c91-2e1d-43a7-9531-6effba6ce0b0
  ID-5: /run/media/cone/Samsung_T5 raw-size: 931.51 GiB
    size: 931.48 GiB (100.00%) used: 763.64 GiB (82.0%) fs: exfat dev: /dev/sdb1
    maj-min: 8:17 label: Samsung_T5 uuid: AE71-3943
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 7.77 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 529 MiB fs: ntfs label: Recovery
    uuid: 647C0D647C0D327A
  ID-2: /dev/sda3 maj-min: 8:3 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-3: /dev/sda4 maj-min: 8:4 size: 464.54 GiB fs: ntfs
    label: Samsung-evo-870-512gb uuid: 4CD61975D619610E
  ID-4: /dev/sda5 maj-min: 8:5 size: 602 MiB fs: ntfs label: N/A
    uuid: 9CB8772DB87704D4
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-8:2 info: Razer USA Huntsman type: keyboard,mouse
    driver: razerkbd,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1532:0227 class-ID: 0300
  Device-2: 1-9:3 info: Microdia USB 2.0 Camera type: video,audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 0c45:636d class-ID: 0102 serial: <filter>
  Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-2:2 info: Samsung Portable SSD T5 type: mass storage
    driver: uas interfaces: 1 rev: 3.1 speed: 10 Gb/s (1.16 GiB/s) lanes: 1
    mode: 3.2 gen-2x1 power: 896mA chip-ID: 04e8:61f5 class-ID: 0806
    serial: <filter>
  Device-2: 2-3:3 info: Realtek RTL9210 M.2 NVME Adapter type: mass storage
    driver: uas interfaces: 1 rev: 3.2 speed: 5 Gb/s (596.0 MiB/s) lanes: 1
    mode: 3.2 gen-1x1 power: 896mA chip-ID: 0bda:9210 class-ID: 0806
    serial: <filter>
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 5-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 5-1:2 info: Razer USA RZ01-0321 Gaming Mouse [DeathAdder V2]
    type: mouse,keyboard driver: razermouse,usbhid interfaces: 4 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 1532:0084 class-ID: 0300
  Hub-6: 6-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 52.5 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 369 Uptime: 21m wakeups: 0 Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 13.1.1 alt: 12 clang: 15.0.7 Packages: 1933
  pm: pacman pkgs: 1876 libs: 418 tools: pamac pm: flatpak pkgs: 57 Shell: Zsh
  v: 5.9 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.27
2

may you post the output of the inxi command described below. that shows all of us a more detailed overview which kernel, gui, etc you’re on
:+1: Welcome to Manjaro! :+1:

  1. Please read this:
    [HowTo] Provide System Information
    and press the three dots … below your post and press the :pencil2: to give us more information so we can see what’s really going on.
    Now we know the symptom of the disease, but we need some more probing to know where the origin lies… :grin:
  2. An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
    Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text. (use the option “preformatted text”)

:+1:

3

Welcome to the forum! :vulcan_salute:

Those are serial terminals. Do you have anything attached to your serial port?

4

As far as I know, no. I have some external USB drives if those count?

5

No, those would not be identified as serial terminals.

6

Anything i can provide to help?

7

No, I’m afraid I have to decline at this point, and hope that someone more knowledgeable than me can pick up on it. :frowning_man: :man_shrugging:

Just one last question: are you using an old-fashioned modem? If so, that could explain the serial terminals. :thinking:

8

Hi @ByConi,

I did a bit of a search, which lead me to this page which in turn lead me to this page, which also sadly didn’t help me much but maybe it does you.

Then I scrolled a bit further on the page in the second link, and:

`systemd-analyze blame` showing way more devices than before · Issue #23629 · systemd/systemd · GitHub

This issue was filed here a while ago. New issue with systemd 251. Expected fixed in 252

Yet, it would seem we are passed that already:

$ pamac search systemd
[...]
systemd                                                                                                                                                                                           [Installed] 253.4-1                              core
system and service manager

So, in summary:

:man_shrugging:

Sorry

:sob:

9

Thank you very much for your help, I’m not on an old fashioned modem or anything. Just seems to be some kind of bug. Maybe an update will come along and fix it? Who knows. Thanks for the help anyways

10

I don’t know if this is applicable or not, but have a look at:

11

Ok will try next boot without my USB drives! Thank you.

1 Like
12

It looks like you have something like 32 TTYs … this shouldnt be the case.
Can you check

find /etc/systemd/ -type f -exec grep VT {} \;
13

Result:

#NAutoVTs=6
#ReserveVT=6
#CrashChangeVT=no
14

Ok it did not fix it

1 Like
15

I have a similarly long list of tty devices. However, they don’t slow down boot time.

A better view on timings would be systemd-analyze critical-chain and systemd-analyze time

1 Like
16

Here’s that output in case it helps

graphical.target @2.269s
└─sddm.service @2.269s
  └─systemd-user-sessions.service @2.227s +38ms
    └─network.target @2.226s
      └─wpa_supplicant.service @3.006s +6ms
        └─dbus.service @2.048s +65ms
          └─basic.target @2.015s
            └─sockets.target @2.015s
              └─dbus.socket @2.015s
                └─sysinit.target @2.013s
                  └─systemd-update-done.service @1.934s +78ms
                    └─systemd-journal-catalog-update.service @1.856s +53ms
                      └─systemd-tmpfiles-setup.service @1.707s +102ms
                        └─local-fs.target @1.705s
                          └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @1.708s
                            └─local-fs-pre.target @1.133s
                              └─systemd-tmpfiles-setup-dev.service @1.090s +43ms
                                └─systemd-sysusers.service @1.002s +67ms
                                  └─systemd-remount-fs.service @664ms +286ms
                                    └─systemd-fsck-root.service @584542y 2w 2d 20h 1min 48.628s +8ms
                                      └─systemd-journald.socket
                                        └─system.slice
                                          └─-.slice
17 
└─systemd-fsck-root.service @584542y 2w 2d 20h 1min 48.628s +8ms

This line is especially weird.
Is your time in UEFI set correctly? Might be an empty CMOS battery if this keeps on happening.
However, do you usually shut down your computer property or kill it slowing by either pressing the power button or quickly by turning of the power?

18

I never hard shutdown, always do it the proper way (except when the system is unresponsive of course).

19

I have a general rule…never start something that takes longer than 500,000 years. :grin:

1 Like
20

Why not :frowning: