From: Andrzej Hajda <andrzej.hajda@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gt: Hold a wakeref for the active VM (rev2)
Date: Mon, 3 Apr 2023 10:58:13 +0200 [thread overview]
Message-ID: <efdd1c4c-8545-76c9-e0b4-05af2b0b4f5e@intel.com> (raw)
In-Reply-To: <168037214477.8633.716359384690927545@emeril.freedesktop.org>
[-- Attachment #1: Type: text/plain, Size: 9652 bytes --]
On 01.04.2023 20:02, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* drm/i915/gt: Hold a wakeref for the active VM (rev2)
> *URL:* https://patchwork.freedesktop.org/series/115873/
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/index.html
>
>
> CI Bug Log - changes from CI_DRM_12951_full -> Patchwork_115873v2_full
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_115873v2_full absolutely
> need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_115873v2_full, please notify your bug team 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
> Patchwork_115873v2_full:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@gem_exec_fence@syncobj-repeat:
> o shard-glk: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-glk5/igt@gem_exec_fence@syncobj-repeat.html>
> -> TIMEOUT
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-glk9/igt@gem_exec_fence@syncobj-repeat.html>
> +2 similar issues
>
The actual test did not even start, because of failure on previous tests.
All tests since igt@perf@enable-disable@0-rcs0 timeouts on this machine[1].
Since igt@perf@enable-disable is untrusted/suppressed I guess it is not
related.
Moreover v1(which differs only by comment) passed.
Summarizing apparently known bug in igt@perf@subtests [2].
[1]:
http://gfx-ci.igk.intel.com/tree/drm-tip/Patchwork_115873v2/shard-glk9/igt_runner13.txt
[2]: https://gitlab.freedesktop.org/drm/intel/-/issues/5213
Regards
Andrzej
> *
>
>
> Warnings
>
> * igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-pwrite:
>
> o shard-glk: SKIP
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-glk5/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-pwrite.html>
> (fdo#109271
> <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) ->
> TIMEOUT
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-glk9/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-pwrite.html>
> +2 similar issues
>
>
> Suppressed
>
> The following results come from untrusted machines, tests, or statuses.
> They do not affect the overall result.
>
> * {igt@perf@enable-disable@0-rcs0}:
> o shard-glk: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-glk5/igt@perf@enable-disable@0-rcs0.html>
> -> TIMEOUT
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-glk9/igt@perf@enable-disable@0-rcs0.html>
>
>
> Known issues
>
> Here are the changes found in Patchwork_115873v2_full that come from
> known issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@gem_exec_fair@basic-deadline:
>
> o shard-glk: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-glk9/igt@gem_exec_fair@basic-deadline.html>
> -> FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-glk8/igt@gem_exec_fair@basic-deadline.html>
> (i915#2846 <https://gitlab.freedesktop.org/drm/intel/issues/2846>)
> *
>
> igt@gen9_exec_parse@allowed-single:
>
> o shard-apl: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-apl7/igt@gen9_exec_parse@allowed-single.html>
> -> ABORT
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-apl3/igt@gen9_exec_parse@allowed-single.html>
> (i915#5566 <https://gitlab.freedesktop.org/drm/intel/issues/5566>)
> *
>
> igt@i915_selftest@live@gt_heartbeat:
>
> o shard-apl: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-apl1/igt@i915_selftest@live@gt_heartbeat.html>
> -> DMESG-FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-apl2/igt@i915_selftest@live@gt_heartbeat.html>
> (i915#5334 <https://gitlab.freedesktop.org/drm/intel/issues/5334>)
> *
>
> igt@kms_async_flips@alternate-sync-async-flip@pipe-a-vga-1:
>
> o shard-snb: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-snb5/igt@kms_async_flips@alternate-sync-async-flip@pipe-a-vga-1.html>
> -> FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-snb2/igt@kms_async_flips@alternate-sync-async-flip@pipe-a-vga-1.html>
> (i915#2521 <https://gitlab.freedesktop.org/drm/intel/issues/2521>)
> *
>
> igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
>
> o shard-glk: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-glk1/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html>
> -> FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-glk2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html>
> (i915#2346 <https://gitlab.freedesktop.org/drm/intel/issues/2346>)
> *
>
> igt@kms_flip@flip-vs-expired-vblank@b-dp1:
>
> o shard-apl: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-apl4/igt@kms_flip@flip-vs-expired-vblank@b-dp1.html>
> -> FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-apl7/igt@kms_flip@flip-vs-expired-vblank@b-dp1.html>
> (i915#79 <https://gitlab.freedesktop.org/drm/intel/issues/79>)
> *
>
> igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes:
>
> o shard-apl: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-apl7/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes.html>
> -> ABORT
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-apl3/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes.html>
> (i915#180 <https://gitlab.freedesktop.org/drm/intel/issues/180>)
>
>
> Possible fixes
>
> *
>
> igt@gem_ctx_exec@basic-nohangcheck:
>
> o {shard-tglu}: FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-tglu-2/igt@gem_ctx_exec@basic-nohangcheck.html>
> (i915#6268
> <https://gitlab.freedesktop.org/drm/intel/issues/6268>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-tglu-10/igt@gem_ctx_exec@basic-nohangcheck.html>
> *
>
> igt@gem_eio@in-flight-contexts-1us:
>
> o {shard-tglu}: TIMEOUT
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-tglu-7/igt@gem_eio@in-flight-contexts-1us.html>
> (i915#3063
> <https://gitlab.freedesktop.org/drm/intel/issues/3063>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-tglu-3/igt@gem_eio@in-flight-contexts-1us.html>
> *
>
> igt@gem_eio@reset-stress:
>
> o {shard-dg1}: FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-dg1-14/igt@gem_eio@reset-stress.html>
> (i915#5784
> <https://gitlab.freedesktop.org/drm/intel/issues/5784>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-dg1-15/igt@gem_eio@reset-stress.html>
> *
>
> igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic:
>
> o shard-glk: FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-glk1/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html>
> (i915#72 <https://gitlab.freedesktop.org/drm/intel/issues/72>)
> -> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-glk2/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html>
> *
>
> igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
>
> o
>
> shard-apl: FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-apl2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html>
> (i915#2346
> <https://gitlab.freedesktop.org/drm/intel/issues/2346>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-apl6/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html>
>
> o
>
> shard-glk: FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12951/shard-glk2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html>
> (i915#2346
> <https://gitlab.freedesktop.org/drm/intel/issues/2346>) ->
> PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115873v2/shard-glk4/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html>
>
> {name}: This element is suppressed. This means it is ignored when
> computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
>
> Build changes
>
> * Linux: CI_DRM_12951 -> Patchwork_115873v2
>
> CI-20190529: 20190529
> CI_DRM_12951: f128906b94b25a0f0c12dc8c647b8adc8d934d8c @
> git://anongit.freedesktop.org/gfx-ci/linux
> IGT_7230: f0485204004305dd3ee8f8bbbb9c552e53a4e050 @
> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> Patchwork_115873v2: f128906b94b25a0f0c12dc8c647b8adc8d934d8c @
> git://anongit.freedesktop.org/gfx-ci/linux
> piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @
> git://anongit.freedesktop.org/piglit
>
[-- Attachment #2: Type: text/html, Size: 14934 bytes --]
next prev parent reply other threads:[~2023-04-03 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 14:16 [Intel-gfx] [PATCH v2] drm/i915/gt: Hold a wakeref for the active VM Andrzej Hajda
2023-03-31 14:51 ` Tvrtko Ursulin
2023-03-31 17:23 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt: Hold a wakeref for the active VM (rev2) Patchwork
2023-03-31 17:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-01 18:02 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-04-03 8:58 ` Andrzej Hajda [this message]
2023-04-04 15:39 ` [Intel-gfx] [PATCH v2] drm/i915/gt: Hold a wakeref for the active VM Andi Shyti
2023-04-04 15:57 ` Tvrtko Ursulin
2023-04-04 16:00 ` Andi Shyti
2023-04-04 16:22 ` Tvrtko Ursulin
2023-04-04 16:29 ` Andi Shyti
2023-04-05 14:16 ` Andrzej Hajda
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=efdd1c4c-8545-76c9-e0b4-05af2b0b4f5e@intel.com \
--to=andrzej.hajda@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