[Intel-gfx] [Mesa3d-dev] i965 OpenGL is heavily broken again

[Florian Mickler]

On Sat, 06 Mar 2010 18:02:51 +0100
Stephan Raue <mailinglists at openelec.tv> wrote:

> looks this like my problems that i have reported some days ago with 
> Subject "Problem using an Mesa based App with recent 
> xorg/mesa/xf86-video-intel (loop?)" to Mesa-dev, xorg and intel-gfx list?
> 
> i have still this issue, but i dont know what you need for informations 
> to fix the issues?
> 
> with ati driver i dont have problems, only here with intel driver on my 
> Thinkpad X200t with intel HDA Graphics card
> 
> Stephan
> 
> Am 06.03.2010 17:46, schrieb Maxim Levitsky:
> > Here, gdb backtrace while running sauerbraten full screen:
> >
> >
> > #2  0xb6e93d80 in ?? () from /usr/lib/libxcb.so.1
> > #3  0xb6e959d2 in xcb_wait_for_reply () from /usr/lib/libxcb.so.1
> > #4  0xb7387e7e in _XReply (dpy=0x9023938, rep=0xbfc6a4dc, extra=0, discard=0) at xcb_io.c:454
> > #5  0xb772ba30 in DRI2GetBuffersWithFormat (dpy=0x9023938, drawable=62914575, width=0x93eed74, height=0x93eed78, attachments=0xbfc6a5dc, count=2,
> >      outCount=0xbfc6a608) at dri2.c:428
> > #6  0xb7729f62 in dri2GetBuffersWithFormat (driDrawable=0x93eed50, width=0x93eed74, height=0x93eed78, attachments=0xbfc6a5dc, count=2, out_count=0xbfc6a608,
> >      loaderPrivate=0x93eecb0) at dri2_glx.c:435
> > #7  0xb6557bf3 in intel_update_renderbuffers (context=0x905c678, drawable=0x93eed50) at intel_context.c:253
> > #8  0xb65581d5 in intel_prepare_render (intel=0x90c6c50) at intel_context.c:395
> > #9  0xb657a423 in brw_try_draw_prims (ctx=<value optimized out>, arrays=0x910418c, prim=0x9102c60, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001',
> >      min_index=0, max_index=3) at brw_draw.c:340
> > #10 brw_draw_prims (ctx=<value optimized out>, arrays=0x910418c, prim=0x9102c60, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001', min_index=0, max_index=3)
> >      at brw_draw.c:441
> > #11 0xb663ea64 in vbo_exec_vtx_flush (exec=0x9102b30, unmap=1 '\001') at vbo/vbo_exec_draw.c:384
> > #12 0xb663a42a in vbo_exec_FlushVertices_internal (ctx=0xfffffdfc, unmap=255 '\377') at vbo/vbo_exec_api.c:872
> > #13 0xb663c230 in vbo_exec_FlushVertices (ctx=0x90c6c50, flags=1) at vbo/vbo_exec_api.c:906
> > #14 0xb65daea5 in _mesa_set_enable (ctx=0x90c6c50, cap=3042, state=1 '\001') at main/enable.c:283
> > #15 0xb65db1bf in _mesa_Enable (cap=3042) at main/enable.c:1007
> > #16 0x080abf08 in ?? ()
> > #17 0x080ad3fc in ?? ()
> > #18 0xb7479b56 in __libc_start_main (main=0x80ad0a0, argc=3, ubp_av=0xbfc6abb4, init=0x824a9f0, fini=0x824a9e0, rtld_fini=0xb789cd20<_dl_fini>,
> >
> >
> > Best regards,
> > 	Maxim Levitsky
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >
> >    
> 
> 

with glxgears I can reproduce a hang in _XReply with the same backtrace
up to intel_prepare_render.. i think there are some vblank events
going awol or somewhat like that.. 

i just have to move glxgears from one xrandr head to the next...
(a little bit timing in there, but nonetheless it is easy to trigger)

with the soon-to-be linux-2.6.34-rc1 however, it will now only
hang some 1 or 2 secs then continue to run. 

i'm running on 64bit... (kernel + userland) ... 

hth,
Flo