[Bug 103810] [kbl] Team Fortress 2 HDR Enabled Crashes

[bugzilla-daemon at freedesktop.org]

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

--- Comment #23 from vadym <vadym.shovkoplias at globallogic.com> ---
Hi Elizabeth,

I tested again with old mesa 17.2.4 (git-1b10d0851a) and issue is 100%
reproducible with exactly the same error as it was initially reported.

Here is crash info from gdb:

Thread 32 "MatQueue0" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xba018b40 (LWP 16639)]
0xda19df88 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/tf/bin/client.so
(gdb) bt
#0  0xda19df88 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/tf/bin/client.so
#1  0xda19e0a6 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/tf/bin/client.so
#2  0xda19e154 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/tf/bin/client.so
#3  0xda19e22d in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/tf/bin/client.so
#4  0xda19e26e in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/tf/bin/client.so
#5  0xda146716 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/tf/bin/client.so
#6  0xda146a19 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/tf/bin/client.so
#7  0xf7d1754b in ?? () from /lib/i386-linux-gnu/libc.so.6
#8  0xf7d175b1 in exit () from /lib/i386-linux-gnu/libc.so.6
#9  0xf510b48e in _intel_batchbuffer_flush_fence.part.5 () from
/usr/local/lib/dri//i965_dri.so
#10 0xf5118ba5 in intel_dri2_flush_with_flags () from
/usr/local/lib/dri//i965_dri.so
#11 0xf7fa7d21 in loader_dri3_flush () from /usr/local/lib/libGL.so.1
#12 0xf7fa2bfe in glx_dri3_flush_drawable () from /usr/local/lib/libGL.so.1
#13 0xf7fa822d in loader_dri3_swap_buffers_msc () from
/usr/local/lib/libGL.so.1
#14 0xf7fa2ea4 in dri3_swap_buffers () from /usr/local/lib/libGL.so.1
#15 0xf7f74bd9 in glXSwapBuffers () from /usr/local/lib/libGL.so.1
#16 0xf5ecacd7 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/bin/libSDL2-2.0.so.0
#17 0xf5ebea31 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/bin/libSDL2-2.0.so.0
#18 0xf5e50704 in SDL_GL_SwapWindow () from
/home/vadym/.steam/steam/steamapps/common/Team Fortress 2/bin/libSDL2-2.0.so.0
#19 0xf65906ad in ?? () from bin/launcher.so
#20 0xf5f58981 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/bin/libtogl.so
#21 0xf5f48f1b in IDirect3DDevice9::Present(_RECT const*, _RECT const*, void*,
RGNDATA const*) () from /home/vadym/.steam/steam/steamapps/common/Team Fortress
2/bin/libtogl.so
#22 0xf157fef5 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/bin/shaderapidx9.so
#23 0xf316b7bb in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/bin/materialsystem.so
#24 0xf316bade in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/bin/materialsystem.so
#25 0xf3145ad1 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/bin/materialsystem.so
#26 0xf314f34a in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/bin/materialsystem.so
#27 0xf314e3f7 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/bin/materialsystem.so
#28 0xf6437d75 in ?? () from /home/vadym/.steam/steam/steamapps/common/Team
Fortress 2/bin/libvstdlib.so
#29 0xf653d9a1 in CThread::ThreadProc(void*) () from
/home/vadym/.steam/steam/steamapps/common/Team Fortress 2/bin/libtier0.so
#30 0xf7ec537c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#31 0xf7dde0c6 in clone () from /lib/i386-linux-gnu/libc.so.6


In Comment 7 you mentioned that 17.3.1 (git-f66496d291) mesa was used for
testing but in console_stdout attachment
(https://bugs.freedesktop.org/attachment.cgi?id=136397) I can see that other
mesa was used: Mesa 17.2.2 (3.0.0). Probably this log was attached by mistake.
Just in case can you please double check that TM2 is linked with mesa 17.3.1 or
older ?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180201/14fe14ea/attachment.html>