https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_124/fi-skl-6700k2/igt@kms_chamelium@hdmi-crc-bgr565.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_123/fi-skl-6700k2/igt@kms_chamelium@hdmi-crc-bgr565.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_124/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-bgr565.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_123/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-bgr565.html (kms_chamelium:1721) igt_chamelium-CRITICAL: Failed assertion: !chamelium->env.fault_occurred (kms_chamelium:1721) igt_chamelium-CRITICAL: Last errno: 113, No route to host (kms_chamelium:1721) igt_chamelium-CRITICAL: Chamelium RPC call failed: libcurl failed to execute the HTTP POST transaction, explaining: Failed to connect to 192.168.1.221 port 9992: No route to host Test kms_chamelium failed.
[16:09:31] <tsa> ickle_: perfectly scientific explanation for that. Both chameliums lost their "BIOS" setup, defaulted macaddr, and since every one of those boards have the same default mac, it didn't go very well
Update: Last seen drmtip_124 (1 week, 6 days / 157 runs ago). This issue occurred twice in two different platforms. Need to wait for 2 more weeks to close this bug.
For this Chamelium SW was also updated by Tomi
(In reply to Jani Saarinen from comment #3) > For this Chamelium SW was also updated by Tomi No, the problem was that it losts its MAC address parameter, which resulted in the wrong IP being set. This is fixed and can be closed.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.