<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] GuC sometimes does not load depending on order the order of some asynchronously initialization operations"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97275">97275</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[APL] GuC sometimes does not load depending on order the order of some asynchronously initialization operations
</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>christophe.prigent@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>Created <span class=""><a href="attachment.cgi?id=125660" name="attach_125660" title="kern.log">attachment 125660</a> <a href="attachment.cgi?id=125660&action=edit" title="kern.log">[details]</a></span>
kern.log
Platform: APL system
CPU Name : Intel(R) Genuine Processor @ 1.1 GHz (family: 6, model: 12,
stepping: 9) 4 cores
QDF : Q6HE
SoC : B1
CRB : Apollo Lake DDR3L RVP1A FAB2
Reworks : R19, R20
Software
Bios: 144_B10 APLK_B0_IFWI_X64_R_2016_06_27_0956_SPI_RVP1.bin from
\\gar\ec\proj\ba\CCG\APL
BIOS\External\BIOS_Release\Daily\v144_10_2016_WW27.1\IFWI\IFWI_RVP1_Release\IFWI
KSC: 1.15
Linux distribution: Ubuntu 16.04 64 bits
Kernel: 4.7.0-rc7 895a714 from <a href="http://cgit.freedesktop.org/drm-intel/">http://cgit.freedesktop.org/drm-intel/</a> with
<a href="https://patchwork.freedesktop.org/patch/99445/">https://patchwork.freedesktop.org/patch/99445/</a> applied
commit 895a714b0b596cfcbe82065f99376ad02d369125
Author: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
Date: Mon Jul 18 14:35:39 2016 +0200
drm-intel-nightly: 2016y-07m-18d-12h-35m-15s UTC integration manifest
drm: libdrm-2.4.68-15 2212a64 from git://anongit.freedesktop.org/mesa/drm
mesa: mesa-11.2.2 3a9f628from git://anongit.freedesktop.org/mesa/mesa
cairo: 1.15.2 db8a7f1 from git://anongit.freedesktop.org/cairo
xserver: xorg-server-1.18.0-460 e8e3675 from
git://git.freedesktop.org/git/xorg/xserver
xf86-video-intel: 2.99.917-676 26f8ab5 from
git://git.freedesktop.org/git/xorg/driver/xf86-video-intel
libva: libva-1.7.0-26 c36971c from git://git.freedesktop.org/git/vaapi/libva
vaapi-intel-driver: 1.7.0-53 bcde10d from
git://git.freedesktop.org/git/vaapi/intel-driver
DMC 1.07 from <a href="https://01.org/linuxgraphics/downloads/broxton-dmc-1.07">https://01.org/linuxgraphics/downloads/broxton-dmc-1.07</a>
Intel-Gpu-Tools 1.15-127 ee5d5c4 from
<a href="http://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools.git">http://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools.git</a>
Steps:
------
1. Boot
2. Reboot several times
3. Check GuC load status
Actual result
--------------
3. Sometimes GuC does not load:
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
Expected result:
----------------
3. GuC successfully loads each time
Info
-----
>From Dave, <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#c38">https://bugs.freedesktop.org/show_bug.cgi?id=96526#c38</a>:
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>