Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org, Tomasz Lis <tomasz.lis@intel.com>,
	"Nilawar, Badal" <badal.nilawar@intel.com>
Subject: Re: ✗ CI.FULL: failure for drm/xe/vf: Post-migration recovery, remove MMIO assert
Date: Sat, 9 Nov 2024 15:05:17 +0100	[thread overview]
Message-ID: <c64c6a2a-99fb-4312-9e92-980a9577bb73@intel.com> (raw)
In-Reply-To: <173110416572.1446338.12338028984883774965@2413ebb6fbb6>



On 08.11.2024 23:16, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe/vf: Post-migration recovery, remove MMIO assert
> URL   : https://patchwork.freedesktop.org/series/141058/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-2181-6f358787ded211657532e2ee4df2e446b03d860f_full -> xe-pw-141058v1_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-141058v1_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-141058v1_full, 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 (4 -> 4)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in xe-pw-141058v1_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 

all unrelated, 2x KMS

>   * igt@kms_rotation_crc@primary-y-tiled-reflect-x-90:
>     - shard-dg2-set2:     NOTRUN -> [SKIP][1]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141058v1/shard-dg2-466/igt@kms_rotation_crc@primary-y-tiled-reflect-x-90.html
> 
>   * igt@kms_vblank@query-forked-hang@pipe-d-dp-2:
>     - shard-bmg:          [PASS][2] -> [INCOMPLETE][3] +1 other test incomplete
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2181-6f358787ded211657532e2ee4df2e446b03d860f/shard-bmg-2/igt@kms_vblank@query-forked-hang@pipe-d-dp-2.html
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141058v1/shard-bmg-5/igt@kms_vblank@query-forked-hang@pipe-d-dp-2.html
> 
>   * igt@xe_gt_freq@freq_low_max:
>     - shard-lnl:          [PASS][4] -> [DMESG-WARN][5]
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2181-6f358787ded211657532e2ee4df2e446b03d860f/shard-lnl-6/igt@xe_gt_freq@freq_low_max.html
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-141058v1/shard-lnl-5/igt@xe_gt_freq@freq_low_max.html

<4> [431.075162] xe 0000:00:02.0: [drm] GT0: G2H fence 7262, action
3003, done
<4> [432.455310] xe 0000:00:02.0: [drm] GT0: G2H fence 7263, action
3003, done

due to warn added in commit e51527233804 ("drm/xe/guc/ct: Flush g2h
worker in case of g2h response timeout")

@Badal, maybe this should be just xe_gt_dbg() ?



      reply	other threads:[~2024-11-09 14:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 15:13 [PATCH v1 0/1] drm/xe/vf: Post-migration recovery, remove MMIO assert Tomasz Lis
2024-11-07 15:13 ` [PATCH v1 1/1] drm/xe/guc: Do not assert CTB state while sending MMIO Tomasz Lis
2024-11-07 16:56   ` Michal Wajdeczko
2024-11-08  3:04     ` Matthew Brost
2024-11-09 14:19       ` Michal Wajdeczko
2024-11-07 15:20 ` ✓ CI.Patch_applied: success for drm/xe/vf: Post-migration recovery, remove MMIO assert Patchwork
2024-11-07 15:20 ` ✓ CI.checkpatch: " Patchwork
2024-11-07 15:22 ` ✓ CI.KUnit: " Patchwork
2024-11-07 15:41 ` ✓ CI.Build: " Patchwork
2024-11-07 15:43 ` ✓ CI.Hooks: " Patchwork
2024-11-07 15:44 ` ✓ CI.checksparse: " Patchwork
2024-11-07 16:25 ` ✓ CI.BAT: " Patchwork
2024-11-08 22:16 ` ✗ CI.FULL: failure " Patchwork
2024-11-09 14:05   ` Michal Wajdeczko [this message]

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=c64c6a2a-99fb-4312-9e92-980a9577bb73@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=tomasz.lis@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