All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203471] New: Tearing on Raven Ridge and RX560X PRIME setup even with Vsync enabled
Date: Wed, 01 May 2019 16:30:33 +0000	[thread overview]
Message-ID: <bug-203471-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=203471

            Bug ID: 203471
           Summary: Tearing on Raven Ridge and RX560X PRIME setup even
                    with Vsync enabled
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.1 rc6
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: haxk612@gmail.com
        Regression: No

I have Acer Nitro 5 AN515-42 with Ryzen 5 2500U and RX560X.
When i launch some game with DRI_PRIME=1 to have it on dGPU there is huge
tearing on top of the screen that is there with or without Vsync.
If i launch the game on iGPU there is no tearing at all.
Also the tearing happens only when the game is in fullscreen.
If i take a screenshot there is no tearing in the screenshot.
And i cannot post a picture as my phone camera is broken in my latest build of
android.
I have tried 5.2-wip branch and there is the same issue.
Will post dmesg and journalctl in few hours.

-- 
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

             reply	other threads:[~2019-05-01 16:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 16:30 bugzilla-daemon [this message]
2019-05-01 21:02 ` [Bug 203471] Tearing on Raven Ridge and RX560X PRIME setup even with Vsync enabled bugzilla-daemon
2019-05-01 21:03 ` bugzilla-daemon
2019-05-02  8:10 ` bugzilla-daemon
2019-05-02 12:30 ` bugzilla-daemon
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@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 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.