On Mon, Jan 17, 2011 at 10:00 AM, Corbin Simpson <mostawesomed...@gmail.com> wrote: > On Mon, Jan 17, 2011 at 1:11 AM, Dave Airlie <airl...@gmail.com> wrote: >> >> Results: (5231 of 5344 passed, 3 timed out) >> >> This was with the latest Intel mesa driver on an Ironlake laptop. >> >> However I got a random crash on a previous run, I'm guessing if we can >> figure out the misc crasher we'd be in a lot better place. > > I already started working on this. (A friend just got hired by Moz and > I owe him one.) > > Basic analysis: The crash is in the Mesa-side DRI2 handler for > flushing the frontbuffer. There's a segfault of very weird > composition. The BT (which I can get if needed) goes back to > glXMakeCurrent, and it looks like glXMakeCurrent is unbinding the > current context, which is calling the DRI2 unbind callbacks, which > calls frontbuffer flush, but part of the DRI2 context is screwy and we > get a segfault. > > There's a couple problems though. The frontbuffer flush usually isn't > fatal; it only kills us about one in five times. Sometimes it dies on > the very first test, sometimes it dies halfway through the suite. > There's no rhyme or reason to it. > > If you've got any ideas, I'm open to them. I bugged Kristian and he had no > idea. >
Sounds like this bug: https://bugs.freedesktop.org/show_bug.cgi?id=31940 Alex > -- > When the facts change, I change my mind. What do you do, sir? ~ Keynes > > Corbin Simpson > <mostawesomed...@gmail.com> > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/mesa-dev > _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
