Bug 501713 - Firefox font corruption after suspend/resume.
Summary: Firefox font corruption after suspend/resume.
Keywords:
Status: CLOSED DUPLICATE of bug 495323
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-20 13:21 UTC by Byron Clark
Modified: 2009-05-20 18:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-20 18:32:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screenshot showing font corruption on planet.gnome.org (207.85 KB, image/png)
2009-05-20 13:21 UTC, Byron Clark
no flags Details

Description Byron Clark 2009-05-20 13:21:06 UTC
Created attachment 344798 [details]
screenshot showing font corruption on planet.gnome.org

Description of problem:
After a suspend/resume cycle, some glyphs in Firefox are corrupted (see attached screenshot).  Happens when opening new pages or even after restarting Firefox.  

Version-Release number of selected component (if applicable):
kernel-2.6.29.3-140.fc11.x86_64
mesa-dri-drivers-7.5-0.14.fc11.x86_64
xorg-x11-drv-intel-2.7.0-4.fc11.x86_64
libdrm-2.4.6-6.fc11.x86_64


How reproducible:
Not every page visited will display the corrupted glyphs, but some will.

Steps to Reproduce:
1. Suspend
2. Resume
3. View web pages from Firefox.


Additional info:
These messages appeared in dmesg around the time the corruption started:
[drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
[drm:i915_gem_object_pin] *ERROR* Failure to bind: -12
[drm:i915_gem_evict_something] *ERROR* inactive empty 1 request empty 1 flushing empty 1

Comment 1 Byron Clark 2009-05-20 14:25:02 UTC
Using KMS and UXA.

Comment 2 Kristian Høgsberg 2009-05-20 18:32:50 UTC

*** This bug has been marked as a duplicate of bug 495323 ***


Note You need to log in before you can comment on or make changes to this bug.