Long boot + Suspend doesn't work

Issues & Assistance Hyprland | Community
1

Hello Community!

during the middle of the day my computer suddenly failed to properly suspend. The swaylock appears but the computer never suspends. This worked perfectly fine the whole day and suddenly it didn’t.

I then updated the whole system only to see that the boot process takes ~5 minutes compared to the few seconds it does usually. It’s stuck on the initramfs part but ulitmately boots properly without issues.

I now updated my bios aswell but i have the exact same issues still.

Here is the inxi (PS: the System install date is completely wrong. I have installed this system months ago but everytime i do a full update, this timer get’s reset for whatever reason)

garuda-inxi
System:
  Kernel: 6.10.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=70298202-3941-4097-b3f6-9e9ab18d10bf rw rootflags=subvol=@
    quiet resume=UUID=2a710883-dad9-4c61-a48e-9712c540943e loglevel=3 ibt=off
  Desktop: Hyprland v: 0.42.0-50-g883463f9 with: waybar tools:
    avail: swayidle,swaylock vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-I GAMING v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    UEFI: American Megatrends v: 5013 date: 03/18/2024
CPU:
  Info: model: AMD Ryzen 7 5800X3D bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA20120E
  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: 96 MiB desc: 1x96 MiB
  Speed (MHz): avg: 3424 high: 4317 min/max: 2200/4549 boost: enabled
    scaling: driver: acpi-cpufreq governor: ondemand cores: 1: 3445 2: 3624
    3: 3453 4: 4317 5: 3450 6: 2200 7: 3400 8: 2200 9: 3453 10: 3714 11: 3453
    12: 4301 13: 3452 14: 3435 15: 3447 16: 3450 bogomips: 108590
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M]
    vendor: Sapphire PULSE driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x
    process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: DP-1,HDMI-A-1 empty: DP-2,HDMI-A-2,Writeback-1
    bus-ID: 0c:00.0 chip-ID: 1002:744c class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
    compositor: Hyprland v: 0.42.0-50-g883463f9 driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: 1
  Monitor-1: DP-1 model: AOC U34G2G4R3 serial: <filter> built: 2020
    res: 3440x1440 hz: 144 dpi: 110 gamma: 1.2 scale: 1
    size: 797x334mm (31.38x13.15") diag: 864mm (34") modes: max: 3440x1440
    min: 720x400
  Monitor-2: HDMI-A-1 model: AOC 2460G5 serial: <filter> built: 2018
    res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2 scale: 1
    size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XT (radeonsi
    navi31 LLVM 18.1.8 DRM 3.57 6.10.6-zen1-1-zen) device-ID: 1002:744c
    memory: 19.53 GiB unified: no
  API: Vulkan v: 1.3.279 layers: 11 device: 0 type: discrete-gpu name: AMD
    Radeon RX 7900 XT (RADV NAVI31) driver: mesa radv v: 24.1.6-arch1.1
    device-ID: 1002:744c surfaces: xcb,xlib,wayland device: 1
    type: discrete-gpu name: AMD Radeon RX 7900 XT driver: amd v: (LLPC)
    device-ID: 1002:744c surfaces: xcb,xlib,wayland device: 2 type: cpu
    name: llvmpipe (LLVM 18.1.8 256 bits) driver: mesa llvmpipe
    v: 24.1.6-arch1.1 (LLVM 18.1.8) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
Audio:
  Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0c:00.1 chip-ID: 1002:ab30
    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: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: SteelSeries ApS GameDAC driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3.2:11
    chip-ID: 1038:1283 class-ID: 0300 serial: <filter>
  API: ALSA v: k6.10.6-zen1-1-zen status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.2.2 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp5s0 state: down mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, sshd, systemd-timesyncd,
    wpa_supplicant
Bluetooth:
  Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2.1.1:8
    chip-ID: 0b05:17cb class-ID: fe01 serial: <filter>
  Report: btmgmt ID: hci1 rfk-id: 1 state: up address: <filter> bt-v: 4.0
    lmp-v: 6 status: discoverable: yes pairing: yes class-ID: 6c0104
  Device-2: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-6:3 chip-ID: 8087:0029
    class-ID: e001
  Report: ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
  Local Storage: total: 3.64 TiB used: 2.04 TiB (56.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 1TB 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: 2B2QEXM7 temp: 45.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1000MX500SSD1
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 033 scheme: GPT
Partition:
  ID-1: / raw-size: 862.24 GiB size: 862.24 GiB (100.00%)
    used: 666.69 GiB (77.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 862.24 GiB size: 862.24 GiB (100.00%)
    used: 666.69 GiB (77.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 862.24 GiB size: 862.24 GiB (100.00%)
    used: 666.69 GiB (77.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 862.24 GiB size: 862.24 GiB (100.00%)
    used: 666.69 GiB (77.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 62.71 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 68.97 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 47.5 C mobo: 42.0 C gpu: amdgpu temp: 43.0 C
    mem: 48.0 C
  Fan Speeds (rpm): fan-1: 1043 fan-2: 1877 fan-5: 1032 fan-7: 0 gpu: amdgpu
    fan: 0
Info:
  Memory: total: 64 GiB note: est. available: 62.71 GiB used: 8.08 GiB (12.9%)
  Processes: 463 Power: uptime: 4m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 25.07 GiB services: upowerd Init: systemd
    v: 256 default: graphical tool: systemctl
  Packages: 2469 pm: pacman pkgs: 2436 libs: 578 tools: pacseek,paru
    pm: flatpak pkgs: 33 Compilers: clang: 18.1.8 gcc: 14.2.1 alt: 12
    Shell: garuda-inxi default: fish v: 3.7.1 running-in: alacritty
    inxi: 3.3.35
Garuda (2.6.26-1):
  System install date:     2024-08-20
  Last full system update: 2024-08-21
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:

of course suspending works now that i’ve tried it again for the what felt like 10th time after this post…

The long boot time is still concerning though :thinking:

3

Maybe you should check the logfile to see why it takes so long, or you should be able to read along with the boot process, because it should run slowly.

Also check

systemd-analyze
systemd-analyze blame
1 Like
4

I tried pressing escape during boot but the processes don’t show up for me

Regarding logs, i am super bad with finding out where and how to find the relevant logs for each process. Can you give me a hint?

5

Above your post and from fish config use jctl in terminal

alias jctl="journalctl -p 3 -xb"
1 Like
6

I get an awful lot of lines in that systemd-analyze blame command about

dev-disk-by\x2did and the likes

7

use both, the first is short, the long you can upload to https://bin.garudalinux.org/

Did you change hardware, disks?
Check /etc/fstab

2 Likes
8

the long one:

9

i didn’t change anything about my system.

My /etc/fstab looks just like it looked before

10

:wink: :smiley:

11

Would be record time for me to make a coffee in 1min 30, but i certainly was able to make a coffe without rushing it during the boot :smiley:

I guess that means something wasn’t tracked here and / or hung before landing in the logs

12

Also 1min 30s is a multitude longer than the few seconds it usually takes :thinking:

Can you see something concerning in those logs?

Without any proof to back it up, i would say that it usually takes around 20 seconds to boot

13

Startup finished in 56.817s (firmware) + 6.279s (loader) + 2min 22.132s (kernel) + 1.732s (initrd) + 1min 30.460s (userspace) = 4min 57.421s

That was in the short command btw :smiley: So my 5 minutes were pretty damn close it seems :smiley:

Also i ran a short SMART test on my nvme and it passed without issues. I can also run a long test aswell but i don’t know if that actually has some use here

14

Rebooted again.


systemd-analyze
Startup finished in 38.334s (firmware) + 10.594s (loader) + 1.068s (kernel) + 1min 36.736s (initrd) + 1min 30.409s (userspace) = 3min 57.145s
graphical.target reached after 8.170s in userspace.

Now suspend doesn’t work again :sweat_smile:

15

running
sudo journalctl -b

i found this:

nvme 0000:04:00.0: PM: pci_pm_suspend(): nvme_suspend [nvme] returns -16
Aug 22 15:10:17 frank-garuda kernel: nvme 0000:04:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -16
Aug 22 15:10:17 frank-garuda kernel: nvme 0000:04:00.0: PM: failed to suspend async: error -16
Aug 22 15:10:17 frank-garuda kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Aug 22 15:10:17 frank-garuda kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache
Aug 22 15:10:17 frank-garuda kernel: PM: Some devices failed to suspend, or early wake event detected
Aug 22 15:10:17 frank-garuda kernel: OOM killer enabled.
Aug 22 15:10:17 frank-garuda kernel: Restarting tasks ... done.
Aug 22 15:10:17 frank-garuda kernel: random: crng reseeded on system resumption
Aug 22 15:10:17 frank-garuda bluetoothd[1026]: Controller resume with wake event 0x0
Aug 22 15:10:17 frank-garuda kernel: PM: suspend exit
Aug 22 15:10:17 frank-garuda kernel: PM: suspend entry (s2idle)
Aug 22 15:10:17 frank-garuda kernel: Filesystems sync: 0.015 seconds
Aug 22 15:10:18 frank-garuda kernel: Freezing user space processes
Aug 22 15:10:18 frank-garuda kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Aug 22 15:10:18 frank-garuda kernel: OOM killer disabled.
Aug 22 15:10:18 frank-garuda kernel: Freezing remaining freezable tasks
Aug 22 15:10:18 frank-garuda kernel: ata1: SATA link down (SStatus 0 SControl 300)
Aug 22 15:10:18 frank-garuda kernel: Freezing remaining freezable tasks completed (elapsed 0.145 seconds)
Aug 22 15:10:18 frank-garuda kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Aug 22 15:10:18 frank-garuda kernel: nvme 0000:04:00.0: PM: pci_pm_suspend(): nvme_suspend [nvme] returns -16
Aug 22 15:10:18 frank-garuda kernel: nvme 0000:04:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -16
Aug 22 15:10:18 frank-garuda kernel: nvme 0000:04:00.0: PM: failed to suspend async: error -16
Aug 22 15:10:18 frank-garuda kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache
Aug 22 15:10:18 frank-garuda kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Aug 22 15:10:18 frank-garuda kernel: PM: Some devices failed to suspend, or early wake event detected
Aug 22 15:10:18 frank-garuda kernel: OOM killer enabled.
Aug 22 15:10:18 frank-garuda kernel: Restarting tasks ... done.
Aug 22 15:10:18 frank-garuda kernel: random: crng reseeded on system resumption
Aug 22 15:10:18 frank-garuda systemd-sleep[127916]: Failed to put system to sleep. System resumed again: Device or resource busy
Aug 22 15:10:18 frank-garuda bluetoothd[1026]: Controller resume with wake event 0x0
Aug 22 15:10:18 frank-garuda kernel: PM: suspend exit
Aug 22 15:10:18 frank-garuda systemd-sleep[127916]: Successfully thawed unit 'user.slice'.
Aug 22 15:10:18 frank-garuda systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
Aug 22 15:10:18 frank-garuda systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
Aug 22 15:10:18 frank-garuda systemd[1]: Failed to start System Suspend.
Aug 22 15:10:18 frank-garuda systemd[1]: Dependency failed for Suspend.
Aug 22 15:10:18 frank-garuda systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
Aug 22 15:10:18 frank-garuda systemd-logind[1038]: Operation 'suspend' finished.
Aug 22 15:10:18 frank-garuda ModemManager[1125]: <msg> [sleep-monitor-systemd] system is resuming

so my nvme drive is failing to suspend :thinking:

16

Alright, found the solution - seems my second nvme drive is faulty.
Sometimes it appears in the bios, sometimes it wont.

When it appears, and subsequently appears in linux aswell, i can’t mount or format it - throwing errors about not being able to read the superblock.

Mystery solved i guess

1 Like
17

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