| Message ID | 20190708091716.12252-1-chris@chris-wilson.co.uk (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [i-g-t] i915/gem_eio: Push the forced reset telltales to kmsg | expand |
Chris Wilson <chris@chris-wilson.co.uk> writes: > 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>
diff --git a/tests/i915/gem_eio.c b/tests/i915/gem_eio.c index dc7afb0fd..4d7362d8f 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);
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> --- tests/i915/gem_eio.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)