Problem using an Mesa based App with recent xorg/mesa/xf86-video-intel (loop?)
jbarnes at virtuousgeek.org
Tue Mar 2 13:59:00 PST 2010
On Tue, 2 Mar 2010 22:48:31 +0100
Florian Mickler <florian at mickler.org> wrote:
> On Tue, 2 Mar 2010 11:50:05 -0800
> Jesse Barnes <jbarnes at virtuousgeek.org> wrote:
> > So the server is hanging when the client tries to get buffers? Can
> > you see what it's doing at the time?
> i'll try tomorrow...
> meanwhile, i watched a film and did some other things and now glxgears
> doesn't start anymore:
> dmk at schatten ~ $glxgears
> Mesa: Mesa 7.8-devel DEBUG build Mar 2 2010 19:57:41
> Mesa warning: couldn't open libtxc_dxtn.so, software DXTn
> compression/decompression unavailable Mesa: Initializing x86-64
> optimizations Running synchronized to the vertical refresh. The
> framerate should be approximately 1/8504368 the monitor refresh rate.
> X Error of failed request: BadDrawable (invalid Pixmap or Window
> parameter) Major opcode of failed request: 133 (DRI2)
> Minor opcode of failed request: 8 (DRI2SwapBuffers )
> Resource id in failed request: 0x1c00002
> Serial number of failed request: 32
> Current serial number in output stream: 32
> does this 1/[bignumber] look alright? maybe that is the culprit...
> waiting some 10^6 time ... i think the monitor refresh rate is
> something about 60 hz? not over some khz? which means that
> 1khz/8504368 is something about 1/8500 hz which amounts to about 140
> secs? (it is late and i may have switched nominater and denominator a
> bit too often... but if i don't have crossed anything, than that could
> cause some hang... don't it?)
I don't know how gears calculates that these days, but it generally
looks wrong for me too.
Author: Eric Anholt <eric at anholt.net>
Date: Wed Feb 24 17:54:13 2010 -0800
In frame event handling, track drawable id instead of drawable
in your xf86-video-intel tree?
Jesse Barnes, Intel Open Source Technology Center
More information about the xorg-devel