This bug is for un-duplicating igt@gem_eio@in-flight-suspend from bug 103375 https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3424/shard-glkb2/igt@gem_eio@in-flight-suspend.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3424/shard-kbl4/igt@gem_eio@in-flight-suspend.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3427/shard-apl4/igt@gem_eio@in-flight-suspend.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3407/shard-snb7/igt@gem_eio@in-flight-suspend.html
Note Chris has a fix: https://bugs.freedesktop.org/show_bug.cgi?id=103375#c43 commit 476c4b462e0453c70ee81664c0227fdddc26cbd0 (upstream/master, origin/master, origin/HEAD) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Nov 30 15:00:51 2017 +0000 igt/gem_eio: Increase wakeup delay for in-flight-suspend For in-flight-suspend, we need to wait for the GPU hang within i915_gem_suspend(). This will take 10-20s, which means that the standard wakeup delay of around 15s may occur before we complete the suspend. This causes a pm_system_wakeup(), causing dpm_suspend() to return -EBUSY. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> This fix should no be used for the other tests on bug 103375. The fix is in CI_DRM_3428, but I need to monitor over the weekend since reproduction rate is ~50%
The issue has not been reproduced. I am closing
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.