Systemd-analyze error

System:
  Kernel: 6.0.12-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux
    root=UUID=f8b64331-9f73-4b5e-8666-683f1b7a55e6 rw [email protected]
    quiet
    cryptdevice=UUID=2e774d55-b39d-4dc3-ab93-dd9d934dd845:luks-2e774d55-b39d-4dc3-ab93-dd9d934dd845
    root=/dev/mapper/luks-2e774d55-b39d-4dc3-ab93-dd9d934dd845 quiet splash
    rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=/dev/mapper/luks-452ae4ef-dbd7-40fd-8185-ce7166dceb2c loglevel=3
    ibt=off
  Desktop: KDE Plasma v: 5.26.4 tk: Qt v: 5.15.7 info: latte-dock
    wm: kwin_x11 vt: 1 dm: 1: LightDM v: 1.32.0 note: stopped 2: SDDM
    note: stopped Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: Micro-Star product: GP63 Leopard 8RD v: REV:1.0
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Micro-Star model: MS-16P6 v: REV:1.0 serial: <superuser required>
    UEFI: American Megatrends v: E16P6IMS.109 date: 05/22/2019
Battery:
  ID-1: BAT1 charge: 40.7 Wh (98.1%) condition: 41.5/53.4 Wh (77.7%)
    volts: 11.9 min: 10.9 model: MSI Corp. MS-16P6 type: Li-ion serial: N/A
    status: not charging
  Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Coffee Lake
    gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xF0
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 9 MiB desc: 1x9 MiB
  Speed (MHz): avg: 2516 high: 4102 min/max: 800/4100 scaling:
    driver: intel_pstate governor: powersave cores: 1: 2200 2: 4101 3: 2200
    4: 4102 5: 2200 6: 2200 7: 2200 8: 2200 9: 2200 10: 2200 11: 2200 12: 2200
    bogomips: 52815
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  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: IBRS, IBPB: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Micro-Star MSI
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: HDMI-A-2 off: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:3e9b class-ID: 0300
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile]
    vendor: Micro-Star MSI driver: nvidia v: 525.60.11
    alternate: nouveau,nvidia_drm non-free: 525.xx+
    status: current (as of 2022-12) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1c8c
    class-ID: 0302
  Device-3: Acer HD Webcam type: USB driver: uvcvideo bus-ID: 1-13:7
    chip-ID: 5986:211b class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.5 with: Xwayland v: 22.1.6
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia dri: iris
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1360x768 s-dpi: 96 s-size: 358x202mm (14.09x7.95")
    s-diag: 411mm (16.18")
  Monitor-1: HDMI-A-2 mapped: HDMI-2 pos: primary model: NS-39D220NA16
    serial: <filter> built: 2015 res: 1360x768 hz: 60 dpi: 49 gamma: 1.2
    size: 698x392mm (27.48x15.43") diag: 976mm (38.4") ratio: 16:9 modes:
    max: 1360x768 min: 720x400
  Monitor-2: eDP-1 note: disabled model: LG Display 0x0590 built: 2017
    res: 1360x768 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
  API: OpenGL v: 4.6 Mesa 22.3.1 renderer: Mesa Intel UHD Graphics 630 (CFL
    GT2) direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl
    bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
  Sound API: ALSA v: k6.0.12-arch1-1 running: yes
  Sound Interface: sndio v: N/A running: no
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.63 running: yes
Network:
  Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Qualcomm Atheros Killer E2400 Gigabit Ethernet
    vendor: Micro-Star MSI driver: alx v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 1969:e0a1 class-ID: 0200
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB
    driver: btusb v: 0.8 bus-ID: 1-14:8 chip-ID: 8087:0aaa class-ID: e001
  Report: bt-adapter note: tool can't run ID: hci0 rfk-id: 1 state: down
    bt-service: disabled rfk-block: hardware: no software: no address: N/A
Drives:
  Local Storage: total: 1.84 TiB used: 840.88 GiB (44.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 2B2QEXE7 temp: 41.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 model: SATA SSD size: 953.87 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter>
    rev: 61.3 temp: 33 C scheme: MBR
Partition:
  ID-1: / raw-size: 914.2 GiB size: 914.2 GiB (100.00%)
    used: 408.56 GiB (44.7%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-2e774d55-b39d-4dc3-ab93-dd9d934dd845
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 752 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 914.2 GiB size: 914.2 GiB (100.00%)
    used: 408.56 GiB (44.7%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-2e774d55-b39d-4dc3-ab93-dd9d934dd845
  ID-4: /var/log raw-size: 914.2 GiB size: 914.2 GiB (100.00%)
    used: 408.56 GiB (44.7%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-2e774d55-b39d-4dc3-ab93-dd9d934dd845
  ID-5: /var/tmp raw-size: 914.2 GiB size: 914.2 GiB (100.00%)
    used: 408.56 GiB (44.7%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-2e774d55-b39d-4dc3-ab93-dd9d934dd845
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.47 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 17.01 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/dm-1 maj-min: 254:1
    mapped: luks-452ae4ef-dbd7-40fd-8185-ce7166dceb2c
Sensors:
  System Temperatures: cpu: 61.0 C pch: 65.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 351 Uptime: 4m wakeups: 3 Memory: 15.47 GiB
  used: 2.17 GiB (14.0%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.0 alt: 11 clang: 14.0.6 Packages:
  pm: pacman pkgs: 2301 libs: 558 tools: cylon,pamac,paru,trizen,yay
  Shell: Bash v: 5.1.16 running-in: gnome-terminal inxi: 3.3.24
Garuda (2.6.10-1):
  System install date:     2022-12-12
  Last full system update: 2022-12-16
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Snapper
  Failed units: 

Dec 16 11:08:45 jedi-gp63leopard8rd kernel: x86/cpu: SGX disabled by BIOS.
Dec 16 11:08:50 jedi-gp63leopard8rd kernel: 
Dec 16 11:08:50 jedi-gp63leopard8rd kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  525.60.11  Wed Nov 23
 23:04:03 UTC 2022
Dec 16 11:09:06 jedi-gp63leopard8rd systemd[2940]: Failed to start BTRFS Assistant Snapper check.
Dec 16 11:09:06 jedi-gp63leopard8rd systemd-analyze[4282]: Bootup is not yet finished (org.freedesktop.systemd1.M
anager.FinishTimestampMonotonic=0).
Dec 16 11:09:06 jedi-gp63leopard8rd systemd-analyze[4282]: Please try again later.
Dec 16 11:09:06 jedi-gp63leopard8rd systemd-analyze[4282]: Hint: Use 'systemctl list-jobs' to see active jobs
Dec 16 11:09:07 jedi-gp63leopard8rd systemd-analyze[4296]: Bootup is not yet finished (org.freedesktop.systemd1.M
anager.FinishTimestampMonotonic=0).
Dec 16 11:09:07 jedi-gp63leopard8rd systemd-analyze[4296]: Please try again later.
Dec 16 11:09:07 jedi-gp63leopard8rd systemd-analyze[4296]: Hint: Use 'systemctl list-jobs' to see active jobs
Dec 16 11:10:14 jedi-gp63leopard8rd systemd[1]: Timed out waiting for device /dev/virtio-ports/org.qemu.guest_age
nt.0.

[[email protected] ~]$ systemctl list-jobs 
No jobs running.

systemd-analyze critical-chain

systemd-analyze plot >bootup.svg
eog bootup.svg&
1 Like

Is there something I am looking for in particular in this image?

First, sometimes it fixed itself after some re/boot.
Check your fstab, wrong UUID, not existing volumes.
In the log check the time.

Reboot did not work.
No issue in fstab.
Trying to upload image. Says to large.
Most of my searches for this issue are pointing to plymouth as the culprit.

[[email protected] ~]$ 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 @1min 30.895s
└─multi-user.target @1min 30.895s
  └─garuda-virtualmachine-guest-config.target @1min 30.895s
    └─spice-vdagentd.socket @2.884s
      └─sysinit.target @2.842s
        └─systemd-update-done.service @2.761s +80ms
          └─ldconfig.service @2.087s +610ms
            └─local-fs.target @2.085s
              └─run-user-1000-doc.mount @20.013s
                └─run-user-1000.mount @19.261s
                  └─swap.target @1.966s
                    └─dev-mapper-luks\x2d452ae4ef\x2ddbd7\x2d40fd\x2d8185\x2dce7166dceb2c.swap @1.858s +27ms
                      └─[email protected]\x2d452ae4ef\x2ddbd7\x2d40fd\x2d8185\x2dce7166dceb2c.target @1.790s
                        └─[email protected]\x2d452ae4ef\x2ddbd7\x2d40fd\x2d8185\x2dce7166dceb2c.service @1.624s +113ms
                          └─dev-disk-by\x2duuid-452ae4ef\x2ddbd7\x2d40fd\x2d8185\x2dce7166dceb2c.device @1.566s
[[email protected] ~]$

Try to enable SGX in your BIOS (it may be set to disabled or software defined).

Remove splash or quiet splash from kernel parameters.

1 Like

No SGX option available in BIOS.
Removed quiet splash from kdernel parameters. Same result.

Can you describe what is happening? There are just a few random log messages pasted in the thread with no context. It's unclear what problem you are trying to solve.

It looks like you have a broken QEMU setup that hangs until timing out. Can you tell us anything about that?

1 Like

I check the error log frequently to see if there is something that needs to be addressed. When I saw the message about bootup is not yet finished I am wondering why that is. As you pointed out the qemu issue that could very well be the cause of the issue. I will have to research that particular issue. I do use qemu to test distros with virtual machine manager. Once again I will need to research that particular issue to see if it is related to thread topic. If anyone know about that particular issue I would love to know. Thanks to everyone for the support.

Findings from error message "Bootup is not yet finished":
for me this error is occurring when logging into KDE. It occurs some time between when I press "Enter" to login and when the desktop is displayed. There is about a 5 second period where the screen will remain blank and then the desktop will be displayed. One of the issues causing this delay was certain applications loading their icons to the task tray such as kdeconnect. Disabling this application from autostart has resolved this issue. This issue does not hinder any functionality or performance but is annoying to see in the error log. Also logging into Cinnamon DE did not produce the error.

Finding from error message "qemu":
I am still attempting to resolve this issue. I have installed the qemu-guest-agent but have been unable to get the service to start. Below is terminal output of what I have tried so far.

Dec 17 16:40:22 jedi-gp63leopard8rd systemd[1]: Timed out waiting for device /dev/virtio-ports/org.qemu.guest_agent.0.

[[email protected] ~]$ sudo systemctl status qemu-guest-agent.service --no-pager 
○ qemu-guest-agent.service - QEMU Guest Agent
     Loaded: loaded (/usr/lib/systemd/system/qemu-guest-agent.service; static)
     Active: inactive (dead)

Dec 17 12:13:25 jedi-gp63leopard8rd systemd[1]: Dependency failed for QEMU Guest Agent.
Dec 17 12:13:25 jedi-gp63leopard8rd systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with resu…ndency'.
Dec 17 16:40:22 jedi-gp63leopard8rd systemd[1]: Dependency failed for QEMU Guest Agent.
Dec 17 16:40:22 jedi-gp63leopard8rd systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with resu…ndency'.
Hint: Some lines were ellipsized, use -l to show in full.

[[email protected] ~]$ clear ; sudo systemctl list-dependencies qemu-guest-agent.service
qemu-guest-agent.service
○ ├─dev-virtio\x2dports-org.qemu.guest_agent.0.device
● ├─system.slice
● └─sysinit.target
●   ├─dev-hugepages.mount
●   ├─dev-mqueue.mount
●   ├─kmod-static-nodes.service
●   ├─ldconfig.service
●   ├─lvm2-lvmpolld.socket
●   ├─lvm2-monitor.service
●   ├─plymouth-read-write.service
●   ├─plymouth-start.service
●   ├─proc-sys-fs-binfmt_misc.automount
●   ├─sys-fs-fuse-connections.mount
●   ├─sys-kernel-config.mount
●   ├─sys-kernel-debug.mount
●   ├─sys-kernel-tracing.mount
○   ├─systemd-ask-password-console.path
●   ├─systemd-binfmt.service
○   ├─systemd-boot-system-token.service
○   ├─systemd-firstboot.service
○   ├─systemd-hwdb-update.service
●   ├─systemd-journal-catalog-update.service
●   ├─systemd-journal-flush.service
●   ├─systemd-journald.service
○   ├─systemd-machine-id-commit.service
●   ├─systemd-modules-load.service
○   ├─systemd-pcrphase-sysinit.service
○   ├─systemd-pcrphase.service
●   ├─systemd-random-seed.service
○   ├─systemd-repart.service
●   ├─systemd-sysctl.service
●   ├─systemd-sysusers.service
●   ├─systemd-timesyncd.service
●   ├─systemd-tmpfiles-setup-dev.service
●   ├─systemd-tmpfiles-setup.service
●   ├─systemd-udev-trigger.service
●   ├─systemd-udevd.service
●   ├─systemd-update-done.service
●   ├─systemd-update-utmp.service
●   ├─cryptsetup.target
●   │ ├─[email protected]\x2d2e774d55\x2db39d\x2d4dc3\x2dab93\x2ddd9d934dd845.service
●   │ └─[email protected]\x2d452ae4ef\x2ddbd7\x2d40fd\x2d8185\x2dce7166dceb2c.service
●   ├─integritysetup.target
●   ├─local-fs.target
●   │ ├─-.mount
●   │ ├─boot-efi.mount
●   │ ├─home.mount
●   │ ├─root.mount
●   │ ├─srv.mount
●   │ ├─systemd-remount-fs.service
●   │ ├─tmp.mount
●   │ ├─var-cache.mount
●   │ ├─var-log.mount
●   │ └─var-tmp.mount
●   ├─swap.target
●   │ ├─dev-mapper-luks\x2d452ae4ef\x2ddbd7\x2d40fd\x2d8185\x2dce7166dceb2c.swap
●   │ └─dev-zram0.swap
●   └─veritysetup.target

https://wiki.archlinux.org/title/Virt-Manager
Resolved issue.

Findings for "SGX BIOS" issue:
https://forums.linuxmint.com/viewtopic.php?t=358981
Resolved issue.

Dec 17 20:25:12 jedi-gp63leopard8rd kernel: 
Dec 17 20:25:12 jedi-gp63leopard8rd kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  525.60.11  Wed Nov 23 23:04:03 UTC 2022
[[email protected] ~]$

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