Re: ✗ CI.FULL: failure for PF: threshold config fixes

[Michal Wajdeczko]

On 31.08.2024 04:41, Patchwork wrote:
> == Series Details ==
> 
> Series: PF: threshold config fixes
> URL   : https://patchwork.freedesktop.org/series/138023/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-1867-876db6b8ef45d285316cc53b5cf44cbc39aa8758_full -> xe-pw-138023v1_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-138023v1_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-138023v1_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-138023v1_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt at xe_vm@munmap-style-unbind-userptr-one-partial:
>     - shard-dg2-set2:     [PASS][1] -> [DMESG-WARN][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1867-876db6b8ef45d285316cc53b5cf44cbc39aa8758/shard-dg2-434/igt@xe_vm@munmap-style-unbind-userptr-one-partial.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138023v1/shard-dg2-433/igt@xe_vm@munmap-style-unbind-userptr-one-partial.html

<3> [196.507166] xe 0000:03:00.0: [drm] *ERROR* GT0: GuC PC Start failed
<4> [196.507215] ------------[ cut here ]------------
<4> [196.507217] xe 0000:03:00.0: [drm] GT0: Failed to start GuC PC: -EIO
<4> [196.507231] WARNING: CPU: 11 PID: 1715 at
drivers/gpu/drm/xe/xe_guc.c:1138 xe_guc_start+0xa3/0x1b0 [xe]
<4> [196.507377] Workqueue: gt-ordered-wq gt_reset_worker [xe]
<4> [196.507427] RIP: 0010:xe_guc_start+0xa3/0x1b0 [xe]
<4> [196.507480] Call Trace:
<4> [196.507481]  <TASK>
<4> [196.507483]  ? show_regs+0x67/0x70
<4> [196.507487]  ? __warn+0x94/0x1b0
<4> [196.507490]  ? xe_guc_start+0xa3/0x1b0 [xe]
<4> [196.507527]  ? report_bug+0x1b7/0x1d0
<4> [196.507531]  ? handle_bug+0x46/0x80
<4> [196.507533]  ? exc_invalid_op+0x19/0x70
<4> [196.507535]  ? asm_exc_invalid_op+0x1b/0x20
<4> [196.507539]  ? xe_guc_start+0xa3/0x1b0 [xe]
<4> [196.507576]  ? cancel_work_sync+0x10/0x20
<4> [196.507579]  xe_uc_start+0x28/0x30 [xe]
<4> [196.507635]  do_gt_restart+0x110/0x670 [xe]

and this looks exactly as #2559

> 
>   
> #### Suppressed ####
> 
>   The following results come from untrusted machines, tests, or statuses.
>   They do not affect the overall result.
> 
>   * igt at kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-pgflip-blt:
>     - {shard-bmg}:        [FAIL][3] ([Intel XE#2333]) -> [INCOMPLETE][4]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-1867-876db6b8ef45d285316cc53b5cf44cbc39aa8758/shard-bmg-3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-pgflip-blt.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138023v1/shard-bmg-8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-pgflip-blt.html
> 
>   * igt at xe_vm:
>     - {shard-bmg}:        NOTRUN -> [INCOMPLETE][5]
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-138023v1/shard-bmg-4/igt@xe_vm.html
> 
>