Bug 103218

Summary: [BAT] igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence - failed in igt_wait_for_vblank_count - dmesg -*ERROR* Timeout waiting for engines to idle
Product: DRI Reporter: Marta Löfstedt <marta.lofstedt>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: critical    
Priority: high CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: CFL i915 features: display/Other

Description Marta Löfstedt 2017-10-11 12:07:22 UTC 
On Ci_DRM_3211 fi-cfl-s failed igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence:

(kms_pipe_crc_basic:4235) igt-kms-CRITICAL: Test assertion failure function igt_wait_for_vblank_count, file igt_kms.c:3149:
(kms_pipe_crc_basic:4235) igt-kms-CRITICAL: Failed assertion: drmWaitVBlank(drm_fd, &wait_vbl) == 0
(kms_pipe_crc_basic:4235) igt-kms-CRITICAL: Last errno: 16, Device or resource busy

from dmesg:
[  441.317128] [drm:drm_atomic_helper_wait_for_flip_done] *ERROR* [CRTC:36:pipe A] flip_done timed out
[  455.717549] i915 0000:00:02.0: Resetting bcs0 after gpu hang
[  455.718230] i915 0000:00:02.0: Resetting vcs0 after gpu hang
[  455.718638] i915 0000:00:02.0: Resetting vecs0 after gpu hang
[  459.685821] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[  459.814408] [drm:i915_gem_idle_work_handler [i915]] *ERROR* Timeout waiting for engines to idle
[  469.989161] [drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:36:pipe A] flip_done timed out
[  481.253276] [drm:drm_atomic_helper_wait_for_flip_done] *ERROR* [CRTC:36:pipe A] flip_done timed out

more data:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3211/fi-cfl-s/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence.html
Comment 1 Marta Löfstedt 2017-10-23 12:52:56 UTC 

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

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.