From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: <John.C.Harrison@Intel.com>, <Intel-GFX@Lists.FreeDesktop.Org>
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH 1/5] drm/i915/guc: Decode another GuC load failure case
Date: Tue, 18 Apr 2023 11:41:35 -0700 [thread overview]
Message-ID: <120661e9-0e05-5d6a-3872-de48276f91cd@intel.com> (raw)
In-Reply-To: <20230415005706.4135485-2-John.C.Harrison@Intel.com>
On 4/14/2023 5:57 PM, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> Explain another potential firmware failure mode and early exit the
> long wait if hit.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Daniele
> ---
> drivers/gpu/drm/i915/gt/uc/abi/guc_errors_abi.h | 1 +
> drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c | 6 ++++++
> 2 files changed, 7 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/abi/guc_errors_abi.h b/drivers/gpu/drm/i915/gt/uc/abi/guc_errors_abi.h
> index bcb1129b36102..dabeaf4f245f3 100644
> --- a/drivers/gpu/drm/i915/gt/uc/abi/guc_errors_abi.h
> +++ b/drivers/gpu/drm/i915/gt/uc/abi/guc_errors_abi.h
> @@ -44,6 +44,7 @@ enum intel_guc_load_status {
> enum intel_bootrom_load_status {
> INTEL_BOOTROM_STATUS_NO_KEY_FOUND = 0x13,
> INTEL_BOOTROM_STATUS_AES_PROD_KEY_FOUND = 0x1A,
> + INTEL_BOOTROM_STATUS_PROD_KEY_CHECK_FAILURE = 0x2B,
> INTEL_BOOTROM_STATUS_RSA_FAILED = 0x50,
> INTEL_BOOTROM_STATUS_PAVPC_FAILED = 0x73,
> INTEL_BOOTROM_STATUS_WOPCM_FAILED = 0x74,
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> index 6fda3aec5c66a..0ff088a5e51a8 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> @@ -129,6 +129,7 @@ static inline bool guc_load_done(struct intel_uncore *uncore, u32 *status, bool
> case INTEL_BOOTROM_STATUS_RC6CTXCONFIG_FAILED:
> case INTEL_BOOTROM_STATUS_MPUMAP_INCORRECT:
> case INTEL_BOOTROM_STATUS_EXCEPTION:
> + case INTEL_BOOTROM_STATUS_PROD_KEY_CHECK_FAILURE:
> *success = false;
> return true;
> }
> @@ -219,6 +220,11 @@ static int guc_wait_ucode(struct intel_guc *guc)
> guc_info(guc, "firmware signature verification failed\n");
> ret = -ENOEXEC;
> break;
> +
> + case INTEL_BOOTROM_STATUS_PROD_KEY_CHECK_FAILURE:
> + guc_info(guc, "firmware production part check failure\n");
> + ret = -ENOEXEC;
> + break;
> }
>
> switch (ukernel) {
next prev parent reply other threads:[~2023-04-18 18:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 0:57 [Intel-gfx] [PATCH 0/5] Improvements to uc firmare management John.C.Harrison
2023-04-15 0:57 ` [Intel-gfx] [PATCH 1/5] drm/i915/guc: Decode another GuC load failure case John.C.Harrison
2023-04-18 18:41 ` Ceraolo Spurio, Daniele [this message]
2023-04-15 0:57 ` [Intel-gfx] [PATCH 2/5] drm/i915/guc: Print status register when waiting for GuC to load John.C.Harrison
2023-04-18 18:37 ` Ceraolo Spurio, Daniele
2023-04-15 0:57 ` [Intel-gfx] [PATCH 3/5] drm/i915/uc: Track patch level versions on reduced version firmware files John.C.Harrison
2023-04-18 22:46 ` Ceraolo Spurio, Daniele
2023-04-19 16:06 ` John Harrison
2023-04-15 0:57 ` [Intel-gfx] [PATCH 4/5] drm/i915/uc: Split firmware table validation to a separate function John.C.Harrison
2023-04-18 23:14 ` Ceraolo Spurio, Daniele
2023-04-19 15:45 ` John Harrison
2023-04-15 0:57 ` [Intel-gfx] [PATCH 5/5] drm/i915/uc: Reject doplicate entries in firmware table John.C.Harrison
2023-04-18 23:24 ` Ceraolo Spurio, Daniele
2023-04-19 17:02 ` John Harrison
2023-04-19 17:12 ` John Harrison
2023-04-19 17:33 ` Ceraolo Spurio, Daniele
2023-04-19 17:59 ` John Harrison
2023-04-15 1:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improvements to uc firmare management Patchwork
2023-04-15 1:28 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-15 1:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-15 8:09 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=120661e9-0e05-5d6a-3872-de48276f91cd@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=John.C.Harrison@Intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox