Summary: | [CI][DRMTIP] igt@drv_suspend@sysfs-reader - incomplete - killed by softdog | ||
---|---|---|---|
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, KBL | i915 features: | power/suspend-resume |
Description
Martin Peres
2018-07-23 14:23:50 UTC
commit 0051163ab3d8090a08ea2ea5edbb738c0920000a Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Jul 16 13:54:24 2018 +0100 drm/i915/execlists: Always clear preempt status on cancelling all On reset/wedging, we cancel all pending replies from the HW and we also want to cancel an outstanding preemption event. Since we use the same function to cancel the pending replies for reset and for a preemption event, we can simply clear the active tracking for all. v2: Keep execlists_user_end() markup for wedging v3: Move assignment to inline to hide the bare assignment. Fixes: 60a943245413 ("drm/i915/execlists: Drop clear_gtiir() on GPU reset") Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180716125424.5715-1-chris@chris-wilson.co.uk Martin, OK to close? Still happening... https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_98/fi-kbl-soraka/igt@drv_suspend@sysfs-reader.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_97/fi-kbl-soraka/igt@drv_suspend@sysfs-reader.html (In reply to Martin Peres from comment #3) > Still happening... > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_98/fi-kbl-soraka/ > igt@drv_suspend@sysfs-reader.html > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_97/fi-kbl-soraka/ > igt@drv_suspend@sysfs-reader.html But they are not the same bug. This issue used to occur in every round of drm-tip execution? Not seen since 1 month 1 week or 22 rounds of drm-tip execution. 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.