Bug 110114 - [CI][SHARDS] igt@kms_universal_plane@universal-plane-pipe-[abc]-functional - fail - Failed assertion: !mismatch, Last errno: 25, Inappropriate ioctl for device
Summary: [CI][SHARDS] igt@kms_universal_plane@universal-plane-pipe-[abc]-functional - ...
Status: RESOLVED DUPLICATE of bug 110037
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-14 13:23 UTC by Martin Peres
Modified: 2019-03-14 13:29 UTC (History)
1 user (show)

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

Attachments

Description Martin Peres 2019-03-14 13:23:56 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5743/shard-glk1/igt@kms_universal_plane@universal-plane-pipe-c-functional.html

Starting subtest: universal-plane-pipe-C-functional
(kms_universal_plane:8352) igt_debugfs-CRITICAL: Test assertion failure function igt_assert_crc_equal, file ../lib/igt_debugfs.c:419:
(kms_universal_plane:8352) igt_debugfs-CRITICAL: Failed assertion: !mismatch
(kms_universal_plane:8352) igt_debugfs-CRITICAL: Last errno: 25, Inappropriate ioctl for device
Subtest universal-plane-pipe-C-functional failed.
Comment 1 CI Bug Log 2019-03-14 13:24:35 UTC 
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* GLK: igt@kms_universal_plane@universal-plane-pipe-[abc]-functional - fail - Failed assertion: !mismatch, Last errno: 25, Inappropriate ioctl for device (No new failures associated)
Comment 2 Martin Peres 2019-03-14 13:29:04 UTC 

*** This bug has been marked as a duplicate of bug 110037 ***
Comment 3 CI Bug Log 2019-03-14 13:29:32 UTC 
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.

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.