| Summary: | [CI][SHARDS] igt@runner@aborted - fail - GEM_BUG_ON(intel_context_is_pinned(ce)) | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | high | CC: | intel-gfx-bugs |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | SNB | i915 features: | GEM/Other |
|
Description
Martin Peres
2019-06-03 11:45:55 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * SNB: igt@runner@aborted - fail - Previous test: i915_module_load (reload-with-fault-injection) - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6170/fi-snb-2600/igt@runner@aborted.html - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_4320/fi-snb-2600/igt@runner@aborted.html commit ac543d7145bf3ad13f67a087196e6879e6993aac (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: Fri May 31 12:32:45 2019 +0100 drm/i915: Report an earlier wedged event when suspending the engines On i915_gem_load_power_context() we do care whether or not we succeed in completing the switch back to the kernel context (via idling the engines). Currently, we detect if an error occurs while we wait, but we do not report one if it occurred beforehand (and the status of the switch is undefined). Check the current terminally wedged status on entering the wait, and report it after flushing the requests, as if it had occurred during our own wait. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110824 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190531113245.30042-1-chris@chris-wilson.co.uk The CI Bug Log issue associated to this bug has been archived. New failures matching the above filters will not be associated to this bug anymore. (In reply to Chris Wilson from comment #3) > commit ac543d7145bf3ad13f67a087196e6879e6993aac (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: Fri May 31 12:32:45 2019 +0100 > > drm/i915: Report an earlier wedged event when suspending the engines > > On i915_gem_load_power_context() we do care whether or not we succeed in > completing the switch back to the kernel context (via idling the > engines). Currently, we detect if an error occurs while we wait, but we > do not report one if it occurred beforehand (and the status of the > switch is undefined). Check the current terminally wedged status on > entering the wait, and report it after flushing the requests, as if it > had occurred during our own wait. > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110824 > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> > Link: > https://patchwork.freedesktop.org/patch/msgid/20190531113245.30042-1- > chris@chris-wilson.co.uk Only happened once, a month ago. Closing the issue, thanks! |
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.