http://bugs.freedesktop.org/show_bug.cgi?id=26051
--- Comment #9 from Michel Dänzer <mic...@daenzer.net> 2010-01-26 02:44:35 PST --- (In reply to comment #8) > The problem (specifically, glxgears locks up before showing any gear wheels) > still exists in HEAD from last Friday > (124a6b1958c630ea049025e2b72547096fdc8f2c). 'HEAD' in Git refers to the most recent commit of the currently checked out branch. 124a6b1958c630ea049025e2b72547096fdc8f2c is a rather old (June/July 2009) commit from the master branch. > 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) It has nothing to do with CVS. A merge in Git is simply the folding of the histories of several branches into a single one. Looking at the commit in question in gitk or another GUI frontend may help visualize this. > is not nice for those of us asked to bisect. Please try if the problem occurs with either of the parent commits of the merge commit. (Although the fact that git bisect identified the merge commit as the first bad one indicates that you already did in the course of the bisection, and neither of them had the problem) > 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). AFAICT that change is still in the current master branch. I suspect 'HEAD' doesn't mean what you thought. (As you don't seem to feel very comfortable with Git yet, it may be a good idea to run 'git status' frequently to verify the current state matches your expectation) > 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. This commit is Gallium specific and irrelevant for this problem. > What I really don't get is that neither of these commits are for r200 The former commit could be relevant, though it probably couldn't cause the problem itself but merely trigger it by making glxgears choose a different visual. If you can confirm that reverting this commit avoids the problem, please attach the glxinfo output from with and without the commit. > This is all on linux-2.6.32.2 - maybe I should upgrade that before > trying to get any further into this mess ? Shouldn't hurt, but don't expect any miracles. -- 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
