Bug 112229 - [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
Summary: [CI][RESUME] igt@kms_flip@2x-flip-vs-suspend-interruptible - dmesg-fail - Fai...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-08 08:16 UTC by Lakshmi
Modified: 2019-11-11 11:01 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-11-08 08:16:59 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7266/re-tgl-u/igt@kms_flip@2x-flip-vs-suspend-interruptible.html
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.


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.