[PATCH i-g-t 0/2] tests/device_reset: Wait for device nodes to re-appear
Janusz Krzysztofik
janusz.krzysztofik at linux.intel.com
Fri Jul 26 08:34:55 UTC 2024
CI sporadically reports the following issue:
(device_reset:1335) DEBUG: rebind the driver to the device
(device_reset:1335) DEBUG: reopen the device
(device_reset:1335) drmtest-DEBUG: Looking for devices to open using filter 0: sys:/sys/devices/pci0000:00/0000:00:02.0
(device_reset:1335) drmtest-DEBUG: Filter matched | /dev/dri/renderD128
(device_reset:1335) drmtest-WARNING: No card matches the filter! [sys:/sys/devices/pci0000:00/0000:00:02.0]
(device_reset:1335) CRITICAL: Test assertion failure function healthcheck, file ../../../usr/src/igt-gpu-tools/tests/device_reset.c:393:
(device_reset:1335) CRITICAL: Failed assertion: dev->fds.dev >= 0
(device_reset:1335) CRITICAL: Last errno: 22, Invalid argument
(device_reset:1335) CRITICAL: file descriptor dev->fds.dev failed
After rebinding a DRM device driver, we now immediately start looking for
DRM devices that match our PCI filter established before unbind. The
above messages indicate that occasionally not all device nodes are ready
by the time we are doing that.
Introduce a delay to give the kernel a chance to re-create in devtmpfs all
device nodes we are going to scan for.
While being at it, fix an inline comment above an equivalent solution
introduced before to core_hotunplug test.
Janusz Krzysztofik (2):
tests/device_reset: Wait for device nodes to re-appear
tests/core_hotunplug: Fix inline comment on missing device nodes
tests/core_hotunplug.c | 2 +-
tests/device_reset.c | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
--
2.45.2
More information about the Intel-gfx
mailing list