From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ CI.BAT: failure for Introduce GuC Doorbells Manager (rev2)
Date: Mon, 11 Dec 2023 19:49:48 +0100 [thread overview]
Message-ID: <d5e452bf-1781-4700-affd-0e0c5abc62d8@intel.com> (raw)
In-Reply-To: <170229286726.19580.2092829560447676100@emeril.freedesktop.org>
On 11.12.2023 12:07, Patchwork wrote:
> == Series Details ==
>
> Series: Introduce GuC Doorbells Manager (rev2)
> URL : https://patchwork.freedesktop.org/series/127608/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-566-00175313322325f73095e61b6cbe550f47184408_BAT -> xe-pw-127608v2_BAT
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-127608v2_BAT absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-127608v2_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 (4 -> 4)
> ------------------------------
>
> No changes in participating hosts
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in xe-pw-127608v2_BAT:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@core_hotunplug@unbind-rebind:
> - bat-adlp-7: [PASS][1] -> [INCOMPLETE][2]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-566-00175313322325f73095e61b6cbe550f47184408/bat-adlp-7/igt@core_hotunplug@unbind-rebind.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-127608v2/bat-adlp-7/igt@core_hotunplug@unbind-rebind.html
oops. I was mislead by the below "known issues" but unfortunately this
is a legit regression due to attempt to use submit.lock in __fini_dbm()
but this lock was already released due to order of init functions:
xe_guc_db_mgr_init() is before xe_guc_submit_init().
>
>
> Known issues
> ------------
>
> Here are the changes found in xe-pw-127608v2_BAT that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@core_hotunplug@unbind-rebind:
> - bat-dg2-oem2: [PASS][3] -> [INCOMPLETE][4] ([Intel XE#764])
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-566-00175313322325f73095e61b6cbe550f47184408/bat-dg2-oem2/igt@core_hotunplug@unbind-rebind.html
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-127608v2/bat-dg2-oem2/igt@core_hotunplug@unbind-rebind.html
> - bat-atsm-2: [PASS][5] -> [INCOMPLETE][6] ([Intel XE#764])
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-566-00175313322325f73095e61b6cbe550f47184408/bat-atsm-2/igt@core_hotunplug@unbind-rebind.html
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-127608v2/bat-atsm-2/igt@core_hotunplug@unbind-rebind.html
>
> * igt@xe_prime_self_import@basic-with_fd_dup:
> - bat-atsm-2: [PASS][7] -> [FAIL][8] ([Intel XE#999])
> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-566-00175313322325f73095e61b6cbe550f47184408/bat-atsm-2/igt@xe_prime_self_import@basic-with_fd_dup.html
> [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-127608v2/bat-atsm-2/igt@xe_prime_self_import@basic-with_fd_dup.html
>
>
> [Intel XE#764]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/764
> [Intel XE#999]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/999
>
>
> Build changes
> -------------
>
> * Linux: xe-566-00175313322325f73095e61b6cbe550f47184408 -> xe-pw-127608v2
>
> IGT_7632: 3fff86827c4728708072b9accbc990fa1084c95d @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> xe-566-00175313322325f73095e61b6cbe550f47184408: 00175313322325f73095e61b6cbe550f47184408
> xe-pw-127608v2: 127608v2
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-127608v2/index.html
>
prev parent reply other threads:[~2023-12-11 18:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 10:17 [PATCH v2 0/9] Introduce GuC Doorbells Manager Michal Wajdeczko
2023-12-11 10:17 ` [PATCH v2 1/9] drm/xe: Add GT oriented drm_printers Michal Wajdeczko
2023-12-11 10:17 ` [PATCH v2 2/9] drm/xe: Use GT oriented functions to report TLB timeout Michal Wajdeczko
2023-12-11 10:17 ` [PATCH v2 3/9] drm/xe: Introduce GuC Doorbells Manager Michal Wajdeczko
2023-12-11 10:17 ` [PATCH v2 4/9] drm/xe/kunit: Set SR-IOV mode of the fake device Michal Wajdeczko
2023-12-11 10:17 ` [PATCH v2 5/9] drm/xe/kunit: Define helper functions to allocate mock device Michal Wajdeczko
2023-12-11 10:17 ` [PATCH v2 6/9] drm/xe/kunit: Use xe kunit helpers in RTP test Michal Wajdeczko
2023-12-11 10:17 ` [PATCH v2 7/9] drm/xe/kunit: Use xe kunit helpers in WA test Michal Wajdeczko
2023-12-11 10:17 ` [PATCH v2 8/9] drm/xe/kunit: Enable CONFIG_LOCKDEP in tests Michal Wajdeczko
2023-12-11 10:17 ` [PATCH v2 9/9] drm/xe/kunit: Add GuC Doorbells Manager tests Michal Wajdeczko
2023-12-11 10:20 ` ✓ CI.Patch_applied: success for Introduce GuC Doorbells Manager (rev2) Patchwork
2023-12-11 10:20 ` ✗ CI.checkpatch: warning " Patchwork
2023-12-11 10:21 ` ✓ CI.KUnit: success " Patchwork
2023-12-11 10:29 ` ✓ CI.Build: " Patchwork
2023-12-11 10:29 ` ✓ CI.Hooks: " Patchwork
2023-12-11 10:30 ` ✓ CI.checksparse: " Patchwork
2023-12-11 11:07 ` ✗ CI.BAT: failure " Patchwork
2023-12-11 18:49 ` 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=d5e452bf-1781-4700-affd-0e0c5abc62d8@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