Bug 103218 - [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
Summary: [BAT] igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence - failed i...
Status: CLOSED DUPLICATE of bug 103165
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
Whiteboard: ReadyForDev
Depends on:
Reported: 2017-10-11 12:07 UTC by Marta Löfstedt
Modified: 2017-10-23 12:56 UTC (History)
1 user (show)

See Also:
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:
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.