<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#c4">Comment # 4</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>The latest failure is interesting, since it actually results in a failed test. >From the logs, it's a little unclear in the warn case why we are getting an RPC call to the Chamelium outside of a running test. The assert location is the same as the failure case, so I'd expect the test to fail in the first case as well. That said, given that 1) we don't have full logs for the successful case and 2) we don't have *any* logs coming off of the Chamelium itself, there isn't a lot to go on. I have a patch up on igt-dev which attempts to extract a little more information from the CI log, although it will only hit in a failure case. Unfortunately the patch requires a new package be added to the CI system. I have a request for this in i915-infra: <a href="https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/29">https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/29</a>. Next steps here are to: 1) Reproduce manually - I haven't been successful there since this issue seems specifically related to DP connectors while my test system only has an HDMI connector. I'll look into this next week. 2) Add better logging capability in these kms_chamelium tests. - This is probably better in the long term anyway to reduce debug time of these types of problems. - This logging can also come from IGT or from the chameleond daemon running on the Chamelium board itself. If I can't get traction in IGT, I'll look into updating chameleond. Another thing that might be interesting is to start producing debug logging even for tests which succeed, at least for CI. I'll see if that's a possibility and possibly file another i915-infra request if it looks promising.</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> </ul> </body> </html>