summaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2019-07-08 10:16:06 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2019-07-08 16:38:03 +0100
commit319675ccbbf3ed4f3f6929edbf5fd1a25b1f258a (patch)
tree31150fed05404b0c3e10923d31a8ea49a16d8482 /tests
parentc6c75e11175baeb6b984e0cc13c6fbe2863a0794 (diff)
i915/gem_eio: Push the forced reset telltales to kmsg
Leave a few more breadcrumbs in the dmesg log to try and spot where the delay occurs. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Diffstat (limited to 'tests')
-rw-r--r--tests/i915/gem_eio.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/tests/i915/gem_eio.c b/tests/i915/gem_eio.c
index dc7afb0f..4d7362d8 100644
--- a/tests/i915/gem_eio.c
+++ b/tests/i915/gem_eio.c
@@ -71,10 +71,11 @@ static void trigger_reset(int fd)
igt_nsec_elapsed(&ts);
+ igt_kmsg(KMSG_DEBUG "Forcing GPU reset\n");
igt_force_gpu_reset(fd);
/* And just check the gpu is indeed running again */
- igt_debug("Checking that the GPU recovered\n");
+ igt_kmsg(KMSG_DEBUG "Checking that the GPU recovered\n");
gem_test_engine(fd, ALL_ENGINES);
igt_drop_caches_set(fd, DROP_ACTIVE);