https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4151/shard-glkb6/igt@kms_chv_cursor_fail@pipe-a-64x64-bottom-edge.html
	
(kms_chv_cursor_fail:1779) igt-debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file igt_debugfs.c:356:
(kms_chv_cursor_fail:1779) igt-debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:1779) igt-debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-A-64x64-bottom-edge failed.

Also seen on KBL: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3664/shard-kbl5/igt@kms_chv_cursor_fail@pipe-a-64x64-top-edge.html

	
(kms_chv_cursor_fail:2000) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:356:
(kms_chv_cursor_fail:2000) igt_debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:2000) igt_debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-A-64x64-top-edge failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3809/shard-apl3/igt@kms_chv_cursor_fail@pipe-a-64x64-right-edge.html

(kms_chv_cursor_fail:1840) igt-debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file igt_debugfs.c:370:
(kms_chv_cursor_fail:1840) igt-debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:1840) igt-debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-A-64x64-right-edge failed.

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4275/shard-apl1/igt@kms_chv_cursor_fail@pipe-a-64x64-left-edge.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4275/shard-glkb2/igt@kms_chv_cursor_fail@pipe-a-64x64-left-edge.html

(kms_chv_cursor_fail:2779) igt-debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file igt_debugfs.c:370:
(kms_chv_cursor_fail:2779) igt-debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:2779) igt-debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-A-64x64-left-edge failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3830/shard-apl1/igt@kms_chv_cursor_fail@pipe-a-64x64-top-edge.html

(kms_chv_cursor_fail:1452) igt-debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file igt_debugfs.c:370:
(kms_chv_cursor_fail:1452) igt-debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:1452) igt-debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-A-64x64-top-edge failed.

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4327/shard-glkb2/igt@kms_chv_cursor_fail@pipe-c-128x128-bottom-edge.html

(kms_chv_cursor_fail:32060) igt-debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file igt_debugfs.c:370:
(kms_chv_cursor_fail:32060) igt-debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:32060) igt-debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-C-128x128-bottom-edge failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3905/shard-apl5/igt@kms_chv_cursor_fail@pipe-a-128x128-left-edge.html

(kms_chv_cursor_fail:1640) igt-debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file igt_debugfs.c:370:
(kms_chv_cursor_fail:1640) igt-debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:1640) igt-debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-A-128x128-left-edge failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3911/shard-apl6/igt@kms_chv_cursor_fail@pipe-a-128x128-top-edge.html

(kms_chv_cursor_fail:2926) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:370:
(kms_chv_cursor_fail:2926) igt_debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:2926) igt_debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-A-128x128-top-edge failed.

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4376/shard-apl5/igt@kms_chv_cursor_fail@pipe-c-128x128-right-edge.html

(kms_chv_cursor_fail:1366) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:370:
(kms_chv_cursor_fail:1366) igt_debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:1366) igt_debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-C-128x128-right-edge failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3984/shard-apl6/igt@kms_chv_cursor_fail@pipe-b-128x128-bottom-edge.html

(kms_chv_cursor_fail:1563) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:370:
(kms_chv_cursor_fail:1563) igt_debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:1563) igt_debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-B-128x128-bottom-edge failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4022/shard-apl8/igt@kms_chv_cursor_fail@pipe-b-256x256-right-edge.html

(kms_chv_cursor_fail:1326) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:370:
(kms_chv_cursor_fail:1326) igt_debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:1326) igt_debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-B-256x256-right-edge failed.

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_15/fi-skl-6600u/igt@kms_chv_cursor_fail@pipe-a-128x128-right-edge.html

(kms_chv_cursor_fail:1356) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:370:
(kms_chv_cursor_fail:1356) igt_debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:1356) igt_debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-A-128x128-right-edge failed.

This no longer appears to be an issue - https://intel-gfx-ci.01.org/tree/drm-tip/igt@kms_chv_cursor_fail@pipe-a-64x64-left-edge.html

Resolving as WORKSFORME

(In reply to James Ausmus from comment #13)
> This no longer appears to be an issue -
> https://intel-gfx-ci.01.org/tree/drm-tip/igt@kms_chv_cursor_fail@pipe-a-
> 64x64-left-edge.html
> 
> Resolving as WORKSFORME

I wish checking one platform on one run would be sufficient to say a bug is gone :s 

In any case, CI Bug Log is always here to remind us of the sad truth: this still happens every single idle run.

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-icl-u/igt@kms_chv_cursor_fail@pipe-c-64x64-right-edge.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-icl-u/igt@kms_chv_cursor_fail@pipe-b-256x256-right-edge.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-icl-u/igt@kms_chv_cursor_fail@pipe-b-256x256-bottom-edge.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-icl-u/igt@kms_chv_cursor_fail@pipe-c-64x64-left-edge.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-gdg-551/igt@kms_chv_cursor_fail@pipe-a-128x128-top-edge.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-gdg-551/igt@kms_chv_cursor_fail@pipe-b-128x128-top-edge.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-gdg-551/igt@kms_chv_cursor_fail@pipe-a-128x128-left-edge.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-gdg-551/igt@kms_chv_cursor_fail@pipe-a-256x256-left-edge.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-byt-clapper/igt@kms_chv_cursor_fail@pipe-a-64x64-left-edge.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-byt-clapper/igt@kms_chv_cursor_fail@pipe-a-128x128-top-edge.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_101/fi-byt-clapper/igt@kms_chv_cursor_fail@pipe-b-64x64-left-edge.html

(kms_chv_cursor_fail:1381) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:371:
(kms_chv_cursor_fail:1381) igt_debugfs-CRITICAL: Failed assertion: !mismatch
(kms_chv_cursor_fail:1381) igt_debugfs-CRITICAL: Last errno: 11, Resource temporarily unavailable
Subtest pipe-B-64x64-left-edge failed.

ICL has not been failing this since drmtip_218, which was 30 runs ago, when it used to be reproducible every single run. Got rid of it in the list of platforms.

The platforms this fails the most on are:
 1) gdg: all the left and top edges failing (128x128 and 256x256) - maybe the cursor size is too big since it is 100%?
 2) SKL: pretty much all the tests, randomly
 3) KBL: Only one platform fails pretty much all the time (fi-kbl-r)

The test is checking that we handle correctly the case where the cursor is found at one of the edges because one CHV had a HW bug that led to glitches when the cursor was in these locations. The customer impact should not be enormous, at worst the cursor will be looking garbled when in these locations and moving the mouse will fix the issue. If this is problematic for users, they can enable SW cursors easily in X. 

Because of this, let's drop the priority to medium.

-- 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/70.