Page MenuHomeSolus

Counter Strike: Global Offensive freeze
Closed, ResolvedPublic

Description

Hello,
Pretty often when I play CS:GO, it freezes when I try to quit the game or alt+tab. I mean it seems to freeze whole Xorg and then sometimes even whole graphic card or something. Could you please help me to debug it? Don't know what could be wrong.

System Spec:
OS: Solus x86_64
Host: MS-7C02 1.0
Kernel: 5.5.7-150.current
Uptime: 59 mins
Packages: 1358 (eopkg), 4 (flatpak)
Shell: bash 5.0.11
Resolution: 1920x1080
DE: Budgie
Theme: Plata [GTK2/3]
Icons: Papirus [GTK2/3]
Terminal: gnome-terminal
CPU: AMD Ryzen 5 3600 6- (12) @ 3.600GHz
GPU: AMD ATI 28:00.0 Navi 10
Memory: 1699MiB / 16023MiB

Event Timeline

Mark12870 renamed this task from Counter Strike: Global Offensive freeze (please, help to debug) to Counter Strike: Global Offensive freeze.Mar 9 2020, 8:31 PM

I have Ryzen 7 2700X and Radeon RX 570 and this doesn't happen to me. Which GPU driver are you using?

Hello, My Mesa version should be 19.3.4. Ye, I know much people don't have my problem. That's why I need some help with debugging. I don't know how to track this.

Is there any way, how I can reset the graphic driver to default configuration?

Run lspci -k | grep -EA3 'VGA|3D|Display' and paste the output here

$ lspci -k | grep -EA3 'VGA|3D|Display'
28:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 (rev c1)
	Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5700 / 5700 XT]
	Kernel driver in use: amdgpu
28:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio

I'm using amdgpu too and I have no problems. How long does the freeze happen? Is it short or do you have to shut down your computer afterwards?

I have to restart computer or unplug monitor and plug it back. I think the computer works fine when this happens, only the screen is frozen.

DataDrake triaged this task as Needs More Info priority.Mar 18 2020, 3:49 PM
DataDrake edited projects, added Hardware; removed Lacks Project.
DataDrake added a subscriber: DataDrake.

Navi support is still pretty new in both the Kernel and Mesalib. Let's see if upgrading those helps. Please follow-up after the next kernel upgrade. Thank you!

Well, it seems it was a cable problem. I don't know how it is possible it was a cable, but I changed it and since then I don't have this issue. But it is only one day of testing right now...

DataDrake claimed this task.

Going to assume this is fixed in lieu of new information to the contrary.