Summary: | [CI][DRMTIP] igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 | ||
---|---|---|---|
Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | BDW, BSW/CHT, BXT, BYT, HSW, SKL | i915 features: | GEM/Other |
Description
Lakshmi
2019-05-13 07:09:37 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BSW: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_283/fi-bsw-n3050/igt@gem_eio@in-flight-suspend.html A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 -} {+ SKL BSW: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_284/fi-skl-gvtdvm/igt@gem_eio@in-flight-suspend.html A CI Bug Log filter associated to this bug has been updated: {- SKL BSW: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 -} {+ BSW SKL KBL GLK: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6084/shard-glk5/igt@gem_eio@in-flight-suspend.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6085/shard-kbl2/igt@gem_eio@in-flight-suspend.html A CI Bug Log filter associated to this bug has been updated: {- BSW SKL KBL GLK: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 -} {+ BSW BDW SKL KBL GLK: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_286/fi-bdw-gvtdvm/igt@gem_eio@in-flight-suspend.html A CI Bug Log filter associated to this bug has been updated: {- BSW BDW SKL KBL GLK: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 -} {+ BYT BSW BDW SKL KBL GLK: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_288/fi-byt-n2820/igt@gem_eio@in-flight-suspend.html A CI Bug Log filter associated to this bug has been updated: {- BYT BSW BDW SKL KBL GLK: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 -} {+ BYT BSW BDW APL SKL KBL GLK: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6114/shard-apl7/igt@gem_eio@in-flight-suspend.html A CI Bug Log filter associated to this bug has been updated: {- BYT BSW BDW APL SKL KBL GLK: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 -} {+ BYT BSW BDW APL SKL KBL GLK ICL: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5015/shard-iclb1/igt@gem_eio@in-flight-suspend.html A CI Bug Log filter associated to this bug has been updated: {- BYT BSW BDW APL SKL KBL GLK ICL: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 -} {+ BYT HSW BSW BDW APL SKL KBL GLK ICL: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_301/fi-hsw-peppy/igt@gem_eio@in-flight-suspend.html A CI Bug Log filter associated to this bug has been updated: {- BYT HSW BSW BDW APL SKL KBL GLK ICL: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 -} {+ SNB BYT HSW BSW BDW APL SKL KBL GLK ICL: igt@gem_eio@in-flight-suspend - fail - Failed assertion: __gem_execbuf(fd, execbuf) == 0, error: -22 != 0 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_311/fi-snb-2520m/igt@gem_eio@in-flight-suspend.html A very strange issue. Possibly even memory corruption after suspend-resume. Sent a patch in https://patchwork.freedesktop.org/series/62854/ to see if it will change the pattern. Let's see if commit 03779dd3de8a57544f124d9952a6d2b3e34e34ca Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Date: Thu Jun 27 13:25:52 2019 +0100 lib/i915: Use engine discovery in gem_test_engines If request is to verify all engines work, use the new engine discovery API so we can actually test all. There is a sporadic and mysterious, possibly memory corruption issue surronding this area so lets see if this changes the pattern. It is easy to do in this function due it re-opening the driver and throwing it away. So there are no concerns that the modified default context can affect any other test. Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> References: https://bugzilla.freedesktop.org/show_bug.cgi?id=110667 Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> does paper over the issue. Last seen drmtip_317 (4 months, 3 weeks old), not seen in the last 90 runs, so closing and archiving this 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.