intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for drm/i915/dp_mst: Disable Panel Replay
Date: Mon, 10 Nov 2025 17:17:54 +0200	[thread overview]
Message-ID: <aRICIjw_j4UzO7eD@ideak-desk> (raw)
In-Reply-To: <176265146623.33229.14392217448285890815@10055242dc62>

Hi Matthew,

could you check the failure below?

On Sun, Nov 09, 2025 at 01:24:26AM +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/i915/dp_mst: Disable Panel Replay
> URL   : https://patchwork.freedesktop.org/series/157224/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160_FULL -> xe-pw-157224v1_FULL
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-157224v1_FULL absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-157224v1_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-157224v1_FULL:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_big_fb@linear-max-hw-stride-32bpp-rotate-0:
>     - shard-adlp:         NOTRUN -> [ABORT][1] +5 other tests abort
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-3/igt@kms_big_fb@linear-max-hw-stride-32bpp-rotate-0.html

It's a memory corruption detected in drm_syncobj_create() AFAICS when
kmallocing a drm_syncobj object. Since the corruption is a 0x6a value
instead of the expected 0x6b object-free-marker value in the first byte
of the object, this looks like a drm_syncobj refcounting issue, i.e. an
extra drm_syncobj_put() somewhere (or lack of a corresponding get).

The issue is not related to change in the patch, but since I checked the
error and noticed your recent "drm/xe: Enforce correct user fence
signaling order using" commit, thought you may have an idea of the root
cause. In the recent CI runs I don't see the issue any more, so it
could've been also fixed already.

>   * igt@kms_flip@nonexisting-fb-interruptible@c-hdmi-a1:
>     - shard-adlp:         NOTRUN -> [DMESG-WARN][2] +1 other test dmesg-warn
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-4/igt@kms_flip@nonexisting-fb-interruptible@c-hdmi-a1.html
> 
>   * igt@kms_frontbuffer_tracking@psr-slowdraw:
>     - shard-dg2-set2:     NOTRUN -> [ABORT][3]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-dg2-435/igt@kms_frontbuffer_tracking@psr-slowdraw.html
> 
>   * igt@xe_evict@evict-small-external:
>     - shard-dg2-set2:     [PASS][4] -> [ABORT][5]
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-dg2-436/igt@xe_evict@evict-small-external.html
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-dg2-436/igt@xe_evict@evict-small-external.html
> 
>   * igt@xe_exec_system_allocator@many-stride-mmap-shared-nomemset:
>     - shard-bmg:          NOTRUN -> [ABORT][6] +2 other tests abort
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-bmg-7/igt@xe_exec_system_allocator@many-stride-mmap-shared-nomemset.html
> 
>   * igt@xe_exec_system_allocator@threads-many-stride-malloc-fork-read-after:
>     - shard-bmg:          [PASS][7] -> [ABORT][8] +2 other tests abort
>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-bmg-6/igt@xe_exec_system_allocator@threads-many-stride-malloc-fork-read-after.html
>    [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-bmg-5/igt@xe_exec_system_allocator@threads-many-stride-malloc-fork-read-after.html
> 
>   * igt@xe_module_load@reload-no-display:
>     - shard-lnl:          [PASS][9] -> [ABORT][10] +2 other tests abort
>    [9]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-lnl-1/igt@xe_module_load@reload-no-display.html
>    [10]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-lnl-5/igt@xe_module_load@reload-no-display.html
> 
>   
> #### Warnings ####
> 
>   * igt@kms_big_fb@linear-32bpp-rotate-90:
>     - shard-adlp:         [SKIP][11] ([Intel XE#316]) -> [ABORT][12]
>    [11]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-adlp-3/igt@kms_big_fb@linear-32bpp-rotate-90.html
>    [12]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-8/igt@kms_big_fb@linear-32bpp-rotate-90.html
> 
>   * igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs:
>     - shard-dg2-set2:     [SKIP][13] ([Intel XE#455] / [Intel XE#787]) -> [ABORT][14]
>    [13]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-dg2-434/igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs.html
>    [14]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-dg2-433/igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs.html
> 
>   * igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs@pipe-a-hdmi-a-6:
>     - shard-dg2-set2:     [SKIP][15] ([Intel XE#787]) -> [ABORT][16]
>    [15]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-dg2-434/igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs@pipe-a-hdmi-a-6.html
>    [16]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-dg2-433/igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs@pipe-a-hdmi-a-6.html
> 
>   * igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-cur-indfb-move:
>     - shard-bmg:          [SKIP][17] ([Intel XE#2312]) -> [ABORT][18]
>    [17]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-bmg-6/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-cur-indfb-move.html
>    [18]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-bmg-7/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-cur-indfb-move.html
> 
>   * igt@kms_frontbuffer_tracking@psr-slowdraw:
>     - shard-adlp:         [SKIP][19] ([Intel XE#653]) -> [ABORT][20]
>    [19]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-adlp-4/igt@kms_frontbuffer_tracking@psr-slowdraw.html
>    [20]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-9/igt@kms_frontbuffer_tracking@psr-slowdraw.html
> 
>   * igt@xe_exec_system_allocator@process-many-large-mmap-new-race-nomemset:
>     - shard-adlp:         [SKIP][21] ([Intel XE#4915]) -> [ABORT][22]
>    [21]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-adlp-8/igt@xe_exec_system_allocator@process-many-large-mmap-new-race-nomemset.html
>    [22]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-6/igt@xe_exec_system_allocator@process-many-large-mmap-new-race-nomemset.html
> 
>   
> Known issues
> ------------
> 
>   Here are the changes found in xe-pw-157224v1_FULL that come from known issues:
> 
> ### IGT changes ###
> 
> #### Issues hit ####
> 
>   * igt@kms_chamelium_frames@hdmi-crc-planes-random:
>     - shard-adlp:         NOTRUN -> [SKIP][23] ([Intel XE#373])
>    [23]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-2/igt@kms_chamelium_frames@hdmi-crc-planes-random.html
> 
>   * igt@kms_frontbuffer_tracking@drrs-1p-primscrn-spr-indfb-fullscreen:
>     - shard-adlp:         NOTRUN -> [SKIP][24] ([Intel XE#651])
>    [24]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-3/igt@kms_frontbuffer_tracking@drrs-1p-primscrn-spr-indfb-fullscreen.html
> 
>   * igt@xe_evict_ccs@evict-overcommit-standalone-instantfree-reopen:
>     - shard-adlp:         NOTRUN -> [SKIP][25] ([Intel XE#688])
>    [25]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-3/igt@xe_evict_ccs@evict-overcommit-standalone-instantfree-reopen.html
> 
>   * igt@xe_exec_system_allocator@many-stride-mmap-prefetch:
>     - shard-adlp:         NOTRUN -> [SKIP][26] ([Intel XE#4915]) +6 other tests skip
>    [26]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-4/igt@xe_exec_system_allocator@many-stride-mmap-prefetch.html
> 
>   * igt@xe_oa@unprivileged-single-ctx-counters:
>     - shard-adlp:         NOTRUN -> [SKIP][27] ([Intel XE#3573])
>    [27]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-3/igt@xe_oa@unprivileged-single-ctx-counters.html
> 
>   * igt@xe_vm@out-of-memory:
>     - shard-adlp:         NOTRUN -> [SKIP][28] ([Intel XE#5745])
>    [28]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-3/igt@xe_vm@out-of-memory.html
> 
>   
> #### Possible fixes ####
> 
>   * igt@xe_vm@compact-64k-pages:
>     - shard-adlp:         [ABORT][29] -> [PASS][30] +4 other tests pass
>    [29]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-adlp-9/igt@xe_vm@compact-64k-pages.html
>    [30]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-3/igt@xe_vm@compact-64k-pages.html
> 
>   * igt@xe_vm@mixed-userptr-binds-3145728:
>     - shard-bmg:          [ABORT][31] -> [PASS][32]
>    [31]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-bmg-1/igt@xe_vm@mixed-userptr-binds-3145728.html
>    [32]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-bmg-8/igt@xe_vm@mixed-userptr-binds-3145728.html
> 
>   * igt@xe_vm@unbind-all-2-vmas:
>     - shard-dg2-set2:     [ABORT][33] -> [PASS][34]
>    [33]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-dg2-466/igt@xe_vm@unbind-all-2-vmas.html
>    [34]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-dg2-435/igt@xe_vm@unbind-all-2-vmas.html
> 
>   
> #### Warnings ####
> 
>   * igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs:
>     - shard-adlp:         [ABORT][35] -> [SKIP][36] ([Intel XE#455] / [Intel XE#787])
>    [35]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-adlp-4/igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs.html
>    [36]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-2/igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs.html
> 
>   * igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs@pipe-a-hdmi-a-1:
>     - shard-adlp:         [ABORT][37] -> [SKIP][38] ([Intel XE#787])
>    [37]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160/shard-adlp-4/igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs@pipe-a-hdmi-a-1.html
>    [38]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/shard-adlp-2/igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs@pipe-a-hdmi-a-1.html
> 
>   
>   [Intel XE#2312]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2312
>   [Intel XE#316]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/316
>   [Intel XE#3573]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/3573
>   [Intel XE#373]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/373
>   [Intel XE#455]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/455
>   [Intel XE#4915]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4915
>   [Intel XE#5745]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/5745
>   [Intel XE#651]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/651
>   [Intel XE#653]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/653
>   [Intel XE#688]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/688
>   [Intel XE#787]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/787
> 
> 
> Build changes
> -------------
> 
>   * Linux: xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160 -> xe-pw-157224v1
> 
>   IGT_8613: b542242f5b116e3b554b4068ef5dfa4451075b2b @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>   xe-4068-35cd059ed9ec8f39c25a160137ba85a150349160: 35cd059ed9ec8f39c25a160137ba85a150349160
>   xe-pw-157224v1: 157224v1
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157224v1/index.html

      reply	other threads:[~2025-11-10 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 12:41 [PATCH] drm/i915/dp_mst: Disable Panel Replay Imre Deak
2025-11-07 13:54 ` Hogander, Jouni
2025-11-07 14:00 ` ✓ CI.KUnit: success for " Patchwork
2025-11-07 14:57 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-11-09  1:24 ` ✗ Xe.CI.Full: " Patchwork
2025-11-10 15:17   ` Imre Deak [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=aRICIjw_j4UzO7eD@ideak-desk \
    --to=imre.deak@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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;
as well as URLs for NNTP newsgroup(s).