<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [HSW BDW SKL BSW] [IGT Basic] kms_pipe_crc_basic is epic fail" href="https://bugs.freedesktop.org/show_bug.cgi?id=92602#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [HSW BDW SKL BSW] [IGT Basic] kms_pipe_crc_basic is epic fail" href="https://bugs.freedesktop.org/show_bug.cgi?id=92602">bug 92602</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>Ok, we need to split this bug up, there's way too many different bugs here. >From the bug filing BKMs: - if the WARNING in dmesg is different, it's a different bug. Special case: for pipe_config mismatch you need to look at the *ERROR* right above. We seem to have mismatches here in has_infoframes (tracked in <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT IGT HSW BDW] has_infoframe pipe config mismatch" href="show_bug.cgi?id=93119">bug #93119</a>), dpll_hw_state.cfgcr1, base.adjusted_mode.crtc_clock and port_clock. The three clock mismatches are probably related. - igt failure below seems to be another issue again. Probably needs a separate bug. rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Thu Nov 26 10:40:57 2015 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Thu Nov 26 10:40:57 2015 suspend-read-crc-pipe-B: Testing connector eDP-1 using pipe B suspend-read-crc-pipe-B: Testing connector HDMI-A-1 using pipe B Test assertion failure function igt_primary_plane_commit_legacy, file igt_kms.c:1532: Failed assertion: ret == 0 Last errno: 22, Invalid argument Stack trace: #0 [__igt_fail_assert+0xf1] #1 [do_display_commit+0xae8] #2 [igt_display_commit2+0xe] #3 [test_read_crc.constprop.1+0x175] #4 [__real_main214+0x2c7] #5 [main+0x29] #6 [__libc_start_main+0xf5] #7 [_start+0x29] #8 [<unknown>+0x29] Subtest suspend-read-crc-pipe-B failed. **** DEBUG **** - once we have split out all the bugs per BKM please add an entry here linking to all the new ones and close this one as invalid/superseeded. All the new bugs should be priority=highest since they're BAT failures. Thanks, Daniel</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>