Bug 110021 - [CI][DRMTIP] igt@kms_chamelium@hdmi-cmp-planes-random - fail - Failed assertion: plane
Summary: [CI][DRMTIP] igt@kms_chamelium@hdmi-cmp-planes-random - fail - Failed asserti...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-13 07:56 UTC by Lakshmi
Modified: 2019-11-29 18:10 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features: display/Other


Attachments

Description Lakshmi 2019-03-13 07:56:52 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_237/fi-kbl-7567u/igt@kms_chamelium@hdmi-cmp-planes-random.html

Starting subtest: hdmi-cmp-planes-random
(kms_chamelium:3453) CRITICAL: Test assertion failure function test_display_planes_random, file ../tests/kms_chamelium.c:1084:
(kms_chamelium:3453) CRITICAL: Failed assertion: plane
Subtest hdmi-cmp-planes-random failed.
**** DEBUG ****
(kms_chamelium:3453) igt_chamelium-DEBUG: Resetting the chamelium
(kms_chamelium:3453) DEBUG: Waiting for DP-1 to disconnect...
(kms_chamelium:3453) DEBUG: Reprobing DP-1...
(kms_chamelium:3453) DEBUG: Test requirement passed: res = drmModeGetResources(data->drm_fd)
(kms_chamelium:3453) igt_chamelium-DEBUG: Plugging DP-1
(kms_chamelium:3453) DEBUG: Waiting for DP-1 to connect...
(kms_chamelium:3453) DEBUG: Reprobing DP-1...
(kms_chamelium:3453) DEBUG: Reprobing DP-1...
(kms_chamelium:3453) DEBUG: Reprobing DP-1...
(kms_chamelium:3453) DEBUG: Reprobing DP-1...
(kms_chamelium:3453) igt_kms-DEBUG: display: DP-1: set_pipe(None)
(kms_chamelium:3453) igt_kms-DEBUG: display: DP-1: Selecting pipe None
(kms_chamelium:3453) igt_kms-DEBUG: display: DP-1: set_pipe(A)
(kms_chamelium:3453) igt_kms-DEBUG: display: DP-1: Selecting pipe A
(kms_chamelium:3453) igt_kms-DEBUG: Test requirement passed: plane_idx >= 0 && plane_idx < pipe->n_planes
(kms_chamelium:3453) igt_fb-DEBUG: igt_create_fb_with_bo_size(width=1920, height=1080, format=0x34325258, tiling=0x0, size=0)
(kms_chamelium:3453) igt_fb-DEBUG: igt_create_fb_with_bo_size(handle=1, pitch=7680)
(kms_chamelium:3453) ioctl_wrappers-DEBUG: Test requirement passed: igt_has_fb_modifiers(fd)
(kms_chamelium:3453) igt_fb-DEBUG: igt_create_fb_with_bo_size(width=1920, height=1080, format=0x34325258, tiling=0x0, size=0)
(kms_chamelium:3453) igt_fb-DEBUG: igt_create_fb_with_bo_size(handle=2, pitch=7680)
(kms_chamelium:3453) ioctl_wrappers-DEBUG: Test requirement passed: igt_has_fb_modifiers(fd)
(kms_chamelium:3453) igt_fb-DEBUG: Test requirement passed: cairo_surface_status(fb->cairo_surface) == CAIRO_STATUS_SUCCESS
(kms_chamelium:3453) igt_fb-DEBUG: Test requirement passed: cairo_surface_status(fb->cairo_surface) == CAIRO_STATUS_SUCCESS
(kms_chamelium:3453) igt_kms-DEBUG: display: A.0: plane_set_fb(110)
(kms_chamelium:3453) igt_kms-DEBUG: display: A.0: plane_set_size (1920x1080)
(kms_chamelium:3453) igt_kms-DEBUG: display: A.0: fb_set_position(0,0)
(kms_chamelium:3453) igt_kms-DEBUG: display: A.0: fb_set_size(1920x1080)
(kms_chamelium:3453) DEBUG: Using 2 overlay planes
(kms_chamelium:3453) DEBUG: Plane 0: framebuffer size 917x322
(kms_chamelium:3453) DEBUG: Plane 0: on-crtc size 198x447
(kms_chamelium:3453) DEBUG: Plane 0: on-crtc position 899x4
(kms_chamelium:3453) DEBUG: Plane 0: in-framebuffer size 896x240
(kms_chamelium:3453) DEBUG: Plane 0: in-framebuffer position 21x82
(kms_chamelium:3453) igt_fb-DEBUG: igt_create_fb_with_bo_size(width=917, height=322, format=0x34325258, tiling=0x0, size=0)
(kms_chamelium:3453) igt_fb-DEBUG: igt_create_fb_with_bo_size(handle=3, pitch=3712)
(kms_chamelium:3453) ioctl_wrappers-DEBUG: Test requirement passed: igt_has_fb_modifiers(fd)
(kms_chamelium:3453) DEBUG: Plane 0: UYVY format (linear) with stride 2624
(kms_chamelium:3453) igt_fb-DEBUG: igt_create_fb_with_bo_size(width=917, height=322, format=0x59565955, tiling=0x0, size=0)
(kms_chamelium:3453) igt_fb-DEBUG: igt_create_fb_with_bo_size(handle=4, pitch=2624)
(kms_chamelium:3453) ioctl_wrappers-DEBUG: Test requirement passed: igt_has_fb_modifiers(fd)
(kms_chamelium:3453) igt_fb-DEBUG: Test requirement passed: cairo_surface_status(fb->cairo_surface) == CAIRO_STATUS_SUCCESS
(kms_chamelium:3453) igt_kms-DEBUG: display: A.1: plane_set_fb(113)
(kms_chamelium:3453) igt_kms-DEBUG: display: A.1: plane_set_size (917x322)
(kms_chamelium:3453) igt_kms-DEBUG: display: A.1: fb_set_position(0,0)
(kms_chamelium:3453) igt_kms-DEBUG: display: A.1: fb_set_size(917x322)
(kms_chamelium:3453) igt_kms-DEBUG: display: A.1: plane_set_position(899,4)
(kms_chamelium:3453) igt_kms-DEBUG: display: A.1: plane_set_size (198x447)
(kms_chamelium:3453) igt_kms-DEBUG: display: A.1: fb_set_position(21,82)
(kms_chamelium:3453) igt_kms-DEBUG: display: A.1: fb_set_size(896x240)
(kms_chamelium:3453) CRITICAL: Test assertion failure function test_display_planes_random, file ../tests/kms_chamelium.c:1084:
(kms_chamelium:3453) CRITICAL: Failed assertion: plane
(kms_chamelium:3453) igt_core-INFO: Stack trace:
(kms_chamelium:3453) igt_core-INFO:   #0 ../lib/igt_core.c:1474 __igt_fail_assert()
(kms_chamelium:3453) igt_core-INFO:   #1 ../tests/kms_chamelium.c:1086 test_display_planes_random()
(kms_chamelium:3453) igt_core-INFO:   #2 ../tests/kms_chamelium.c:1452 __real_main1217()
(kms_chamelium:3453) igt_core-INFO:   #3 ../tests/kms_chamelium.c:1217 main()
(kms_chamelium:3453) igt_core-INFO:   #4 ../csu/libc-start.c:344 __libc_start_main()
(kms_chamelium:3453) igt_core-INFO:   #5 [_start+0x2a]
****  END  ****
Subtest hdmi-cmp-planes-random: FAIL (1.630s)
Comment 2 Martin Peres 2019-11-29 18:10:35 UTC
-- 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/245.


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.