Bug 13456

The mentioned display corruption with EXA disappears completely after running glxdemo or glxgears and restarting X, as long as the pc isn't shut down.

Jos van Wolput

The mentioned display corruption with EXA disappears completely after running glxdemo or glxgears and restarting X, as long as the pc isn't shut down.

Jos van Wolput

Does EXA ever work correctly on these machines? I mean does it work before or with current upstream master?

It looks people are having problem with 855GM and 965 desktop and laptop, which all work fine here, although I use master branches.

How about try with Option "Tiling" "FALSE"?

(In reply to comment #4)
> How about try with Option "Tiling" "FALSE"?
> 
 
Doesn't make any difference!

(In reply to comment #3)
> Does EXA ever work correctly on these machines? I mean does it work before or
> with current upstream master?
> 
> It looks people are having problem with 855GM and 965 desktop and laptop, which
> all work fine here, although I use master branches.
>
 
EXA never worked correctly since I first tried it with Debian's v. 2.0.0 of  xserver-xorg-video-intel half a year ago. It only works after running
something like glxdemo or another app from /usr/share/mesademos/progs/xdemos.
I am using Debian (unstable) on a 855GM laptop.

(In reply to comment #6)
> EXA never worked correctly since I first tried it with Debian's v. 2.0.0 of 
> xserver-xorg-video-intel half a year ago. It only works after running
> something like glxdemo or another app from /usr/share/mesademos/progs/xdemos.
> I am using Debian (unstable) on a 855GM laptop.
> 

What's your 855gm model? I just can't reproduce this on hp nx5000 as noted on
bug 11402.

So is it issue with current exa rendering state init on 855gm that may be fixed after some mesa apps run?

Could you first try Option "EXANoComposite" "TRUE" to see if thing goes fine?

(In reply to comment #7)
> 
> What's your 855gm model? 
>
 
It 's a Jewel Topaz 9600 (dutch brand), made in China by Uniwill, type 223ii0
 
> 
> Could you first try Option "EXANoComposite" "TRUE" to see if thing goes fine?
> 

No more problems with Option "EXANoComposite" "TRUE", only RENDER acceleration disabled.

I took a few screenshots of my system, available here:
  http://www.dannf.org/bugs/451791/

The first shows a gdm login screen where I've typed a few characters. The cursor moves forward, but I see no text appear.

The next two show the screen right after login. The corruption in the center of the screen is where the GNOME splash screen should be. Also, the top panel normally contains the normal GNOME menu pulldowns (Applications, Places, System) and a few other icons, but with this issue I only see the battery charge monitor. I can click where the other components *should* be, and they still respond - though not correctly (no text in the menus, etc).

I'm successfully working around the issue by using:
  Option "AccelMethod" "XAA"

(In reply to comment #8)
> No more problems with Option "EXANoComposite" "TRUE", only RENDER acceleration
> disabled.

No, render should not be disabled, just composite operation fall back.
You mean if you add EXANoComposite in xorg.conf, then there's no more rendering failure you've seen, right? So there must be some place which doesn't get initialized correctly..

(In reply to comment #9)
> I took a few screenshots of my system, available here:
>   http://www.dannf.org/bugs/451791/

What's your chipset please?
 
> I'm successfully working around the issue by using:
>   Option "AccelMethod" "XAA"
>
how about "EXANoComposite" "TRUE"?

(In reply to comment #10)
> No, render should not be disabled, just composite operation fall back.
render is not disabled, only render acceleration.
From Xorg.0.log:
(**) Extension "RENDER" is enabled
(**) intel(0): Option "EXANoComposite" "TRUE"
(II) intel(0): EXA: Disabling Composite operation (RENDER acceleration)

> You mean if you add EXANoComposite in xorg.conf, then there's no more rendering
> failure you've seen, right? So there must be some place which doesn't get
> initialized correctly..
Correct, no more rendering failure after adding Option "EXANoComposite" "TRUE"

Created attachment 12922 [details] [review]
try to emit invarient state every time

Could you try this patch with your origin xorg.conf? I suspect some states should
always to set, but this's just for debug.

(In reply to comment #13)

> Could you try this patch with your origin xorg.conf? 

I tried the patch but it doesn't solve the problem, the rendering failure still
appears when Option "EXANoComposite" "TRUE" is NOT set!

I've tried to reproduce this on a sony VGN-T26C, I'm looking into this.

(In reply to comment #15)
> I've tried to reproduce this on a sony VGN-T26C, I'm looking into this.
> 

I did some tests with EXA options.
Setting Option "MigrationHeuristic" "greedy" (and removing "EXANoComposite") gives
a clear screen,apps look good but the Terminal (an xfce4 package) is still corrupted.
Setting to "always" or "smart" produces corrupted screen.

Created attachment 12993 [details] [review]
i830 render fix

This patch fixes exa issue on my sony 855gm. Pls test it to see if it also fixes your problems.

i830 3d more states initialized according with mesa code.

(In reply to comment #17)
 
> This patch fixes exa issue on my sony 855gm. Pls test it to see if it also
> fixes your problems.

Yes, that's it, also on my laptop no more exa render failure with your patch of i830_3d.c
Thank you very much! 谢谢您！

Thanks to verify this! 不用谢!:)

Brice, as this patch fixes for some 855gm users, I'm not sure about your copied issues on those i965s... Anyway I'll let our QA team double-check if we can reproduce or not.

I think we may close this, as it seems only affect 855gm. If you still can reproduce on some i965 boxes, pls reopen or open new bug. Thanks.

I am still waiting for some feedback of the bug reporters. So far, one i965 said he still had problems (missing fonts and icons). I'll open a new bug for this when I will have gathered enough info.