Shutdown and reboot take about 90 seconds

Hi all

Just started with this distro and I'm liking it. My main issue is that reboot and shutdown take about 90 seconds when done via the gui and the 'shutdown now' command. 'Poweroff -f' and 'reboot -f' commands are near instantaneous.

Any ideas?

System:    Kernel: 5.10.16-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 10.2.1 
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=bdfc4503-f56a-4697-92ba-5f399022df77 rw 
[email protected] splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 
loglevel=3 systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on enforcing=0 
Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 dm: SDDM Distro: Garuda Linux 
Machine:   Type: Desktop Mobo: Micro-Star model: B550M PRO-VDH WIFI (MS-7C95) v: 1.0 serial: <filter> 
UEFI: American Megatrends v: 2.51 date: 11/13/2020 
CPU:       Info: 8-Core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3 family: 19 (25) model-id: 21 (33) 
stepping: N/A microcode: A201009 L2 cache: 4 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 121612 
Speed: 3594 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 3594 2: 3590 3: 3595 4: 3593 5: 3596 
6: 3588 7: 3601 8: 3596 9: 3636 10: 3577 11: 3600 12: 3585 13: 3622 14: 3602 15: 3587 16: 3606 
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 and seccomp 
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP: always-on, RSB filling 
Type: srbds status: Not affected 
Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Tonga PRO [Radeon R9 285/380] vendor: PC Partner Limited driver: amdgpu 
v: kernel bus ID: 2b:00.0 chip ID: 1002:6939 class ID: 0300 
Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: amdgpu,ati unloaded: modesetting 
alternate: fbdev,vesa display ID: :0 screens: 1 
Screen-1: 0 s-res: 3440x1440 s-dpi: 96 s-size: 910x381mm (35.8x15.0") s-diag: 987mm (38.8") 
Monitor-1: DisplayPort-0 res: 3440x1440 dpi: 110 size: 797x334mm (31.4x13.1") diag: 864mm (34") 
OpenGL: renderer: AMD Radeon R9 380 Series (TONGA DRM 3.40.0 5.10.16-zen1-1-zen LLVM 11.0.1) v: 4.6 Mesa 20.3.4 
direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Tonga HDMI Audio [Radeon R9 285/380] vendor: PC Partner Limited 
driver: snd_hda_intel v: kernel bus ID: 2b:00.1 chip ID: 1002:aad8 class ID: 0403 
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel 
v: kernel bus ID: 2d:00.4 chip ID: 1022:1487 class ID: 0403 
Device-3: Focusrite-Novation Scarlett 2i4 type: USB driver: snd-usb-audio bus ID: 1-4.1:4 chip ID: 1235:800a 
class ID: fe01 
Device-4: JMTek LLC. KLIM Impact type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-4.2:6 
chip ID: 0c76:1466 class ID: 0300 
Device-5: Sunplus Innovation SPCA2281 Web Camera type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-4.4:9 
chip ID: 1bcf:2281 class ID: 0102 serial: <filter> 
Sound Server: ALSA v: k5.10.16-zen1-1-zen 
Network:   Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel bus ID: 29:00.0 
chip ID: 8086:24fb class ID: 0280 
IF: wlo1 state: up mac: <filter> 
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel 
port: f000 bus ID: 2a:00.0 chip ID: 10ec:8168 class ID: 0200 
IF: enp42s0 state: down mac: <filter> 
Bluetooth: Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8 bus ID: 1-9:7 chip ID: 8087:0aa7 
class ID: e001 
Message: Required tool hciconfig not installed. Check --recommends 
Drives:    Local Storage: total: 1.39 TiB used: 33.03 GiB (2.3%) 
SMART Message: Unable to run smartctl. Root privileges required. 
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: A-Data model: SX8200PNP size: 953.87 GiB block size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: 32B3T8EA temp: 36.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: 00WD scheme: GPT
Partition: ID-1: / raw size: 149.41 GiB size: 149.41 GiB (100.00%) used: 21.79 GiB (14.6%) fs: btrfs dev: /dev/nvme0n1p4
maj-min: 259:4
ID-2: /boot/efi raw size: 1000 MiB size: 996 MiB (99.60%) used: 25.8 MiB (2.6%) fs: vfat dev: /dev/nvme0n1p1
maj-min: 259:1
ID-3: /home raw size: 465.76 GiB size: 465.76 GiB (100.00%) used: 11.22 GiB (2.4%) fs: btrfs dev: /dev/sda1
maj-min: 8:1
ID-4: /var/log raw size: 149.41 GiB size: 149.41 GiB (100.00%) used: 21.79 GiB (14.6%) fs: btrfs
dev: /dev/nvme0n1p4 maj-min: 259:4
ID-5: /var/tmp raw size: 149.41 GiB size: 149.41 GiB (100.00%) used: 21.79 GiB (14.6%) fs: btrfs
dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:      Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100)
ID-1: swap-1 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
ID-2: swap-2 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1
ID-3: swap-3 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2
ID-4: swap-4 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3
ID-5: swap-5 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4
ID-6: swap-6 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5
ID-7: swap-7 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6
ID-8: swap-8 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7
ID-9: swap-9 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram8
ID-10: swap-10 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram9
ID-11: swap-11 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram10
ID-12: swap-12 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram11
ID-13: swap-13 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram12
ID-14: swap-14 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram13
ID-15: swap-15 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram14
ID-16: swap-16 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram15
Sensors:   System Temperatures: cpu: 49.4 C mobo: N/A gpu: amdgpu temp: 52.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 620
Info:      Processes: 385 Uptime: 6m wakeups: 0 Memory: 31.34 GiB used: 4.1 GiB (13.1%) Init: systemd v: 247 Compilers:
gcc: 10.2.0 clang: 11.0.1 Packages: 1619 pacman: 1615 lib: 468 flatpak: 4 Shell: fish v: 3.1.2 running in: yakuake
inxi: 3.3.01

Thanks!

Read

How to search for solutions the right way

please
and post

systemd-analyze blame
systemd-analyze

and
:slight_smile:

2 Likes
6.446s NetworkManager-wait-online.service                                                       
2.446s systemd-swap.service                                                                     
1.710s upower.service                                                                           
228ms lvm2-monitor.service                                                                     
191ms systemd-tmpfiles-setup.service                                                           
150ms systemd-random-seed.service                                                              
146ms udisks2.service                                                                          
122ms dev-nvme0n1p4.device                                                                     
119ms [email protected]                                                                        
115ms [email protected]                                                         
83ms ananicy.service                                                                          
49ms systemd-journal-flush.service                                                            
44ms systemd-logind.service                                                                   
41ms systemd-udevd.service                                                                    
37ms systemd-journald.service                                                                 
35ms systemd-udev-trigger.service                                                             
33ms [email protected]\x2duuid-0CDE\x2d8B9A.service                                    
32ms polkit.service                                                                           
30ms systemd-modules-load.service                                                             
29ms smb.service                                                                              
29ms ModemManager.service                                                                     
28ms NetworkManager.service                                                                   
25ms systemd-timesyncd.service                                                                
21ms avahi-daemon.service                                                                     
21ms plymouth-deactivate.service                                                              
20ms plymouth-quit-wait.service                                                               
20ms plymouth-quit.service                                                                    
20ms dev-zram3.swap                                                                           
20ms dev-zram15.swap                                                                          
18ms dev-zram9.swap                                                                           
17ms systemd-guest-user.service                                                               
17ms dev-zram7.swap                                                                           
17ms dev-zram5.swap                                                                           
17ms dev-zram13.swap                                                                          
16ms dev-zram4.swap                                                                           
16ms systemd-vconsole-setup.service                                                           
15ms nmb.service                                                                              
15ms dev-zram8.swap                                                                           
15ms dev-zram2.swap                                                                           
14ms thermald.service                                                                         
14ms plymouth-start.service                                                                   
14ms dev-zram0.swap                                                                           
13ms dev-zram1.swap                                                                           
12ms dev-zram11.swap                                                                          
12ms dev-zram10.swap                                                                          
12ms [email protected]\x2duuid-349b82ed\x2d0084\x2d42ae\x2d8b70\x2d8b1b54fc68be.service
11ms dev-zram14.swap                                                                          
11ms dev-zram12.swap                                                                          
11ms plymouth-read-write.service                                                              
10ms systemd-sysctl.service                                                                   
10ms home.mount                                                                               
9ms systemd-guest-config.service                                                             
9ms dev-zram6.swap                                                                           
8ms systemd-remount-fs.service                                                               
8ms cups.service                                                                             
8ms boot-efi.mount                                                                           
7ms systemd-tmpfiles-clean.service                                                           
6ms keychron.service                                                                         
6ms [email protected]
6ms modprob[email protected]
5ms [email protected]
5ms colord.service
5ms [email protected]
5ms bluetooth.service
5ms [email protected]
5ms dev-hugepages.mount
5ms [email protected]
5ms [email protected]
5ms dev-mqueue.mount
5ms [email protected]
5ms systemd-tmpfiles-setup-dev.service
5ms [email protected]
5ms [email protected]
4ms sys-kernel-debug.mount
4ms systemd-binfmt.service
4ms sys-kernel-tracing.mount
4ms tmp.mount
4ms kmod-static-nodes.service
3ms [email protected]
3ms [email protected]
3ms [email protected]
3ms [email protected]\x2duuid-bdfc4503\x2df56a\x2d4697\x2d92ba\x2d5f399022df77.service
3ms systemd-user-sessions.service
2ms systemd-update-utmp.service
2ms root.mount
2ms rtkit-daemon.service
2ms srv.mount
2ms var-cache.mount
2ms wpa_supplicant.service
2ms var-log.mount
1ms systemd-rfkill.service
1ms var-tmp.mount
1ms home-guest.mount
1ms proc-sys-fs-binfmt_misc.mount
990us sys-kernel-config.mount
632us sys-fs-fuse-connections.mount

Startup finished in 20.661s (firmware) + 6.336s (loader) + 2.302s (kernel) + 7.198s (userspace) = 36.499s
graphical.target reached after 7.198s in userspace

Check your /etc/fstab for wrong UUID or missing harware:

sudo blkid | grep sd
1 Like
/dev/nvme0n1p1: UUID="0CDE-8B9A" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="ff10d880-affd-43d0-b996-7dd396d2191e"
/dev/nvme0n1p3: BLOCK_SIZE="512" UUID="E058DC4F58DC2656" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="1e5dc3de-b083-4e7f-912e-4e49f6997e9c"
/dev/nvme0n1p4: UUID="bdfc4503-f56a-4697-92ba-5f399022df77" UUID_SUB="da670ce5-b093-4b73-a272-951cb9b29d5e" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="a23ee579-7ed1-4442-a8a9-e05df7d29895"
/dev/sda1: UUID="349b82ed-0084-42ae-8b70-8b1b54fc68be" UUID_SUB="a429af80-ad3c-414f-90f7-5640c7e41d50" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="3d6beaf9-7658-b842-99b5-75cdaf04f6c4"
/dev/zram0: UUID="09fca2fa-9ae4-4a37-96ef-3067b1654b32" TYPE="swap"
/dev/zram1: UUID="7099c716-6d41-4ebf-bb3d-ae3947979d25" TYPE="swap"
/dev/zram2: UUID="bc22a708-14c2-43e0-ae13-a6a998040ed5" TYPE="swap"
/dev/zram3: UUID="338bf3f9-0c1c-48b4-b8c5-d56f6ebed832" TYPE="swap"
/dev/zram4: UUID="17e23327-8eaf-4566-87ba-9677066dba63" TYPE="swap"
/dev/zram5: UUID="a3c8fc9c-0dc0-4e2d-aaea-666055265efc" TYPE="swap"
/dev/zram6: UUID="c4f228ee-951a-4e21-8bdd-490f64608b1e" TYPE="swap"
/dev/zram7: UUID="3ed03f67-bd36-4997-96f1-0e992e664e29" TYPE="swap"
/dev/zram8: UUID="31ef1dd6-6c23-46b7-9983-0d48e1cd4a34" TYPE="swap"
/dev/zram9: UUID="cb69d0af-4a52-4475-a139-7c17ef0a20f5" TYPE="swap"
/dev/zram10: UUID="7ec8a0e3-6cd7-4d14-aef9-ce722a8f3400" TYPE="swap"
/dev/zram11: UUID="04be0b67-18c1-43fe-84e7-e7053364ee7c" TYPE="swap"
/dev/zram12: UUID="86ae1532-7362-4966-9c48-b6a914759926" TYPE="swap"
/dev/zram13: UUID="502f415f-2cf5-4250-96f2-b4eed6207aeb" TYPE="swap"
/dev/zram14: UUID="518beb94-6173-4867-b36d-cd5ceb690f2c" TYPE="swap"
/dev/zram15: UUID="4a94c126-aef5-48b4-8129-d68e77df3d2d" TYPE="swap"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="d6661e71-96fe-4f9d-a950-cf56d7572139"

Garuda root is on nvme0n1p4 and home on sda1.

I'm not sure what I'm supposed to be checking here, how do I tell if a UUID is wrong?

Dual boot with win?
The value "graphical.target reached after 7.198s in userspace" seem ok.
You are sure with 90 sec.?

If fstab is wrong your PC search long time for hardware on boot.
Shutdown could be save btrfs things and also if you save and boot with "Desktop Session".

and it is KDE :smiley: , IIRC I have same, some times :slight_smile:

1 Like

Yeah win10 and garuda root on nvme, garuda home on sda.

It's the shutdown that's taking 90 seconds. Booting is fine every time.

I'm getting a new Desktop session every boot, so it must be btrfs.

Check journal log of your last boot reversed

journalctl -b -1 -r

Don't post the whole log. Review what happens from the moment you send the shutdown signal.
Mostly find this and time after that

systemd-logind[400]: System is powering down
2 Likes

90 seconds is a common timeout value. This probably indicates a process or service is not exiting when told to and is instead being killed by systemd after waiting 90 seconds.

You'll have to pay attention to any log messages shown on screen during shutdown, and you can see the full journal for the previous boot using

journalctl -b -1

(please don't just paste the output of that here - look at it to see which process is hanging)

3 Likes

Hello! Sorry, been quite busy!

My previous boot had a lot of these in the logs:

Feb 26 15:08:43 reticent-monolith kernel: amdgpu: 
                                           last message was failed ret is 0
Feb 26 15:08:37 reticent-monolith kernel: amdgpu: 
                                           failed to send message 148 ret is 0 
Feb 26 15:08:34 reticent-monolith kernel: amdgpu: 
                                           last message was failed ret is 0
Feb 26 15:08:31 reticent-monolith kernel: amdgpu: 
                                           failed to send message 5e ret is 0 
Feb 26 15:08:28 reticent-monolith kernel: amdgpu: 
                                           last message was failed ret is 0
Feb 26 15:08:25 reticent-monolith kernel: amdgpu: 
                                           failed to send message 146 ret is 0 
Feb 26 15:08:22 reticent-monolith kernel: amdgpu: 
                                           last message was failed ret is 0

Use PrivateBin upper right to post the longer log.

"If you include terminal outputs in your post please use the proper output format in your post. Using "~" 3 times above and "~" 3 times below the text block will provide a readable, raw look."

1 Like

That may or may not be related., therefore you should look first for a service or process that is triggering the 90 second timeout towards the very end of the log.

3 Likes