<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [CI][BAT] igt@. - dmesg-warn - WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1))" href="https://bugs.freedesktop.org/show_bug.cgi?id=108070#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [CI][BAT] igt@. - dmesg-warn - WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1))" href="https://bugs.freedesktop.org/show_bug.cgi?id=108070">bug 108070</a> from <a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> Imre Deak</a> <pre>Different bug with the same error message.(In reply to Martin Peres from <a href="show_bug.cgi?id=108070#c17">comment #17</a>) > (In reply to Imre Deak from <a href="show_bug.cgi?id=108070#c16">comment #16</a>) > > Fix merged: > > > > commit 602438ead302aaa844899db5214b489d0d93fe18 > > Author: Imre Deak <<a href="mailto:imre.deak@intel.com">imre.deak@intel.com</a>> > > Date: Tue Nov 6 18:06:21 2018 +0200 > > > > drm/i915/icl: Fix port B combo PHY context loss after DC transitions > > Thanks, this really helped! Yep, I think different bug leading to the same error message. This one is due to our modeset vs. TC port connected state tracking being broken, a known issue. The test generates an HPD disconnect interrupt on the HDMI output during suspend and so we run the TypeC disconnect sequence, but there is no time for userspace/kernel console to react doing a modeset to disable the output. Then after resume we try to restore the output but since the port is in a disconnected state that will fail, leading to the timeout during powerwell enabling. So in general HPD on ICL type C ports is broken or not implemented yet, depending on how you want to look at it.</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> </ul> </body> </html>