Bug 106066 - [CI] igt@kms_vblank@pipe-[b|c]-wait-forked-hang | igt@gem_eio@in-flight-suspend - fail - Test assertion failure function gem_execbuf - Failed assertion: __gem_execbuf(fd, execbuf) == 0
Summary: [CI] igt@kms_vblank@pipe-[b|c]-wait-forked-hang | igt@gem_eio@in-flight-suspe...
Status: CLOSED DUPLICATE of bug 106064
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Francesco Balestrieri
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-16 07:36 UTC by Marta Löfstedt
Modified: 2018-04-23 10:50 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features: GEM/Other

Attachments

Description Marta Löfstedt 2018-04-16 07:36:14 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_20/fi-kbl-r/igt@kms_vblank@pipe-c-query-forked-hang.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_20/fi-kbl-r/igt@kms_vblank@pipe-b-wait-forked-hang.html

(kms_vblank:1482) ioctl_wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ../lib/ioctl_wrappers.c:604:
(kms_vblank:1482) ioctl_wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0
(kms_vblank:1482) ioctl_wrappers-CRITICAL: error: -5 != 0
Subtest pipe-C-query-forked-hang failed.
Comment 1 Chris Wilson 2018-04-17 12:13:50 UTC 

*** This bug has been marked as a duplicate of bug 106064 ***
Comment 2 Martin Peres 2018-04-18 13:21:47 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_22/fi-kbl-r/igt@gem_eio@in-flight-suspend.html

(gem_eio:1438) ioctl_wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ../lib/ioctl_wrappers.c:604:
(gem_eio:1438) ioctl_wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0
(gem_eio:1438) ioctl_wrappers-CRITICAL: error: -5 != 0
Subtest in-flight-suspend failed.
Comment 3 Jani Saarinen 2018-04-23 10:50:49 UTC 
Closing dups.

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.