From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ CI.BAT: failure for drm/xe/pf: Sanitize VF scratch registers on FLR
Date: Thu, 5 Sep 2024 17:13:32 +0200 [thread overview]
Message-ID: <99291baf-3d11-40de-a18d-306d78be266b@intel.com> (raw)
In-Reply-To: <172530990530.908431.16385326892500773298@2413ebb6fbb6>
On 02.09.2024 22:45, Patchwork wrote:
> == Series Details ==
>
> Series: drm/xe/pf: Sanitize VF scratch registers on FLR
> URL : https://patchwork.freedesktop.org/series/138113/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-1879-0c71de2cc65c5f4ee75046f1c04fdf56ea7c5f30_BAT -> xe-pw-138113v1_BAT
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-138113v1_BAT absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-138113v1_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 (9 -> 9)
> ------------------------------
>
> No changes in participating hosts
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in xe-pw-138113v1_BAT:
>
> ### IGT changes ###
>
> #### Possible regressions ####
unrelated, series is about VF FLR, while "regression" is in KMS
>
> * igt@kms_addfb_basic@addfb25-4-tiled:
> - bat-lnl-1: [PASS][1] -> [DMESG-WARN][2] +2 other tests dmesg-warn
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1879-0c71de2cc65c5f4ee75046f1c04fdf56ea7c5f30/bat-lnl-1/igt@kms_addfb_basic@addfb25-4-tiled.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138113v1/bat-lnl-1/igt@kms_addfb_basic@addfb25-4-tiled.html
<6> [302.207037] xe 0000:00:02.0: [drm] GT0: Engine reset:
engine_class=bcs, logical_mask: 0x2, guc_id=0
<5> [302.207126] xe 0000:00:02.0: [drm] GT0: Timedout job:
seqno=4294967169, lrc_seqno=4294967169, guc_id=0, flags=0x13 in no
process [-1]
<6> [302.207883] xe 0000:00:02.0: [drm] Xe device coredump has been created
<6> [302.207885] xe 0000:00:02.0: [drm] Check your
/sys/class/drm/card0/device/devcoredump/data
<4> [302.208583] ------------[ cut here ]------------
<4> [302.208585] xe 0000:00:02.0: [drm] GT0: Kernel-submitted job timed out
<4> [302.208603] WARNING: CPU: 2 PID: 11 at
drivers/gpu/drm/xe/xe_guc_submit.c:1190
guc_exec_queue_timedout_job+0x8be/0xc00 [xe]
<7> [302.208643] xe 0000:00:02.0: [drm:drm_mode_addfb2 [drm]] [FB:190]
>
>
> Known issues
> ------------
>
> Here are the changes found in xe-pw-138113v1_BAT that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@kms_frontbuffer_tracking@basic:
> - bat-adlp-7: [PASS][3] -> [FAIL][4] ([Intel XE#1861])
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1879-0c71de2cc65c5f4ee75046f1c04fdf56ea7c5f30/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138113v1/bat-adlp-7/igt@kms_frontbuffer_tracking@basic.html
>
> * igt@xe_live_ktest@xe_bo:
> - bat-lnl-1: [PASS][5] -> [SKIP][6] ([Intel XE#1192]) +2 other tests skip
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1879-0c71de2cc65c5f4ee75046f1c04fdf56ea7c5f30/bat-lnl-1/igt@xe_live_ktest@xe_bo.html
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138113v1/bat-lnl-1/igt@xe_live_ktest@xe_bo.html
>
>
> #### Possible fixes ####
>
> * igt@kms_flip@basic-flip-vs-wf_vblank:
> - bat-lnl-1: [FAIL][7] ([Intel XE#886]) -> [PASS][8] +2 other tests pass
> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1879-0c71de2cc65c5f4ee75046f1c04fdf56ea7c5f30/bat-lnl-1/igt@kms_flip@basic-flip-vs-wf_vblank.html
> [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138113v1/bat-lnl-1/igt@kms_flip@basic-flip-vs-wf_vblank.html
>
>
> [Intel XE#1192]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1192
> [Intel XE#1861]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1861
> [Intel XE#886]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/886
>
>
> Build changes
> -------------
>
> * Linux: xe-1879-0c71de2cc65c5f4ee75046f1c04fdf56ea7c5f30 -> xe-pw-138113v1
>
> IGT_8001: d3a77fc98e89cc94b03be2b0903d44f83480b8a0 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> xe-1879-0c71de2cc65c5f4ee75046f1c04fdf56ea7c5f30: 0c71de2cc65c5f4ee75046f1c04fdf56ea7c5f30
> xe-pw-138113v1: 138113v1
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138113v1/index.html
>
next prev parent reply other threads:[~2024-09-05 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 19:29 [PATCH] drm/xe/pf: Sanitize VF scratch registers on FLR Michal Wajdeczko
2024-09-02 19:55 ` ✓ CI.Patch_applied: success for " Patchwork
2024-09-02 19:55 ` ✓ CI.checkpatch: " Patchwork
2024-09-02 19:56 ` ✓ CI.KUnit: " Patchwork
2024-09-02 20:08 ` ✓ CI.Build: " Patchwork
2024-09-02 20:10 ` ✓ CI.Hooks: " Patchwork
2024-09-02 20:12 ` ✓ CI.checksparse: " Patchwork
2024-09-02 20:45 ` ✗ CI.BAT: failure " Patchwork
2024-09-05 15:13 ` Michal Wajdeczko [this message]
2024-09-03 3:23 ` ✗ CI.FULL: " Patchwork
2024-09-05 16:07 ` Michal Wajdeczko
2024-09-04 12:31 ` [PATCH] " Piotr Piórkowski
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=99291baf-3d11-40de-a18d-306d78be266b@intel.com \
--to=michal.wajdeczko@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