http://bugs.freedesktop.org/show_bug.cgi?id=26051
--- Comment #8 from ken moffat <zarniwhoo...@googlemail.com> 2010-01-25 17:08:43 PST --- The problem (specifically, glxgears locks up before showing any gear wheels) still exists in HEAD from last Friday (124a6b1958c630ea049025e2b72547096fdc8f2c). I tried git-bisect against this, again it came back to 28471cfa970702128d822c2ecbb1703eedbca245 which is a merge, and as I'm sure you already know, this usage of git (apparently, merging from cvs) is not nice for those of us asked to bisect. Some of the apparent commits in the range shown for the log from that merge seem to have wrong (SHA1?) IDs, or be missing. This time, I diffed against the "last good" commit and identified 8 commits on cgit which seem to match the commit messages. To cut a long story short, when I got back to reverting 25b492b976632269dfa3de164545d50a53c090ce |From: Michel Dänzer <daen...@vmware.com> |Date: Tue, 07 Jul 2009 11:52:35 +0000 |Subject: GLX/DRI1: Mark GLX visuals with depth != screen depth non-conformant. | |Such visuals are subject to automatic compositing in the X server, so DRI1 |can't render to them properly. I again have a working glxgears (the test includes letting the machine sit powered-off, not just a reboot - power off seems to be important). So, at this point I tried to revert it from HEAD to prove it would fix it. Problem: it has already been reverted in HEAD (and, to repeat, that still locks up - unless I mistested). At the moment, I have one other commit to try reverting : |From 71633abafc935c25da9731bab48c228ceb9b4097 Mon Sep 17 00:00:00 2001 |From: Michel Dänzer <daen...@vmware.com> |Date: Tue, 07 Jul 2009 12:49:52 +0000 |Subject: gallium: Fixes for clobbering stencil values in combined |depth/stencil textures. | |Also fix one case where a 32 bit depth value was incorrectly converted to a |combined depth/stencil value. But since my previous attempt isn't helping on HEAD, perhaps I'm doing something wrong ? At the moment I feel like the narrator in "the third policeman" (google Flann O'Brien) - I'm beginning to think I've died and gone to a place for ungood people (or even ++ungood). What I really don't get is that neither of these commits are for r200 (so, apparently I've misidentified the area) - I can understand problems in r200 hanging around because these agp cards are now old and probably not much used by people close to the leading edge. But don't people use glxgears any more ? This is all on linux-2.6.32.2 - maybe I should upgrade that before trying to get any further into this mess ? Thanks for listening. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
