<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BSW] Using multiple DP, can cause second output to blank until reboot by quickly transition cursor across screen border"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92826#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BSW] Using multiple DP, can cause second output to blank until reboot by quickly transition cursor across screen border"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92826">bug 92826</a>
from <span class="vcard"><a class="email" href="mailto:max@warheads.net" title="Jason Plum <max@warheads.net>"> <span class="fn">Jason Plum</span></a>
</span></b>
<pre>(In reply to Jani Nikula from <a href="show_bug.cgi?id=92826#c4">comment #4</a>)
<span class="quote">> Please try current drm-intel-nightly, add drm.debug=14 module parameter, and
> attach the (plain text!) dmesg all the way from boot to reproducing the
> problem. If the early boot doesn't fit in the buffer, please add
> log_buf_len=4M (or larger) and try again.</span >
I will rebuild and re-test.
I will not pre-compress them this time. Might I ask why drm.debug=14 vs the
drm.debug=0x1e that I have? (documentation purposes for my team)
<span class="quote">> (In reply to Jason Plum from <a href="show_bug.cgi?id=92826#c3">comment #3</a>)
> > Bumped to high. This is blocking a product release
>
> This bugzilla is best-effort only. If you have a support contract with
> Intel, please escalate through your normal support channels.</span >
Understood. I have sent my manufacturer this bug and they are going through
said channels.</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>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>