Created attachment 27669 [details]
corrupt.png

Created attachment 27670 [details]
Screenshot.png

Created attachment 27671 [details]
Xorg.0.log

Created attachment 27672 [details]
Xorg.0.log.old

00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02)
	Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:3106]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02)
	Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:3106]

Thanks for reporting this over here, Bryce.  Note that I originally saw various corruption on a 965 and lately I have seen it on a G31, if that makes a difference.

Thanks for the bug report Jeffrey,

As for the two different chipsets, the 965 and G31 belong to the same family of harware, (and no, the naming rarely makes that obvious), so it's not too surprising that the behave similarly.

As for the corruption shown in the screenshots, the two effects look quite distinct so likely have different underlying causes. The font corruption looks a lot like a bug that was fixed in the kernel as of the commit below, (which should have first appeared in 2.6.30-rc8 and subsequently in 2.6.31). The attached X.org.log file shows kernel 2.6.31 so hopefully that commit is in place.

It might be worth attempting to boot with a different kernel, (say vanilla 2.6.31 or so), to see if that results in anything different.

-Carl

commit 07f4f3e8a24138ca2f3650723d670df25687cd05
Author: Kristian Høgsberg <krh@redhat.com>
Date:   Wed May 27 14:37:28 2009 -0400

    i915: Set object to gtt domain when faulting it back in
    
    When a GEM object is evicted from the GTT we set it to the CPU domain,
    as it might get swapped in and out or ever mmapped regularly.  If the
    object is mmapped through the GTT it can still get evicted in this way
    by other objects requiring GTT space.  When the GTT mapping is touched
    again we fault it back into the GTT, but fail to set it back to the
    GTT domain.  This means we fail to flush any cached CPU writes to the
    pages backing the object which will then happen "eventually", typically
    after we write to the page through the uncached GTT mapping.
    
    [anholt: Note that userland does do a set_domain(GTT, GTT) when starting
    to access the GTT mapping.  That covers getting the existing mapping of the
    object synchronized if it's bound to the GTT.  But set_domain(GTT, GTT)
    doesn't do anything if the object is currently unbound.  This fix covers the
    transition to being bound for GTT mapping.]
    
    Fixes glyph and other pixmap corruption during swapping.  fd.o bug #21790
    
    Signed-off-by: Kristian Høgsberg <krh@redhat.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>

And we've also fixed a few missing cache flushes which may also be significant:

commit 9a2c18fb92659d57741bfdcacbe4f69aab361532
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Sun Nov 29 21:07:45 2009 +0000

    batch: Emit a 'pipelined' flush when using a dirty source.
    
    Ensure that the render caches and texture caches are appropriately
    flushed when switching a pixmap from a target to a source.
    
    This should fix bug 24315,
      [855GM] Rendering corruption in text (usually)
      https://bugs.freedesktop.org/show_bug.cgi?id=24315

Is this bug still reproducible after these fixes? Thanks.

Created attachment 33885 [details]
screenshot with ugly font corruption

This bug still occures when using the following versions:

mesa-7.5.2
xorg-server 1.7.5
intel driver svn build (2010-03-06)
drm-intel kernel svn build (2010-03-06)

This bug only occures after a suspend / resume cycle. I also attached a screenshot with red rectangles around two corruption sections.

Ok, I am wondering if the memory corruption with i915 suspend fixed by Linus in 2.6.35-rc6 is a critical factor here. Please can you try the latest bits.

Hello,

I have similar issues with Intel Integrated graphics. For me the drawing problems first occured when I switched from an old 19" to a new 24" screen, using 1900x1200 resolution. I am using Arch Linux, which means I have a newer kernel:
$ uname -a
Linux abpc1154 2.6.38-ARCH #1 SMP PREEMPT Fri May 13 09:24:47 CEST 2011 x86_64 Intel(R) Pentium(R) D CPU 3.40GHz GenuineIntel GNU/Linux

From lspci:
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)

I first reported it as a kwin bug since I did not know where to go with the information, you can find that report here:
https://bugs.kde.org/show_bug.cgi?id=272412

Please let me know if this is the same bug or if I should open a new report (or look further if it is reported elsewhere). Please also let me know if you need further information. Thanks.

Mass status change to NEEDINFO based on presence of NEEDINFO keyword. Please reopen if you can still reproduce the bug and are able to provide the information requested, thanks.

Timeout. Please do reopen if you can still reproduce the issue and help us diagnose the problem, thanks.