From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203471] Tearing on Raven Ridge and RX560X PRIME setup even with Vsync enabled
Date: Thu, 02 May 2019 12:30:21 +0000 [thread overview]
Message-ID: <bug-203471-2300-HlWH0d66RP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203471-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203471
--- Comment #4 from Haxk20 (haxk612@gmail.com) ---
Created attachment 282585
--> https://bugzilla.kernel.org/attachment.cgi?id=282585&action=edit
Xorg log
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-02 12:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 16:30 [Bug 203471] New: Tearing on Raven Ridge and RX560X PRIME setup even with Vsync enabled bugzilla-daemon
2019-05-01 21:02 ` [Bug 203471] " bugzilla-daemon
2019-05-01 21:03 ` bugzilla-daemon
2019-05-02 8:10 ` bugzilla-daemon
2019-05-02 12:30 ` bugzilla-daemon [this message]
2019-05-02 12:31 ` bugzilla-daemon
2019-05-02 12:32 ` bugzilla-daemon
2019-05-04 15:48 ` bugzilla-daemon
2019-05-10 21:03 ` bugzilla-daemon
2019-05-13 9:16 ` bugzilla-daemon
2019-05-13 13:11 ` bugzilla-daemon
2019-06-05 22:55 ` bugzilla-daemon
2019-08-07 17:52 ` bugzilla-daemon
2019-08-08 7:58 ` bugzilla-daemon
2019-08-12 5:06 ` bugzilla-daemon
2019-08-12 13:02 ` bugzilla-daemon
2019-08-12 17:48 ` bugzilla-daemon
2019-09-21 13:37 ` bugzilla-daemon
2019-09-26 21:22 ` bugzilla-daemon
2019-09-27 7:26 ` bugzilla-daemon
2019-09-27 7:31 ` bugzilla-daemon
2019-09-27 7:31 ` bugzilla-daemon
2019-10-27 23:35 ` bugzilla-daemon
2019-11-08 12:39 ` bugzilla-daemon
2019-11-08 17:02 ` bugzilla-daemon
2019-11-12 6:20 ` bugzilla-daemon
2020-10-16 15:34 ` 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-203471-2300-HlWH0d66RP@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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