Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Don't disable interrupts and pretend a lock as been acquired in __timeline_mark_lock().

[Sebastian Andrzej Siewior <bigeasy@linutronix.de>]

On 2021-11-19 08:47:56 [-0000], Patchwork wrote:
> == Series Details ==
> 
> Series: drm/i915: Don't disable interrupts and pretend a lock as been acquired in __timeline_mark_lock().
> URL   : https://patchwork.freedesktop.org/series/97082/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_10900_full -> Patchwork_21633_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with Patchwork_21633_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_21633_full, please notify your bug team to allow them
>   to document this new failure mode, which will reduce false positives in CI.

My bug team?

> #### Possible regressions ####
> 
>   * igt@kms_vblank@pipe-b-query-forked-hang:
>     - shard-tglb:         [PASS][1] -> [INCOMPLETE][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10900/shard-tglb8/igt@kms_vblank@pipe-b-query-forked-hang.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21633/shard-tglb6/igt@kms_vblank@pipe-b-query-forked-hang.html

By comparing the two dmesg outputs I see that the INCOMPLETE ones stops,
while the PASS one continues with
|<7> [82.256394] heartbeat rcs0 heartbeat {seqno:5:7, prio:2147483646} not ticking

I cloned igt-gpu-tools and run 'kms_vblank' on my box. I was a little
surprised by the suspend part but the test passed here.

Sebastian