<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Regression with Dell TB16 dock and Linux kernel 4.16.x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106250#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Regression with Dell TB16 dock and Linux kernel 4.16.x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106250">bug 106250</a>
from <span class="vcard"><a class="email" href="mailto:stanislav.lisovskiy@intel.com" title="Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>"> <span class="fn">Stanislav Lisovskiy</span></a>
</span></b>
<pre>I've discovered one more "funny" issue, which probably Patrik was also facing:
each second time, when Thunderbolt is disconnected and then connected back, the
external display doesn't work.
I've checked with logs + added own traces - seems that kernel(4.18-rc7) sends
hotplug event as it should, however each second time, we don't get
drm_mode_setcrtc for PIPE_B from userspace. To me it looks like a userspace
issue, as kernel seems to reach properly.
I've attached the corresponding logs (not_working_pipe_b - for not working case
and working_pipe_b - for working case).
It changes for each second time mostly, which indicates some logic problem and
the only difference is that we simply don't get drm_mode_setcrtc for pipe B
despite that hotplug was sent through sysfs, which was verified by additional
traces(see the logs).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>