Summary: | [i965] Text corruption in some applications after several hours on Dell 1420 (regression since 2.7.1) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Bryce Harrington <bryce> | ||||||||
Component: | Driver/intel | Assignee: | Carl Worth <cworth> | ||||||||
Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
Severity: | major | ||||||||||
Priority: | high | CC: | johnlen7+freedesktop, michael.terry, nalimilan | ||||||||
Version: | 7.4 (2008.09) | Keywords: | regression | ||||||||
Hardware: | x86 (IA32) | ||||||||||
OS: | Linux (All) | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Bryce Harrington
2009-06-05 09:38:48 UTC
Created attachment 26464 [details]
text-corruption.png
Created attachment 26465 [details]
CurrentDmesg.gz
When you say "it works with 2.7.1", does it use EXA (default) or UXA? *** Bug 22113 has been marked as a duplicate of this bug. *** 1. I see the same corruption with 2.6.30rc6 X.org GIT snapshot of 26 May 2009 on both 946GZ and i965. 2. I have only noticed such issues after power saving (e.g. display turning off on desktop, or suspend to RAM on laptop), with the bitmaps getting back to normal after X.org restart. 3. The corruption appears on other bitmaps as well, not only fonts. My "works with 2.7.1" comment was with the default config. So EXA. Sorry for the bouncing bug reports, but this looks like a duplicate of bug #21790 (which you can see for more details). It was fixed with this commit to the kernel, which I believe first appeared in 2.6.30-rc8. -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> *** This bug has been marked as a duplicate of bug 21790 *** |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.