<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><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> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - [IVB/SNB/BYT/HSW/BDW] GuC boot kernel command lines are causing regressions"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97573">bug 97573</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;">Resolution</td>
<td>---
</td>
<td>NOTABUG
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - [IVB/SNB/BYT/HSW/BDW] GuC boot kernel command lines are causing regressions"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97573#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - [IVB/SNB/BYT/HSW/BDW] GuC boot kernel command lines are causing regressions"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97573">bug 97573</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><span class="quote">> Steps:
> ------
> 1. Boot with kernel boot command lines: </span >
i915.enable_guc_loading=2 i915.enable_guc_submission=2
Please note that these variables are marked as UNSAFE.
That means that:
(a) you shouldn't set them unless you know what you're doing, and what they
mean, and
(b) the kernel is *tainted* when you do so, which in turn means,
(c) whatever happens, it's not a bug, because you asked for it.
Secondly, the number "2" for these variables means that you are telling the
driver that loading and use of the GuC is *mandatory*, and the driver *must*
fail startup (leaving the GPU wedged) if *for any reason* those mandatory
requirements cannot be fulfilled.
Good reasons to fail here include
(a) you don't have the (correct) GuC firmware installed, or
(b) the driver doesn't know what GuC firmware would be appropriate, or
(c) you don't have a GuC!
Therefore, this part of the bug report is wrong
<span class="quote">> Expected result:
> ---------------
> 2. Trying to load GuC has no impact</span >
The expected result of telling the driver that it *must* use the GuC on a
platform that doesn't have one, is that it will develop paranoid schizophrenia
^W^W^W log an error and leave the GPU wedged. Which, according to the attached
log, is exactly what it is doing :)
Note that setting either or both of these variables to "1" is much more
sensible. That means "try to load/use the GuC, but continue in execlist mode if
you can't". Or even "-1", meaning "try to use the GuC *if it's supported on
this platform*, but fall back to execlist mode if it isn't supported, or the
firmware is missing, or there's any other reason it can't be used".</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>