From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110671] Regression: DP outputs out of sync on dual-DP tiled 5k screen
Date: Mon, 13 May 2019 11:04:19 +0000 [thread overview]
Message-ID: <bug-110671-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1587 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110671
Bug ID: 110671
Summary: Regression: DP outputs out of sync on dual-DP tiled 5k
screen
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: bugs@bzatek.net
With kernel 5.1.1 I get corrupted image on my Dell UP2715K screen (again). The
symptomps are similar to the ones in bug 98461 (see also attachment 127570). In
my theory this is caused by the two DisplayPort outputs not being in sync - the
screen needs both tiles to be in sync (i.e. scanlines to match) to make a
composite final image.
The Dell UP2715K monitor has two DP 1.2 inputs, two tiles expecting
2560x2880@60Hz modes (as exposed in EDID/DisplayInfo data). Connected to Radeon
Pro WX2100 (Polaris 12).
This used to be actually working reliably in kernel 4.20.0, yesterday I fired
up kernel 5.1.1 and only got garbage on my screen. Also tested drm-tip kernel
that includes drm-next-5.2 branch from the agd5f repo
(https://patchwork.freedesktop.org/patch/304430/) - same issue.
I haven't got time to bisect the change yet, I was hoping you could point me to
a possible commit that broke this. By any chance, do you AMD guys have a 5k
tiled screen inhouse for testing?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3296 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-05-13 11:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 11:04 bugzilla-daemon [this message]
2019-05-13 13:25 ` [Bug 110671] Regression: DP outputs out of sync on dual-DP tiled 5k screen bugzilla-daemon
2019-05-13 19:22 ` bugzilla-daemon
2019-05-13 19:23 ` bugzilla-daemon
2019-05-13 19:38 ` bugzilla-daemon
2019-05-18 12:31 ` bugzilla-daemon
2019-05-18 12:33 ` bugzilla-daemon
2019-05-20 20:23 ` bugzilla-daemon
2019-05-20 21:12 ` bugzilla-daemon
2019-06-15 21:06 ` bugzilla-daemon
2019-07-22 20:30 ` bugzilla-daemon
2019-08-08 20:41 ` bugzilla-daemon
2019-08-08 20:48 ` bugzilla-daemon
2019-11-19 9:26 ` 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-110671-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.