Bug 108313

Summary:	[CI][DRMTIP] igt@kms_chamelium@hdmi-crc-bgr565 - fail - Last errno: 113, No route to host
Product:	DRI	Reporter:	Martin Peres <martin.peres>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	CLOSED FIXED	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	medium	CC:	intel-gfx-bugs
Version:	XOrg git
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:	ALL	i915 features:	display/Other

Description Martin Peres 2018-10-10 10:48:38 UTC

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.

Comment 1 Martin Peres 2018-10-10 13:19:29 UTC

[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

Comment 2 Lakshmi 2018-10-23 13:10:19 UTC

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.

Comment 3 Jani Saarinen 2018-10-23 13:51:18 UTC

For this Chamelium SW was also updated  by Tomi

Comment 4 Martin Peres 2018-10-23 14:10:50 UTC

(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.