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.
References: https://intel-gfx-ci.01.org/tree/drm-tip/igt@[email protected] References: https://bugs.freedesktop.org/show_bug.cgi?id=103289 Suggested-by: Chris Wilson <[email protected]> Signed-off-by: Petri Latvala <[email protected]> CC: Daniel Vetter <[email protected]> CC: Joonas Lahtinen <[email protected]> CC: "Lofstedt, Marta" <[email protected]> CC: Martin Peres <[email protected]> --- Tested on my SNB and the machine survived the test. tests/gem_eio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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); -- 2.14.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
