<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [APL] [BAT] GuC firmware goes missing"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97088">97088</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[APL] [BAT] GuC firmware goes missing
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>david.s.gordon@intel.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Split off from
<a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [APL] [BAT execlists] Sporadic - gem_exec_suspend basic-s4 GPU hang after resume"
href="show_bug.cgi?id=96526">Bug 96526</a> - [APL] [BAT execlists] Sporadic - gem_exec_suspend basic-s4 GPU hang
after resume
One of the logs attached to that bug
(<a href="https://bugs.freedesktop.org/attachment.cgi?id=124911">https://bugs.freedesktop.org/attachment.cgi?id=124911</a>) shows the GuC firmware
disappearing between reboots.
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. Hence, this bug report has
been opened to track it separately.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>