Bug#529830: git bisecting

[Adrian Knoth]

On Tue, Jun 02, 2009 at 06:54:44PM +0200, I wrote:

> > > It's a HP nx6325 laptop with ATI xpress 200M (RS482).
> > Any chance you could use git bisect to track down what changes in the
> > radeon driver caused the problem?
> 
> adi at chopin:~/xserver-xorg-video-ati$ git bisect good
> b6cd47ec007af2022af180f537a7ba01244b2c88 is first bad commit
> commit b6cd47ec007af2022af180f537a7ba01244b2c88
> Author: Alex Deucher <alexdeucher at gmail.com>
> Date:   Fri May 8 12:21:33 2009 -0400
> 
>     AVIVO: fix cursor corruption bands for real
>     
>     Don't have to leave both cursors enabled, just have to use
>     the same mode for both cursors whether or not they are enabled.
> 
> :040000 040000 9434b74a8329bf6cd6c076fe512a333834641e99 e2bfdc6168042c7a1a6ef14b60ded5c6655fda77 M      src

The "git bisect good" was probably too early. I'm still getting freezes,
so it's easy to say when a revision is "bad", but even five successful
resumes in a row are not enough to call it "good".

IOW: It takes some time for testing, and in the meantime, the accused
commit mentioned above isn't probably the culprit.


Sorry for not testing it enough in the first place.


-- 
mail: adi at thur.de  	http://adi.thur.de	PGP/GPG: key via keyserver