Created attachment 10484 [details]
snapshot

Created attachment 10485 [details]
log file

I forgot to mention that this is with today's git driver.

Should be fixed in current git tip.

I updated to your git commit 5faee02e97b7543b41bb1f8e3751558c48802833, but I still get exactly the same result (this is really a deterministic output). 

Could you send me your fontconfig file? My knowledge on it is limited, so may be easy to try with your config.

And what font are you using?

Created attachment 12084 [details]
/etc/fonts

Here is my /etc/fonts. This seems to happen with all fonts, Mono and Sans for instance. Just in case, here are versions:

ii  fontconfig                  2.4.2-1.2
ii  libfreetype6                2.3.5-1+b1
ii  ttf-freefont                20060501cvs-12

I have tried to enable all fonts with antialias, but still can't see this on 855GM here. What about current intel video driver?

Still the same :/ 

what's your xserver version? And which font are you using? people reported pcf font bug with current xserver. Could you test with current stable xserver-1.4?

Created attachment 12579 [details] [review]
log file

Here is the log file. This is the xserver 1.4 package from debian.  As said previously, this seems to happen with all fonts (I haven't tried the hundreds I have, but a couple of dozens from various packages have the issue). Mono and Sans for instance.

Created attachment 12581 [details]
AA font on my 855GM

Created attachment 12582 [details]
Non-AA font on my 855GM

Here's my two window dumps on my 855GM. The first is from "xterm -fa mono" window, and the second is plain xterm window.

I have upgraded components to master, it seems working fine...so how about your pixman version? we've seen pixman brokenness cause render failure before, not sure
if it's relevant.

my pixman is the debian package version 0.9.5-3 

I upgraded the xserver-xorg-core package to the recent 2:1.4.1~git20071117-1 package, and now things work fine!

ok, thanks for resolving this!

Eergl, talked too fast.  This morning it's not working again, but I'm in a different screen configuration than yesterday evening, I'll dig more this evening.

For a yet unknown reason, sometimes it works (and then I can't manage to make it fail again without power cycling), sometimes it fails, and I can't find the way to make it work.

Something that may be related: when I use xrandr --rotate left or any other than normal, I get similar display corruption. This is independant of setting XAA or EXA, however.

Upgrading to libpixman 0.9.6 doesn't help

Also, the xrandr display corruption can't be dumped through import for instance.

As I can't see this on 855GM here, could you paste your current x logs?
and try to disable fbc by
Option "FramebufferCompression" "FALSE" in Device section.

Created attachment 12636 [details]
X log

I had already posted a log, but here is another one, with framebuffer compression disabled. Still produces bogus AA fonts.

Created attachment 12637 [details]
configuration file

I realize that I haven't posted my xorg.conf, here it is.

Could this bug be related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451893 ? These guys get no font at all when EXA is enabled.

On my HP 855GM, I've upgraded to sid with xserver-xorg-core 2:1.4.1~git20071119-1, and intel driver version 2.2.0. Fonts are all ok with me. I've tried to reboot many times, but no broken has been seen.

older xorg-core 2:1.4-3 also works.

it seems we have to mark it as worksforme..

Interestingly, the screenshot from bug #13367 looks very similar to the one here, and it's still reproducible.  Maybe something is wrong with how we do render accel save/restore on 8xx...

Jesse, S3 with X works great on my HP compaq nx5000. just echo "mem" > /sys/power/state, I can't see any render broken after resume.

reproduced on one sony vaio, i'll look into this.

Fix patch available on bug #13456

A quick test showed no problem, I'll keep testing next week, and hope hence be able to mark this as "verified"! 

No problem any more.