All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105910] Graphical artifacts on unresposible surfaces on AMD Radeon RX 570
Date: Thu, 05 Apr 2018 18:51:40 +0000	[thread overview]
Message-ID: <bug-105910-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 105910
           Summary: Graphical artifacts on unresposible surfaces on AMD
                    Radeon RX 570
           Product: Mesa
           Version: 17.3
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: nb@chebykin.org
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 138627
  --> https://bugs.freedesktop.org/attachment.cgi?id=138627&action=edit
Example of artifacts

Hello,

I want to report some graphical artifacts with AMD Radeon RX 570 card.

I've been noticing some random artifacts when I open/resize/close windows.
I was able to narrow down this problem to mesa surfaces updating. For instance
if i suspend program with such surface and try to resize it, I will see these
artifacts. So I think there is a moment between receiving resize event and
updating surface when driver somehow render those artifacts.

I'm using Arch Linux with i3, but I was able to reproduce this bug on wayland
by resizing alacritty terminal emulator.

Versions:
Kernel:

4.15.14-1-ARCH

Mesa:

libva-mesa-driver 17.3.7-1
mesa 17.3.7-1
mesa-vdpau 17.3.7-1
xf86-video-amdgpu 18.0.1-1

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

[-- Attachment #1.2: Type: text/html, Size: 3010 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:[~2018-04-05 18:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 18:51 bugzilla-daemon [this message]
2018-04-05 18:52 ` [Bug 105910] Graphical artifacts on unresposible surfaces on AMD Radeon RX 570 bugzilla-daemon
2018-04-05 18:53 ` bugzilla-daemon
2018-04-05 18:53 ` bugzilla-daemon
2018-04-05 18:53 ` bugzilla-daemon
2018-04-05 18:54 ` bugzilla-daemon
2018-04-05 19:00 ` [Bug 105910] Graphical artifacts on unresponsible " bugzilla-daemon
2018-05-07 11:14 ` bugzilla-daemon
2018-05-07 11:16 ` bugzilla-daemon
2018-05-15 13:22 ` bugzilla-daemon
2018-12-25 15:36 ` bugzilla-daemon
2018-12-28 17:00 ` bugzilla-daemon
2018-12-28 17:17 ` bugzilla-daemon
2019-01-04 17:29 ` 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-105910-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.