Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: Counter-Strike Global Offensive Hangs and never recovers  (Read 213 times)

Offline usernameusername

  • User
  • Posts: 5
When I play CSGO on siduction, online, either in casual or in competitive, the game almost always hangs and freezes.


At this point I have to hold the power button. I thought it was an issue with SDDM because I had a hang at the lock screen twice, but I removed SDDM and switched to lightdm with KDE and I am still having hanging and complete system freeze in CSGO.


This is very frustrating.


I tried journalctl but there is just TOO much information in there - even from the last minute there is endless information and I can't find anything about steam or CSGO.



Hardware: Lenovo Legion 510, NVIDIA GTX 1080, newest kernels and newest drivers, been ongoing through numerous updates of both kernel and drivers. I have never had this issue on Arch based distros, Ubuntu, etc (chronic hopper here).


Is there some way to track down why this is happening? Thank you in advance. Vielen dank! Dziekuje! Gracias!

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.569
Re: Counter-Strike Global Offensive Hangs and never recovers
« Reply #1 on: 2021/06/25, 19:51:26 »
You could provide us with what journalctl knows about this after it freezes. You can pin journalctl to print certain timeframes with
Code: [Select]
journalctl --since "1 hour ago" or you could specify
Code: [Select]
journalctl --since "2021-06-25 20:00:00" --until "2016-08-04 20:55:00" You can also use -r in combination, which instructs the system to display the output in reverse order, so latest is on top.

I know nothing about NVIDIA cards, but someone else might be interested in the exact driver-version you use.

Offline usernameusername

  • User
  • Posts: 5
Re: Counter-Strike Global Offensive Hangs and never recovers
« Reply #2 on: 2021/06/26, 14:41:27 »

Code: [Select]
-- Journal begins at Mon 2021-05-24 01:20:50 CEST, ends at Sat 2021-06-26 14:36:23 CEST. --
Jun 26 14:33:33 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:33:36 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:33:48 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:33:51 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:33:58 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:02 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:09 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:14 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:18 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:22 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:24 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:26 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:29 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:34 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:35 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:37 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:45 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:50 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:54 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:34:59 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:35:01 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Jun 26 14:35:06 siduction wpa_supplicant[759]: wlp7s0: CTRL-EVENT-BEACON-LOSS
-- Boot 441861ac116c4eebacd49a2ecbcd625c --
Jun 26 14:35:35 siduction kernel: microcode: microcode updated early to revision 0xea, date = 2021-01-05
Jun 26 14:35:35 siduction kernel: Linux version 5.12.13-2-siduction-amd64 (towo@siduction.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT siduction 5.12-13 (2021-06-23)
Jun 26 14:35:35 siduction kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-5.12.13-2-siduction-amd64 root=UUID=a21db860-f889-4350-a21a-5466aa505510 ro rootflags=subvol=@ quiet systemd.show_status=1
Jun 26 14:35:35 siduction kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun 26 14:35:35 siduction kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun 26 14:35:35 siduction kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun 26 14:35:35 siduction kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Jun 26 14:35:35 siduction kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Jun 26 14:35:35 siduction kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jun 26 14:35:35 siduction kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Jun 26 14:35:35 siduction kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Jun 26 14:35:35 siduction kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Jun 26 14:35:35 siduction kernel: BIOS-provided physical RAM map:
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000030fff] usable
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x0000000000031000-0x0000000000031fff] reserved
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x0000000000032000-0x0000000000087fff] usable
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x0000000000088000-0x00000000000fffff] reserved
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000073797fff] usable
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x0000000073798000-0x0000000074897fff] reserved
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x0000000074898000-0x000000008aaaefff] usable
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x000000008aaaf000-0x000000008acaefff] type 20
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x000000008acaf000-0x000000008b49efff] reserved
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x000000008b49f000-0x000000008bb8efff] ACPI NVS
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x000000008bb8f000-0x000000008bc0efff] ACPI data
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x000000008bc0f000-0x000000008bc0ffff] usable
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x000000008bc10000-0x000000008f7fffff] reserved
Jun 26 14:35:35 siduction kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved

Offline usernameusername

  • User
  • Posts: 5
Re: Counter-Strike Global Offensive Hangs and never recovers
« Reply #3 on: 2021/06/26, 14:42:23 »
You can see that my system hanged at 1435 sometime. Then I had to hold down the power button to get it to turn off and boot again.

Offline usernameusername

  • User
  • Posts: 5
Re: Counter-Strike Global Offensive Hangs and never recovers
« Reply #4 on: 2021/06/26, 14:43:06 »
NVIDIA-SMI 460.84       Driver Version: 460.84
Linux siduction 5.12.13-2-siduction-amd64 #1 SMP PREEMPT siduction 5.12-13 (2021-06-23) x86_64 GNU/Linux

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.569
Re: Counter-Strike Global Offensive Hangs and never recovers
« Reply #5 on: 2021/06/26, 22:37:42 »
Unfortunately, the output of journalctl does not help, at least not me.

Offline usernameusername

  • User
  • Posts: 5
Re: Counter-Strike Global Offensive Hangs and never recovers
« Reply #6 on: 2021/06/27, 08:49:12 »
Unfortunately, the output of journalctl does not help, at least not me.
Yeah I agree. Any other ways to figure this one out? I can replicate this bug, so maybe some active monitoring tool with an output?

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.569
Re: Counter-Strike Global Offensive Hangs and never recovers
« Reply #7 on: 2021/06/27, 11:53:11 »
As I am not a gamer at all and know nothing about Nvidia, I am at a loss. Does xorg.log or xsession-errors tell you anything new?