All tests - abort - abort condition: !chamelium_wait_reachable(chamelium, 20), cannot reach the configured chamelium!|abort condition: !chamelium_wait_all_configured_ports_connected(chamelium, drm_fd), not all configured chamelium ports are connected!

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5618/fi-kbl-7500u/igt@debugfs_test@read_all_entries.html

Starting subtest: read_all_entries
Subtest read_all_entries: SUCCESS (0.039s)
(debugfs_test:1113) igt_kms-CRITICAL: Test abort in function igt_display_require, file ../lib/igt_kms.c:1899:
(debugfs_test:1113) igt_kms-CRITICAL: abort condition: !chamelium_wait_reachable(chamelium, 20)
(debugfs_test:1113) igt_kms-CRITICAL: Last errno: 113, No route to host
(debugfs_test:1113) igt_kms-CRITICAL: cannot reach the configured chamelium!
Test debugfs_test failed.

This log signature indicates that chamelium is not reachable through network. There is two main reasons:

• Chamelium hardware (Arm board) goes sometimes in unresponsive state. Visible indication is flickering debug light (~2Hz) on the board. Recovery happens with Chamelium reboot
• Rarer case is when host wakes from the suspend and there is some shuffling with the network interface and not all hosts are reachable. This has been mitigated with network interface settings, eg. forcing the speed and duplex on both host IF and switch IF so that there is no time spent on handshake