<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [guc/huc] Deep Package C-states never reached after laptop screen is turned off"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111594#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [guc/huc] Deep Package C-states never reached after laptop screen is turned off"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111594">bug 111594</a>
from <span class="vcard"><a class="email" href="mailto:don.hiatt@intel.com" title="Don Hiatt <don.hiatt@intel.com>"> <span class="fn">Don Hiatt</span></a>
</span></b>
<pre>(In reply to kitestramuort from <a href="show_bug.cgi?id=111594#c19">comment #19</a>)
<span class="quote">> (In reply to Don Hiatt from <a href="show_bug.cgi?id=111594#c17">comment #17</a>)
> > What value of guc_enable are you giving? Also, this is what it looks like on
> > KBL with drm-tip with the proper firmware.
> >
> > [ 213.513852] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin
> > (v1.4)
> > [ 213.573467] [drm] GuC communication enabled
> > [ 213.578063] i915 0000:00:02.0: GuC firmware i915/kbl_guc_33.0.0.bin
> > version 33.0 submission:disabled
> > [ 213.578065] i915 0000:00:02.0: HuC firmware i915/kbl_huc_4.0.0.bin
> > version 4.0 authenticated:yes
> > [ 213.579030] [drm] Initialized i915 1.6.0 20191007 for 0000:00:02.0 on
> > minor 0
> > [ 213.581581] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
>
> I'm on the current stable kernel, 5.3.8. enable_guc is -1, which on this
> platform should be equivalent to 2. 5.3 only accepts guc 32.0.3 and huc 02
>
> [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0)
> [ 116.266798] [drm] GuC: Loaded firmware i915/kbl_guc_32.0.3.bin (version
> 32.0)
> [ 116.266967] i915 0000:00:02.0: GuC firmware version 32.0
> [ 116.266968] i915 0000:00:02.0: GuC submission disabled
> [ 116.266969] i915 0000:00:02.0: HuC enabled</span >
Yes, enable_guc = -1 is equivalent to 2. That said, I've been debugging this
issue with drmtip and the latest firmware. So that seems to be the reason it is
working for others and not you. BTW, just to confirm, you did apply the patch?</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>
</ul>
</body>
</html>