From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107334] Artifacts in Unigine Valley with RX 580
Date: Sun, 29 Jul 2018 19:27:31 +0000 [thread overview]
Message-ID: <bug-107334-502-OXUkU0GmmS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107334-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 529 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107334
--- Comment #1 from Christian Widmer <cwidmer@umbrox.de> ---
This is actually a regression. Bisecting identified commit
60299e9abe8513b36fe7979fbf36a99e4070e8d1 (radeonsi: don't emit partial flushes
for internal CS flushes only) as the one introducing the issue. And reverting
that commit in current master (0ddae4acae08cc6b216c49f85c6ffb969dea0969) does
indeed make the artifacts go away.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1294 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
next prev parent reply other threads:[~2018-07-29 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 12:59 [Bug 107334] Artifacts in Unigine Valley with RX 580 bugzilla-daemon
2018-07-29 19:27 ` bugzilla-daemon [this message]
2018-08-01 13:47 ` bugzilla-daemon
2018-08-01 13:48 ` bugzilla-daemon
2018-08-01 13:48 ` bugzilla-daemon
2018-09-20 4:50 ` bugzilla-daemon
2018-09-20 4:51 ` bugzilla-daemon
2018-09-20 8:58 ` bugzilla-daemon
2018-09-20 20:36 ` bugzilla-daemon
2018-10-22 21:26 ` bugzilla-daemon
2018-10-23 8:30 ` bugzilla-daemon
2018-10-29 20:46 ` 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-107334-502-OXUkU0GmmS@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox