Bug 109192 - [CI][DRMTIP] igt@kms_flip@2x-flip-vs-expired-vblank* - fail - Failed assertion: timercmp(&reply.ts, &o->flip_state.last_ts, ==)
Summary: [CI][DRMTIP] igt@kms_flip@2x-flip-vs-expired-vblank* - fail - Failed assertio...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-31 12:21 UTC by Martin Peres
Modified: 2019-04-10 13:16 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2018-12-31 12:21:44 UTC
Starting subtest: 2x-flip-vs-expired-vblank
(kms_flip:1578) CRITICAL: Test assertion failure function run_test_step, file ../tests/kms_flip.c:714:
(kms_flip:1578) CRITICAL: Failed assertion: timercmp(&reply.ts, &o->flip_state.last_ts, ==)
(kms_flip:1578) CRITICAL: Last errno: 25, Inappropriate ioctl for device
Subtest 2x-flip-vs-expired-vblank failed.
Comment 1 CI Bug Log 2018-12-31 12:22:26 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* CFL: igt@kms_flip@2x-flip-vs-expired-vblank* - fail - Failed assertion: timercmp(&reply.ts, &o->flip_state.last_ts, ==), Last errno: 25
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_160/fi-cfl-8109u/igt@kms_flip@2x-flip-vs-expired-vblank.html
Comment 2 CI Bug Log 2019-04-10 13:16:28 UTC
A CI Bug Log filter associated to this bug has been updated:

{- CFL: igt@kms_flip@2x-flip-vs-expired-vblank* - fail - Failed assertion: timercmp(&reply.ts, &o->flip_state.last_ts, ==), Last errno: 25 -}
{+ CFL: igt@kms_flip@2x-flip-vs-expired-vblank* - fail - Failed assertion: timercmp(&reply.ts, &o->flip_state.last_ts, ==) +}

 No new failures caught with the new filter


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.