[Bug 108680] [CI][BAT] igt@kms_chamelium may need to wait a little bit for the network to come back up before connecting to chamelium
https://bugs.freedesktop.org/show_bug.cgi?id=108680
Bug ID: 108680 Summary: [CI][BAT] igt@kms_chamelium may need to wait a little bit for the network to come back up before connecting to chamelium Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: IGT Assignee: dri-devel@lists.freedesktop.org Reporter: martin.peres@free.fr
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5091/fi-skl-6700k2/igt@kms_c...
Starting subtest: common-hpd-after-suspend Subtest common-hpd-after-suspend: SUCCESS (36.272s) (kms_chamelium:3059) igt_chamelium-CRITICAL: Test assertion failure function chamelium_rpc, file ../lib/igt_chamelium.c:303: (kms_chamelium:3059) igt_chamelium-CRITICAL: Failed assertion: !chamelium->env.fault_occurred (kms_chamelium:3059) igt_chamelium-CRITICAL: Last errno: 113, No route to host (kms_chamelium:3059) igt_chamelium-CRITICAL: Chamelium RPC call failed: libcurl failed to execute the HTTP POST transaction, explaining: Failed to connect to 192.168.1.220 port 9992: No route to host
https://bugs.freedesktop.org/show_bug.cgi?id=108680
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|medium |highest Whiteboard| |ReadyForDev
https://bugs.freedesktop.org/show_bug.cgi?id=108680
--- Comment #1 from Jani Saarinen jani.saarinen@intel.com ---
From Petri:
"The story for it is that the test suspends a couple of times and then reports success, and chamelium's atexit handlers attempt to reset the chamelium to a good default state for other tests, and that fails with "No route to host". To be investigated: Is the theory correct that the DUT doesn't have an IP when that happens, or the link is down still? If the dut's network interface is still down from the suspend, can a wait (using netlink) be added to chamelium_rpc() if the interface is coming up, or if this can be made more robust in some other way."
https://bugs.freedesktop.org/show_bug.cgi?id=108680
--- Comment #2 from Petri Latvala petri.latvala@intel.com --- Turns out, fi-skl-6700k2's network interface is just prone to completely disappearing on suspend. Work is ongoing to make IGT instead check for working network connectivity after suspending to mitigate this.
https://bugs.freedesktop.org/show_bug.cgi?id=108680
--- Comment #3 from Martin Peres martin.peres@free.fr --- Another example of this issue. The watchdog just randomly killed the platform before it was done:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5110/fi-skl-6700k2/igt@drv_s...
https://bugs.freedesktop.org/show_bug.cgi?id=108680
Lakshmi lakshminarayana.vudum@intel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|dri-devel@lists.freedesktop |petri.latvala@intel.com |.org |
--- Comment #4 from Lakshmi lakshminarayana.vudum@intel.com --- IGT infrastructure issue rather than driver issue.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org