Bug 101091 - [BAT][BWR] igt@prime_vgem@basic-wait-default generated flip_done timed out
Summary: [BAT][BWR] igt@prime_vgem@basic-wait-default generated flip_done timed out
Status: CLOSED WORKSFORME
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
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-18 13:54 UTC by Martin Peres
Modified: 2017-06-16 17:06 UTC (History)
1 user (show)

See Also:
i915 platform: I965G
i915 features: display/Other

Attachments

Description Martin Peres 2017-05-18 13:54:26 UTC 
After running igt@prime_vgem@basic-wait-default on CI_DRM_2627, the machine fi-bwr-2160 started outputting a "flip_done timed out" message in dmesg for all the tests following it, until the machine hard hanged in igt@drv_module_reload@basic-reload.

Here is the message:
[  532.977094] [drm:drm_atomic_helper_commit_cleanup_done] *ERROR* [CRTC:30:pipe A] flip_done timed out

No other test before appeared to behave any differently from usual, aside from the following tests happily passing:
 - igt@gem_exec_suspend@basic-s3
 - igt@gem_exec_suspend@basic-s4-devices

Full logs: https://intel-gfx-ci.01.org/CI/CI_DRM_2627/fi-bwr-2160/igt@vgem_basic@dmabuf-fence.html

All the tests that failed (look at run 2627): https://intel-gfx-ci.01.org/CI/fi-bwr-2160.html
Comment 1 Jani Saarinen 2017-05-29 08:25:07 UTC 
Last seen: Statistics: Failure rate 1/36 run(s) (2%)
Last seen: 2017-05-18
Comment 2 Jani Saarinen 2017-06-02 08:11:51 UTC 
Last seen: 2017-05-18
Statistics: Failure rate 1/61 run(s) (1%)
Comment 3 Jani Saarinen 2017-06-15 07:07:31 UTC 
Same last seen still.
Statistics: Failure rate 1/92 run(s) (1%).
Proposing resolving as works for me ?
Comment 4 Martin Peres 2017-06-15 09:58:29 UTC 
Yes, it has been very common only one day, nothing since. Let's close this.

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.