Problem using an Mesa based App with recent xorg/mesa/xf86-video-intel (loop?)

[Florian Mickler]

On Tue, 2 Mar 2010 09:32:57 -0800
Jamey Sharp <jamey at minilop.net> wrote:

> On Tue, Mar 2, 2010 at 4:37 AM, Stephan Raue <mailinglists at openelec.tv> wrote:
> > i have problems running an Application that depends on Mesa. It seems there
> > is an loop after starting this App and before the GUI loads. I use
> 
> A loop? Or just a hang?
> 
> > #1  0xb5e47fb6 in *__GI___poll (fds=0xb5ec7ff4, nfds=1, timeout=-1) at
> > ../sysdeps/unix/sysv/linux/poll.c:87
> > #2  0xb5d5d268 in _xcb_conn_wait (c=0x9571ca0, cond=0xbf9dbbe0, vector=0x0,
> > count=0x0) at xcb_conn.c:306
> > #3  0xb5d5ee09 in xcb_wait_for_reply (c=0x9571ca0, request=30, e=0xbf9dbc6c)
> > at xcb_in.c:390
> 
> Judging only by the stack trace, it looks like your application is
> waiting for a reply that never comes. There are a variety of bugs that
> can cause that. The sequence number (30) looks reasonable for
> application startup, which rules out one or two things.
> 
> For the rest, if the Intel/Mesa folks don't have an answer, it would
> help if you could get a trace of the X wire protocol using something
> like Wireshark.
> 
> Jamey
> _______________________________________________
> xorg-devel mailing list
> xorg-devel at lists.x.org
> http://lists.x.org/mailman/listinfo/xorg-devel



i'm seeing the same with glxgears, see below for a gdb run...

if i login glxgears runs fine, until i start up some programs (licq,
psi, twinkle, skype)... then it hangs sometimes and doesnt redraw the
screen anymore. if i start it after that point it never draws...

seems to me, like some event goes missing somewhere... ? 

anyway, i'm on amd64 with intel from git, using the new event-driven
invalidate stuff...

what debugging would be helpful here? dmesg doesn't show anything
(abnormal) with kernel drm.debug=1 ...

cheers,
Flo

p.s.: i verified with strace that it hangs on that poll... 


(gdb) r
Starting program: /usr/bin/glxgears 
[Thread debugging using libthread_db enabled]
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
^C
Program received signal SIGINT, Interrupt.
0x00007ffff766410f in poll () from /lib/libc.so.6
(gdb) bt
#0  0x00007ffff766410f in poll () from /lib/libc.so.6
#1  0x00007ffff6219a32 in _xcb_conn_wait () from /usr/lib/libxcb.so.1
#2  0x00007ffff621b5e1 in xcb_wait_for_reply () from /usr/lib/libxcb.so.1
#3  0x00007ffff72c00be in _XReply () from /usr/lib/libX11.so.6
#4  0x00007ffff7bbe996 in DRI2GetBuffersWithFormat ()
   from //usr/lib64/opengl/xorg-x11/lib/libGL.so.1
#5  0x00007ffff7bbd6c8 in dri2GetBuffersWithFormat ()
   from //usr/lib64/opengl/xorg-x11/lib/libGL.so.1
#6  0x00007ffff5780cef in intel_update_renderbuffers ()
   from /usr/lib64/dri/i965_dri.so
#7  0x00007ffff57810b7 in intel_prepare_render ()
   from /usr/lib64/dri/i965_dri.so
#8  0x00007ffff57af15a in brw_draw_prims () from /usr/lib64/dri/i965_dri.so
#9  0x00007ffff5857383 in vbo_exec_DrawArrays ()
   from /usr/lib64/dri/i965_dri.so
#10 0x00007ffff58d2987 in _mesa_meta_Clear () from /usr/lib64/dri/i965_dri.so
#11 0x00007ffff577fccb in intelClear () from /usr/lib64/dri/i965_dri.so
#12 0x0000000000402be6 in draw ()
#13 0x000000000040360b in main ()
(gdb)