[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

https://bugs.freedesktop.org/show_bug.cgi?id=96678 Nicolai Hähnle changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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

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 > sti

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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

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&action=edit gdb Do I need also lib32-llvm-db? -- You are receiving this mail because: You are the assignee for the

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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&action=edit Complete Valgrind output I added --error-limit=no and then deleted the 1000 harmless conditional errors

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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 P

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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 (presumab

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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:

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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 regard

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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 l

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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 HTM

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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. -- n

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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)

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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&action=edit Valgrind output. Here is the Valgrind output, the game started up correctly under Valgrind. It was takin

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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 g

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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&action=edit GDB bt full of the crash (dbg packages installed) Thanks for providing some information Joost :) @Nicola

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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 co

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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, nothi

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

https://bugs.freedesktop.org/show_bug.cgi?id=96678 Quentin Quaadgras changed: What|Removed |Added Attachment #124880|0 |1 is obsolete|

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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 En

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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, p

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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&action=edit Padoka with R600_DEBUG set -- You are receiving this mail because: You are the assignee for the bug. ---

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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 R

[Bug 96678] Awesomenauts cannot launch AMD PITCAIRN

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: m