Bug#476309: bisect'ed bad commit

[Brice Goglin <Brice.Goglin@ens-lyon.org>]

forwarded 476309 https://bugs.freedesktop.org/show_bug.cgi?id=15612
thank you



Roland Lezuo wrote:
> On Sat, 2008-04-19 at 19:48 +0200, Brice Goglin wrote:
>   
>> Roland Lezuo wrote:
>>     
>>> I've double bisected the regression and I'm rather confident that the
>>> first bad commit is this one:
>>>
>>> af0c64d897f7f2288419b6e43468850e1037bb59 is first bad commit
>>> commit af0c64d897f7f2288419b6e43468850e1037bb59
>>> Author: Luc Verhaegen <libv@skynet.be>
>>> Date:   Mon Jan 28 13:09:55 2008 +0100
>>>
>>>     R5xx accel: Add XAA support.
>>>     
>>>     MMIO path only, no CP support yet.
>>>
>>> I could reliable trigger the bug by activating the screensaver. The hack
>>> running is a python based gnome-screensaver plugin written by me. The
>>> freeze occured after the screen faded out, at or shortly after the the
>>> first few seconds of the hack running. I can provide a debian package of
>>> the software if needed for testing.
>>>   
>>>       
>> And the bug still happens with latest upstream git ?
>>
>> Brice
>>
>>     
>
> Yes, it does.
>   

Ok thanks, forwarded upstream at the URL above. I would be nice if you
could subscribe to this bug report so that you can talk to the upstream
devs directly.

Brice