Forcewake handling is a prime suspect now. Keep ref
always on tgl to test the theory and reveal the coverage.

Testcase: igt/gem_sync
Cc: Chris Wilson <ch...@chris-wilson.co.uk>
Suggested-by: Chris Wilson <ch...@chris-wilson.co.uk>
Signed-off-by: Mika Kuoppala <mika.kuopp...@linux.intel.com>
---
 drivers/gpu/drm/i915/i915_gem.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 141024c66f36..2ab970b4d534 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -1144,7 +1144,10 @@ void i915_gem_sanitize(struct drm_i915_private *i915)
         */
        intel_gt_sanitize(&i915->gt, false);
 
-       intel_uncore_forcewake_put(&i915->uncore, FORCEWAKE_ALL);
+       /* XXX Forcewake handling is a prime suspect now */
+       if (INTEL_GEN(i915) < 12)
+               intel_uncore_forcewake_put(&i915->uncore, FORCEWAKE_ALL);
+
        intel_runtime_pm_put(&i915->runtime_pm, wakeref);
 }
 
-- 
2.17.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to