My garuda is often Freezing

Hello,
My garuda is often freezing and I have no idea why .
It often happen when I'm using google chrome or when I make update via yay or pacman at the time where is it "syncing filesystem"
I have no idea what is the problem, could you help me ?

Here is inxi -Faz result :

System:
  Kernel: 5.15.12-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=83004ee3-d6f4-4737-bbfa-faae9ee9d2ed rw rootflags=subvo[email protected]
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1 loglevel=3
  Desktop: Xfce 4.16.0 tk: Gtk 3.24.29 info: xfce4-panel wm: xfwm 4.16.1
    vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: TRX40 AORUS PRO WIFI v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: TRX40 AORUS PRO WIFI serial: <superuser required>
    UEFI: American Megatrends LLC. v: FCa date: 10/20/2021
CPU:
  Info: model: AMD Ryzen Threadripper 3990X bits: 64 type: MT MCP arch: Zen 2
    family: 0x17 (23) model-id: 0x31 (49) stepping: 0 microcode: 0x8301039
  Topology: cpus: 1x cores: 64 tpc: 2 threads: 128 smt: enabled cache:
    L1: 4 MiB desc: d-64x32 KiB; i-64x32 KiB L2: 32 MiB desc: 64x512 KiB
    L3: 256 MiB desc: 16x16 MiB
  Speed (MHz): avg: 3613 high: 4343 min/max: 2200/4375 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 3593 2: 3577
    3: 3590 4: 3591 5: 3588 6: 3817 7: 4341 8: 3777 9: 3586 10: 3592 11: 3591
    12: 3591 13: 3594 14: 3593 15: 3593 16: 3591 17: 3664 18: 3538 19: 3576
    20: 3591 21: 3593 22: 3594 23: 3593 24: 3587 25: 3596 26: 3588 27: 3584
    28: 3593 29: 3589 30: 3589 31: 3598 32: 3591 33: 3593 34: 3596 35: 3597
    36: 3594 37: 3595 38: 3586 39: 3591 40: 3594 41: 3592 42: 3592 43: 3592
    44: 3597 45: 3593 46: 3592 47: 3592 48: 3593 49: 3593 50: 3593 51: 3590
    52: 3587 53: 3589 54: 3594 55: 3589 56: 3594 57: 3588 58: 3514 59: 3539
    60: 3588 61: 3594 62: 3596 63: 3585 64: 3593 65: 3541 66: 3594 67: 3530
    68: 3546 69: 4342 70: 4324 71: 4343 72: 3494 73: 3588 74: 3594 75: 3589
    76: 3582 77: 3585 78: 3590 79: 3596 80: 3589 81: 3677 82: 3488 83: 3481
    84: 3587 85: 3591 86: 3591 87: 3587 88: 3592 89: 3587 90: 3592 91: 3585
    92: 3512 93: 3595 94: 3599 95: 3587 96: 3593 97: 3595 98: 3597 99: 3596
    100: 3591 101: 3598 102: 3592 103: 3592 104: 3591 105: 3592 106: 3591
    107: 3593 108: 3595 109: 3594 110: 3592 111: 3592 112: 3593 113: 3589
    114: 3592 115: 3592 116: 3593 117: 3583 118: 3593 119: 3590 120: 3591
    121: 3593 122: 3588 123: 3592 124: 3585 125: 3590 126: 3590 127: 3588
    128: 3588 bogomips: 741041
  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: Full AMD retpoline, IBPB: conditional,
    STIBP: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660] vendor: ZOTAC driver: nvidia
    v: 495.46 alternate: nouveau,nvidia_drm bus-ID: 21:00.0 chip-ID: 10de:2184
    class-ID: 0300
  Display: x11 server: X.Org 1.21.1.2 compositor: xfwm4 v: 4.16.1 driver:
    loaded: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 5760x1080 s-dpi: 96 s-size: 1524x286mm (60.0x11.3")
    s-diag: 1551mm (61")
  Monitor-1: DP-0 res: 1920x1080 hz: 60 dpi: 94
    size: 521x293mm (20.5x11.5") diag: 598mm (23.5")
  Monitor-2: HDMI-0 res: 1920x1080 hz: 60 dpi: 70
    size: 698x392mm (27.5x15.4") diag: 801mm (31.5")
  Monitor-3: DP-5 res: 1920x1080 hz: 60 dpi: 82
    size: 598x336mm (23.5x13.2") diag: 686mm (27")
  Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
  Device-1: NVIDIA TU116 High Definition Audio vendor: ZOTAC
    driver: snd_hda_intel v: kernel bus-ID: 21:00.1 chip-ID: 10de:1aeb
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel v: kernel
    bus-ID: 23:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Focusrite-Novation Scarlett Solo (3rd Gen.) type: USB
    driver: snd-usb-audio bus-ID: 1-2:2 chip-ID: 1235:8211 class-ID: 0102
    serial: <filter>
  Device-4: Nektar Impact LX61+ type: USB driver: snd-usb-audio
    bus-ID: 7-4.1:5 chip-ID: 2467:2017 class-ID: 0103
  Device-5: Giga-Byte USB Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 7-5:4 chip-ID: 0414:a002
    class-ID: 0300
  Sound Server-1: ALSA v: k5.15.12-zen1-1-zen running: yes
  Sound Server-2: JACK v: 1.9.19 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.42 running: no
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
    port: 9000 bus-ID: 43:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: enp67s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 44:00.0
    chip-ID: 8086:2723 class-ID: 0280
  IF: wlo2 state: up mac: <filter>
  IF-ID-1: br-6f9b3b7fb6bc state: down mac: <filter>
  IF-ID-2: br-7c1fb8f13621 state: down mac: <filter>
  IF-ID-3: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 9-5:2 chip-ID: 8087:0029 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: no
    address: <filter>
Drives:
  Local Storage: total: 2.73 TiB used: 501.88 GiB (18.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung model: SSD 980 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 3B2QGXA7 temp: 32.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 3B2QGXA7
    temp: 33.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 501.85 GiB (26.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
    used: 27.5 MiB (10.8%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:5
  ID-3: /home raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 501.85 GiB (26.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
  ID-4: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 501.85 GiB (26.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
  ID-5: /var/tmp raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 501.85 GiB (26.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 125.71 GiB used: 21.8 MiB (0.0%)
    priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 16.8 C mobo: N/A gpu: nvidia temp: 37 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 38%
Info:
  Processes: 1595 Uptime: 1d 8h 46m wakeups: 0 Memory: 125.71 GiB
  used: 21.53 GiB (17.1%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.1.0 Packages: 1816 pacman: 1806 lib: 353 snap: 10 Shell: Zsh v: 5.8
  running-in: terminator inxi: 3.3.11

Try other Garuda DE,
try other Kernel,
start htop and check CPU, RAM values.

Welcome to the Forum :slight_smile:

2 Likes

Welcome to Garuda.

Is your Bios up to date?

Does the same thing happen on different Garuda live disks?

Is this a complete freeze up with no keyboard or mouse responsiveness?

Is this a fresh install or did this just start, perhaps after an update?

Test alternate kernels such as, linux , linux-mainline , linux-lts , and linux-next-git .

There are numerous threads on the forum dealing with freezing issues with many different suggestions posted on how to hopefully correct the issue. Please search the forum and report in painstaking detail every fix you attempt and post relevant logs and any command outputs. Threads already covering this topic on the forum should provide plenty of information on the steps you need to take to troubleshoot this issue.

Please answer all questions fully as we need far more information to help. Also, please provide feedback on all suggestions put to you.

Good luck.

2 Likes

Is your Bios up to date

Yes it should be I updated it not a long time ago

Does the same thing happen on different Garuda live disks?

Sorry but I dont get what do you mean ?

Is this a complete freeze up with no keyboard or mouse responsiveness?

no it is only the applications that doesn't respond, I can switch windows etc but the application are frozen, when I click on it nothing happen for a few seconds/minutes

Is this a fresh install or did this just start, perhaps after an update?

It does it for approximately 1 month, i thought it was kde before but i switched to XFCE and it happens too

Test alternate kernels such as, linux , linux-mainline , linux-lts , and linux-next-git .

Thank you I'll try that thanks

Htop is a terminal application that will tell you how your system resources are being used. You will need to check on how much ram especially is being used when you experience a freeze. You need to identify what exactly is causing this issue.

A live boot disk is what you used to install your version of Garuda (usually it is written to a flashdrive). It would help to know if your system performs properly in the live environment. This will tell us if perhaps your system has been altered to cause these issues.

Something that sometimes helps correct stutters and freezes is deleting all your snapshots and then performing a btrfs balance.

You will need to check your logs to see what types of errors are present. Your logs should be quite helpful as you aren't experiencing a full system freeze up. In a full lock up logs often aren't very helpful as nothing usually gets recorded during a full lock up.

You can brush up on your search skills to find which commands are best for identifying errors in your Linux journal logs. Please post any log errors that may help with your case.

2 Likes

Hey @tbg
The freeze happens when one of those two programs is running : sync, btrfs-transacti or btrfs-cleaner

You may want to try disabling btrfs quotas.

See:

https://forum.garudalinux.org/[email protected]%20freeze%20disable%20btrfs%20quotas

3 Likes

I think disabling btrfs quotas is working ! Thank you !

1 Like

If this an installation with Snapper and BTRFS quotas are not disabled by default, we should definitely look into making it default :eyes: Although i remember someone telling me it was disabled by default, so it might be coincidence? Either way, we should make sure it's actually disabled.

1 Like

@dr460nf1r3 if I recall correctly when I researched the subject last, it was enabled by default when we were using timeshift as the default. This was because timeshift required BTRFS quotas to be enabled to calculate the space remaining on drives correctly.

Perhaps now that we've switched to using snapper this wouldn't be such a problem. I keep quotas disabled on my system, but I'm careful to keep an eye on my space usage myself.

1 Like

Might be something to look into. I know Snapper - ArchWiki mentions qgroup has been reported to cause slowdowns and recommends to disable them if they do.

I am thinking on disabling it myself since my Garuda install initially had Timeshift, so I have qgroup enabled still with Snapper.

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