Summary: | [CI][BAT] igt@drv_selftest@live_hangcheck - dmesg-fail - GEM_BUG_ON(!execlists_is_active(execlists, 0)) | ||
---|---|---|---|
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: | CFL | i915 features: | GEM/execlists |
Description
Martin Peres
2018-07-23 14:36:24 UTC
The cause is same problem as bug 106560, but still we are not allowed to trip over after declaring wedged. In this case it's that we have declared wedged, cleared the active marker, but left HWSP alone (due to races with the GPU we can't until we actually reset). Then on a second wedging(!!) we trip over residual events in the CSB. Should be papered over by commit 3970c65c2b47c450f917bc8a29c5849563a95dfe (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: Mon Jul 23 15:53:35 2018 +0100 drm/i915: Skip repeated calls to i915_gem_set_wedged() If we already wedged, i915_gem_set_wedged() becomes a complicated no-op. References: https://bugs.freedesktop.org/show_bug.cgi?id=107343 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180723145335.24579-1-chris@chris-wilson.co.uk (Not the cause of the wedging, just the nasty side-effect here of wedging twice.) Martin, OK to close? Only occurred twice, and not for 2+ weeks. Closing. (In reply to Francesco Balestrieri from comment #5) > Only occurred twice, and not for 2+ weeks. Closing. Please don't close this sort of bug super quickly. Only close the obviously fixed ones please. |
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.