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 <[EMAIL PROTECTED]> > Date: Mon Jan 28 13:09:55 2008 +0100 > > R5xx accel: Add XAA support. > > MMIO path only, no CP support yet. > > :040000 040000 200a88e434a3e1b1b7dfdfe9007ac063f7c7e7d2 > eca764300b61c65c03417800e9dd8fe5eb7f5219 M src > > 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
