Bug 112229

Summary: [CI][RESUME] igt@kms_flip@2x-flip-vs-suspend-interruptible - dmesg-fail - Failed assertion: (do_page_flip(o, new_fb_id, !(o->flags & (1 << 16)))) == 0
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED MOVED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: not set    
Priority: not set CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
i915 platform: TGL i915 features: display/Other

Description Lakshmi 2019-11-08 08:16:59 UTC
Starting subtest: 2x-flip-vs-suspend-interruptible
(kms_flip:927) CRITICAL: Test assertion failure function run_test_step, file ../tests/kms_flip.c:766:
(kms_flip:927) CRITICAL: Failed assertion: (do_page_flip(o, new_fb_id, !(o->flags & (1 << 16)))) == 0
(kms_flip:927) CRITICAL: Last errno: 16, Device or resource busy
Subtest 2x-flip-vs-suspend-interruptible failed.
Comment 1 CI Bug Log 2019-11-08 08:17:53 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@kms_flip@2x-flip-vs-suspend-interruptible - dmesg-fail - Failed assertion: (do_page_flip(o, new_fb_id, !(o-&gt;flags &amp; (1 &lt;&lt; 16)))) == 0
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7266/re-tgl-u/igt@kms_flip@2x-flip-vs-suspend-interruptible.html
Comment 2 Juha-Pekka Heikkilä 2019-11-11 11:01:34 UTC
This look like test error on first look. There's call to drmModePageFlip() which return "16, Device or resource busy" which would mean it's second call to drmModePageFlip() before page flip event happened.
Comment 3 Martin Peres 2019-11-29 19:46:26 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/583.

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.