Bug 102625

Summary: Game Crashlands crashes on startup
Product: Mesa Reporter: ratatosk.yggdrasil
Component: Drivers/Gallium/radeonsiAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact: Default DRI bug account <dri-devel>
Severity: normal    
Priority: medium CC: lockert.fredrick, ratatosk.yggdrasil
Version: git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 105797    
Bug Blocks:    
Attachments: gdb output when running crashlands
gdb output when running crashlands
Output with R600_DEBUG="ps,vs,tcs,tes,cs,gs"

Description ratatosk.yggdrasil 2017-09-08 13:27:43 UTC
Created attachment 134084 [details]
gdb output when running crashlands

Running on Arch with latest Mesa in the official repositories (17.1.8) via mesa-git from AUR or 17.0.x in Ubuntu 16.04 and 17.04 Crashlands crashes on startup (a window opens and immediately closes again) in combination with a Radeon RX 470. On another machine using integrated HD 6620G it runs fine (Ubuntu 16.04).

Using LLVMPIPE via LIBGL_ALWAYS_SOFTWARE=1 and GALLIUM_DRIVER=llvmpipe the game runs as expected.

When starting the game from command line I get a segfault with this message:
./run.sh: Zeile 3:  2218 Speicherzugriffsfehler  (Speicherabzug geschrieben) LD_LIBRARY_PATH=./lib:$LD_LIBRARY_PATH ./runner

This error however seems to be unrelated to the crash because it remains even if using LLVMPIPE.

Running via gdb produces the attached output.

GNU gdb (GDB) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from runner...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/nagezahn/.local/share/Steam/steamapps/common/Crashlands/runner 
/home/nagezahn/.local/share/Steam/steamapps/common/Crashlands/runner: /usr/lib32/libcrypto.so.1.0.0: no version information available (required by /home/nagezahn/.local/share/Steam/steamapps/common/Crashlands/runner)
/home/nagezahn/.local/share/Steam/steamapps/common/Crashlands/runner: /usr/lib32/libssl.so.1.0.0: no version information available (required by /home/nagezahn/.local/share/Steam/steamapps/common/Crashlands/runner)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

***************************************
*     YoYo Games Linux Runner V1.3    *
***************************************	 
CommandLine: -game game.unx
ExeName= /home/nagezahn/.local/share/Steam/steamapps/common/Crashlands/runner
MemoryManager allocated: 1723148
INI DisplayName=Crashlands
SavePrePend /home/nagezahn/.config/Crashlands/ 
GAMEPAD: Initialising Ubuntu support
Attempting to set gamepadcount to 4
Steam being initialised with appId 391730
Steam_Init
Error: Failed to load libsteam_api.so: libsteam_api.so: cannot open shared object file: No such file or directory
Failed LoadSteamLib() call: Error loading libsteam_api.so
SteamInit failed: Error loading libsteam_api.so
Display Size(Pixels): 1920,1200
GameDisplayName=Crashlands
Win #1
XF86VidModeExtension-Version 2.2
libGL error: failed to create dri screen
libGL error: failed to load driver: swrast
Got Doublebuffered Visual!
glX-Version 1.4
Icon: w=120 h=120
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  30
  Current serial number in output stream:  32
[Inferior 1 (process 3337) exited with code 01]
Comment 1 ratatosk.yggdrasil 2017-09-08 13:44:20 UTC
Created attachment 134086 [details]
gdb output when running crashlands
Comment 2 ratatosk.yggdrasil 2017-09-08 13:46:11 UTC
Apologies, please ignore the previous gdb output. The error printed there was transient which was gone after a reboot. I have updated the attached gdb output which should be more helpful now.
Comment 3 Samuel Pitoiset 2017-09-08 14:26:38 UTC
I bet if you launch the game with R600_DEBUG="ps,vs,tcs,tes,cs,gs" it will work.

It's similar to the "Peace, Death!" issue because they both use the same engine.
Comment 4 Philipp Überbacher 2017-09-08 23:53:11 UTC
Created attachment 134101 [details]
Output with R600_DEBUG="ps,vs,tcs,tes,cs,gs"

Radeon RX 560
Arch Linux, mesa 17.1.8, xf86-video-amdgpu 1.3.0

R600_DEBUG="ps,vs,tcs,tes,cs,gs" LD_LIBRARY_PATH=~/.steam/bin32/ ./run.sh
Comment 5 Philipp Überbacher 2017-09-10 10:03:14 UTC
With xf86-video-amdgpu 1.4.0 and mesa 17.2.0 the game starts for me. Seems this bug has already been fixed.
Comment 6 Philipp Überbacher 2017-09-10 10:33:08 UTC
In this particular situation it would be good to know what fixed the issue and whether there is a workaround available.

Any ideas?
Comment 7 ratatosk.yggdrasil 2017-09-10 11:39:23 UTC
As far as I know there was an update of the game engine included.
Comment 8 Timothy Arceri 2018-03-29 07:36:42 UTC
Reopening as the game engine version is the same in both logs. Can you confirm if its working or was it just working when you ran with R600_DEBUG="ps,vs,tcs,tes,cs,gs" ?
Comment 9 GitLab Migration User 2019-09-25 18:00:13 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1281.

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.