All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95413] Oversaturation + Artifacts on screen refresh with Redwood GPU
Date: Sun, 15 May 2016 21:52:55 +0000	[thread overview]
Message-ID: <bug-95413-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1704 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=95413

            Bug ID: 95413
           Summary: Oversaturation + Artifacts on screen refresh with
                    Redwood GPU
           Product: Mesa
           Version: 11.2
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: sawyerbergeron@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

In any compositor (XRender still affected, but to lesser degree) the screen
first appears somewhat oversaturated/of too high contrast, but on each
subsequent screen redraw the entire screen becomes less and less possible to
decipher until it becomes 2 bit black and white for every part of the screen
except for the areas that were most recently refreshed (while other parts of
the screen were redrawn, even if not refreshed.)

This bug occurs in Gnome 3, Plasma (4 and 5), and Unity, though it has no
effect on non X-sessions, nor does it appear to affect login screens (sddm,
gdm, or lightdm). Sessions composited using XRender are oversaturated/have too
high a contrast and are oddly colored, but do not exhibit increasing
saturation/contrast issues on redraw. OpenGL 2/3 are worst using GXL, though
OpenGL 3 with EGL is sometimes somewhat better (though far worse than XRender.)

For a graphics card, I use a FirePro v4800 (based on Redwood XT, I believe) 

If a screenshot would help, please let me know so I can post one

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3069 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-05-15 21:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-15 21:52 bugzilla-daemon [this message]
2016-05-15 23:22 ` [Bug 95413] Oversaturation + Artifacts on screen refresh with Redwood GPU bugzilla-daemon
2016-05-16 13:28 ` bugzilla-daemon
2016-05-16 23:17 ` bugzilla-daemon
2016-05-16 23:18 ` bugzilla-daemon
2016-05-16 23:18 ` bugzilla-daemon
2016-05-16 23:18 ` bugzilla-daemon
2016-05-19 16:16 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-95413-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.