[Bug 109732] DiRT Rally has extreme graphical corruption and performance loss

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Mar 23 03:58:42 UTC 2019


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

--- Comment #10 from leozinho29_eu at hotmail.com ---
Using Mesa 19.1.0-devel (git-dacb11a585), iris performance is nearly the same
compared to i965: average FPS is 4 lower (80 using i965 versus 76 using iris),
minimum FPS is 16 lower (60 vs. 44) and maximum FPS is 3 lower (111 vs 108).
The game performance with iris increased 80% in one month. This is impressive.

Iris seems to be refusing to free memory or is freeing much less than it should
and it crashed with segmentation fault twice. It seems it is a different
problem from the BLORP one. 

Messages when it crashed:

Thread 56 "OGL_Dispatch_33" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f6e557fa700 (LWP 4873)]
iris_upload_dirty_render_state (ice=ice at entry=0x6812170,
batch=batch at entry=0x6812668, draw=draw at entry=0x7f6e557f9230) at
../src/gallium/drivers/iris/iris_state.c:4350
4350    ../src/gallium/drivers/iris/iris_state.c: Arquivo ou diretório
inexistente.

The backtrace:

#0  0x00007f6ecdcd9f07 in iris_upload_dirty_render_state
(ice=ice at entry=0x6812170, batch=batch at entry=0x6812668,
draw=draw at entry=0x7f6e557f9230) at
../src/gallium/drivers/iris/iris_state.c:4350
#1  0x00007f6ecdcdaa44 in iris_upload_render_state (ice=0x6812170,
batch=0x6812668, draw=0x7f6e557f9230) at
../src/gallium/drivers/iris/iris_state.c:5021
#2  0x00007f6ecde7dff5 in iris_draw_vbo (ctx=0x6812170, info=0x7f6e557f9230) at
../src/gallium/drivers/iris/iris_draw.c:149
#3  0x00007f6ecd732457 in cso_draw_arrays (cso=cso at entry=0x5475040,
mode=mode at entry=5, start=start at entry=0, count=count at entry=4) at
../src/gallium/auxiliary/cso_cache/cso_context.c:1725
#4  0x00007f6ecd84b8c4 in st_pbo_draw (st=st at entry=0x549ed90,
addr=addr at entry=0x7f6e557f94e0, surface_width=<optimized out>,
surface_height=32) at ../src/mesa/state_tracker/st_pbo.c:282
#5  0x00007f6ecd838dda in try_pbo_upload_common (ctx=ctx at entry=0x6f52920,
surface=surface at entry=0x7f6d7ef80710, addr=addr at entry=0x7f6e557f94e0,
src_format=<optimized out>) at ../src/mesa/state_tracker/st_cb_texture.c:1283
#6  0x00007f6ecd83e0af in try_pbo_upload (unpack=0x6f5c330, pixels=0x0,
depth=1, height=32, width=32, zoffset=<optimized out>, yoffset=<optimized out>,
xoffset=0, dst_format=<optimized out>, type=33639, format=32993,
texImage=0x7f6d7d59de60, dims=2, ctx=0x6f52920) at
../src/mesa/state_tracker/st_cb_texture.c:1401
#7  0x00007f6ecd83e0af in st_TexSubImage (ctx=0x6f52920, dims=2,
texImage=0x7f6d7d59de60, xoffset=0, yoffset=0, zoffset=0, width=32, height=32,
depth=1, format=32993, type=33639, pixels=0x0, unpack=0x6f5c330) at
../src/mesa/state_tracker/st_cb_texture.c:1522
#8  0x00007f6ecd7f7124 in texture_sub_image (ctx=ctx at entry=0x6f52920,
dims=dims at entry=2, texObj=texObj at entry=0x7f6d7d799710, texImage=0x7f6d7d59de60,
target=target at entry=3553, level=level at entry=0, xoffset=<optimized out>,
yoffset=0, zoffset=0, width=32, height=32, depth=1, format=32993, type=33639,
pixels=0x0) at ../src/mesa/main/teximage.c:3333
#9  0x00007f6ecd7f9e10 in texsubimage_err (ctx=0x6f52920, dims=2, target=3553,
level=0, xoffset=0, yoffset=0, zoffset=0, width=32, height=32, depth=1,
format=32993, type=33639, pixels=0x0, callerName=0x7f6ecdebeb1e
"glTexSubImage2D") at ../src/mesa/main/teximage.c:3391
#10 0x00007f6ecd7fdd58 in _mesa_TexSubImage2D (target=<optimized out>,
level=<optimized out>, xoffset=<optimized out>, yoffset=<optimized out>,
width=<optimized out>, height=<optimized out>, format=32993, type=33639,
pixels=0x0) at ../src/mesa/main/teximage.c:3609
#11 0x0000000001cf7c34 in  ()
#12 0x0000000001d0de30 in  ()
#13 0x00000000020f8e8e in  ()
#14 0x0000000002173bfe in  ()
#15 0x00007f6ee61d36db in start_thread (arg=0x7f6e557fa700) at
pthread_create.c:463
#16 0x00007f6edf62788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

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


More information about the intel-3d-bugs mailing list