Random freezes

Hello Garuda users.

System:
  Kernel: 6.1.6-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=db82c088-ba88-4bcb-97d3-88ca94030fd3 rw [email protected]
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3 ibt=off
  Desktop: awesome v: 4.3 vt: 1 dm: SDDM Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Desktop System: Micro-Star product: MS-7C02 v: 1.0
    serial: <superuser required>
  Mobo: Micro-Star model: B450 TOMAHAWK (MS-7C02) v: 1.0
    serial: <superuser required> UEFI: American Megatrends v: 1.70
    date: 03/06/2019
Battery:
  Device-1: hidpp_battery_0 model: Logitech G305 Lightspeed Wireless Gaming
    Mouse serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ gen: 2
    level: v3 note: check built: 2018-21 process: GF 12nm family: 0x17 (23)
    model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 576 KiB desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 1649 high: 2800 min/max: 1550/3400 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1540 2: 1550
    3: 1550 4: 1550 5: 1502 6: 1550 7: 1550 8: 2800 9: 1550 10: 1550 11: 1549
    12: 1550 bogomips: 81589
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2060 Rev. A] vendor: Micro-Star MSI
    driver: nvidia v: 525.78.01 alternate: nouveau,nvidia_drm non-free: 525.xx+
    status: current (as of 2022-12) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s
    lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 1c:00.0
    chip-ID: 10de:1f08 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7
    compositor: Picom v: git-b700a driver: N/A display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 95 s-size: 513x291mm (20.20x11.46")
    s-diag: 590mm (23.22")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 96
    size: 510x287mm (20.08x11.3") diag: 585mm (23.04") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.78.01 renderer: NVIDIA GeForce RTX
    2060/PCIe/SSE2 direct render: Yes
Audio:
  Device-1: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 1c:00.1 chip-ID: 10de:10f9 class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 1e:00.3 chip-ID: 1022:1457 class-ID: 0403
  Sound API: ALSA v: k6.1.6-zen1-2-zen running: yes
  Sound Interface: sndio v: N/A running: no
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.64 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 18:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp24s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 2.05 TiB used: 365.16 GiB (17.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: A-Data model: SX8200PNP
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: R0906I temp: 34.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM001-1CH164
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: CC29 scheme: GPT
Partition:
  ID-1: / raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
    used: 49.78 GiB (20.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 608 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
    used: 49.78 GiB (20.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
    used: 49.78 GiB (20.9%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
    used: 49.78 GiB (20.9%) 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: 15.57 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 38.8 C mobo: N/A gpu: nvidia temp: 43 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 317 Uptime: 5h 52m wakeups: 23 Memory: 15.57 GiB
  used: 4.03 GiB (25.9%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: 1792
  pm: pacman pkgs: 1785 libs: 504 tools: octopi,paru pm: snap pkgs: 7
  Shell: Zsh v: 5.9 running-in: kitty inxi: 3.3.24
Garuda (2.6.14-1):
  System install date:     2023-01-05
  Last full system update: 2023-01-20
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
  Windows dual boot:       No/Undetected
  Failed units:            

I have been lately getting random display freezes for about 1-3 seconds where the display just freezes meaning If i am watching a video it just stops(Audio still works though) or when playing a game it completely freeze but the mouse and the keyboard are still responsive though. I have been investigating the issue and noticed a pattern in journalctl that every time this happens the program "/usr/bin/true" is trying to run with sudo privileges and a password is required the message is the following:
"Jan 23 20:27:18 pengu sudo[120707]: peng : a password is required ; TTY=pts/1 ; PWD=/home/peng ; USER=root ; COMMAND=/usr/bin/true"

I am aware that this program is meant to be run and never fail and can sometimes could be used for scripts but it looks like it's been scheduled by the OS and just takes over the whole CPU for a second or two maybe that's the issue? I don't really know.

How can I investigate the issue more?!

I am sure Garuda dos not have a DE with "awesome".

You change something?

3 Likes

Yeah I have the KDE Plasma edition of garuda, but I just use the awesome wm

It may be that no one can help you then, because we do not have the same basis.

Test with a live ISO, without your modification, if the problem persists.

By the way, welcome to the forum.

6 Likes