<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Video cutout on Kaby Lake U processors." href="https://bugs.freedesktop.org/show_bug.cgi?id=107543#c26">Comment # 26</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Video cutout on Kaby Lake U processors." href="https://bugs.freedesktop.org/show_bug.cgi?id=107543">bug 107543</a> from <a class="email" href="mailto:phil.smith@adder.com" title="phil.smith@adder.com">phil.smith@adder.com</a> <pre>> I could see multiple hot-plug events and under-runs around those events, Is hot > plug/un-plug is involved in test scenario or this is monitor/cable problem which > is triggering hotplug? We have seen the issue under a variety of different circumstances including: - Kicking off a Linux kernel compile. - Shortly after boot into Wayland/Weston. - Wayland/Weston idling. - After bringing a monitor out of standby. I.e. Physical hot-plug/unplug are not specifically required to trigger the issue. We have not been able find a reliable reproduction case and sometimes we can go over a week without a failure. > Is it particular 4K monitor in which issue is reproducible or all 4K monitor are > causing this issue. Can you please try with some other 4K monitor to see if > issue is still reproducible. The issue has been observed with at least three different 4k monitors (Eizo, Samsung and LG). We believe it has never occurred with a HD monitor.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>