<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - commit c1132367 "Extract GT render sleep (rc6) management" prevents entering s2idle"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111909#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - commit c1132367 "Extract GT render sleep (rc6) management" prevents entering s2idle"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111909">bug 111909</a>
from <span class="vcard"><a class="email" href="mailto:kenny@panix.com" title="Kenneth C <kenny@panix.com>"> <span class="fn">Kenneth C</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=111909#c9">comment #9</a>)
<span class="quote">> > <a href="https://patchwork.freedesktop.org/series/67954/">https://patchwork.freedesktop.org/series/67954/</a> is worth a short to see what happens and how much work would be required.</span >
(In reply to Lakshmi from <a href="show_bug.cgi?id=111909#c12">comment #12</a>)\
<span class="quote">> @Kenneth, have you tried this as well?</span >
So I applied these commits in order against the drm-tip as of 8d527b772ec330 .
I had a merge error in the first patch related to commit e7abf8141935d in
drivers/gpu/drm/i915/gt/intel_gt_pm.c , but I fixed it up easily enough.
So I booted into it, used it for about 5 mins, then suspended the machine ...
and it never came back.
You'd think that since Intel was among the companies pushing this S3
"improvement" that there'd be a box there somewhere to test against s01x
regressions (including the commit referenced in the initial bug).
... ah well</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>