Bug 38661 - [i915g] src/gallium/drivers/i915/i915_state_static.c:122:update_framebuffer: Assertion `offset == 0' failed.
Summary: [i915g] src/gallium/drivers/i915/i915_state_static.c:122:update_framebuffer: ...
Status: CLOSED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/i915g (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-24 17:36 UTC by Vinson Lee
Modified: 2011-12-29 12:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Vinson Lee 2011-06-24 17:36:43 UTC
mesa: 3a7953910a7c3babebd6479bbefe9a1032bd8299 (master)

chipset: 945GM (Intel GMA 950)
system architecture: i686
xserver-xorg-video-intel: 2:2.14.0-4ubuntu7.1
libdrm-intel1: 2.4.23-1ubuntu6
kernel version: 2.6.38-8-generic
Linux distribution: Ubuntu 11.04 i386


Run piglit fbo-clear-formats GL_ARB_depth_texture test.

$ ./bin/fbo-clear-formats GL_ARB_depth_texture -auto
Using test set: GL_ARB_depth_texture
Testing GL_DEPTH_COMPONENT
src/gallium/drivers/i915/i915_state_static.c:122:update_framebuffer: Assertion `offset == 0' failed.
Trace/breakpoint trap (core dumped)

(gdb) bt
#0  0x01174574 in _debug_assert_fail (expr=0x1a7c0eb "offset == 0", file=0x1a7c0b8 "src/gallium/drivers/i915/i915_state_static.c", line=122, 
    function=0x1a7c11d "update_framebuffer") at src/gallium/auxiliary/util/u_debug.c:282
#1  0x01121a1f in update_framebuffer (i915=0x9cf93f8) at src/gallium/drivers/i915/i915_state_static.c:122
#2  0x0111ef18 in i915_update_derived (i915=0x9cf93f8) at src/gallium/drivers/i915/i915_state_derived.c:195
#3  0x01119f86 in i915_draw_vbo (pipe=0x9cf93f8, info=0xbfd48b14) at src/gallium/drivers/i915/i915_context.c:66
#4  0x011766a3 in util_draw_arrays (pipe=0x9cf93f8, mode=6, start=0, count=4) at src/gallium/auxiliary/util/u_draw.h:63
#5  0x0117677a in util_draw_vertex_buffer (pipe=0x9cf93f8, cso=0x9dda148, vbuf=0x9e5d058, offset=0, prim_type=6, num_verts=4, num_attribs=2)
    at src/gallium/auxiliary/util/u_draw_quad.c:69
#6  0x019fc957 in draw_quad (st=0x9dc5598, x0=-1, y0=-1, x1=-0.984375, y1=1, z=0.00390625, color=0xbfd48c3c) at src/mesa/state_tracker/st_cb_clear.c:199
#7  0x019fcf2a in clear_with_quad (ctx=0x9d875e8, color=0 '\000', depth=2 '\002', stencil=0 '\000') at src/mesa/state_tracker/st_cb_clear.c:332
#8  0x019fd5fa in st_Clear (ctx=0x9d875e8, mask=16) at src/mesa/state_tracker/st_cb_clear.c:563
#9  0x019856c5 in _mesa_Clear (mask=256) at src/mesa/main/clear.c:250
#10 0x0806ac47 in do_depth_clear ()
#11 0x0806ae3a in create_tex ()
#12 0x0806b716 in test_format ()
#13 0x0806a66c in fbo_formats_display ()
#14 0x0806b824 in piglit_display ()
#15 0x0806c20b in display ()
#16 0x00317c1e in fghRedrawWindow (window=0x9cf1a00, enumerator=0xbfd48f58) at freeglut_main.c:210
#17 fghcbDisplayWindow (window=0x9cf1a00, enumerator=0xbfd48f58) at freeglut_main.c:227
#18 0x0031b590 in fgEnumWindows (enumCallback=0x317b20 <fghcbDisplayWindow>, enumerator=0xbfd48f58) at freeglut_structure.c:394
#19 0x0031802e in fghDisplayAll () at freeglut_main.c:249
#20 glutMainLoopEvent () at freeglut_main.c:1450
#21 0x00318935 in glutMainLoop () at freeglut_main.c:1498
#22 0x0806c3af in main ()
(gdb) frame 1
#1  0x01121a1f in update_framebuffer (i915=0x9cf93f8) at src/gallium/drivers/i915/i915_state_static.c:122
122	      assert(offset == 0);
(gdb) print offset
$1 = 262144
(gdb) print /x offset
$2 = 0x40000
Comment 1 Stephane Marchesin 2011-06-24 17:44:36 UTC
Was also fixed a very little while ago.
Comment 2 Vinson Lee 2011-06-24 18:52:29 UTC
mesa: 773556e0f537eba82d9d68d618e229140f413620 (master)

Assert still occurs.
Comment 3 Vinson Lee 2011-12-12 16:50:10 UTC
mesa: 23895cc006f3dbf96a502ddd15e291e071aff25a (master)

Assert still occurs.
Comment 4 Vinson Lee 2011-12-29 12:33:08 UTC
mesa: 747f0307626ef5bcf2f889ab66bcc95ab8eda2c8 (master)

Verified fixed.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.