<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][DRMTIP] igt@kms_chamelium@dp-edid-read - warn - Chamelium RPC call failed: RPC failed at server. <class 'chameleond.utils.i2c.I2cBusError'>:I2C access error" href="https://bugs.freedesktop.org/show_bug.cgi?id=109483#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][DRMTIP] igt@kms_chamelium@dp-edid-read - warn - Chamelium RPC call failed: RPC failed at server. <class 'chameleond.utils.i2c.I2cBusError'>:I2C access error" href="https://bugs.freedesktop.org/show_bug.cgi?id=109483">bug 109483</a> from <a class="email" href="mailto:stuart.summers@intel.com" title="Stuart Summers <stuart.summers@intel.com>"> Stuart Summers</a> <pre>From initial analysis of the logs themselves, the tests are passing, but it appears we're getting an out of band error during DP hotplug, specifically an error code sent to IGT as a result of a command sent via XML-RPC. I don't see anything obvious in dmesg at this point indicating the time in which the error occurred with respect to the passing dp-edid-read subtest. The two commands sent as part of dp-edid-read are "ApplyEdid" and "Plug", so perhaps the plug event is taking too long to return or getting some unexpected i2c delays? I do see this around the time of the failure (dmesg): <7>[ 145.024275] [drm:i915_hotplug_work_func [i915]] Connector DP-1 (pin 5) received hotplug event. <7>[ 145.024306] [drm:intel_dp_detect [i915]] [CONNECTOR:85:DP-1] <7>[ 145.024577] [drm:drm_fb_helper_hotplug_event.part.24] <7>[ 145.024627] [drm:drm_setup_crtcs] <7>[ 145.025115] [drm:intel_dp_read_dpcd [i915]] DPCD: 11 0a 84 01 01 00 01 00 02 00 00 00 00 00 00 <7>[ 145.025517] [drm:intel_dp_print_rates [i915]] source rates: 162000, 216000, 270000, 324000, 432000, 540000 <7>[ 145.025558] [drm:intel_dp_print_rates [i915]] sink rates: 162000, 270000 <7>[ 145.025598] [drm:intel_dp_print_rates [i915]] common rates: 162000, 270000 <7>[ 145.026021] [drm:drm_dp_read_desc] DP sink: OUI 00-00-00 dev-ID HW-rev 0.0 SW-rev 0.0 quirks 0x0000 <7>[ 145.026062] [drm:intel_dp_detect [i915]] MST support? port B: yes, sink: no, modparam: yes <7>[ 145.029336] [drm:drm_dp_i2c_xfer] Partial I2C reply: requested 16 bytes got 2 bytes <7>[ 145.032999] [drm:drm_dp_i2c_xfer] Partial I2C reply: requested 2 bytes got 1 bytes <7>[ 145.033493] [drm:drm_dp_i2c_do_msg] I2C defer <7>[ 145.067560] [drm:drm_dp_i2c_xfer] Partial I2C reply: requested 16 bytes got 2 bytes Specifically those last few lines are unique to the dmesg log (only time we get an I2C defer from the Chamelium). I am planning to work on this further early next week when I get access to a Chamelium device to try to reproduce.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>