Summary: | [CI] igt@gem_eio@in-flight-suspend - dmesg-warn - *ERROR* timeout waiting for GT wells to go off | ||
---|---|---|---|
Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> |
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: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | BSW/CHT, BYT | i915 features: | GEM/Other |
Description
Marta Löfstedt
2018-03-19 07:13:37 UTC
Looks like it still occurs with commit ac697ae8013a7c7301174c9c3b02a92fe418b7ea Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Mar 15 15:10:15 2018 +0000 drm/i915: Stop engines when declaring the machine wedged so time to accept the failure and turn off the DRM_ERROR. commit e01569ab962145b2fb46f6240bf1f07ec3a6261a Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Apr 9 10:49:05 2018 +0100 drm/i915: Silence debugging DRM_ERROR for failing to suspend vlv powerwells If we try to suspend a wedged device following a GPU reset failure, we will also fail to turn off the rc6 powerwells (on vlv), leading to a *ERROR*. This is quite expected in this case, so the best we can do is shake our heads and reduce the *ERROR* to a debug so CI stops complaining. Testcase: igt/gem_eio/in-flight-suspend #vlv Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105583 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Imre Deak <imre.deak@intel.com> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Acked-by: Jani Nikula <jani.nikula@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180409094905.4516-1-chris@chris-wilson.co.uk This has not stopped happening. Here are the latest failures: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_30/fi-byt-n2820/igt@gem_eio@in-flight-suspend.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_30/fi-bsw-n3050/igt@gem_eio@in-flight-suspend.html (In reply to Martin Peres from comment #3) > This has not stopped happening. Here are the latest failures: > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_30/fi-byt-n2820/ > igt@gem_eio@in-flight-suspend.html > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_30/fi-bsw-n3050/ > igt@gem_eio@in-flight-suspend.html But that kernel was from before the fix was applied. (In reply to Chris Wilson from comment #4) > (In reply to Martin Peres from comment #3) > > This has not stopped happening. Here are the latest failures: > > > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_30/fi-byt-n2820/ > > igt@gem_eio@in-flight-suspend.html > > > > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_30/fi-bsw-n3050/ > > igt@gem_eio@in-flight-suspend.html > > But that kernel was from before the fix was applied. Not being seen after these failures, you were right! Thanks and sorry! |
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.