Seem with igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size and igt@kms_cursor_legacy@basic-flip-before-cursor-varying-size. [ 404.863191] ------------[ cut here ]------------ [ 404.863361] WARNING: CPU: 0 PID: 9607 at drivers/gpu/drm/i915/intel_display.c:12603 intel_atomic_commit_tail+0xfd3/0xfe0 [i915] [ 404.863380] pipe A vblank wait timed out [ 404.863396] Modules linked in: vgem snd_hda_codec_hdmi intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core lpc_ich snd_pcm i2c_designware_platform i2c_designware_core r8169 mii i915 prime_numbers sdhci_acpi i2c_hid sdhci mmc_core [ 404.863799] CPU: 0 PID: 9607 Comm: kms_cursor_lega Tainted: G U 4.11.0-rc1-CI-CI_DRM_2293+ #1 [ 404.863816] Hardware name: \xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff \xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff/DN2820FYK, BIOS FYBYT10H.86A.0055.2016.0919.1948 09/19/2016 [ 404.863831] Call Trace: [ 404.863859] dump_stack+0x67/0x92 [ 404.863887] __warn+0xc6/0xe0 [ 404.863917] warn_slowpath_fmt+0x4a/0x50 [ 404.863946] ? finish_wait+0x5e/0x80 [ 404.864095] intel_atomic_commit_tail+0xfd3/0xfe0 [i915] [ 404.864138] ? wake_atomic_t_function+0x30/0x30 [ 404.864290] intel_atomic_commit+0x42f/0x540 [i915] [ 404.864323] ? drm_atomic_set_crtc_for_connector+0xcb/0x100 [ 404.864352] drm_atomic_commit+0x46/0x50 [ 404.864377] drm_atomic_helper_set_config+0x7e/0xc0 [ 404.864405] drm_mode_set_config_internal+0x60/0x110 [ 404.864430] drm_mode_setcrtc+0x3a8/0x480 [ 404.864473] drm_ioctl+0x200/0x450 [ 404.864495] ? drm_mode_getcrtc+0x170/0x170 [ 404.864544] ? __this_cpu_preempt_check+0x13/0x20 [ 404.864572] do_vfs_ioctl+0x90/0x6e0 [ 404.864595] ? entry_SYSCALL_64_fastpath+0x5/0xb1 [ 404.864617] ? __this_cpu_preempt_check+0x13/0x20 [ 404.864640] ? trace_hardirqs_on_caller+0xe7/0x200 [ 404.864666] SyS_ioctl+0x3c/0x70 [ 404.864695] entry_SYSCALL_64_fastpath+0x1c/0xb1 [ 404.864713] RIP: 0033:0x7f9e5d385357 [ 404.864729] RSP: 002b:00007fffd322a5a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 404.864761] RAX: ffffffffffffffda RBX: ffffffff81482e33 RCX: 00007f9e5d385357 [ 404.864777] RDX: 00007fffd322a5e0 RSI: 00000000c06864a2 RDI: 0000000000000003 [ 404.864793] RBP: ffffc90000d8ff88 R08: 0000000000000000 R09: 00000000008eb238 [ 404.864808] R10: 00000000008eb258 R11: 0000000000000246 R12: 00000000008ea5c0 [ 404.864824] R13: 0000000000000003 R14: 00000000c06864a2 R15: 0000000000000003 [ 404.864850] ? __this_cpu_preempt_check+0x13/0x20 [ 404.871925] ---[ end trace 66c72bcf4a5c0059 ]--- http://benchsrv.fi.intel.com/archive/results/CI_IGT_test/CI_DRM_2293/fi-byt-n2820/igt@kms_cursor_legacy@basic-flip-before-cursor-varying-size.html http://benchsrv.fi.intel.com/archive/results/CI_IGT_test/CI_DRM_2281/fi-byt-n2820/igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size.html Also: https://intel-gfx-ci.01.org/CI/Patchwork_3939/fi-byt-n2820/igt@prime_vgem@basic-fence-flip.html
Still hapening: https://intel-gfx-ci.01.org/CI/CI_DRM_2354/fi-byt-n2820/igt@kms_pipe_crc_basic@read-crc-pipe-a.html
https://intel-gfx-ci.01.org/CI/Patchwork_4243/ another occurence. Is someone working on this?
Failure rates, only seen on fi-byt-n2820: - igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size: Failure rate 1/105 run(s) (0%) - igt@prime_vgem@basic-fence-flip: Failure rate 1/42 run(s) (2%) - igt@kms_pipe_crc_basic@read-crc-pipe-a: Failure rate 2/32 run(s) (6%) - igt@kms_cursor_legacy@basic-flip-before-cursor-varying-size: Failure rate 3/93 run(s) (3%) Increasing the severity of this bug because it is reducing our test coverage on CI
I'm unable to reproduce, I tried replugging the connector too but that results in a few missed vblanks during the test, but not the vblank wait timed out failure.
*** Bug 100126 has been marked as a duplicate of this bug. ***
Seen last 4th of Apr Statistics: Failure rate 1/86 run(s) (1%) Is this issue gone due to maxcpu=2?
I would say the issue is gone with the changes. Last occurrence still april 4, could be closed?
Ok, lets resolve, close. Marked to CI as whitelisted.
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.