<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#c37">Comment # 37</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>This doesn't really appear to be GuC-related. For example, the
APL-gem-exec-suspend-basic-s4 test logs show exactly the same failure (GPU
HANG) with or without GuC submission. GuC mode may expose it more quickly but
the issue itself is not caused by the GuC.
dmesg_gem_exec_suspend_apl.log shows:
[ 331.343467] [drm:intel_guc_setup] GuC fw status: path
i915/bxt_guc_ver8_7.bin, fetch FAIL, load NONE
in other words the (correct) firmware is not present. Ditto for dmesg_bxt_log:
[ 1.671603] i915 0000:00:02.0: Direct firmware load for
i915/bxt_guc_ver8_7.bin failed with error -2
As for dmes_bsw.log, that contains:
[ 351.405681] [drm:intel_guc_setup] GuC fw status: path (null), fetch NONE,
load NONE
where the (null) path means that this kernel does not support BSW.</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>