Shutdown takes upwards of 2min

Issues & Assistance Unsupported Software (AUR & Other)
1

Hi, I'm new to linux and have been using fedora KDE for a few weeks. I decided to move over to an arch based distro and decided to go with garuda linux. I've been enjoying it quite a lot, but I've encountered a weird issue. My shutdown times take upwards of 2 min. This only happens when I shutdown from within the session. If I first logout and then shutdown, it takes no longer than 20s.

This issue seems to be similar to the bug described in this KDE bug report: 445449 – Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM.

I'm not that well versed with linux so I havent tried much, since I'm affraid of breaking something. I tried changing my shutdown options, resting KDE and disabling my CPU OC, but nothing seems to help.

Console output:

System:
Kernel: 5.17.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=6aa451d8-b325-4bb2-913b-1fada89126f6 rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3
Desktop: KDE Plasma v: 5.24.4 tk: Qt v: 5.15.3 info: latte-dock
wm: kwin_wayland vt: 2 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B550-E GAMING v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 2604
date: 02/25/2022
Battery:
ID-1: hidpp_battery_0 charge: 41% condition: N/A volts: 3.8 min: N/A
model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse type: N/A
serial: <filter> status: discharging
CPU:
Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3
family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
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: 1x32 MiB
Speed (MHz): avg: 3600 high: 3692 min/max: 2200/4850 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3594 2: 3596
3: 3593 4: 3592 5: 3600 6: 3588 7: 3593 8: 3600 9: 3591 10: 3593 11: 3612
12: 3692 13: 3593 14: 3593 15: 3592 16: 3591 bogomips: 121600
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: 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, IBRS_FW,
STIBP: always-on, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6900 XT] vendor: Tul / PowerColor
driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: DP-2 off: DP-1 empty: DP-3,HDMI-A-1 bus-ID: 0a:00.0
chip-ID: 1002:73af class-ID: 0300
Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa gpu: amdgpu
display-ID: 0
Monitor-1: DP-2 res: 3840x1600 size: N/A modes: N/A
OpenGL: renderer: AMD Radeon RX 6900 XT (sienna_cichlid LLVM 13.0.1 DRM
3.44 5.17.1-zen1-1-zen)
v: 4.6 Mesa 22.0.0 direct render: Yes
Audio:
Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0a:00.1 chip-ID: 1002:ab28 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: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
Sound Server-1: ALSA v: k5.17.1-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.49 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp6s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 07:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp7s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-5:4 chip-ID: 8087:0029 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
Local Storage: total: 2.73 TiB used: 1.02 TiB (37.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Gigabyte
model: GP-ASM2NE6100TTTD size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: EGFM13.0 temp: 46.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Western Digital
model: WDS100T2B0C-00PXH0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 211210WD temp: 38.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 13.95 GiB (1.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 13.95 GiB (1.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 13.95 GiB (1.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 13.95 GiB (1.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.32 GiB used: 2.2 MiB (0.0%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 38.0 C mobo: 31.0 C gpu: amdgpu temp: 56.0 C
mem: 52.0 C
Fan Speeds (RPM): cpu: 705 gpu: amdgpu fan: 0
Info:
Processes: 432 Uptime: 56m wakeups: 2 Memory: 31.32 GiB
used: 4.99 GiB (15.9%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 Packages: pacman: 1536 lib: 490 Shell: fish v: 3.4.1
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.14
2

WELCOME to the Garuda Forums! :smiley:

What you could do is boot up, do what you need to do to reproduce the issue, shutdown or reboot and than upon the next boot up, login and issue this in Terminal (Konsole):

journalctl -b -1 -r

This will display all msgs logged from last boot (not the one you are booted into), sorting recursively through time (LIFO style).

4 Likes
3

Hi, thanks for the fast reply, but when I do that command I get upwards of 3k lines. I cant really post it here. Is there a way to filter the output?

4

Yes. you post it within the following:

~ ~ ~
HERE
~ ~ ~

3 tildes on first line (no spaces), 3 tildes on last line (no spaces).
On my installation it automatically shows a certain number of lines and I can manually scroll, not sure why it doesn't on yours. :frowning:

2 Likes
5

It is a KDE wayland bug. Switch to X until they fix it (don't hold your breath) or just deal with the log out first then reboot scenario. You can also use reboot but when it logs out to the blinking cursor hit CTRL+ALT+F1 and it will reboot normally.
EDIT
You can also enable the magic REISUB key:

[Tip] Enable Magic SysRq Key (REISUB) - General system / Kernel & Hardware - EndeavourOS

and use that for rebooting.

3 Likes
6

Here are the first 90 lines, after which I have to start manually scrolling.

Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounted /srv.
Apr 04 13:42:33 SmelterDemon systemd[1]: srv.mount: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounted /root.
Apr 04 13:42:33 SmelterDemon systemd[1]: root.mount: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounted /home.
Apr 04 13:42:33 SmelterDemon systemd[1]: home.mount: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounted /boot/efi.
Apr 04 13:42:33 SmelterDemon systemd[1]: boot-efi.mount: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopping Flush Journal to Persistent Storage...
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounting /var/tmp...
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounting /var/cache...
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounting /tmp...
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounting /srv...
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounting /run/media/ashen_one/SATASSD...
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounting /run/media/ashen_one/NVME3SSD...
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounting /root...
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounting /home...
Apr 04 13:42:33 SmelterDemon systemd[1]: Unmounting /boot/efi...
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped target Local File Systems.
Apr 04 13:42:33 SmelterDemon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped Create Volatile Files and Directories.
Apr 04 13:42:33 SmelterDemon systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped Record System Boot/Shutdown in UTMP.
Apr 04 13:42:33 SmelterDemon systemd[1]: systemd-update-utmp.service: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: proc-sys-fs-binfmt_misc.mount: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Unset automount Arbitrary Executable File Formats File System Automount Point.
Apr 04 13:42:33 SmelterDemon audit[39365]: SYSTEM_SHUTDOWN pid=39365 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: proc-sys-fs-binfmt_misc.automount: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-binfmt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped Set Up Additional Binary Formats.
Apr 04 13:42:33 SmelterDemon systemd[1]: systemd-binfmt.service: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon kernel: audit: type=1131 audit(1649072553.040:182): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped Network Time Synchronization.
Apr 04 13:42:33 SmelterDemon systemd[1]: systemd-timesyncd.service: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopping Record System Boot/Shutdown in UTMP...
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopping Network Time Synchronization...
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped Load Kernel Modules.
Apr 04 13:42:33 SmelterDemon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: systemd-modules-load.service: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped Apply Kernel Variables.
Apr 04 13:42:33 SmelterDemon systemd[1]: systemd-sysctl.service: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopping Set Up Additional Binary Formats...
Apr 04 13:42:33 SmelterDemon kernel: audit: type=1131 audit(1649072553.039:181): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped target Local Verity Protected Volumes.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped target Local Integrity Protected Volumes.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Apr 04 13:42:33 SmelterDemon systemd[1]: systemd-ask-password-wall.path: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped target Local Encrypted Volumes.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped target System Initialization.
Apr 04 13:42:33 SmelterDemon systemd[1]: Closed D-Bus System Message Bus Socket.
Apr 04 13:42:33 SmelterDemon systemd[1]: dbus.socket: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
Apr 04 13:42:33 SmelterDemon systemd[1]: avahi-daemon.socket: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped target Socket Units.
Apr 04 13:42:33 SmelterDemon systemd[1]: user.slice: Consumed 3min 30.406s CPU time.
Apr 04 13:42:33 SmelterDemon systemd[1]: Removed slice User and Session Slice.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped target Slice Units.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped Monitors for new snapshots.
Apr 04 13:42:33 SmelterDemon systemd[1]: grub-btrfs-snapper.path: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped target Path Units.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
Apr 04 13:42:33 SmelterDemon systemd[1]: systemd-ask-password-plymouth.path: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped target Basic System.
Apr 04 13:42:33 SmelterDemon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped D-Bus System Message Bus.
Apr 04 13:42:33 SmelterDemon systemd[1]: dbus.service: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon kernel: audit: type=1131 audit(1649072553.037:180): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopping D-Bus System Message Bus...
Apr 04 13:42:33 SmelterDemon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:33 SmelterDemon systemd[1]: Stopped Network Manager.
Apr 04 13:42:33 SmelterDemon systemd[1]: NetworkManager.service: Deactivated successfully.
Apr 04 13:42:33 SmelterDemon NetworkManager[590]: <info>  [1649072553.0350] exiting (success)
Apr 04 13:42:33 SmelterDemon dbus-daemon[572]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.
Apr 04 13:42:33 SmelterDemon dbus-daemon[572]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=590 comm="/usr/bin/NetworkManager --no-daemon")
Apr 04 13:42:33 SmelterDemon NetworkManager[590]: <info>  [1649072553.0292] device (p2p-dev-wlp6s0): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Apr 04 13:42:32 SmelterDemon kernel: audit: type=1334 audit(1649072552.849:179): prog-id=0 op=UNLOAD
Apr 04 13:42:32 SmelterDemon audit: BPF prog-id=0 op=UNLOAD
Apr 04 13:42:32 SmelterDemon kernel: audit: type=1131 audit(1649072552.834:178): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:32 SmelterDemon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:32 SmelterDemon systemd[1]: Stopped WPA supplicant.
Apr 04 13:42:32 SmelterDemon systemd[1]: wpa_supplicant.service: Deactivated successfully.
Apr 04 13:42:32 SmelterDemon NetworkManager[590]: <info>  [1649072552.8353] device (wlp6s0): set-hw-addr: reset MAC address to 44:AF:28:31:82:FB (unmanage)
Apr 04 13:42:32 SmelterDemon wpa_supplicant[2871]: wlp6s0: CTRL-EVENT-TERMINATING
Apr 04 13:42:32 SmelterDemon wpa_supplicant[2871]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Apr 04 13:42:32 SmelterDemon wpa_supplicant[2871]: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 04 13:42:32 SmelterDemon kernel: audit: type=1131 audit(1649072552.833:177): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 13:42:32 SmelterDemon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lines 1-90
7

Tnx @AshenOne
Basically when troubleshooting these things you need to look for a gap in the timestamp, cuz something is holding on the shutdown. Those 90 lines occurred most probably after what's holding on the shutdown as they are all within 1sec, but like elloquin said it seems to be a Wayland bug for which you'd have to wait until it gets fixed, so not much we could do about it...

8

I'll think Ill stick with just logging out. I sadly cant use X11 since I require VRR support while using two screens. That said, how dows Garuda sway compare to KDE? It should also support VRR while using two screens.

9

Well it was worth a try, that said thanks a lot for the help. Maybe I'll try sway since it also supports VRR with two screens.

10

Could you please try to do a CTRL+ALT+F1 after you shutdown and it seems to be hanging?
It happened to me in a different laptop where I was trying KDE + wayland.
Searching on the internet I found that workaround, and I remember it worked (shutting down safely, of course).
Unfurtunately it was only some kind of quick testing, so I don't remember much, nor took notes.

Edit: I see only now it was basically mentioned also by @elloquin. In my case, it worked also for shutdown, not only reboot.

2 Likes
11

It is not only a wayland bug, this happened to me under X, so much so, I took to the internets and found a solution.

Find the solution here. Scroll down to the section on installing and activating Watchdog. I had to get Watchdog from AUR, but after installing, no more 2 min waits.

4 Likes
12

That is a totally different issue. Similar but totally different. I have no such issues on x and do not need this fix to reboot. Watchdog errors are usually very specific to certain hardware.

2 Likes
13

Maybe not for YOU, but maybe it might help the OP. As you said, different systems.

2 Likes
14

Power off with Garuda Sway takes literally two seconds, sometimes one or less. It still takes me by surprise sometimes! :joy:

3 Likes
15
  • amdgpu kernel driver may be haunting around as well… hear me out :sunglasses:

@AshenOne Please run journalctl again… :arrow_up:

  • again… run journalctl - grep amdgpu - and pipe to less…
journalctl -b -1 -r | grep -A3 amdgpu | less

This should be interesting to scroll through for you. -)

Find the lines containing amdgpu :arrow_down:
Note ten or so lines before and after amdgpu failed to send message for hints…
Look closer in the journalctl output and search for lines like such:

Apr 04 14:09:30 garuda-iMac systemd[1]: sddm-plymouth.service: Consumed 59.497s CPU time.
Apr 04 14:09:30 garuda-iMac systemd[1]: Stopped Simple Desktop Display Manager.
Apr 04 14:09:30 garuda-iMac audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sddm-plymouth comm="sy>
Apr 04 14:09:30 garuda-iMac systemd[1]: sddqm-plymouth.service: Failed with result 'timeout'.
Apr 04 14:09:30 garuda-iMac kernel: amdgpu:
                                     failed to send message 146 ret is 0

:point_up_2: 1 minute 27 second GAP IN TIME STAMP STARTS HERE @14:09:30 marker…

Take note of this 1 minute 27 second GAP IN TIME STAMP here.

  • During this time gap no other processes except amdgpu are logged in journactl. Nothing. Nada.

For me, this is an/the issue comes with using certain AMD Radeon GPU Chips that run the kernels opensource amdgpu driver/module. the kernel driver amdgpu is causing/reporting this (01:27) one minute 27 second DELAY in this particular boot log instance.

This log is my machine here. Using amdgpu kernel opensource amd driver
that you are using also.

:point_down: 1 minute 27 second GAP IN TIME STAMP STOPS HERE here @14:08:03 marker…

Apr 04 14:08:03 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:00 garuda-iMac kernel: audit: type=1334 audit(1649099280.480:228): prog-id=0 op=UNLOAD
Apr 04 14:08:00 garuda-iMac audit: BPF prog-id=0 op=UNLOAD
Apr 04 14:08:00 garuda-iMac systemd[1]: user-1001.slice: Consumed 2min 27.053s CPU time.
Apr 04 14:08:00 garuda-iMac systemd[1]: Removed slice User Slice of UID 1001.

:arrow_down: More Relevant Logs section from journalctl on my machine… timegaps

Apr 04 14:09:30 garuda-iMac systemd[1]: Stopping Network Manager...
Apr 04 14:09:30 garuda-iMac systemd[1]: Stopped target Remote File Systems.
Apr 04 14:09:30 garuda-iMac systemd[1]: Stopped target Network.
Apr 04 14:09:30 garuda-iMac audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions c
omm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 14:09:30 garuda-iMac systemd[1]: Stopped Permit User Sessions.
Apr 04 14:09:30 garuda-iMac systemd[1]: systemd-user-sessions.service: Deactivated successfully.
Apr 04 14:09:30 garuda-iMac systemd[1]: Received SIGRTMIN+20 from PID 4887 (plymouthd).
Apr 04 14:09:30 garuda-iMac systemd[1]: Stopping Permit User Sessions...
Apr 04 14:09:30 garuda-iMac systemd[1]: Stopping User Login Management...
Apr 04 14:09:30 garuda-iMac systemd[1]: Starting Show Plymouth Reboot Screen...
Apr 04 14:09:30 garuda-iMac systemd[1]: Stopped Terminate Plymouth Boot Screen.
Apr 04 14:09:30 garuda-iMac systemd[1]: plymouth-quit.service: Deactivated successfully.
Apr 04 14:09:30 garuda-iMac systemd[1]: Stopped Deactivate Plymouth Boot Screen.
Apr 04 14:09:30 garuda-iMac audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-quit comm="sys
temd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 14:09:30 garuda-iMac kernel: audit: type=1131 audit(1649099370.063:231): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=
'unit=plymouth-quit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 14:09:30 garuda-iMac kernel: audit: type=1131 audit(1649099370.062:230): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=
'unit=plymouth-deactivate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 14:09:30 garuda-iMac kernel: audit: type=1131 audit(1649099370.062:229): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=
'unit=sddm-plymouth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 04 14:09:30 garuda-iMac systemd[1]: plymouth-deactivate.service: Deactivated successfully.
Apr 04 14:09:30 garuda-iMac audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-deactivate com
m="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 14:09:30 garuda-iMac systemd[1]: sddm-plymouth.service: Consumed 59.497s CPU time.
Apr 04 14:09:30 garuda-iMac systemd[1]: Stopped Simple Desktop Display Manager.
Apr 04 14:09:30 garuda-iMac audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sddm-plymouth comm="sys
temd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 04 14:09:30 garuda-iMac systemd[1]: sddm-plymouth.service: Failed with result 'timeout'.
Apr 04 14:09:30 garuda-iMac kernel: amdgpu:
                                     failed to send message 146 ret is 0
Apr 04 14:09:28 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:09:25 garuda-iMac kernel: amdgpu:
                                     failed to send message 145 ret is 0
Apr 04 14:09:23 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:09:20 garuda-iMac kernel: amdgpu:
                                     failed to send message 148 ret is 0
Apr 04 14:09:18 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:09:17 garuda-iMac kernel: amdgpu:
                                     failed to send message 146 ret is 0
Apr 04 14:09:15 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:09:12 garuda-iMac kernel: amdgpu:
                                     failed to send message 145 ret is 0
Apr 04 14:09:10 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:09:07 garuda-iMac kernel: amdgpu:
                                     failed to send message 148 ret is 0
Apr 04 14:09:06 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:09:04 garuda-iMac kernel: amdgpu:
                                     failed to send message 146 ret is 0
Apr 04 14:09:02 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:59 garuda-iMac kernel: amdgpu:
                                     failed to send message 145 ret is 0
Apr 04 14:08:58 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:54 garuda-iMac kernel: amdgpu:
                                     failed to send message 148 ret is 0
Apr 04 14:08:53 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:51 garuda-iMac kernel: amdgpu:
                                     failed to send message 5e ret is 0
Apr 04 14:08:50 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:48 garuda-iMac kernel: amdgpu:
                                     failed to send message 146 ret is 0
Apr 04 14:08:46 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:43 garuda-iMac kernel: amdgpu:
                                     failed to send message 145 ret is 0
Apr 04 14:08:42 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:38 garuda-iMac kernel: amdgpu:
                                     failed to send message 146 ret is 0
Apr 04 14:08:37 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:34 garuda-iMac kernel: amdgpu:
                                     failed to send message 145 ret is 0
Apr 04 14:08:32 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:29 garuda-iMac kernel: amdgpu:
                                     failed to send message 148 ret is 0
Apr 04 14:08:27 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:26 garuda-iMac kernel: amdgpu:
                                     failed to send message 146 ret is 0
Apr 04 14:08:24 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:21 garuda-iMac kernel: amdgpu:
                                     failed to send message 145 ret is 0
Apr 04 14:08:19 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:16 garuda-iMac kernel: amdgpu:
                                     failed to send message 148 ret is 0
Apr 04 14:08:14 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:13 garuda-iMac kernel: amdgpu:
                                     failed to send message 5e ret is 0
Apr 04 14:08:11 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:10 garuda-iMac kernel: amdgpu:
                                     failed to send message 146 ret is 0
Apr 04 14:08:08 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:05 garuda-iMac kernel: amdgpu:
                                     failed to send message 145 ret is 0
Apr 04 14:08:03 garuda-iMac kernel: amdgpu:
                                     last message was failed ret is 0
Apr 04 14:08:00 garuda-iMac kernel: audit: type=1334 audit(1649099280.480:228): prog-id=0 op=UNLOAD
Apr 04 14:08:00 garuda-iMac audit: BPF prog-id=0 op=UNLOAD
Apr 04 14:08:00 garuda-iMac systemd[1]: user-1001.slice: Consumed 2min 27.053s CPU time.
Apr 04 14:08:00 garuda-iMac systemd[1]: Removed slice User Slice of UID 1001.
Apr 04 14:08:00 garuda-iMac kernel: audit: type=1131 audit(1649099280.473:227): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 14:08:00 garuda-iMac audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 04 14:08:00 garuda-iMac systemd[1]: Stopped User Runtime Directory /run/user/1001.
Apr 04 14:08:00 garuda-iMac systemd[1]: user-runtime-dir@1001.service: Deactivated successfully.
Apr 04 14:08:00 garuda-iMac systemd[1]: Unmounted /run/user/1001.

amdgpu :point_up_2: reporting “failed to send message” errors

I noticed you have AMD Radeon as well.

I wish you luck. If you find the amdgpu driver is causing delays you can generally
just live with the delays. I ended up a few years back, on this same issue, doing
hours and days of research.

At this point I follow the LKML and watch development on the amdgpu driver.
Frankly, if they fix the driver amdgpu, a new kernel will come that will include
the driver fix and like magic, this delay issue will disappear. :sunglasses:

Note: This may not be the same issue as I can not see your full/relevant journalctl
output. Certainly worth the while to check. Could be multiple causes adding up
to larger total delays.

I think when all is said and done here, I am saying to you I lose minutes in various
degrees all from the amdgpu/Radeon combo-smack. It never does any harm
and will always… eventually… [ Reboot | Shutdown | Logout ] properly.

For instance… On average If I am currently logged in to kde it takes me 8-Full-Minutes
to shutdown-from-kde-menu / powerup / login-to-kde :point_down:

Shutdown from KDE menu or terminal : 3-4 minutes - Full Halt
Powerup: 3-4 minutes to DM / KDE Login screen

This happens for me on [ any linux distro - wayland or xorg - every de/wm ]
Why?
Because the common denominator is… tada! —>>> the kernel amdgpu
driver radeon-combo glitch.
That’s why.

I wish you all the luck and thought I would chip this in the pot.
You can add this to your troubleshooting arsenal.
Always be suspicious of the radeon+amdgpu combo when it
comes to delays in [ shutdown|reboot|logout|login|powerup ]. :grinning:

  • Pro Troubleshooting Tips

Rule out KDE…

Install another DE or window manager.

  • Note: Some folks avoid installing a different/second de/wm due to possible conflicts.

If you have the same issue on a different de/wm then you can’t blame KDE. check.

Ruling out can be very very useful in these cases.

Or… Use a bootable LIVE iso (not KDE) and test for the same issue there. check.

  • You can use any Garuda Linux Official Installation ISO for testing

Ruling OUT kde, and things like wayland or xorg, can save you valuable time trying
to nail things like this down, IMHO.

Good luck

5 Likes
16

I've had this issue too where it's just a black screen for a while. I also found that Alt F1 shuts it down. What does this command even do though? Forces a shutdown?

17

Alt-F1 brings up kde menu in well… kde. :sunglasses: Probably a keybinding specific to your DE/WM.