<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@hdmi-crc|cmp-* - fail - Failed assertion: !chamelium->env.fault_occurred" href="https://bugs.freedesktop.org/show_bug.cgi?id=109635#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@kms_chamelium@hdmi-crc|cmp-* - fail - Failed assertion: !chamelium->env.fault_occurred" href="https://bugs.freedesktop.org/show_bug.cgi?id=109635">bug 109635</a> from <a class="email" href="mailto:stuart.summers@intel.com" title="Stuart Summers <stuart.summers@intel.com>"> Stuart Summers</a> <pre>The failure is basically saying the chamelium is trying to read an I2C slave address and never gets the expected value indicating the video input status reads stable. I'm wondering if there's something faulty with the i2c lines on one of the chamelium boards in CI? There are a couple of I2C related sightings open right now. I haven't been able to reproduce this or <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="show_bug.cgi?id=109483">https://bugs.freedesktop.org/show_bug.cgi?id=109483</a> with a Chamelium board I'm running locally (only running HDMI to a kbl NUC). These failures are all ICL related I'm seeing. That said, the I2C timeout is on the Chamelium side, not the GPU side. Maybe there's some other timing constraint being exposed by ICL here?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>