Bug 97294

Summary:	[BAT BDW] igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-frame-sequence "Failed assertion: crcs[j].frame + 1 == crcs[j + 1].frame"
Product:	DRI	Reporter:	Tvrtko Ursulin <tvrtko.ursulin>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	major
Priority:	highest	CC:	intel-gfx-bugs
Version:	DRI git
Hardware:	Other
OS:	Linux (All)
Whiteboard:
i915 platform:	BDW	i915 features:	display/eDP

Description Tvrtko Ursulin 2016-08-11 10:20:42 UTC

(kms_pipe_crc_basic:8255) CRITICAL: Test assertion failure function test_read_crc_for_output, file kms_pipe_crc_basic.c:148:
(kms_pipe_crc_basic:8255) CRITICAL: Failed assertion: crcs[j].frame + 1 == crcs[j + 1].frame
(kms_pipe_crc_basic:8255) CRITICAL: Last errno: 11, Resource temporarily unavailable
(kms_pipe_crc_basic:8255) CRITICAL: error: 134 != 133
Subtest nonblocking-crc-pipe-B-frame-sequence failed.
**** DEBUG ****
(kms_pipe_crc_basic:8255) DEBUG: Test requirement passed: !(pipe >= data->display.n_pipes)
(kms_pipe_crc_basic:8255) INFO: nonblocking-crc-pipe-B-frame-sequence: Testing connector eDP-1 using pipe B
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display: eDP-1: set_pipe(B)
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display: commit {
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     eDP-1: Selecting pipe B
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     SetCrtc pipe A, disabling
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     SetPlane pipe A, plane 1, disabling
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     SetCursor pipe A, disabling
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     SetCrtc pipe B, disabling
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     SetPlane pipe B, plane 1, disabling
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     SetCursor pipe B, disabling
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     SetCrtc pipe C, disabling
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     SetPlane pipe C, plane 1, disabling
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     SetCursor pipe C, disabling
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display: }
(kms_pipe_crc_basic:8255) DEBUG: Clearing the fb with color (0.00,1.00,0.00)
(kms_pipe_crc_basic:8255) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1920, height=1080, format=0x34325258, tiling=0x0, size=0)
(kms_pipe_crc_basic:8255) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=1, pitch=7680)
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display: B.0: plane_set_fb(60)
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display: commit {
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     eDP-1: Selecting pipe B
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display:     eDP-1: SetCrtc pipe B, fb 60, src (0, 0), mode 1920x1080
(kms_pipe_crc_basic:8255) igt-kms-DEBUG: display: }
(kms_pipe_crc_basic:8255) DEBUG: CRC for this fb: d30a1687 00000000 00000000 00000000 00000000
(kms_pipe_crc_basic:8255) CRITICAL: Test assertion failure function test_read_crc_for_output, file kms_pipe_crc_basic.c:148:
(kms_pipe_crc_basic:8255) CRITICAL: Failed assertion: crcs[j].frame + 1 == crcs[j + 1].frame
(kms_pipe_crc_basic:8255) CRITICAL: Last errno: 11, Resource temporarily unavailable
(kms_pipe_crc_basic:8255) CRITICAL: error: 134 != 133
****  END  ****

Comment 1 Jani Saarinen 2016-09-08 16:02:50 UTC

Tvrtko, do you see this issue still. This has not been seen on CI lately.

Comment 2 Tvrtko Ursulin 2016-09-09 08:24:42 UTC

If it is gone from CI then it can be closed. But ideally someone would dig out the commit which fixed it.

Comment 3 yann 2016-09-09 09:56:52 UTC

(In reply to Jani Saarinen from comment #1)
> Tvrtko, do you see this issue still. This has not been seen on CI lately.

Confirming also on QA side that this issue is not seen on any platforms.

I recommend to resolved as worksforme

Comment 4 Jari Tahvanainen 2016-09-09 10:52:26 UTC

Merked resolved+worksforme. World is not always perfect/ideal ...

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.