Bug#464353: How can we provide more info ?

2008-03-23 Thread Julien Cristau
On Sun, Mar 23, 2008 at 00:46:24 +0100, Michel Dänzer wrote: They look good to me. Can you push them upstream yourself? Pushed, thanks! Cheers, Julien

Bug#464353: How can we provide more info ?

2008-03-22 Thread Julien Cristau
On Thu, Mar 20, 2008 at 11:53:37 +0100, Michel Dänzer wrote: On Wed, 2008-03-19 at 22:13 +0100, Julien Cristau wrote: from hw/xfree86/exa/examodule.c: if (xf86IsOptionSet(pScreenPriv-options, EXAOPT_NO_COMPOSITE)) { xf86DrvMsg(pScreen-myNum, X_INFO, EXA:

Bug#464353: How can we provide more info ?

2008-03-22 Thread Michel Dänzer
On Sat, 2008-03-22 at 17:55 +0100, Julien Cristau wrote: On Thu, Mar 20, 2008 at 11:53:37 +0100, Michel Dänzer wrote: On Wed, 2008-03-19 at 22:13 +0100, Julien Cristau wrote: from hw/xfree86/exa/examodule.c: if (xf86IsOptionSet(pScreenPriv-options, EXAOPT_NO_COMPOSITE)) {

Bug#464353: How can we provide more info ?

2008-03-20 Thread Michel Dänzer
On Wed, 2008-03-19 at 22:13 +0100, Julien Cristau wrote: On Wed, Mar 19, 2008 at 21:37:56 +0100, Apelete Seketeli wrote: On Wed, Mar 19, 2008 at 6:33 PM, Michel Dänzer [EMAIL PROTECTED] wrote: (and using ExaNoComposite falsedoes improve compositing if you use MigrationHeuristic

Bug#464353: How can we provide more info ?

2008-03-19 Thread Michel Dänzer
On Sat, 2008-03-15 at 23:30 +0100, Apelete Seketeli wrote: I have tried some more options in order to enable video playing with Metacity's compositing effects (which boils down to re-enable EXA). I have found that if I use EXA with the option MigrationHeuristic greedy, xserver does not hang

Bug#464353: How can we provide more info ?

2008-03-19 Thread Apelete Seketeli
On Wed, Mar 19, 2008 at 6:33 PM, Michel Dänzer [EMAIL PROTECTED] wrote: (and using ExaNoComposite falsedoes improve compositing if you use MigrationHeuristic greedy, but that's out of subject). That's the default, so it shouldn't make any difference... It's indeed written in EXA man

Bug#464353: How can we provide more info ?

2008-03-19 Thread Julien Cristau
On Wed, Mar 19, 2008 at 21:37:56 +0100, Apelete Seketeli wrote: On Wed, Mar 19, 2008 at 6:33 PM, Michel Dänzer [EMAIL PROTECTED] wrote: (and using ExaNoComposite falsedoes improve compositing if you use MigrationHeuristic greedy, but that's out of subject). That's the default, so

Bug#464353: How can we provide more info ?

2008-03-15 Thread Apelete Seketeli
Hello, I tried Option AccelMethod XAA and didn't experience a single crash with it (even with using an external monitor on my laptop). It seems that EXA is definitely the source of the current intel driver instability. Metacity 2.22 just landed in the Debian unstable repos, and I noticed that

Bug#464353: How can we provide more info ?

2008-03-15 Thread Apelete Seketeli
Hello, I tried Option AccelMethod XAA and the didn't experience a single crash with it (even with using an external monitor on my laptop). It seems that EXA is definitely the source of the current intel driver instability. Metacity 2.22 just landed in the Debian unstable repos, and I noticed

Bug#464353: How can we provide more info ?

2008-03-15 Thread Apelete Seketeli
I have tried some more options in order to enable video playing with Metacity's compositing effects (which boils down to re-enable EXA). I have found that if I use EXA with the option MigrationHeuristic greedy, xserver does not hang anymore (and using ExaNoComposite falsedoes improve compositing

Bug#464353: How can we provide more info ?

2008-02-28 Thread Apelete Seketeli
Package: xserver-xorg-video-intel Version: 2:2.2.1-1 Followup-For: Bug #464353 Hi, I was reading some bugs reports before posting this one, and I came to the conclusion that many people were experiencing Xserver lock-ups with the same message showing up at some point in the log files: Error in

Bug#464353: How can we provide more info ?

2008-02-28 Thread Brice Goglin
Apelete Seketeli wrote: Package: xserver-xorg-video-intel Version: 2:2.2.1-1 Followup-For: Bug #464353 Hi, I was reading some bugs reports before posting this one, and I came to the conclusion that many people were experiencing Xserver lock-ups with the same message showing up at some