dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106529] dc=1 kernels somehow trigger a disconnect of an lg ultrawide monitor during DP link training while attempting a wakeup
Date: Thu, 09 Aug 2018 20:29:46 +0000	[thread overview]
Message-ID: <bug-106529-502-Y3juCzzs45@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106529-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from Mariusz Mazur <mariusz.g.mazur@gmail.com> ---
I've tried the same thing with only the DP ultrawide monitor connected and got
the same issue. dc logs, reading code and some kernel tracers (ftrace) on DC
link training code basically tell me that the important part is this:

21:23:16 [drm] [LKTN]        [DP][ConnIdx:0] RBRx4 pass VS=2, PE=1^
21:23:16 [drm] link=0, dc_sink_in=          (null) is now Disconnected
21:23:18 [drm] [LKTN]        [DP][ConnIdx:0] HBRx4 pass VS=1, PE=0^
21:23:18 [drm] link=0, dc_sink_in=00000000dbbee48e is now Connected
21:23:18 [drm] [LKTN]        [DP][ConnIdx:0] RBRx4 pass VS=1, PE=1^

Whatever's going on with the first attempt at link training, it ends up with
the monitor disconnecting (not sure if deliberately or by causing some error in
the monitor; didn't dive deep enough into the code).

Pre-DC codepaths did not have an issue like this at all until Michel Dänzer
created this patch: https://patchwork.freedesktop.org/patch/209464/ for bug
105308 thereby introducing a problem with the same effects (DC monitor gets
disconnected on wakeup, which on multi-display causes issues) via a quite
different approach (a deliberate DRM_MODE_DPMS_OFF & ON). But that should be a
separate bug, I think.

And since Michel's patch got applied to all the kernels, the effect is that on
any up to date 4.15+ kernel the same issue shows up whether you're doing dc=1
or dc=0, while the actual code paths causing it are different. (Which made this
a PITA to figure out.)

Anyway, since I know nothing about DP link training and how to fix code
relating to it, I've just bought a DP->HDMI cable thus "fixing" my problem
entirely (including the second issue of a 2s lag with DP audio).

Hopefully someone in the future, a future man so to speak, will fix this issue
eventually. Cause currently DP support is quite bad, it seems.

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

[-- Attachment #1.2: Type: text/html, Size: 3043 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-08-09 20:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 15:00 [Bug 106529] Kernels 4.16+ confuses KDE wrt what the primary display is when waking up multiple displays bugzilla-daemon
2018-05-15 15:01 ` [Bug 106529] Kernels 4.16+ confuse " bugzilla-daemon
2018-05-15 15:19 ` bugzilla-daemon
2018-08-09 20:07 ` [Bug 106529] dc=1 kernels somehow trigger a disconnect of an lg ultrawide monitor during DP link training while attempting a wakeup bugzilla-daemon
2018-08-09 20:29 ` bugzilla-daemon [this message]
2018-08-15 14:43 ` bugzilla-daemon
2018-08-15 16:08 ` bugzilla-daemon
2018-08-15 17:29 ` bugzilla-daemon
2018-08-16  7:36 ` bugzilla-daemon
2019-11-19  8:38 ` 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-106529-502-Y3juCzzs45@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