Bug 14474 - Screen artifacts on task switching and other wide-ranging screen updates
Summary: Screen artifacts on task switching and other wide-ranging screen updates
Status: RESOLVED DUPLICATE of bug 14328
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/radeonhd (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Luc Verhaegen
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-12 16:01 UTC by Sebastian Redl
Modified: 2008-02-27 08:17 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
xorg log (41.38 KB, text/plain)
2008-02-12 16:01 UTC, Sebastian Redl 		no flags Details
View All

Description Sebastian Redl 2008-02-12 16:01:43 UTC 
Created attachment 14292 [details]
xorg log

I have a R516 with two 1280x1024 LCDs connected. On task switching, visual artifacts appear for a split second on either or both of the screens. These artifacts are either other areas of the framebuffer or horizontal, black or white lines at a random vertical position. These lines, a few pixels high, push down the entire remaining content of the screen for the split second they exist, causing flickering.

This happens only when hardware acceleration (either XAA or EXA) is enabled.

Card PnPID is 7187:174B:3000.

Device section of xorg.conf:

Section "Device"
    Identifier  "The Card"
    Driver      "radeonhd"
    BusID       "PCI:1:0:0"
    Option      "XAANoOffscreenPixmaps" "true"

    Option      "monitor-VGA_1"         "Right Monitor"
    Option      "monitor-DVI-I_1/digital"       "Left Monitor"
    Option      "RROutputOrder" "DVI-I_1/digital"

    Option      "AccelMethod" "xaa"
EndSection


Xorg log is attached.
Comment 1 Egbert Eich 2008-02-27 08:17:42 UTC 
This seems to be a duplicate of Bug #14328.

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

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.