All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michal Wajdeczko" <michal.wajdeczko@intel.com>
To: intel-gfx@lists.freedesktop.org, Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH 2/2] drm/i915/guc: Turn on GuC/HuC auto mode
Date: Wed, 03 Jul 2019 15:02:51 +0200	[thread overview]
Message-ID: <op.z4cru1xwxaggs7@mwajdecz-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <156215400635.20783.16587348502567240067@skylake-alporthouse-com>

On Wed, 03 Jul 2019 13:40:06 +0200, Chris Wilson  
<chris@chris-wilson.co.uk> wrote:

> Quoting Michal Wajdeczko (2019-07-03 12:36:40)
>> GuC firmware is now mature, so let it run by default.
>> Note that today GuC is only used for HuC authentication.
>
> https://bugs.freedesktop.org/show_bug.cgi?id=110617 ?

Above bug was found on suspicious kernel with old GuC 9.39:

[    2.381803] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin  
(version 2.0)
[    2.386316] [drm] GuC: Loaded firmware i915/kbl_guc_ver9_39.bin  
(version 9.39)
[    2.438318] [drm:intel_huc_auth] *ERROR* HuC: Firmware not verified  
0x6000
[    2.445235] [drm:intel_huc_auth] *ERROR* HuC: Authentication failed -110
[    2.451975] i915 0000:00:02.0: GuC initialization failed -110

while results from try-bot [1] with 33.0.0 on KBL are looking fine:

[    3.854084] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin  
(version 2.0)
[    3.865419] [drm] GuC: Loaded firmware i915/kbl_guc_33.0.0.bin (version  
33.0)
[    3.876243] i915 0000:00:02.0: GuC submission disabled
[    3.876245] i915 0000:00:02.0: HuC enabled

Note that newer GuC fixes other known issue [2] that has similar signature:

[160.168623] [drm:intel_huc_auth [i915]] *ERROR* HuC: Firmware not  
verified -110
[160.168839] [drm:intel_huc_auth [i915]] *ERROR* HuC: Authentication  
failed -110
[160.169159] [drm:i915_gem_init_hw [i915]] *ERROR* Enabling uc failed  
(-110)

Michal

[1]  
https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_4514/fi-kbl-7567u/boot0.log
[2] https://bugs.freedesktop.org/show_bug.cgi?id=110820




_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-07-03 13:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03 11:36 [PATCH 1/2] drm/i915/guc: Upgrade to GuC 33.0.0 Michal Wajdeczko
2019-07-03 11:36 ` [PATCH 2/2] drm/i915/guc: Turn on GuC/HuC auto mode Michal Wajdeczko
2019-07-03 11:40   ` Chris Wilson
2019-07-03 13:02     ` Michal Wajdeczko [this message]
2019-07-04 15:59       ` Chris Wilson
2019-07-09 14:17   ` Joonas Lahtinen
2019-07-10 14:27     ` Michal Wajdeczko
2019-07-10 17:51       ` Srivatsa, Anusha
2019-07-11  4:24       ` Ye, Tony
2019-07-03 15:21 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/guc: Upgrade to GuC 33.0.0 Patchwork
2019-07-03 21:50 ` [PATCH 1/2] " Daniele Ceraolo Spurio
2019-07-04 15:47 ` ✓ Fi.CI.IGT: success for series starting with [1/2] " Patchwork
2019-07-12 11:14 [PATCH 0/2] Enable HuC by default for Gen11+ Michal Wajdeczko
2019-07-12 11:14 ` [PATCH 2/2] drm/i915/guc: Turn on GuC/HuC auto mode Michal Wajdeczko
2019-07-12 11:25   ` Joonas Lahtinen
2019-07-12 11:29   ` Rodrigo Vivi
2019-07-12 13:44     ` Chris Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.z4cru1xwxaggs7@mwajdecz-mobl1.ger.corp.intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.