[+-SOLVED] Random freezes problem on KDE Manjaro

Xorg.0.log (40.5 KB)
Hello,
I am using KDE Manjaro on my PC with a Geforce GTX 1660 with the last Nvidia Driver.
For a while (4-5 hours) everything’s goes fine until the system slowly starting freezing more and more until it stop the music on the back stopped playing and cursour’s moving.
(I JUST OPENED 5 CHROME TABS ON D: C’MON!)
After 3 minutes everything’s back to normal, so I decided to find the reason of these freezes and stop what causes them. Checked drivers, surfed the forums etc.
After all of this I found Xorg.0.log which where (I suppose, not really sure) I found log with the system’s emount of operations. To me numbers was well at the top: 12.725-14.717 but right after it increases to 1500.00 and to 12000.00 an to the very 33K. You may see all of this in the file I attached.

[    14.630] (**) Option "Device" "/dev/input/event16"
[    14.630] (II) libinput: COMPANY USB Device Keyboard: is a virtual subdevice
[    14.630] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:07.1/0000:07:00.3/usb5/5-4/5-4:1.2/0003:09DA:F624.0006/input/input16/event16"
[    14.630] (II) XINPUT: Adding extended input device "COMPANY USB Device Keyboard" (type: KEYBOARD, id 16)
[    14.630] (**) Option "xkb_layout" "us,ru"
[    14.630] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[    14.674] (--) NVIDIA(GPU-0): Samsung C27JG5x (DFP-4): connected
[    14.674] (--) NVIDIA(GPU-0): Samsung C27JG5x (DFP-4): Internal TMDS
[    14.674] (--) NVIDIA(GPU-0): Samsung C27JG5x (DFP-4): 600.0 MHz maximum pixel clock
[    14.674] (--) NVIDIA(GPU-0): 
[    14.717] (--) NVIDIA(GPU-0): Samsung C27JG5x (DFP-4): connected
[    14.717] (--) NVIDIA(GPU-0): Samsung C27JG5x (DFP-4): Internal TMDS
[    14.717] (--) NVIDIA(GPU-0): Samsung C27JG5x (DFP-4): 600.0 MHz maximum pixel clock
[    14.717] (--) NVIDIA(GPU-0): 
[  1537.043] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  1537.043] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[  1537.043] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[  1537.043] (--) NVIDIA(GPU-0): 
.
.
.
[ 32655.080] (--) NVIDIA(GPU-0): DFP-5: disconnected
[ 32655.080] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[ 32655.080] (--) NVIDIA(GPU-0): DFP-5: 2660.0 MHz maximum pixel clock
[ 32655.080] (--) NVIDIA(GPU-0): 
[ 32655.080] (--) NVIDIA(GPU-0): DFP-6: disconnected
[ 32655.080] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[ 32655.080] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[ 32655.080] (--) NVIDIA(GPU-0): 
[ 33675.701] (EE) event7  - COMPANY USB Device: client bug: event processing lagging behind by 27ms, your system is too slow
[ 34178.986] (EE) event7  - COMPANY USB Device: client bug: event processing lagging behind by 32ms, your system is too slow

I guess some kind of error causes “NVIDIAA(GPU-0)” and some kind of “event 7” to repeat lots of operations which were counted up to the 33K.

I have some issues with English and I’ve been using Linux OC not for a very long time but I hope that I might find here solution to fix my PC.

Any help in investigating this would be appreciated!

nvidia-bug-report.log (866.1 KB)
Here’s nvidia-bug-report.log.

The numbers are not counts but seconds of uptime. So after 30 minutes, your monitor gets requeried, also after 10 hours, etc. Nothing to see or worry.
The real issue can be seen in dmesg, some application you’re running is eating/leaking memory, you’re running out of memory so the kernel is heavily swapping to disk, the system comes down to a crawl, the the oom killer takes actions, then it works again.
You should regulary check the activity monitor for applications eating memory, check if you have any broken chrome plugins.

1 Like

I see.
Thank you for explaining! I’ll try to regulary check the activity monitor and dmesg.

My first guess would be “baloo_file”