| Summary: | [BAT] igt@drv_selftest@live_workarounds - WARN_ON(i915->gt.awake) | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| 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: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | BSW/CHT, CFL, KBL, SKL | i915 features: | GEM/Other |
|
Description
Martin Peres
2018-07-17 08:25:21 UTC
The pronouncement from live_workarounds about the nature of the failure is a little misleading. The root cause here is the unrecoverable reset (same as live_hangcheck), but what's more interesting in this case is the subsequent oops after we have wedged the device... That shouldn't occur -- wedging should be fail-safe! Also seen on CFL: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4503/fi-cfl-8109u/igt@drv_selftest@live_workarounds.html commit 01f8f33e9986aed42a0366704f715cf30e7cb41c (HEAD -> drm-intel-next-queued, drm-intel/for-linux-next, drm-intel/drm-intel-next-queued) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Jul 17 09:41:21 2018 +0100 drm/i915: Always retire residual requests before suspend If the driver is wedged, we skip idling the GPU. However, we may still have a few requests still not retired following the wedging (since they will be waiting for a background worker trying to acquire struct_mutex). As we hold the struct_mutex, always do a quick request retirement in order to flush the wedged path. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107257 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180717084121.28185-1-chris@chris-wilson.co.uk will reduce this down to the existing bug for the reset failing inside live_workaround: bug 107188. While the test still fails, WARN_ON(i915->gt.awake) appears to have been fixed. Can we close this then? Martin? Closing the bug, last time seen one month ago. This bug used to appear after every 5 rounds of execution, but this doesn't appear since last 198 rounds. Closing this bug. |
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.