Bug 104295 - Launching counter strike global offensive fails after update from 17.2 to 17.3
Summary: Launching counter strike global offensive fails after update from 17.2 to 17.3
Status: RESOLVED WORKSFORME
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: 17.3
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-16 21:13 UTC by kaspar.tint
Modified: 2018-01-02 14:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
CS:GO coredump (10.50 KB, text/plain)
2017-12-16 21:13 UTC, kaspar.tint
Details

Description kaspar.tint 2017-12-16 21:13:50 UTC
Created attachment 136230 [details]
CS:GO coredump

As mentioned in the summary, CS:GO does not launch anymore after mesa update.

I have attached a core dump with this bug report. I could notice that most of it was referring to radeonsi so that's why I turned here. If I am wrong and you have nothing to do here then close this ticket.

This issue appears every time when I open CS:GO. The game window is created after launch, it's black for ~2 seconds and then quits.
Comment 1 kaspar.tint 2017-12-16 21:16:43 UTC
I am using Arch Linux with Steam using the operating systems native runtime if this makes any difference.

Some system info also:

phoronix-test-suite system-info

Phoronix Test Suite v7.6.0
System Information


  PROCESSOR:          Intel Core i5-4570 @ 3.60GHz
    Core Count:       4
    Extensions:       SSE 4.2 + AVX2 + AVX + RDRAND + FSGSBASE
    Cache Size:       6144 KB
    Microcode:        0x22
    Scaling Driver:   intel_pstate powersave

  GRAPHICS:           MSI AMD Radeon RX 470/480/570/580 8192MB
    Display Driver:   modesetting 1.19.1
    Monitor:          BenQ xl2411t
    Screen:           1920x1080

  MOTHERBOARD:        ASUS B85-PLUS
    Memory:           16384MB
    Chipset:          Intel 4th Gen Core DRAM
    Network:          Realtek RTL8111/8168/8411

  DISK:               128GB Samsung SSD 840 + 1000GB Seagate ST1000DM010-2DM1 + 1000GB Seagate ST1000DM003-1CH1
    File-System:      btrfs
    Mount Options:    relatime rw space_cache ssd subvol=/ subvolid=5
    Disk Scheduler:   CFQ

  OPERATING SYSTEM:   Arch rolling
    Kernel:           4.14.5-1-ARCH (x86_64)
    Desktop:          GNOME Shell 3.26.2
    Compiler:         GCC 7.2.1 20171128
Comment 2 Michel Dänzer 2017-12-18 11:19:31 UTC
Can you bisect?
Comment 3 kaspar.tint 2017-12-18 12:32:13 UTC
(In reply to Michel Dänzer from comment #2)
> Can you bisect?

Not familiar enough with the project probably to do it in a reasonable time.
Comment 4 sleepyoh 2017-12-28 18:52:25 UTC
Running Arch, Had the same problem but is since today solved.

Today there was updates from mesa (17.3.0-2 -> 17.3.1-2) and xorg-server (1.19.5-1 -> 1.19.6-2) wich solved this problem, working fine again.

https://bbs.archlinux.org/viewtopic.php?id=232925

I had problems for weeks, now working fine, resolved for me.
Comment 5 Emil Velikov 2017-12-28 20:19:53 UTC
(In reply to sleepyoh from comment #4)
> Running Arch, Had the same problem but is since today solved.
> 
> Today there was updates from mesa (17.3.0-2 -> 17.3.1-2) and xorg-server
> (1.19.5-1 -> 1.19.6-2) wich solved this problem, working fine again.
> 
> https://bbs.archlinux.org/viewtopic.php?id=232925
> 
> I had problems for weeks, now working fine, resolved for me.

I fear your observation is unrelated - Mesa 17.3.1 includes commit 5ac9d91ee3d897016d54e970a977c3fbbbe2488e, which
 a) is exclusive for Intel (Skylake or newer)
 b) resolved a GPU lockup

While the issue here seems to be:
 a) radeonsi hardware
 b) program crash
Comment 6 sleepyoh 2017-12-29 01:32:30 UTC
(In reply to Emil Velikov from comment #5)
> (In reply to sleepyoh from comment #4)
> > Running Arch, Had the same problem but is since today solved.
> > 
> > Today there was updates from mesa (17.3.0-2 -> 17.3.1-2) and xorg-server
> > (1.19.5-1 -> 1.19.6-2) wich solved this problem, working fine again.
> > 
> > https://bbs.archlinux.org/viewtopic.php?id=232925
> > 
> > I had problems for weeks, now working fine, resolved for me.
> 
> I fear your observation is unrelated - Mesa 17.3.1 includes commit
> 5ac9d91ee3d897016d54e970a977c3fbbbe2488e, which
>  a) is exclusive for Intel (Skylake or newer)
>  b) resolved a GPU lockup
> 
> While the issue here seems to be:
>  a) radeonsi hardware
>  b) program crash

Hm, well the only thing that's changed on my system from not working csgo to working csgo was today's new mesa and xorg, only packages that got updated and now it's working fine. Maybe xorg then, idk.
Comment 7 kaspar.tint 2018-01-02 14:22:22 UTC
Can confirm that updates to either X.org or Mesa fixed this issue already. Can close this I guess.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.