Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ CI.BAT: failure for Build PM into GuC CT layer (rev2)
Date: Thu, 18 Jul 2024 18:42:43 +0000	[thread overview]
Message-ID: <ZpliI+lLtsV+ILfz@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <172132675089.287349.11586045289897142861@2413ebb6fbb6>

On Thu, Jul 18, 2024 at 06:19:10PM +0000, Patchwork wrote:
>    Patch Details
> 
>    Series:  Build PM into GuC CT layer (rev2)
>    URL:     [1]https://patchwork.freedesktop.org/series/136226/
>    State:   failure
>    Details:
>    [2]https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136226v2/index.html
> 
>  CI Bug Log - changes from xe-1626-943ad04000a54cc7fdb5347606d0ce6a93ea286d_BAT
>                              -> xe-pw-136226v2_BAT
> 
> Summary
> 
>    FAILURE
> 
>    Serious unknown changes coming with xe-pw-136226v2_BAT absolutely need
>    to be
>    verified manually.
> 
>    If you think the reported changes have nothing to do with the changes
>    introduced in xe-pw-136226v2_BAT, please notify your bug team
>    (I915-ci-infra@lists.freedesktop.org) to allow them
>    to document this new failure mode, which will reduce false positives in
>    CI.
> 
> Participating hosts (7 -> 7)
> 
>    No changes in participating hosts
> 
> Possible new issues
> 
>    Here are the unknown changes that may have been introduced in
>    xe-pw-136226v2_BAT:
> 
>   IGT changes
> 
>     Possible regressions
> 
>      * igt@xe_vm@shared-pde-page:
>           + bat-atsm-2: [3]PASS -> [4]DMESG-WARN

It looks like this series needs to be combined with [1] to be fully safe
due to TLB invalidations of bind being kicked to a worker after a bind
job signals. Still worthwhile for correctness, I don't think a device
should be suspended when G2H are inflight or scheduler messages are
inflight either.

Will post a combined series shortly.

Matt

[1] https://patchwork.freedesktop.org/series/136219/

> 
> Known issues
> 
>    Here are the changes found in xe-pw-136226v2_BAT that come from known
>    issues:
> 
>   IGT changes
> 
>     Issues hit
> 
>      * igt@xe_live_ktest@xe_migrate:
>           + bat-atsm-2: [5]PASS -> [6]SKIP ([7]Intel XE#2109) +2 other
>             tests skip
> 
>     Possible fixes
> 
>      * igt@kms_flip@basic-flip-vs-wf_vblank:
>           + bat-lnl-1: [8]FAIL ([9]Intel XE#886) -> [10]PASS +1 other test
>             pass
> 
> Build changes
> 
>      * Linux: xe-1626-943ad04000a54cc7fdb5347606d0ce6a93ea286d ->
>        xe-pw-136226v2
> 
>    IGT_7930: 7930
>    xe-1626-943ad04000a54cc7fdb5347606d0ce6a93ea286d:
>    943ad04000a54cc7fdb5347606d0ce6a93ea286d
>    xe-pw-136226v2: 136226v2
> 
> References
> 
>    1. https://patchwork.freedesktop.org/series/136226/
>    2. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136226v2/index.html
>    3. https://intel-gfx-ci.01.org/tree/intel-xe/xe-1626-943ad04000a54cc7fdb5347606d0ce6a93ea286d/bat-atsm-2/igt@xe_vm@shared-pde-page.html
>    4. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136226v2/bat-atsm-2/igt@xe_vm@shared-pde-page.html
>    5. https://intel-gfx-ci.01.org/tree/intel-xe/xe-1626-943ad04000a54cc7fdb5347606d0ce6a93ea286d/bat-atsm-2/igt@xe_live_ktest@xe_migrate.html
>    6. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136226v2/bat-atsm-2/igt@xe_live_ktest@xe_migrate.html
>    7. https://gitlab.freedesktop.org/drm/xe/kernel/issues/2109
>    8. https://intel-gfx-ci.01.org/tree/intel-xe/xe-1626-943ad04000a54cc7fdb5347606d0ce6a93ea286d/bat-lnl-1/igt@kms_flip@basic-flip-vs-wf_vblank.html
>    9. https://gitlab.freedesktop.org/drm/xe/kernel/issues/886
>   10. https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-136226v2/bat-lnl-1/igt@kms_flip@basic-flip-vs-wf_vblank.html

  reply	other threads:[~2024-07-18 18:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 17:34 [PATCH v3 0/1] Build PM into GuC CT layer Matthew Brost
2024-07-18 17:34 ` [PATCH v3 1/1] drm/xe: " Matthew Brost
2024-07-18 17:52   ` Matthew Auld
2024-07-18 18:00     ` Matthew Brost
2024-07-18 18:46   ` Nirmoy Das
2024-07-18 17:39 ` ✓ CI.Patch_applied: success for Build PM into GuC CT layer (rev2) Patchwork
2024-07-18 17:40 ` ✓ CI.checkpatch: " Patchwork
2024-07-18 17:41 ` ✓ CI.KUnit: " Patchwork
2024-07-18 17:53 ` ✓ CI.Build: " Patchwork
2024-07-18 17:55 ` ✓ CI.Hooks: " Patchwork
2024-07-18 17:56 ` ✓ CI.checksparse: " Patchwork
2024-07-18 18:19 ` ✗ CI.BAT: failure " Patchwork
2024-07-18 18:42   ` Matthew Brost [this message]
2024-07-19  0:35 ` ✗ CI.FULL: " 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=ZpliI+lLtsV+ILfz@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@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