Bug 110379

Summary: [CI][SHARDS] igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-* - fail - Failed assertion: !mismatch
Product: DRI Reporter: Martin Peres <martin.peres>
Component: DRM/IntelAssignee: Swati Sharma <swati2.sharma>
Status: NEW --- QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: high CC: intel-gfx-bugs, swati2.sharma
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: KBL, SKL i915 features: display/Other

Description Martin Peres 2019-04-10 12:13:25 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4920/shard-skl8/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-gtt.html

Starting subtest: fbc-rgb101010-draw-mmap-gtt
(kms_frontbuffer_tracking:1166) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:419:
(kms_frontbuffer_tracking:1166) igt_debugfs-CRITICAL: Failed assertion: !mismatch
Subtest fbc-rgb101010-draw-mmap-gtt failed.
Comment 1 CI Bug Log 2019-04-10 12:15:30 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL KBL WHL: igt@kms_frontbuffer_tracking@fbc(psr)?-rgb101010-draw-* - fail - Failed assertion: !mismatch (No new failures associated)
Comment 2 Mika Kahola 2019-08-22 10:12:11 UTC
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).

Worst case scenario for a user is black or frozen screen. One may experience flickering too. 

#assessment
Comment 3 Swati Sharma 2019-08-22 12:27:26 UTC
Based on bug history issue is seen only 5% times on KBL platform whereas seen 95% times on shard-skl. On KBL, reproduction rate is quite low - issue occurred 5 times almost 3 months back whereas on shard-skl issue is seen recently (almost a week back). May be we can drop, KBL from the affected platforms.

IGT has 100% failure rate. IGT is getting failed because of CRC mismatch issue. Issue is happening for the following subtests:

igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-gtt
igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-cpu
igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-render
igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-wc
igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-blt
igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-pwrite
igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-gtt
igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-cpu
igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-render
igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-wc
igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-blt
igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-pwrite

The real subtest to be executed depends on whether the pixel format(rgb101010) is supported by the features being tested or not. Need to check which subtest is actually failing (draw_subtest(t) or badformat_subtest(t)).

In last 15 runs https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html?testfilter=@fbcpsr-rgb101010-, issue is not seen.

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.