[Bug 104097] [CI][SHARDS] igt at pm_rpm@i2c - fail - Test assertion failure function test_i2c - Failed assertion: diff <= vga_outputs && diff >= 0

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Apr 30 05:10:02 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=104097

--- Comment #15 from Arek Hiler <arkadiusz.hiler at intel.com> ---
Indeed, on ICL we have seen only the (i2c edids = drm edids - 1) failure mode,
e.g.:
    (i915_pm_rpm:12284) DEBUG: i2c edids:1 drm edids:2 vga outputs:0

On other machines we see:
   i915_pm_rpm:1186) DEBUG: i2c edids:1 drm edids:0 vga outputs:0

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-hsw-4770r/igt@i915_pm_rpm@i2c.html

Current implementation is rather naive, and goes through /dev/i2c-* trying to
read out EDID:
         while ((dirent = readdir(dir))) {
                 if (strncmp(dirent->d_name, "i2c-", 4) == 0) {
                         sprintf(full_name, "/dev/%s", dirent->d_name);
                         fd = open(full_name, O_RDWR);
                         igt_assert_neq(fd, -1);
                         if (i2c_edid_is_valid(fd))
                                 ret++;
                         close(fd);
                 }
         }

The drmModeRes part is as sophisticated:
         while ((dirent = readdir(dir))) {
                 if (strncmp(dirent->d_name, "i2c-", 4) == 0) {
                         sprintf(full_name, "/dev/%s", dirent->d_name);
                         fd = open(full_name, O_RDWR);
                         igt_assert_neq(fd, -1);
                         if (i2c_edid_is_valid(fd))
                                 ret++;
                         close(fd);
                 }
         }


I think we should change implementation a bit and add extra logging around
this, i.e. use /sys/class/drm/card?-*/i2c-* to do readouts, and compare EDIDs
on a connector basis, printing out both in case one is corrupted. This may tell
us something about particular screen or connectors that are being troublesome.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190430/98615fac/attachment.html>


More information about the intel-gfx-bugs mailing list