Bug 111857

Summary: [CI][DRMTIP] igt@gem_exec_balancer@bonded-slice - fail - Failed assertion: !"GPU hung"
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED MOVED 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:
i915 platform: BDW, ICL i915 features: GEM/Other

Description Lakshmi 2019-09-29 20:29:02 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_379/fi-icl-dsi/igt@gem_exec_balancer@bonded-slice.html
Starting subtest: bonded-slice
(gem_exec_balancer:1156) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:502:
(gem_exec_balancer:1156) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
Subtest bonded-slice failed.


https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_380/fi-bdw-gvtdvm/igt@gem_exec_balancer@bonded-slice.html

Starting subtest: bonded-slice
(gem_exec_balancer:1075) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:502:
(gem_exec_balancer:1075) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
Subtest bonded-slice failed.
Comment 2 Chris Wilson 2019-10-02 11:05:57 UTC
The test looks in order, the fix makes sense, so this failure is unexpected. Not yet observed in the shards, so play it slow and wait for the pattern in the idle runs to develop.
Comment 3 Francesco Balestrieri 2019-10-04 11:10:28 UTC
Setting to medium for now, let's keep monitoring.
Comment 5 Martin Peres 2019-11-29 19:36:04 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/464.

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.