<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@kms_chamelium may need to wait a little bit for the network to come back up before connecting to chamelium" href="https://bugs.freedesktop.org/show_bug.cgi?id=108680#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@kms_chamelium may need to wait a little bit for the network to come back up before connecting to chamelium" href="https://bugs.freedesktop.org/show_bug.cgi?id=108680">bug 108680</a> from <a class="email" href="mailto:jani.saarinen@intel.com" title="Jani Saarinen <jani.saarinen@intel.com>"> Jani Saarinen</a> <pre>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."</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>