Shutdown glitch

Hi​:wave:
I am using Garuda Mate and i am getting an issue.
My pc take around 30 seconds for shutting down after pressing the shutdown button.. looks like freezing.

Please provide your:

garuda-inxi

As required by the topic template.
Maybe include also an abstract of the journal at the time of the last shutdown.
Format the text like this
~~~
text
~~~

4 Likes

I have my a little old garuda inxi command output.
Here it is,

garuda-inxi
System:
  Kernel: 6.2.13-zen-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=a07da2a9-0e78-41ad-9fea-d9403d0b7047 rw rootflags=subvol=@
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=ec83f55d-694c-4175-a51c-0254db737104 loglevel=3 ibt=off
  Desktop: MATE v: 1.26.1 info: mate-panel wm: marco v: 1.26.1 vt: 7
    dm: LightDM v: 1.32.0 Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: INTEL model: H61 serial: <superuser required>
    UEFI: American Megatrends v: 4.6.5 date: 05/29/2019
CPU:
  Info: model: Intel Core i3-3220 bits: 64 type: MT MCP arch: Ivy Bridge
    gen: core 3 level: v2 built: 2012-15 process: Intel 22nm family: 6
    model-id: 0x3A (58) stepping: 9 microcode: 0x21
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1598 high: 1600 min/max: 1600/3300 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 1600 2: 1600 3: 1597
    4: 1597 bogomips: 26338
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics driver: i915
    v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports:
    active: VGA-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:0152 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 compositor: marco v: 1.26.1 driver:
    X: loaded: modesetting alternate: fbdev,intel,vesa dri: crocus gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
    s-diag: 414mm (16.31")
  Monitor-1: VGA-1 model: EW32S3PW serial: <filter> built: 2012
    res: 1366x768 hz: 60 dpi: 30 gamma: 1.2 size: 1150x650mm (45.28x25.59")
    diag: 1321mm (52") ratio: 16:9 modes: max: 1366x768 min: 720x400
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo
    missing.
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20
    class-ID: 0403
  API: ALSA v: k6.2.13-zen-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 0.3.70 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: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0
    chip-ID: 10ec:8136 class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u
    bus-ID: 2-1.5:5 chip-ID: 148f:7601 class-ID: 0000 serial: <filter>
  IF: wlp0s29u1u5 state: up mac: <filter>
Drives:
  Local Storage: total: 599.6 GiB used: 16.07 GiB (2.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST500DM002-1BD142
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: KC48 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 model: SATA SSD 128GB size: 119.24 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD
    serial: <filter> rev: 537 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: Cruzer Blade
    size: 14.59 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: 1.00 scheme: MBR
Partition:
  ID-1: / raw-size: 40 GiB size: 40 GiB (100.00%) used: 3.97 GiB (9.9%)
    fs: btrfs dev: /dev/sdb3 maj-min: 8:19
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 576 KiB (0.1%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
  ID-3: /home raw-size: 304.1 GiB size: 304.1 GiB (100.00%)
    used: 50.3 MiB (0.0%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
  ID-4: /var/log raw-size: 40 GiB size: 40 GiB (100.00%)
    used: 3.97 GiB (9.9%) fs: btrfs dev: /dev/sdb3 maj-min: 8:19
  ID-5: /var/tmp raw-size: 40 GiB size: 40 GiB (100.00%)
    used: 3.97 GiB (9.9%) fs: btrfs dev: /dev/sdb3 maj-min: 8:19
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 6.72 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 7.81 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sdb2 maj-min: 8:18
Sensors:
  System Temperatures: cpu: 39.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 226 Uptime: 18m wakeups: 0 Memory: 6.73 GiB
  used: 2.01 GiB (29.9%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 Packages: pm: pacman pkgs: 1174
  libs: 347 tools: octopi,paru Shell: Bash v: 5.1.16 running-in: mate-terminal
  inxi: 3.3.26
Garuda (2.6.16-1):
  System install date:     2023-07-17
  Last full system update: 2023-07-17
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:

This is not necessarily the root cause of your issue, but you should really update, otherwise it will get more challenging in the future.

garuda-update 
5 Likes

I had updated this.. but still its taking time..

No message?
Are there still programs open that the system closes?
Are external drives/sticks connected?

5 Likes

It’s a bug of mine, but please check if there is an update for your 2019 BIOS.

It’s just to check it off the list. Also, have you tried any other kernels yet?

And, finally, please post the output of the following command (use sudo):

# systemd-analyze blame

‘#’ indicates a root superuser command

6 Likes

How to update bios?

Start with answer the questions, please.
Post output from.

journalctl -b -1 -r
5 Likes

Now its working properly after running these commands again.
sudo pacman -Sy
sudo pacman -Syu

The second includes the first one, and both are covered by the garuda-update alrady executed earlier.
So, the solution remains a mystery, but all good...!

7 Likes

Lol. Idk how i fixed this maybe some glitch or something

forum helpers gotta go check their necks for puncture wounds now >.>

2 Likes

No need, my white shirt has blood red stains on the neck. :grin:

I mark the solution.

5 Likes

Well, at least when (not if) they screw the pooch again, at least now they have a few troubleshooting tips in their box o' tools.
:wink:

2 Likes