From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/pxp/mtl: Update gsc-heci cmd size and timeout
Date: Wed, 12 Jul 2023 17:39:23 +0000 [thread overview]
Message-ID: <f5068fdb0f01a52e05a4402158d90a79fceb1267.camel@intel.com> (raw)
In-Reply-To: <168877342003.14757.3694771101892267398@emeril.freedesktop.org>
On Fri, 2023-07-07 at 23:43 +0000, Patchwork wrote:
> Patch Details
> Series: drm/i915/pxp/mtl: Update gsc-heci cmd size and timeout
> URL: https://patchwork.freedesktop.org/series/120360/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120360v1/index.html
> CI Bug Log - changes from CI_DRM_13355_full -> Patchwork_120360v1_full
> Summary
>
> FAILURE
>
> Serious unknown changes coming with Patchwork_120360v1_full absolutely need to be
> verified manually.
alan:snip
> Possible new issues
>
> Here are the unknown changes that may have been introduced in Patchwork_120360v1_full:
>
> IGT changes
> Possible regressions
>
> * igt@kms_vblank@pipe-b-accuracy-idle:
>
> * shard-glk: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13355/shard-glk4/igt@kms_vblank@pipe-b-accuracy-idle.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120360v1/shard-glk8/igt@kms_vblank@pipe-b-accuracy-idle.html>
> * igt@prime_vgem@fence-wait@ccs0:
>
> * shard-mtlp: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13355/shard-mtlp-3/igt@prime_vgem@fence-wait@ccs0.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120360v1/shard-mtlp-4/igt@prime_vgem@fence-wait@ccs0.html>
> * igt@prime_vgem@fence-wait@vecs0:
>
> * shard-mtlp: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13355/shard-mtlp-3/igt@prime_vgem@fence-wait@vecs0.html> -> ABORT<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_120360v1/shard-mtlp-4/igt@prime_vgem@fence-wait@vecs0.html>
>
Above 3 reported regressions are unrelated to PXP at all - the first is a display issue and the remaining two are about gt park-unpark incorrectly attempting to free a vma (looks
to me like a genuine bug not related to PXP but related to some last bits of GT code that dont seem to be aware of dual-GT concurrent operation)
alan:snip
next prev parent reply other threads:[~2023-07-12 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 18:34 [Intel-gfx] [PATCH v1] drm/i915/pxp/mtl: Update gsc-heci cmd size and timeout Alan Previn
2023-07-07 19:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-07-07 23:43 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-07-12 17:39 ` Teres Alexis, Alan Previn [this message]
2023-08-10 23:55 ` [Intel-gfx] [PATCH v1] " Teres Alexis, Alan Previn
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=f5068fdb0f01a52e05a4402158d90a79fceb1267.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox