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
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4657/shard-skl9/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-blt.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_127/fi-skl-6700hq/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-blt.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_126/fi-skl-6700hq/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-gtt.html
Also on ICL https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_169/fi-icl-u3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-cpu.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_168/fi-icl-u3/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-mmap-cpu.html
A CI Bug Log filter associated to this bug has been updated: {- SKL ICL: igt@kms_frontbuffer_tracking@(fbc)?psr-* - incomplete -} {+ SKL ICL: igt@kms_frontbuffer_tracking@(fbc)?psr-* - incomplete +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_205/fi-icl-u3/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-mmap-gtt.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_206/fi-icl-u3/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-mmap-gtt.html
A CI Bug Log filter associated to this bug has been updated: {- SKL ICL: igt@kms_frontbuffer_tracking@(fbc)?psr-* - incomplete -} {+ SKL ICL: igt@kms_frontbuffer_tracking@(fbc)?psr-* - incomplete +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_251/fi-icl-u3/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-indfb-msflip-blt.html
A CI Bug Log filter associated to this bug has been updated: {- SKL ICL: igt@kms_frontbuffer_tracking@(fbc)?psr-* - incomplete -} {+ SKL ICL: igt@kms_frontbuffer_tracking@(fbc)?psr-* - incomplete +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_253/fi-icl-u2/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-indfb-pgflip-blt.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_253/fi-icl-y/igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-msflip-blt.html
Bumping the priority to high, since we get incompletes from time to time and since PSR/FBC is now enabled by default on gen9.
Looks like this might be GEM related - got one pstore log that ends in a GEM wait_for_idle on rcs0 - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_253/fi-icl-y/pstore15-1517155641_Panic_1.log
u2, u3, re-icl-u and shards have now updated BIOS( ICLSFWR1.R00.3175.A00.1904261428 04/26/2019). To be seen if we see issues after updates.
Update: u2/u3/re/ and half of the shards now on BIOS ICLSFWR1.R00.3183.A00.1905020411 05/02/2019
While this continues happening, the GEM error hasn't appeared for a while according to another thread of discussion. I'm removing GEM from the component list.
Test definition kms_frontbuffer_tracking tests tracking mechanisms and its related features such as framebuffer compression (FBC), panel self refresh (PRS) and display refresh rate switching (DRRS). User impact Worst case scenario for a user is black or frozen screen. One may experience flickering too. Reproduction rate Currently 15.4% #assessment
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/123.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.