Bug 20521 - [UXA] font glyph and pixmap corruption after a period of time
Summary: [UXA] font glyph and pixmap corruption after a period of time
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Eric Anholt
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-07 03:40 UTC by Anand Kumria
Modified: 2009-07-02 11:21 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
screenshot of glyph corruption (573.87 KB, image/png)
2009-03-07 03:40 UTC, Anand Kumria
no flags Details
Xorg.0.log (66.89 KB, text/x-log)
2009-03-09 06:08 UTC, Anand Kumria
no flags Details
Xorg.0.log when uxa is commented out (25.00 KB, text/x-log)
2009-03-09 07:17 UTC, Anand Kumria
no flags Details
glyph-cache.png (66.21 KB, image/png)
2009-06-08 03:38 UTC, Christoph Brill
no flags Details

Description Anand Kumria 2009-03-07 03:40:32 UTC
Created attachment 23624 [details]
screenshot of glyph corruption

Hi,

I am experiencing significant glyph corruption when using the newest versions of X, the kernel and other libraries. The corruption does not immediately occur.

I have to be using the system for approximately 15 minutes before I see the first artifacts (typically shearing) and after an hour or so I get the kind of screen that is attached in the screenshot.

Environment:

anand@eve[~]% uname -a
Linux eve 2.6.29-020629rc6-generic #020629rc6 SMP Mon Feb 23 12:53:58 UTC 2009 i686 GNU/Linux

This is 2.6.29rc6 as packaged by Ubuntu.

anand@eve[~]% dpkg -l | grep xorg
ii  xorg                                         1:7.4~5ubuntu13                   X.Org X Window System
ii  xserver-xorg                                 1:7.4~5ubuntu13                   the X.Org X server
ii  xserver-xorg-core                            2:1.6.0-0ubuntu1                  Xorg X server - core server
ii  xserver-xorg-input-evdev                     1:2.1.1-1ubuntu3                  X.Org X server -- evdev input driver
ii  xserver-xorg-input-synaptics                 0.99.3-2ubuntu3                   Synaptics TouchPad driver for X.Org/XFree86 server
ii  xserver-xorg-video-all                       1:7.4~5ubuntu13                   the X.Org X server -- output driver metapackage
[...]
ii  xserver-xorg-video-fbdev                     1:0.4.0-3                         X.Org X server -- fbdev display driver
ii  xserver-xorg-video-i128                      1:1.3.1-2                         X.Org X server -- i128 display driver
ii  xserver-xorg-video-i740                      1:1.2.0-2                         X.Org X server -- i740 display driver
ii  xserver-xorg-video-intel                     2:2.6.1-1ubuntu4                  X.Org X server -- Intel i8xx, i9xx display driver
[...]
anand@eve[~]% 

I have an "older" device:

anand@eve[~]% lspci
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

anand@eve[~]% cat /etc/X11/xorg.conf | grep -v "^#"

Section "Device"
	Identifier	"Configured Video Device"
	Option		"UseFBDev"		"true"
    Option      "AccelMethod"   "uxa"
EndSection

Section "Monitor"
	Identifier	"Configured Monitor"
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Monitor		"Configured Monitor"
	Device		"Configured Video Device"
EndSection
Comment 1 Gordon Jin 2009-03-07 04:46:35 UTC
Does this happen without uxa set?

Please attach Xorg.0.log.
Comment 2 Anand Kumria 2009-03-09 06:08:06 UTC
Created attachment 23690 [details]
Xorg.0.log

Attached the Xorg.0.log as requested.
Comment 3 Anand Kumria 2009-03-09 07:17:14 UTC
Commenting out 'Option      "AccelMethod"   "uxa"' results in X not being able to startup correctly.

I get dumped into Ubuntu 'low-graphics' system.

The reason is:

(EE) intel(0): Failed ot pin front buffer: Cannot allocate memory.

I have attached the Xorg.0.log for when the configuration looks like:

anand@eve:~$ grep -v "^#" /etc/X11/xorg.conf 

Section "Device"
	Identifier	"Configured Video Device"
	Option		"UseFBDev"		"true"
EndSection

Section "Monitor"
	Identifier	"Configured Monitor"
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Monitor		"Configured Monitor"
	Device		"Configured Video Device"
EndSection

Comment 4 Anand Kumria 2009-03-09 07:17:57 UTC
Created attachment 23692 [details]
Xorg.0.log when uxa is commented out

Xorg.0.log when uxa is commented out.
Comment 5 Michal Suchanek 2009-05-04 06:17:06 UTC
I have similar problem on i945G.

After some time I get blurry squares instead of some letters in my terminals (rxvt-unicode, truetype fonts). The corruption is not limited to a particular terminal, all terminals seem to be affected in the same way, and they are separate processes (not the hydra-like server process).

I am running UXA as XAA crashes on startup and EXA tends to lock up on this hardware.
Comment 6 Christoph Brill 2009-06-08 03:38:17 UTC
Created attachment 26529 [details]
glyph-cache.png

The same happens with UXA on my "Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)" with xf86-video-intel 2.7.1, mesa 7.5_rc3, libdrm 2.4.11 and X.org 1.6.1.901.

It seems to happen often with lasge subpixel hinted fonts, something like 14-16 pt, but only at that specific size. Larger and smaller fonts are not affected (at least for me).
Comment 7 Christoph Brill 2009-06-08 03:39:53 UTC
One addition: Italic text more commonly seems to trigger the issue.
Comment 8 Michal Suchanek 2009-06-08 04:00:45 UTC
To me this seems like a general pixmap corruption that is more likely to manifest on fonts.

For some reason fonts used in gkrellm are not affected - perhaps they are rendered in different way than what Firefox and urxvt. does.

Uncommon font sizes (like very large or very small) are probably not affected because they are not chaced and have to be freshly re-rendered. In one case I was able to completely clear the terminal corruption by invoking the visual bell feature.

It is not only fonts what is corrupted. Sometimes images in Firefox (both HTML and XUL) or the xscreensaver logo would get corrupted by horizontal lines in toolkit background color or some garbage.

The letters in the affected fonts sometimes seem incomplete or partially replaced by something different, sometimes replaced completely with garbage or a letter from a different font.
Comment 9 Christoph Brill 2009-06-08 11:18:57 UTC
I have to agree. Some icons in eclipse were corrupted, too. So it's not limited to font glyphs.
Comment 10 Michal Suchanek 2009-06-09 02:33:04 UTC
Updating summary accordingly.
Comment 11 Eric Anholt 2009-07-02 11:21:32 UTC
This should have been fixed by:

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

in 2.6.30.  Please reopen if retesting with 2.6.30 release continues to show this bug.


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.