[CI][SHARDS] igt@kms_frontbuffer_tracking@(fpcpsr|psr)-* - incomplete - no good logs
Submitted by Martin Peres @mupuf
Assigned to Intel GFX Bugs mailing list
Link to original bug (#106978)
Description
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_67/fi-skl-6700hq/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-pwrite.html
Unfortunately, the logs don't contain anything that looks useful to me:
<0>[ 416.098437] perf_pmu-1635 5.... 383392595us : reset_all_global_seqno.part.5: bcs0 seqno 0 (current 0) -> 0
<0>[ 416.098473] perf_pmu-1635 5.... 383392598us : reset_all_global_seqno.part.5: vcs0 seqno 0 (current 0) -> 0
<0>[ 416.098509] perf_pmu-1635 5.... 383392601us : reset_all_global_seqno.part.5: vecs0 seqno 0 (current 0) -> 0
<0>[ 416.098545] perf_pmu-1635 5.... 383392691us : i915_gem_wait_for_idle: flags=3 (locked)
<0>[ 416.098581] perf_pmu-1635 5.... 383392903us : i915_gem_wait_for_idle: flags=3 (locked)
<0>[ 416.098616] perf_pmu-1635 5.... 383392994us : i915_gem_wait_for_idle: flags=3 (locked)
<0>[ 416.098651] gem_exec-1638 2.... 383507823us : i915_gem_wait_for_idle: flags=3 (locked)
<0>[ 416.098685] gem_exec-1638 2.... 383508318us : i915_gem_wait_for_idle: flags=3 (locked)
<0>[ 416.098722] gem_exec-1638 2.... 383508320us : reset_all_global_seqno.part.5: rcs0 seqno 0 (current 0) -> 0
<0>[ 416.098759] gem_exec-1638 2.... 383508501us : reset_all_global_seqno.part.5: bcs0 seqno 0 (current 0) -> 0
<0>[ 416.098796] gem_exec-1638 2.... 383508507us : reset_all_global_seqno.part.5: vcs0 seqno 0 (current 0) -> 0
<0>[ 416.098832] gem_exec-1638 2.... 383508527us : reset_all_global_seqno.part.5: vecs0 seqno 0 (current 0) -> 0
<0>[ 416.098868] gem_exec-1638 2.... 383535719us : i915_gem_wait_for_idle: flags=3 (locked)
<0>[ 416.098903] kms_fron-1646 5.... 383679597us : i915_gem_wait_for_idle: flags=3 (locked)
<0>[ 416.098938] kms_fron-1646 5.... 383734604us : i915_gem_unpark:
<0>[ 416.098974] kms_fron-1646 5.... 383734880us : i915_request_add: bcs0 fence 45f:1
<0>[ 416.099011] kms_fron-1646 5.... 383734882us : i915_request_add: marking kms_frontbuffer[1646]/0 as active