<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:rodrigo.vivi@gmail.com" title="Rodrigo Vivi <rodrigo.vivi@gmail.com>"> <span class="fn">Rodrigo Vivi</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [BDW] GPU HANG: ecode 0:0x00200003 on resume from suspend (fixed on drm-intel-next and up)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85054">bug 85054</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [BDW] GPU HANG: ecode 0:0x00200003 on resume from suspend (fixed on drm-intel-next and up)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85054#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [BDW] GPU HANG: ecode 0:0x00200003 on resume from suspend (fixed on drm-intel-next and up)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85054">bug 85054</a>
from <span class="vcard"><a class="email" href="mailto:rodrigo.vivi@gmail.com" title="Rodrigo Vivi <rodrigo.vivi@gmail.com>"> <span class="fn">Rodrigo Vivi</span></a>
</span></b>
<pre>Apparently the patch that fixes it is:
<a href="http://cgit.freedesktop.org/drm-intel/commit/drivers/gpu/drm/i915?h=drm-intel-next&id=6689c167ae14c312972e89be1121e933e4de0001">http://cgit.freedesktop.org/drm-intel/commit/drivers/gpu/drm/i915?h=drm-intel-next&id=6689c167ae14c312972e89be1121e933e4de0001</a>
drm/i915: Rework GPU reset sequence to match driver load & thaw
This patch is to address Daniels concerns over different code during reset:
<a href="http://lists.freedesktop.org/archives/intel-gfx/2014-June/047758.html">http://lists.freedesktop.org/archives/intel-gfx/2014-June/047758.html</a>
"The reason for aiming as hard as possible to use the exact same code for
driver load, gpu reset and runtime pm/system resume is that we've simply
seen too many bugs due to slight variations and unintended omissions."
Tested using igt drv_hangman.
V2: Cleaner way of preventing check_wedge returning -EAGAIN
V3: Clean the last_context during reset, to ensure do_switch() does the
MI_SET_CONTEXT. As per review.
Signed-off-by: McAulay, Alistair <<a href="mailto:alistair.mcaulay@intel.com">alistair.mcaulay@intel.com</a>>
Reviewed-by: Mika Kuoppala <<a href="mailto:mika.kuoppala@intel.com">mika.kuoppala@intel.com</a>>
[danvet: Rebase over ctx->ppgtt rework and extend the comment in
check_wedge a bit.]
Signed-off-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>></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>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>