Summary: | [CI][DRMTIP] igt@gem_gpgpu_fill - fail - Test assertion failure function gen7_render_flush, Failed assertion: ret == 0, Last errno: 5, Input/output error | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | IGT | Assignee: | Default DRI bug account <dri-devel> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | KBL | i915 features: | GEM/Other |
Description
Martin Peres
2018-07-25 15:15:23 UTC
The gpu was never the same after the hang in kms_draw_crc, and it ended up being declared wedged when a reset failed shortly after in perf. commit 3806547319038879f1c7939671b9e35937f0cae6 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Jul 12 16:22:51 2018 +0100 igt/gem_gpgpu_fill: Check for GEM before use As we need GEM and the GPU to do a GPGPU fill, we should check that it is operable before using -- skipping rather than failing when the device is wedged. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Closing this bug, this issue not seen since 1 month. 15 rounds ago this issue occurred only once with drmtip. So, this issue is closed. I will also add the following (old issues) here, since the signature matches and it stopped right after the actual fix was committed. https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_86/fi-kbl-7560u/igt@pm_rpm@gem-idle.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_87/fi-kbl-7560u/igt@pm_rpm@gem-idle.html (pm_rpm:3143) i915/gem_submission-CRITICAL: Test assertion failure function gem_test_engine, file ../lib/i915/gem_submission.c:212: (pm_rpm:3143) i915/gem_submission-CRITICAL: Failed assertion: !is_wedged(i915) (pm_rpm:3143) i915/gem_submission-CRITICAL: Last errno: 5, Input/output error |
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.