<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [APL] [BAT execlists] Sporadic - gem_exec_suspend basic-s4 GPU hang after resume"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96526#c38">Comment # 38</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [APL] [BAT execlists] Sporadic - gem_exec_suspend basic-s4 GPU hang after resume"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96526">bug 96526</a>
from <span class="vcard"><a class="email" href="mailto:david.s.gordon@intel.com" title="david.s.gordon@intel.com">david.s.gordon@intel.com</a>
</span></b>
<pre>To contradict my previous comment, APL-gem_exec_suspend_gpu-hang_kern.log shows
something very odd: the GuC firmware has disappeared. Early in the log we have
Jul 5 16:56:27 BXTP5 kernel: [ 1.689144] [drm:intel_guc_setup] GuC fw
status: path i915/bxt_guc_ver8_7.bin, fetch SUCCESS, load NONE
but 5 minutes later, on the next reboot cycle:
Jul 5 17:01:44 BXTP5 kernel: [ 1.711802] i915 0000:00:02.0: Direct firmware
load for i915/bxt_guc_ver8_7.bin failed with error -2
The kernel logs for each cycle look generally similar, but the order of some
operations is not identical. In particular, the appearance of the MMC devices
can come before OR after the attempt to load the GuC firmware.
So this is really a completely different issue, related to the way that devices
are initialised asynchronously w.r.t one another. It should be moved to a
separate bug report.
.Dave.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>