os: 32 bit
Bug detailed description:
We run 3DMarkMobileES2.0 on T410 32bit system with the newest code on mesa master branch, it can't run with "Segmentation fault". I find it can run without segmentation fault before glsl2 branch merge to master branch. And with the merge point of glsl2 to master or on glsl2 branch, it will has such issue.
There is a message in dmesg: 3DMarkMobileES2: segfault at 4 ip 080691be sp bfb316c0 error 4 in 3DMarkMobileES20[8048000+67000]
The backtrace is as following.
Program received signal SIGSEGV, Segmentation fault.
0x080691be in oes_draw_elements (engine=0x80b3740, mode=4, count=768,
Missing separate debuginfos, use: debuginfo-install expat-2.0.1-10.fc13.i686 glibc-2.12-1.i686 libXdmcp-1.0.3-3.fc13.i686 libgcc-4.4.4-2.fc13.i686 libstdc++-4.4.4-2.fc13.i686 libtalloc-2.0.1-1.fc13.i686
#0 0x080691be in oes_draw_elements (engine=0x80b3740, mode=4, count=768,
#1 0x08065a1c in oes_batch_draw (player=0x80b7a48)
#2 0x080622aa in oes_transform_and_draw_object_batch (player=0x80b7a48,
#3 0x08062434 in oes_object_set_draw (player=0x80b7a48, object_set=0xb6c00170)
#4 0x08064a23 in oes_scene_player_draw (player=0x80b7a48)
#5 0x08076741 in render_scene (app=0x80b0010)
#6 0x0806c1e1 in app_update (app=0x80b0010)
#7 0x0804c8ea in main ()
run the 3DMarkMobileES2.0 with newest code in mesa master or glsl2 branch.
I can't reproduce this, sorry. I tried building 3DMarkMobileES2.0 on my 64-bit Linux system and hit all kinds of build failures due to #include picking up 3DMark's "string.h" and "math.h" rather than the system headers. After patching 17 different files I was able to get it to build, but it crashes at application startup, well before any real work is done.
So I'm not sure how to proceed.
I don't believe this bug should delay the Q4 release. ES is still a somewhat new and thus experimental feature (though working more and more each time!), and I don't think this is a regression from prior releases. We also still haven't tracked it to a specific issue in our driver.
It still warrants looking into, but I don't think it's a top-priority bug.
agree this doesn't block Q4 release.
but note this is regression as the original description mentions this worked before glsl2 merge.
It seems to run with Mesa master, which has Chad's fixes for dealing with the "precision" qualifier.
Last I checked (some time ago) 3DMarkMobileES2.0 runs without crashing. Closing this report. There are likely other 3DMarkMobileES2.0 issues, but they can be opened as new reports.
(In reply to comment #5)
> Last I checked (some time ago) 3DMarkMobileES2.0 runs without crashing.
> Closing this report. There are likely other 3DMarkMobileES2.0 issues, but they
> can be opened as new reports.
With the newest code in master branch and kernel in drm-intel-next, the 3DMarkMobileES2.0 was successfully begin to test instead of crashing. Tested with:
on Mar 28, 2017 at 15:52:06.
(provided by the Example extension).