[igt-dev] [PATCH] i915/gem_eio: increasing the timeout for forced reset completion
krishnaiah.bommu at intel.com
krishnaiah.bommu at intel.com
Mon Apr 18 05:04:17 UTC 2022
From: Bommu Krishnaiah <krishnaiah.bommu at intel.com>
GUC log capture is taking more time on few platforms, so increasing the timeout
Signed-off-by: Bommu Krishnaiah <krishnaiah.bommu at intel.com>
Cc: Konieczny Kamil <kamil.konieczny at intel.com>
Cc: John Harrison <john.c.harrison at intel.com>
Cc: Andi Shyti <andi.shyti at intel.com>
---
tests/i915/gem_eio.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/tests/i915/gem_eio.c b/tests/i915/gem_eio.c
index d9689534d5a..d7fa9e02e92 100644
--- a/tests/i915/gem_eio.c
+++ b/tests/i915/gem_eio.c
@@ -72,8 +72,14 @@ static void trigger_reset(int fd)
igt_kmsg(KMSG_DEBUG "Forcing GPU reset\n");
igt_force_gpu_reset(fd);
- /* The forced reset should be immediate */
- igt_assert_lte(igt_seconds_elapsed(&ts), 2);
+ /* The forced reset should be immediate, even though
+ * GUC log capture is taking more time on few platforms,
+ * so Increasing the timeout
+ */
+ if (gem_using_guc_submission(fd))
+ igt_assert_lte(igt_seconds_elapsed(&ts), 10);
+ else
+ igt_assert_lte(igt_seconds_elapsed(&ts), 2);
/* And just check the gpu is indeed running again */
igt_kmsg(KMSG_DEBUG "Checking that the GPU recovered\n");
--
2.25.1
More information about the igt-dev
mailing list