Manjaro becomes unresponsive, sound loops, cant do anything

It happens maybe once or twice a day when i am loading into games or downloading stuff. I installed manjaro with gnome and had this issue, after reinstalling it with kde it sadly did not disappear.
inxi -Fazy:

  Kernel: 5.13.19-2-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.13-x86_64 
  root=UUID=b251fe3f-d88d-4680-99aa-6d60d0b5248c rw quiet 
  root=/dev/mapper/luks-55638b23-9718-4100-9f89-8519893000fa apparmor=1 
  security=apparmor udev.log_priority=3 
  Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 
  dm: SDDM Distro: Manjaro Linux base: Arch Linux 
  Type: Desktop Mobo: ASRock model: A320M-DGS serial: <filter> 
  UEFI-[Legacy]: American Megatrends v: P5.10 date: 10/04/2018 
  Info: Quad Core model: AMD Ryzen 3 2200G with Radeon Vega Graphics bits: 64 
  type: MCP arch: Zen family: 17 (23) model-id: 11 (17) stepping: 0 
  microcode: 810100B cache: L2: 2 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 27959 
  Speed: 2662 MHz min/max: 1600/3500 MHz boost: enabled Core speeds (MHz): 
  1: 2662 2: 1583 3: 1978 4: 1409 
  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, STIBP: 
  disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Micro-Star MSI 
  driver: nvidia v: 470.63.01 alternate: nouveau,nvidia_drm bus-ID: 10:00.0 
  chip-ID: 10de:1c03 class-ID: 0300 
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
  loaded: nvidia display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 3600x1225 s-dpi: 98 s-size: 933x317mm (36.7x12.5") 
  s-diag: 985mm (38.8") 
  Monitor-1: DVI-D-0 res: 1680x1050 hz: 60 dpi: 99 
  size: 433x271mm (17.0x10.7") diag: 511mm (20.1") 
  Monitor-2: HDMI-0 res: 1920x1080 hz: 75 dpi: 102 
  size: 480x270mm (18.9x10.6") diag: 551mm (21.7") 
  OpenGL: renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 
  v: 4.6.0 NVIDIA 470.63.01 direct render: Yes 
  Device-1: NVIDIA GP106 High Definition Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus-ID: 10:00.1 chip-ID: 10de:10f1 
  class-ID: 0403 
  Device-2: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel 
  v: kernel bus-ID: 38:00.6 chip-ID: 1022:15e3 class-ID: 0403 
  Device-3: C-Media USB Audio Device type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-6:3 chip-ID: 0d8c:0012 
  class-ID: 0300 
  Sound Server-1: ALSA v: k5.13.19-2-MANJARO 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.37 running: yes 
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASRock driver: r8169 v: kernel port: e000 bus-ID: 25:00.0 
  chip-ID: 10ec:8168 class-ID: 0200 
  IF: enp37s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  Local Storage: total: 912.89 GiB used: 112.53 GiB (12.3%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  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: 6.0 Gb/s 
  type: HDD rpm: 7200 serial: <filter> rev: KC44 scheme: GPT 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Kingston model: HyperX Fury 3D 480GB 
  size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  type: SSD serial: <filter> rev: 5A scheme: MBR 
  ID-1: / raw-size: 447.13 GiB size: 439.02 GiB (98.19%) 
  used: 112.53 GiB (25.6%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0 
  mapped: luks-55638b23-9718-4100-9f89-8519893000fa 
  Alert: No swap data was found. 
  System Temperatures: cpu: 36.0 C mobo: N/A gpu: nvidia temp: 40 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 49% 
  Processes: 218 Uptime: 9m wakeups: 0 Memory: 7.7 GiB used: 2.28 GiB (29.6%) 
  Init: systemd v: 249 tool: systemctl Compilers: gcc: 11.1.0 Packages: 
  pacman: 1443 lib: 465 flatpak: 0 Shell: Zsh v: 5.8 default: Bash v: 5.1.8 
  running-in: konsole inxi: 3.3.06 

Apparently your system cannot handle the heavy load you are putting on it and is crashing. The looping sound before the kernel dies is quite typical. However, it does indicate a hardware problem, possibly triggered by the higher thermal load associated with whatever you’re doing. So try monitoring your various temperature sensors and see whether they are reaching critical levels just before the crash.

Another thing I notice from your inxi output is that you’ve got an Nvidia GPU and that you’re using the proprietary driver. That makes it very hard to debug these things, because that driver is closed-source, and there are loads and loads of problems with Nvidia in GNU/Linux nowadays.

You could of course always try the GPL’d nouveau driver instead, but unfortunately, if you’re a gamer then that’s out of the question. The nouveau driver is good enough for some casual day-to-day use, but it sucks badly at doing fancy things like 3D acceleration. :man_shrugging:

On windows i did not have such issue, but after trying linux i absolutely don’t want to come back.
Guess i’ll just wait for a miracle for now.

If it’s due to thermal overloading, then maybe you can check whether the fans are still working properly ─ no dust or cat hair in the fans, etc. ─ and possibly, if the system allows for it, install an extra case fan.

Another possibility could be that your power supply is dying. Check if it’s still supplying enough current on each of its channels ─ have a professional test that for you, so that you don’t get electrocuted. And if you’re uncertain about the wall power, buy a cheap UPS; it will catch brownouts and will make sure your computer is always receiving the correct voltage.

Ok thanks, i’ll try.

Mea culpa ─ I forgot to actually mention the obvious, which is to try a different kernel. The 5.4 and 5.10 kernels are both LTS (“long-term support”) and are pretty stable.

You may need to rebuild the Nvidia driver for that, but if you have dkms installed, then it should do that for you automatically at boot time ─ it’ll add a few seconds to your boot time, but only once.

there many points that can explain

  1. UEFI-[Legacy]: American Megatrends v: P5.10 date: 10/04/2018
    you have installed in fact in Legacy ( so only disks MBR ) , also version UEFI may be not up to date
  2. you have mixed disks GPT & MBR
  3. you have version Kernel 5.13.x EOL , you shold have installed 5.10 LTS & 5.14

Changing kernel didn’t work for me (but i will stick to 5.10 LTS anyway), cleaned my pc just in case, but after making swap file problem seems to have gone.

1 Like

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