From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: John.C.Harrison@Intel.com, Intel-GFX@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH 2/4] drm/i915/guc: Improved reporting when GuC fails to load
Date: Mon, 21 Sep 2020 17:33:13 -0700 [thread overview]
Message-ID: <99e54169-2d26-c9da-59f6-bdd3f68f9faa@intel.com> (raw)
In-Reply-To: <20200921175428.2914478-3-John.C.Harrison@Intel.com>
On 9/21/2020 10:54 AM, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> Rather than just saying 'GuC failed to load: -110', actually print out
> the GuC status register and break it down into the individual fields.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c | 27 ++++++++++++++++++-----
> 1 file changed, 22 insertions(+), 5 deletions(-)
>
> 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 d4a87f4c9421..eac84baf34e6 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> @@ -74,8 +74,9 @@ static inline bool guc_ready(struct intel_uncore *uncore, u32 *status)
> ((val & GS_MIA_CORE_STATE) && (uk_val == GS_UKERNEL_LAPIC_DONE));
> }
>
> -static int guc_wait_ucode(struct intel_uncore *uncore)
> +static int guc_wait_ucode(struct intel_gt *gt)
No need to pass the GT here, you already have i915 in the uncore
structure and you don't seem to be using the GT for anything else.
> {
> + struct intel_uncore *uncore = gt->uncore;
> u32 status;
> int ret;
>
> @@ -91,16 +92,32 @@ static int guc_wait_ucode(struct intel_uncore *uncore)
> DRM_DEBUG_DRIVER("GuC status %#x\n", status);
>
> if ((status & GS_BOOTROM_MASK) == GS_BOOTROM_RSA_FAILED) {
> - DRM_ERROR("GuC firmware signature verification failed\n");
> + drm_err(>->i915->drm, "GuC firmware signature verification failed\n");
> ret = -ENOEXEC;
> + goto out;
> }
>
> if ((status & GS_UKERNEL_MASK) == GS_UKERNEL_EXCEPTION) {
> - DRM_ERROR("GuC firmware exception. EIP: %#x\n",
> - intel_uncore_read(uncore, SOFT_SCRATCH(13)));
> + drm_err(>->i915->drm, "GuC firmware exception. EIP: %#x\n",
> + intel_uncore_read(uncore, SOFT_SCRATCH(13)));
> ret = -ENXIO;
> + goto out;
> }
>
> + if (ret) {
> + drm_err(>->i915->drm, "GuC load failed: status: Reset = %d, "
> + "BootROM = 0x%02X, UKernel = 0x%02X, "
> + "MIA = 0x%02X, Auth = 0x%02X\n",
> + (status >> GS_RESET_SHIFT) & 1,
> + (status & GS_BOOTROM_MASK) >> GS_BOOTROM_SHIFT,
Could use the REG_FIELD_GET macro here and below to simplify the code
> + (status & GS_UKERNEL_MASK) >> GS_UKERNEL_SHIFT,
> + (status & GS_MIA_MASK) >> GS_MIA_SHIFT,
> + (status & GS_AUTH_STATUS_MASK) >> GS_AUTH_STATUS_SHIFT);
IMO it'd be worth printing the status breakdown for all failures cases,
even the 2 above, but not a blocker.
With the function parameter flipped back to uncore, this is:
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Daniele
> + }
> +
> +out:
> + if (ret)
> + drm_err(>->i915->drm, "GuC load failed: status = 0x%08X\n", status);
> return ret;
> }
>
> @@ -139,7 +156,7 @@ int intel_guc_fw_upload(struct intel_guc *guc)
> if (ret)
> goto out;
>
> - ret = guc_wait_ucode(uncore);
> + ret = guc_wait_ucode(gt);
> if (ret)
> goto out;
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-09-22 0:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 17:54 [Intel-gfx] [PATCH 0/4] drm/i915/guc: Update to GuC v49 John.C.Harrison
2020-09-21 17:54 ` [Intel-gfx] [PATCH 1/4] drm/i915/guc: Update to use firmware v49.0.1 John.C.Harrison
2020-09-22 0:24 ` Daniele Ceraolo Spurio
2020-09-22 0:38 ` John Harrison
2020-09-22 1:01 ` Daniele Ceraolo Spurio
2020-09-21 17:54 ` [Intel-gfx] [PATCH 2/4] drm/i915/guc: Improved reporting when GuC fails to load John.C.Harrison
2020-09-22 0:33 ` Daniele Ceraolo Spurio [this message]
2020-09-21 17:54 ` [Intel-gfx] [PATCH 3/4] drm/i915/guc: Clear pointers on free John.C.Harrison
2020-09-21 17:54 ` [Intel-gfx] [PATCH 4/4] drm/i915/uc: turn on GuC/HuC auto mode by default John.C.Harrison
2020-09-21 18:24 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Update to GuC v49 Patchwork
2020-09-21 18:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-09-21 19:59 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-09-25 23:26 [Intel-gfx] [PATCH 0/4] " John.C.Harrison
2020-09-25 23:26 ` [Intel-gfx] [PATCH 2/4] drm/i915/guc: Improved reporting when GuC fails to load John.C.Harrison
2020-10-01 0:38 ` Daniele Ceraolo Spurio
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=99e54169-2d26-c9da-59f6-bdd3f68f9faa@intel.com \
--to=daniele.ceraolospurio@intel.com \
--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