igt@kms_fbcon_fbt@fbc(-suspend)? - fail - Back to fbcon. FBC status: FBC disabled: no suitable CRTC for FBC

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8817/re-rkl-1/igt@kms_fbcon_fbt@fbc-suspend.html

(kms_fbcon_fbt:1441) INFO: Back to fbcon.
(kms_fbcon_fbt:1441) DEBUG: FBC status: FBC disabled: no suitable CRTC for FBC

(kms_fbcon_fbt:1441) CRITICAL: Test assertion failure function subtest, file ../tests/kms_fbcon_fbt.c:320:
(kms_fbcon_fbt:1441) CRITICAL: Failed assertion: feature->wait_until_update(drm)
(kms_fbcon_fbt:1441) igt_core-INFO: Stack trace:
(kms_fbcon_fbt:1441) igt_core-INFO:   #0 ../lib/igt_core.c:1727 __igt_fail_assert()
(kms_fbcon_fbt:1441) igt_core-INFO:   #1 ../tests/kms_fbcon_fbt.c:198 subtest()
(kms_fbcon_fbt:1441) igt_core-INFO:   #2 ../tests/kms_fbcon_fbt.c:379 __real_main368()
(kms_fbcon_fbt:1441) igt_core-INFO:   #3 ../tests/kms_fbcon_fbt.c:368 main()
(kms_fbcon_fbt:1441) igt_core-INFO:   #4 ../csu/libc-start.c:344 __libc_start_main()
(kms_fbcon_fbt:1441) igt_core-INFO:   #5 [_start+0x2a]
****  END  ****

added feature: display/Other platform: RKL labels

The CI Bug Log issue associated to this bug has been updated by Lakshmi Vudum.

New filters associated

• RKL: igt@kms_fbcon_fbt@fbc(-suspend)? - fail - Back to fbcon. FBC status: FBC disabled: no suitable CRTC for FBC
  • https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8817/re-rkl-1/igt@kms_fbcon_fbt@fbc.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8817/re-rkl-1/igt@kms_fbcon_fbt@fbc-suspend.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8834/re-rkl-1/igt@kms_fbcon_fbt@fbc.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8834/re-rkl-1/igt@kms_fbcon_fbt@fbc-suspend.html

assigned to @ramesh

closed

reopened

marked this issue as related to #1602 (closed)

The test is failing because of rtcwake is not able to put e1000e driver into suspend/wakeup. Removing e1000e driver making test passed hence duplicating this issue to #1602 (closed).

closed

The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.