Re: ✗ Xe.CI.Full: failure for Cancel ongoing H2G requests when stopping CT

Michal Wajdeczko michal.wajdeczko at intel.com
Thu Jul 10 19:31:40 UTC 2025



On 09.07.2025 23:48, Patchwork wrote:
> == Series Details ==
> 
> Series: Cancel ongoing H2G requests when stopping CT
> URL   : https://patchwork.freedesktop.org/series/151406/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-3384-8cbc0224847589e88bb3ea0c00952c51e00f5bd6_FULL -> xe-pw-151406v1_FULL
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-151406v1_FULL absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-151406v1_FULL, please notify your bug team (I915-ci-infra at 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-151406v1_FULL:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####

unrelated

> 
>   * igt at kms_async_flips@test-time-stamp at pipe-b-dp-4:
>     - shard-dg2-set2:     NOTRUN -> [FAIL][1]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-151406v1/shard-dg2-434/igt@kms_async_flips@test-time-stamp@pipe-b-dp-4.html

kms_async_flips:7150) CRITICAL: Test assertion failure function
test_timestamp, file ../tests/kms_async_flips.c:537:
(kms_async_flips:7150) CRITICAL: Failed assertion: seq1 == seq + 1
(kms_async_flips:7150) CRITICAL: Vblank sequence is expected to be
incremented by one(6047 != (6041 + 1)

> 
>   * igt at xe_pm@s4-vm-bind-userptr:
>     - shard-dg2-set2:     NOTRUN -> [INCOMPLETE][2]
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-151406v1/shard-dg2-433/igt@xe_pm@s4-vm-bind-userptr.html

no logs, but it looks that device was lost after it already resumed,
while patch touches reset/suspend paths



More information about the Intel-xe mailing list