Summary: | [BDW] GPU HANG: ecode 0:0x00200003 on resume from suspend (fixed on drm-intel-next and up) | ||
---|---|---|---|
Product: | DRI | Reporter: | Timo Aaltonen <tjaalton> |
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: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Timo Aaltonen
2014-10-15 10:32:12 UTC
hm, can't attach error-state files since they are >3MB, so put it here: http://koti.kapsi.fi/~tjaalton/bdw/3.17.0-error-state-resume Thank you Timo. It would be good if you could bisect the development branch to identify what patches fix the issue. So we would be able to mark it for Stable. Can you please help us on that? sure thing, easiest to test drm-intel-next-* builds first.. Apparently the patch that fixes it is: http://cgit.freedesktop.org/drm-intel/commit/drivers/gpu/drm/i915?h=drm-intel-next&id=6689c167ae14c312972e89be1121e933e4de0001 drm/i915: Rework GPU reset sequence to match driver load & thaw This patch is to address Daniels concerns over different code during reset: http://lists.freedesktop.org/archives/intel-gfx/2014-June/047758.html "The reason for aiming as hard as possible to use the exact same code for driver load, gpu reset and runtime pm/system resume is that we've simply seen too many bugs due to slight variations and unintended omissions." Tested using igt drv_hangman. V2: Cleaner way of preventing check_wedge returning -EAGAIN V3: Clean the last_context during reset, to ensure do_switch() does the MI_SET_CONTEXT. As per review. Signed-off-by: McAulay, Alistair <alistair.mcaulay@intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com> [danvet: Rebase over ctx->ppgtt rework and extend the comment in check_wedge a bit.] Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Thanks! Verified with v3.17.0 + the original v3 patch from the list (that one applied). Tested-by: Timo Aaltonen <timo.aaltonen@canonical.com> |
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.