Many of the selftests try to completely fill global resources; resources that are presumed available for bringing up the display. Avoid the contention by simply not bringing up the display!
This does limit the effectiveness of selftesting to GEM for the time being. To exercise KMS from selftests we would essentially have to always mock the displays. References: https://bugs.freedesktop.org/show_bug.cgi?id=103718 Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk> --- tests/drv_selftest.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/tests/drv_selftest.c b/tests/drv_selftest.c index 96dd8bf1..80e515c6 100644 --- a/tests/drv_selftest.c +++ b/tests/drv_selftest.c @@ -28,6 +28,10 @@ IGT_TEST_DESCRIPTION("Basic unit tests for i915.ko"); igt_main { - igt_kselftests("i915", "mock_selftests=-1", NULL, "mock"); - igt_kselftests("i915", "live_selftests=-1", "live_selftests", "live"); + igt_kselftests("i915", + "mock_selftests=-1 disable_display=1", + NULL, "mock"); + igt_kselftests("i915", + "live_selftests=-1 disable_display=1", + "live_selftests", "live"); } -- 2.15.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
