<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][BAT] igt@i915_pm_rpm@basic-pci-d3-state - fail - Failed assertion: wait_for_suspended()"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110829#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][BAT] igt@i915_pm_rpm@basic-pci-d3-state - fail - Failed assertion: wait_for_suspended()"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110829">bug 110829</a>
from <span class="vcard"><a class="email" href="mailto:don.hiatt@intel.com" title="Don Hiatt <don.hiatt@intel.com>"> <span class="fn">Don Hiatt</span></a>
</span></b>
<pre>(In reply to Martin Peres from <a href="show_bug.cgi?id=110829#c8">comment #8</a>)
<span class="quote">> (In reply to Jon Ewins from <a href="show_bug.cgi?id=110829#c7">comment #7</a>)
> > Looks like a display related issue, possibly on the target board.
> > intel_hdmi_detect() is called by the drm subsystem when the device is
> > suspended, and then an HDMI interrupt wakes it back up. There are several
> > HDMI-related logs in dmesg about invalid settings.
>
> Thanks for looking into this. However, could you follow the normal bug
> assessment process so as a priority could be set? Right now, the only thing
> you have done is saying it wasn't likely due to the GuC.</span >
Hey Martin/John, I'll do the bug assessment process on this. Thanks.</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>