<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [KBL] Switching multihead mode fails" href="https://bugs.freedesktop.org/show_bug.cgi?id=100226#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [KBL] Switching multihead mode fails" href="https://bugs.freedesktop.org/show_bug.cgi?id=100226">bug 100226</a> from <a class="email" href="mailto:quanxian.wang@intel.com" title="qwang13 <quanxian.wang@intel.com>"> qwang13</a> <pre>After working with Aaron, we have reproduced the issue and get the log. From the log we found: Case: extend mode - > mirror mode Bad machine (Raven-2) hdmi connector is unplugged after the change. This is the key point. With this mode change, HDMI module is crashed, and unplugged. And after a while, HDMI is reconnected again with new plug event. We got all the hot-plug events. Also the log shows that process. Raven-2 has a complete different HDMI hardware module design which uses TBT(thunderbolt) IC to control DP/HDMI/Type-C connector. With general process, Thai-2 (good machine) works normal with normal HDMI connector. But with same process on Raven-2, The control signal and data from graphics kernel driver will be firstly directed to TBT IC and then to HDMI connector. The issue happens on TBT IC signal/data transfer. HDMI is lost when kernel driver send data to TBT IC. Suggestion: We need TBT IC designer to double confirm, what happens in IC? HDMI is unplugged under some case. We are doubt in some case, TBT IC doesn't follow interface defined in HDMI spec. Need hardware design engineer to track why this happens on Raven-2.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>