Bug 102917

Summary:	[IGT] kms_flip@modeset-vs-vblank-race fail on HSW ssertion failure function run_test_step, file kms_flip.c:780
Product:	DRI	Reporter:	Sagar Kamble <sagar.a.kamble>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	medium	CC:	intel-gfx-bugs
Version:	DRI git
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Sagar Kamble 2017-09-21 03:08:19 UTC

(kms_flip:1631) CRITICAL: Test assertion failure function run_test_step, file kms_flip.c:780:
(kms_flip:1631) CRITICAL: Failed assertion: end - start > 0.9 * mode_frame_time(o) && end - start < 2.1 * mode_frame_time(o)
(kms_flip:1631) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_flip:1631) CRITICAL: wait for two vblanks took 49508 usec (frame time 16665.600000 usec)
Subtest modeset-vs-vblank-race failed.
**** DEBUG ****
(kms_flip:1631) DEBUG: Test requirement passed: (flags & TEST_HANG) == 0 || !is_wedged(drm_fd)
(kms_flip:1631) DEBUG: Test requirement passed: modes
(kms_flip:1631) INFO: Beginning modeset-vs-vblank-race on pipe A, connector VGA-1
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1024, height=768, format=0x34325258, tiling=0x0, size=0)
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=2, pitch=4096)
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1024, height=768, format=0x34325258, tiling=0x0, size=0)
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=3, pitch=4096)
(kms_flip:1631) igt-kms-INFO:   1024x768 60 1024 1048 1184 1344 768 771 777 806 0xa 0x40 65000
(kms_flip:1631) INFO: 
modeset-vs-vblank-race on pipe A, connector VGA-1: PASSED

(kms_flip:1631) INFO: Beginning modeset-vs-vblank-race on pipe B, connector VGA-1
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1024, height=768, format=0x34325258, tiling=0x0, size=0)
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=2, pitch=4096)
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1024, height=768, format=0x34325258, tiling=0x0, size=0)
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=3, pitch=4096)
(kms_flip:1631) igt-kms-INFO:   1024x768 60 1024 1048 1184 1344 768 771 777 806 0xa 0x40 65000
(kms_flip:1631) INFO: 
modeset-vs-vblank-race on pipe B, connector VGA-1: PASSED

(kms_flip:1631) INFO: Beginning modeset-vs-vblank-race on pipe C, connector VGA-1
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1024, height=768, format=0x34325258, tiling=0x0, size=0)
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=2, pitch=4096)
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1024, height=768, format=0x34325258, tiling=0x0, size=0)
(kms_flip:1631) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=3, pitch=4096)
(kms_flip:1631) igt-kms-INFO:   1024x768 60 1024 1048 1184 1344 768 771 777 806 0xa 0x40 65000
(kms_flip:1631) CRITICAL: Test assertion failure function run_test_step, file kms_flip.c:780:
(kms_flip:1631) CRITICAL: Failed assertion: end - start > 0.9 * mode_frame_time(o) && end - start < 2.1 * mode_frame_time(o)
(kms_flip:1631) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_flip:1631) CRITICAL: wait for two vblanks took 49508 usec (frame time 16665.600000 usec)
(kms_flip:1631) igt-core-INFO: Stack trace:
(kms_flip:1631) igt-core-INFO:   #0 [__igt_fail_assert+0x101]
(kms_flip:1631) igt-core-INFO:   #1 [run_test_on_crtc_set.constprop.14+0x1fe5]
(kms_flip:1631) igt-core-INFO:   #2 [_fini+0x1179]
(kms_flip:1631) igt-core-INFO:   #3 [<unknown>+0x1179]
****  END  ****

Comment 1 Elizabeth 2017-09-25 22:25:27 UTC

Hello Sagar, could you please share in what platform are you testing? HSW? Thank you.

Marking as dup since is the same issue than bug 102919.

*** This bug has been marked as a duplicate of bug 102919 ***

Comment 2 Sagar Kamble 2017-09-26 16:33:16 UTC

Yes. this was on HSW found in CI BAT testing.

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.