From: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>,
Krzysztof Karas <krzysztof.karas@intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
intel-gfx@lists.freedesktop.org,
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Subject: [PATCH i-g-t] tests/intel/i915_module_load: Ignore missing PCI reset
Date: Thu, 20 Aug 2026 20:41:43 +0200 [thread overview]
Message-ID: <20260820184304.1968012-2-janusz.krzysztofik@linux.intel.com> (raw)
Subtest fault-injection now performs PCI device reset before every driver
bind attempt and fails if that reset doesn't succeed. That was OK if all
devices being tested supported a PCI reset method. However, machines
with DG1 SKU 0x4905 used in CI suffer from device breakage and system
freezes after any PCI reset attempts, triggering CI job aborts. That's
going to change soon with an upcoming kernel patch that disables PCI
reset capabilities on that card.
Attempt PCI reset and fail if not successful only if supported, otherwise
submit a debug message and continue the exercise. With that in place,
the subtest should no longer abort CI jobs on DG1 as soon as the above
mentioned kernel fix is in place.
Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
---
tests/intel/i915_module_load.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/intel/i915_module_load.c b/tests/intel/i915_module_load.c
index 26e30a1000..68e2386465 100644
--- a/tests/intel/i915_module_load.c
+++ b/tests/intel/i915_module_load.c
@@ -463,7 +463,8 @@ inject_fault_probe(int fd, const char pci_slot[], const char function_name[],
injection_list_add(function_name);
set_retval(function_name, inject_error);
- igt_assert(igt_sysfs_set(devicefd, "reset", "1"));
+ if (!igt_debug_on(!igt_sysfs_has_attr(devicefd, "reset")))
+ igt_assert(igt_sysfs_set(devicefd, "reset", "1"));
igt_kmod_bind("i915", pci_slot);
err = -errno;
--
2.54.0
next reply other threads:[~2026-08-20 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 18:41 Janusz Krzysztofik [this message]
2026-08-20 20:04 ` ✓ Xe.CI.BAT: success for tests/intel/i915_module_load: Ignore missing PCI reset Patchwork
2026-08-20 20:26 ` ✓ i915.CI.BAT: " Patchwork
2026-08-20 21:21 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-08-21 1:42 ` ✗ i915.CI.Full: " Patchwork
2026-08-21 8:37 ` Janusz Krzysztofik
2026-08-21 11:49 ` Ravali, JupallyX
2026-08-21 9:59 ` [PATCH i-g-t] " Kamil Konieczny
2026-08-21 11:34 ` ✓ i915.CI.Full: success for " Patchwork
2026-08-26 7:22 ` [PATCH i-g-t] " Krzysztof Karas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260820184304.1968012-2-janusz.krzysztofik@linux.intel.com \
--to=janusz.krzysztofik@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.com \
--cc=sebastian.brzezinka@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.