[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

Nicolai Hähnle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #29 from Nicolai Hähnle  ---
Closing as per previous comment.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #28 from Quentin Quaadgras  ---
Yes

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #27 from Marek Olšák  ---
(In reply to Quentin Quaadgras from comment #26)
> I just by chance tried running awesomenauts through the command line again
> after updating to a recent daily build and the game is now running. It is
> still not running within the steam client but this is a good sign.

So is this fixed for you?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #26 from Quentin Quaadgras  ---
I just by chance tried running awesomenauts through the command line again
after updating to a recent daily build and the game is now running. It is still
not running within the steam client but this is a good sign.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #25 from Quentin Quaadgras  ---
Any conclusions on this?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #24 from cosiekvfj at o2.pl ---
Created attachment 125049
  --> https://bugs.freedesktop.org/attachment.cgi?id=125049=edit
gdb

Do I need also lib32-llvm-db?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #23 from Quentin Quaadgras  ---
Created attachment 124944
  --> https://bugs.freedesktop.org/attachment.cgi?id=124944=edit
Complete Valgrind output

I added --error-limit=no and then deleted the 1000 harmless conditional errors
from before. This looks better.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #22 from Nicolai Hähnle  ---
Valgrind has options --gen-suppressions and --suppressions to help with
suppressing unrelated errors. The first option will output suggested
suppression statements that need to be put into a file that can be loaded with
the suppressions option on a second run. Based on the Valgrind log, something
like

{
   
   Memcheck:Cond

obj:/home/user/.steam/steam/steamapps/common/Awesomenauts/Awesomenauts.bin.x86
}

should actually be sufficient as a suppression file.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #21 from Bart van Heukelom  ---
Another Awesomenauts developer here. I don't know much about our OpenGL code,
but I do about our Linux version. Our linking options in CMakeLists are as
follows:

SET_TARGET_PROPERTIES(Awesomenauts
PROPERTIES
LINK_FLAGS_RELEASE "-Wl,--allow-shlib-undefined,-s,-x"

We don't do anything special with libstdc++

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #20 from Michel Dänzer  ---
Presumably it works with valgrind because it prevents the fatal effect of the
bad memory access which causes the problem. Note that valgrind stopped logging
errors after 1000 instances of the same (presumably harmless) issue in the
Awesomenauts code. Maybe there's some way to suppress those, so we can see the
problem?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #19 from Quentin Quaadgras  ---
LIBGL_ALWAYS_SOFTWARE=y results in the game correctly launching.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #18 from Nicolai Hähnle  ---
Sorry, I don't know what the difference could be in the Valgrind runs. For
completeness, could you try whether the game also crashes with
LIBGL_ALWAYS_SOFTWARE=y?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #17 from Quentin Quaadgras  ---
Multithreading setting has no effect for me, @Nicolai is there any workaround
then? The game was running under Valgrind, I am not so familiar with the
software, is it doing anything differently in regards to the libraries it
loads?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #16 from Nicolai Hähnle  ---
I'm not familiar with Manjaro Linux, but usually there is a package with a -dbg
or similar suffix, e.g. mesa-dbg, llvm-dbg, something like that.

And yes, it's not surprising that the r300 driver crashes later because it
doesn't usually use LLVM. My guess is that Awesomenauts hits a path where some
of the software paths for vertex shading are used and then it crashes.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #15 from cosiekvfj at o2.pl ---
And I forgot to add that in my case game crash after the intro.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #14 from cosiekvfj at o2.pl ---
Yes of course. How to do that? :)

Yes, multithreading is a setting of the game.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #13 from Nicolai Hähnle  ---
Thank you for the additional info. Could you also attach the output with debug
symbols installed?

When you say multithreading off vs. on, is that a setting of the game?

It seems increasingly likely that this is a problem related to libstdc++
linking or something else that Awesomenauts does.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #12 from cosiekvfj at o2.pl ---
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
RC410M [Mobility Radeon Xpress 200M]

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #11 from cosiekvfj at o2.pl ---
Can confirm on

Linux EasyNoteMZ35 4.4.13-1-MANJARO #1 SMP PREEMPT Wed Jun 8 09:21:59 UTC 2016
x86_64 GNU/Linux


Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org R300 Project (0x1002)
Device: ATI RC410 (0x5a62)
Version: 11.1.2
Accelerated: yes
Video memory: 128MB
Unified memory: no
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: X.Org R300 Project
OpenGL renderer string: Gallium 0.4 on ATI RC410
OpenGL version string: 2.1 Mesa 11.1.2
OpenGL shading language version string: 1.20


The weird thing is that game crash only with multithread off. With multithread
on I can play.

http://pastebin.com/7EaGcn2B

http://pastebin.com/XHnF0Ur8

http://pastebin.com/gGxjWpde

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #10 from Quentin Quaadgras  ---
Created attachment 124928
  --> https://bugs.freedesktop.org/attachment.cgi?id=124928=edit
Valgrind output.

Here is the Valgrind output, the game started up correctly under Valgrind. It
was taking a rather long time in the loading screen so I killed it. Hopefully
the log contains some useful information.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #9 from Nicolai Hähnle  ---
Thanks.

The crash happens inside the implementation of std::stable_sort when called
from LLVM. An internal buffer pointer seems to be corrupted. Since the buffer
pointer lives on the stack I don't have a good explanation for this, just some
hypotheses we can follow up on:

1. Joost, does Awesomenauts do anything non-standard when linking to libstdc++?
Perhaps symbols get mixed up in a way that leads to the wrong code being
executed. It wouldn't be the first time that problems come from there, although
usually when games do that they just fail to load in the dynamic linker.

2. Quentin, you could try running the game with Valgrind and see if anything
comes up. It's going to be slow, but if there is a stack-smashing bug here in
LLVM (extremely unlikely, but whatever) then Valgrind should catch it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #8 from Quentin Quaadgras  ---
Created attachment 124900
  --> https://bugs.freedesktop.org/attachment.cgi?id=124900=edit
GDB bt full of the crash (dbg packages installed)

Thanks for providing some information Joost :)

@Nicolai
I have attached the gdb bt full trace.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #7 from Nicolai Hähnle  ---
Hi Joost, nice to see you here :)

He's indeed running the open-source radeonsi driver. The shader being compiled
is very simple and probably from the glClear() call. Those don't usually crash,
and I can compile the LLVM IR from the log here just fine.

Quentin: Could you please install debug packages of 32-bit LLVM and Mesa so
that we can get a more informative backtrace?

With the debug packages installed, also try running the game from gdb, and
produce a detailed backtrace using `bt full` after the crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #6 from Joost van Dongen  ---
Joost here, lead programmer on Awesomenauts. Based on these logs it seems like
a driver problem since the crash is in an extremely early part of our OpenGL
code, before we do anything exciting. Also, nothing recently changed in that
part of our OpenGL code.

I'm not a Linux expert myself but it seems like you might not be running
proprietary AMD drivers or something like that? Maybe try other drivers?

Based on these logs the crash is somewhere in this bit of code:

GLint swapInterval = 0;
switch (interval)
{
case VSI_ONE:   swapInterval = 1;   break;
case VSI_TWO:   swapInterval = 2;   break;
case VSI_NONE:
default:   
break;
}   
if (GLXEW_EXT_swap_control)
{
glXSwapIntervalEXT(glXGetCurrentDisplay(),
glXGetCurrentDrawable(), swapInterval);
}
else if (GLXEW_SGI_swap_control)
{
glXSwapIntervalSGI(swapInterval);
}

glViewport(0, 0, windowWidth, windowHeight);
glScissor(0, 0, windowWidth, windowHeight);
glClearColor(0.f, 0.f, 0.f, 0.f);
glEnable(GL_DEPTH_TEST);

// perform an initial rendering to clear the screen on startup
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT |
GL_STENCIL_BUFFER_BIT);
SDL_GL_SwapBuffers();

glDisable(GL_CULL_FACE);
glDisable(GL_DEPTH_TEST);

I don't see any shader code here so if the problem is that a shader isn't
compiling then maybe glClear generates a basic shader to perform the clear, and
fails at that?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

Quentin Quaadgras  changed:

   What|Removed |Added

 Attachment #124880|0   |1
is obsolete||

--- Comment #5 from Quentin Quaadgras  ---
Created attachment 124881
  --> https://bugs.freedesktop.org/attachment.cgi?id=124881=edit
Padoka with R600_DEBUG set

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #4 from Quentin Quaadgras  ---
Comment on attachment 124880
  --> https://bugs.freedesktop.org/attachment.cgi?id=124880
Padoka with R600_DEBUG set

SystemManager constructor starts
SystemManager constructor ends
Start SSL initialise
End SSL initialise
Checking current matchmaking beta state
SDLWindowAndEventManager constructor starts
Game version:  Version 3.1.5a
SDLWindowAndEventManager constructor ends
SDLWindowAndEventManager::run() starts
SDLWindowAndEventManager::createWindow() starts
LoadBinaryFile: "Data/Config.txt"
[Config]  Input:  version  =  2
[Config]  Input:  resolutionx  =  1920
[Config]  Input:  resolutiony  =  1080
[Config]  Input:  windowmode  =  windowed
[Config]  Input:  texturequality  =  low
[Config]  Input:  vsync  =  off
[Config]  Input:  backgroundquality  =  low
[Config]  Input:  sharpen  =  off
[Config]  Input:  multithreading  =  off
[Config]  Input:  supersampling  =  off
[Config]  xRes:  1920  yRes:  1080  textureQuality:  LOW  windowMode:  windowed
[Config]  vSyncEnabled:  0
[Config]  sharpen:  0  supersampling:  0  backgroundQuality  LOW 
multithreading  0
GraphicsQualityHandler constructor starts
GraphicsQualityHandler constructor ends
GraphicsQualityHandler::setBackgroundsQuality switches from  MEDIUM  to  LOW
SDL_SetVideoMode starts
SDL_SetVideoMode ends
Resolution of actual screen:  1920  1080
unbindGLFromCallingThread starts, threadID:  4119840704
unbindGLFromCallingThread ends
SDLWindowAndEventManager::createWindow() ends
GameLoop constructor starts
Constructor of SteamLinuxSingleGameInstanceEnforcer starts
Main Thread ID is  3800734528
Thread that calls SceneManager::render Thread ID is  3800734528
SceneManager constructor starts
RenderThreadManager constructor starts
StatisticsManager constructor starts
StatisticsManager constructor ends
bindGLToCallingThread starts, threadID:  3800734528
bindGLToCallingThread ends
Renderer constructor starts
Renderer constructor ends
ShaderBasedRenderer constructor starts
ShaderBasedRenderer constructor ends
GLRenderer constructor starts
GLRenderer constructor ends
PCMacRenderer constructor starts
PCMacRenderer constructor ends
LinuxRenderer constructor starts
LinuxRenderer constructor ends
PCMacRenderer::initialise starts
OpenGL GL_VENDOR  X.Org
OpenGL GL_RENDERER  Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0 / 4.4.0-28-generic,
LLVM 3.9.0)
OpenGL GL_VERSION  3.0 Mesa 12.1.0-devel - padoka PPA (git-d8d6091)
OpenGL GL_EXTENSIONS  GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra
GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract
GL_EXT_copy_texture GL_EXT_polygon_offset GL_EXT_subtexture
GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array
GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters
GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters
GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp
GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp
GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture
GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays
GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add
GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord
GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add
GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias
GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent
GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc
GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression
GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc
GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos
GL_NV_packed_depth_stencil GL_NV_texture_rectangle GL_ARB_depth_texture
GL_ARB_occlusion_query GL_ARB_shadow GL_ARB_texture_env_combine
GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3
GL_ARB_texture_mirrored_repeat GL_ARB_window_pos GL_ATI_fragment_shader
GL_EXT_stencil_two_side GL_EXT_texture_cube_map GL_NV_depth_clamp
GL_NV_fog_distance GL_APPLE_packed_pixels GL_APPLE_vertex_array_object
GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader
GL_ARB_shader_objects GL_ARB_vertex_program GL_ARB_vertex_shader
GL_ATI_draw_buffers GL_ATI_texture_env_combine3 GL_ATI_texture_float
GL_EXT_depth_bounds_test GL_EXT_shadow_funcs GL_EXT_stencil_wrap
GL_MESA_pack_invert GL_NV_primitive_restart GL_ARB_depth_clamp
GL_ARB_fragment_program_shadow GL_ARB_half_float_pixel GL_ARB_occlusion_query2
GL_ARB_point_sprite GL_ARB_shading_language_100 GL_ARB_sync
GL_ARB_texture_non_power_of_two GL_ARB_vertex_buffer_object
GL_ATI_blend_equation_separate GL_EXT_blend_equation_separate
GL_OES_read_format GL_ARB_color_buffer_float GL_ARB_pixel_buffer_object
GL_ARB_texture_compression_rgtc GL_ARB_texture_float GL_ARB_texture_rectangle
GL_ATI_texture_compression_3dc GL_EXT_packed_float GL_EXT_pixel_buffer_object

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #3 from Quentin Quaadgras  ---
(In reply to Nicolai Hähnle from comment #1)
> This is a crash while compiling a shader.
> 
> Could you please check whether the crash also occurs with latest LLVM? The
> padoka PPA has it. If it does, please provide the output with the
> environment variable R600_DEBUG=ps,vs,gs,tes,tcs,cs set.

I added the trace of the crash with the version of mesa and LLVM in the Padoka
PPA.
There does not appear to be any difference.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #2 from Quentin Quaadgras  ---
Created attachment 124880
  --> https://bugs.freedesktop.org/attachment.cgi?id=124880=edit
Padoka with R600_DEBUG set

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

--- Comment #1 from Nicolai Hähnle  ---
This is a crash while compiling a shader.

Could you please check whether the crash also occurs with latest LLVM? The
padoka PPA has it. If it does, please provide the output with the environment
variable R600_DEBUG=ps,vs,gs,tes,tcs,cs set.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96678

Bug ID: 96678
   Summary: Awesomenauts cannot launch AMD PITCAIRN
   Product: Mesa
   Version: git
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
  Severity: major
  Priority: medium
 Component: Drivers/Gallium/radeonsi
  Assignee: dri-devel at lists.freedesktop.org
  Reporter: quentin at splizard.com
QA Contact: dri-devel at lists.freedesktop.org

Created attachment 124723
  --> https://bugs.freedesktop.org/attachment.cgi?id=124723=edit
Stacktrace of the crash

The video game Awesomenauts crashes on startup when initialising OpenGL
renderer. This is on AMD PITCAIRN (DRM 2.43.0 / 4.4.0-24-generic, LLVM 3.8.0)
Using mesa found in Ubuntu 16.04 and Mesa 12.1.0-devel (git-81978c6 2016-06-25
xenial-oibaf-ppa).

Crashes while trying to free an invalid pointer.
The game worked fine with a previous AMD card. (not radeonsi)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: