[Bug 100918] [APL] igt/gem_workarounds test failed in suspend_resume Subtest

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=100918

--- Comment #6 from Tvrtko Ursulin <tvrtko.ursulin at linux.intel.com> ---
I tried the test on SKL and it seems to work fine there. So I went to
eyeballing the code but did not in the first pass spot any reasons the cited
commit would be bad.

Dmesg is a bit noisy on the other hand. You got these two warns triggered by
suspend resume - is this normal on BXT?

[  192.355269] [drm:skl_set_power_well [i915]] Disabling power well 1
[  192.359796] [drm:skl_set_power_well [i915]] *ERROR* power well 1 disable
timeout
[  192.359809] ------------[ cut here ]------------
[  192.359881] WARNING: CPU: 0 PID: 680 at
drivers/gpu/drm/i915/intel_runtime_pm.c:503 bxt_enable_dc9+0x11e/0x160 [i915]
[  192.359883] Power well on.

[  193.227743] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[  193.227786] ------------[ cut here ]------------
[  193.227840] WARNING: CPU: 0 PID: 693 at drivers/gpu/drm/i915/i915_gem.c:4493
i915_gem_sanitize+0x4a/0x50 [i915]
[  193.227841] WARN_ON(reset && reset != -19)

Worth trying without decoupled mmio perhaps? 

diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
index f80db2ccd92f..df6551609d1f 100644
--- a/drivers/gpu/drm/i915/i915_pci.c
+++ b/drivers/gpu/drm/i915/i915_pci.c
@@ -385,7 +385,7 @@ static const struct intel_device_info
intel_skylake_gt3_info = {
        .has_gmbus_irq = 1, \
        .has_logical_ring_contexts = 1, \
        .has_guc = 1, \
-       .has_decoupled_mmio = 1, \
+       .has_decoupled_mmio = 0, \
        .has_aliasing_ppgtt = 1, \
        .has_full_ppgtt = 1, \
        .has_full_48bit_ppgtt = 1, \

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170504/bc63ebe1/attachment.html>