All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107334] Artifacts in Unigine Valley with RX 580
Date: Mon, 22 Oct 2018 21:26:12 +0000	[thread overview]
Message-ID: <bug-107334-502-t2ER81sx0B@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107334-502@http.bugs.freedesktop.org/>


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

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

--- Comment #8 from Christian Widmer <cwidmer@umbrox.de> ---
I took the recently released kernel 4.19 as an incentive to test this again and
it looks like the issue is gone. I do, however, not know if it is indeed the
new kernel driver part or a mesa/LLVM update that happened in the meantime (I
did not test it after every update).

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

[-- Attachment #1.2: Type: text/html, Size: 1256 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

  parent reply	other threads:[~2018-10-22 21:26 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
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 [this message]
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-t2ER81sx0B@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.