From: John Harrison <John.C.Harrison@Intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Petri Latvala <petri.latvala@intel.com>
Cc: "Sarvela, Tomi P" <tomi.p.sarvela@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/guc: Update to GuC v49
Date: Mon, 21 Sep 2020 14:21:42 -0700 [thread overview]
Message-ID: <2a58d05b-e9e8-64ab-46fc-9a83c011e4cc@Intel.com> (raw)
In-Reply-To: <661176f4-2ead-0ce7-ce1a-5ff7e982660b@intel.com>
On 9/21/2020 13:36, Daniele Ceraolo Spurio wrote:
> On 9/21/2020 12:22 PM, John Harrison wrote:
>> On 9/16/2020 23:48, Petri Latvala wrote:
>>> On Wed, Sep 16, 2020 at 06:22:45PM -0700, John Harrison wrote:
>>>> Hello,
>>>>
>>>> The failures below all appear to be because the new GuC firmware
>>>> was not
>>>> found on the test system.
>>>>
>>>> My understanding is that all we need to do to get the CI system to
>>>> update
>>>> with new firmwares is to push the firmware to a branch on the FDO
>>>> drm-firmware repo and then send a pull request to this mailing
>>>> list. That
>>>> was done yesterday.
>>> That pull request used an ssh:// url though. Can you send it again
>>> with a git:// url? I suppose that's a plausible reason why I don't see
>>> the binaries in CI's deploy dir.
>>>
>>
>> Hello,
>>
>> We reset the pull request with a git:// URL as requested. I even gave
>> it a full weekend to propagate through. However, I am still getting
>> missing firmware failures after posting a new patch set.
>>
>> John.
>>
>
> You sure you're looking at the correct logs? AFAICS BAT on the new
> patches passed (https://patchwork.freedesktop.org/series/81906/) and I
> see the correct GuC being loaded in the logs.
> e.g.
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18542/fi-icl-u2/boot0.txt:
>
> <6>[ 9.283866] i915 0000:00:02.0: [drm] GuC firmware
> i915/icl_guc_49.0.1.bin version 49.0 submission:disabled
>
> Daniele
Grrr. When I downloaded the dmesg.txt it saved is as dmesg.txt.1. So
yes, I was looking at a stale log :(.
I guess the other question is are we supposed to be supporting HuC by
default on KBL? It is running the gem_huc_copy test but we have only
enabled GuC/HuC loading on Gen11+ platforms.
John.
_______________________________________________
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-21 21:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 17:16 [Intel-gfx] [PATCH 00/12] drm/i915/guc: Update to GuC v49 John.C.Harrison
2020-09-16 17:16 ` [Intel-gfx] [PATCH 01/12] drm/i915/guc: New GuC IDs based on engine class and instance John.C.Harrison
2020-09-16 17:16 ` [Intel-gfx] [PATCH 02/12] drm/i915/guc: Support logical engine mapping table in ADS John.C.Harrison
2020-09-16 23:27 ` Daniele Ceraolo Spurio
2020-09-17 1:19 ` John Harrison
2020-09-16 17:16 ` [Intel-gfx] [PATCH 03/12] drm/i915/guc: Setup private_data pointer in GuC ADS John.C.Harrison
2020-09-16 23:30 ` Daniele Ceraolo Spurio
2020-09-16 17:16 ` [Intel-gfx] [PATCH 04/12] drm/i915/guc: Remove GUC_CTL_CTXINFO init param John.C.Harrison
2020-09-16 23:32 ` Daniele Ceraolo Spurio
2020-09-16 17:16 ` [Intel-gfx] [PATCH 05/12] drm/i915/guc: Kill guc_ads.reg_state_buffer John.C.Harrison
2020-09-16 23:46 ` Daniele Ceraolo Spurio
2020-09-16 17:16 ` [Intel-gfx] [PATCH 06/12] drm/i915/guc: ADS changes for GuC v42 John.C.Harrison
2020-09-16 17:16 ` [Intel-gfx] [PATCH 07/12] drm/i915/guc: Setup doorbells data in ADS John.C.Harrison
2020-09-16 17:16 ` [Intel-gfx] [PATCH 08/12] drm/i915/guc: Increased engine classes " John.C.Harrison
2020-09-16 17:16 ` [Intel-gfx] [PATCH 09/12] drm/i915/guc: Update firmware to v49.0.1 John.C.Harrison
2020-09-16 17:16 ` [Intel-gfx] [PATCH 10/12] drm/i915/guc: Improved reporting when GuC fails to load John.C.Harrison
2020-09-16 17:16 ` [Intel-gfx] [PATCH 11/12] drm/i915/guc: Clear pointers on free John.C.Harrison
2020-09-16 17:16 ` [Intel-gfx] [PATCH 12/12] drm/i915/uc: turn on GuC/HuC auto mode by default John.C.Harrison
2020-09-16 18:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Update to GuC v49 Patchwork
2020-09-16 18:35 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-09-17 1:22 ` John Harrison
2020-09-17 6:35 ` Saarinen, Jani
2020-09-17 6:48 ` Petri Latvala
2020-09-21 19:22 ` John Harrison
2020-09-21 20:36 ` Daniele Ceraolo Spurio
2020-09-21 21:21 ` John Harrison [this message]
2020-09-16 23:21 ` [Intel-gfx] [PATCH 00/12] " 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=2a58d05b-e9e8-64ab-46fc-9a83c011e4cc@Intel.com \
--to=john.c.harrison@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
--cc=tomi.p.sarvela@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