Re: ✗ Xe.CI.FULL: failure for drm/xe/memirq: Update interrupt handler logic

[Michal Wajdeczko <michal.wajdeczko@intel.com>]

On 5/12/2026 12:07 PM, Patchwork wrote:
> *Patch Details*
> *Series:*	drm/xe/memirq: Update interrupt handler logic
> *URL:*	https://patchwork.freedesktop.org/series/166351/ <https://patchwork.freedesktop.org/series/166351/>
> *State:*	failure
> *Details:*	https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-166351v1/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-166351v1/index.html>
> 
> 
>   CI Bug Log - changes from xe-5043-0ce1c813197dfbe15ff14143da97ec11161e1795_FULL -> xe-pw-166351v1_FULL
> 
> 
>     Summary
> 
> *FAILURE*
> 
> Serious unknown changes coming with xe-pw-166351v1_FULL absolutely need to be
> verified manually.
> 
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-166351v1_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 (2 -> 2)
> 
> No changes in participating hosts
> 
> 
>     Possible new issues
> 
> Here are the unknown changes that may have been introduced in xe-pw-166351v1_FULL:
> 
> 
>       IGT changes
> 
> 
>         Possible regressions

all unrelated (KMS or non-VF mode)

> 
>   *
> 
>     igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic:
> 
>       o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-5043-0ce1c813197dfbe15ff14143da97ec11161e1795/shard-bmg-3/igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic.html> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-166351v1/shard-bmg-2/igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic.html>


<4> [159.232535] xe 0000:03:00.0: [drm] vblank wait timed out on crtc 0


>   *
> 
>     igt@xe_exec_reset@long-spin-comp-reuse-many-preempt-threads:
> 
>       o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-5043-0ce1c813197dfbe15ff14143da97ec11161e1795/shard-bmg-6/igt@xe_exec_reset@long-spin-comp-reuse-many-preempt-threads.html> -> FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-166351v1/shard-bmg-4/igt@xe_exec_reset@long-spin-comp-reuse-many-preempt-threads.html>

(xe_exec_reset:5234) [thread:5236] xe/xe_ioctl-CRITICAL: Test assertion failure function xe_exec, file ../lib/xe/xe_ioctl.c:652:
(xe_exec_reset:5234) [thread:5236] xe/xe_ioctl-CRITICAL: Failed assertion: __xe_exec(fd, exec) == 0
(xe_exec_reset:5234) [thread:5236] xe/xe_ioctl-CRITICAL: error: -125 != 0


>   *
> 
>     igt@xe_fault_injection@vm-bind-fail-vm_bind_ioctl_ops_execute:
> 
>       o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-5043-0ce1c813197dfbe15ff14143da97ec11161e1795/shard-bmg-6/igt@xe_fault_injection@vm-bind-fail-vm_bind_ioctl_ops_execute.html> -> ABORT <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-166351v1/shard-bmg-4/igt@xe_fault_injection@vm-bind-fail-vm_bind_ioctl_ops_execute.html>

<4> [317.960612]  slab kmalloc-rnd-01-512 start ffff8881a10f1800 data offset 512 pointer offset 0 size 512 allocated at xe_guc_capture_steered_list_init+0x673/0x840 [xe]
<6> [317.960721]     drmm_kmalloc+0x3c/0x100
<6> [317.960725]     xe_guc_capture_steered_list_init+0x673/0x840 [xe]
<6> [317.960805]     xe_guc_ads_populate+0x6d6/0x2100 [xe]
<6> [317.960883]     xe_guc_upload+0x19/0x70 [xe]
<6> [317.960958]     xe_uc_load_hw+0x86/0x2a0 [xe]
<6> [317.961093]     xe_gt_init+0x3ae/0xdd0 [xe]
<6> [317.961268]     xe_device_probe+0x32e/0xc10 [xe]
<6> [317.961391]     xe_pci_probe+0x39b/0x620 [xe]
<6> [317.961527]     local_pci_probe+0x47/0xb0
<6> [317.961532]     pci_call_probe+0x6c/0x360
<6> [317.961535]     pci_device_probe+0xa9/0x140
<6> [317.961538]     really_probe+0xf1/0x410
<6> [317.961542]     __driver_probe_device+0x9f/0x1d0
<6> [317.961545]     device_driver_attach+0x57/0xd0
<6> [317.961548]     bind_store+0x77/0xd0
<6> [317.961550]     drv_attr_store+0x24/0x50
<4> [317.961554] ------------[ cut here ]------------
<4> [317.961556] list_del corruption. next->prev should be ffff88817ed4b640, but was 0000000000000000. (next=ffff8881a10f1a00)