diff options
author | Petri Latvala <petri.latvala@intel.com> | 2017-10-30 11:48:19 +0200 |
---|---|---|
committer | Petri Latvala <petri.latvala@intel.com> | 2017-11-06 18:00:43 +0200 |
commit | b9f2abda9503bd55690cf3c2ccf2f20e8fc19ab3 (patch) | |
tree | 96427fa03d2cc605c7b70b71e849c160ceb18711 | |
parent | 2204b3b17be0c05027ed6df2def3fff2b9a9c841 (diff) |
tests/gem_eio: Nerf in-flight-suspend
Use TEST_NONE instead of TEST_DEVICES to prevent a machine death that
happens on a particular model of SNB (2600 is affected, 2520m is
not). Reset is unreliable, but the exact setup to trigger the death
and how to work around it are not found at this time. There is some
kind of a race lurking, and this commit is a workaround that avoids
it, leaving the test still exercising some of the codepaths.
References: https://intel-gfx-ci.01.org/tree/drm-tip/igt@gem_eio@in-flight-suspend.html
References: https://bugs.freedesktop.org/show_bug.cgi?id=103289
Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
CC: Daniel Vetter <daniel.vetter@ffwll.ch>
CC: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
CC: "Lofstedt, Marta" <marta.lofstedt@intel.com>
CC: Martin Peres <martin.peres@linux.intel.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
-rw-r--r-- | tests/gem_eio.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/gem_eio.c b/tests/gem_eio.c index 2d4c95f4..ca0020f1 100644 --- a/tests/gem_eio.c +++ b/tests/gem_eio.c @@ -238,7 +238,7 @@ static void test_inflight_suspend(int fd) } igt_system_suspend_autoresume(SUSPEND_STATE_MEM, - SUSPEND_TEST_DEVICES); + SUSPEND_TEST_NONE); igt_post_hang_ring(fd, hang); |