<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@kms_flip@(2x-)absolute-wf_vblank-interruptible - Failed assertion: timercmp(&es->last_received_ts, &es->current_ts, <)" href="https://bugs.freedesktop.org/show_bug.cgi?id=106087#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@kms_flip@(2x-)absolute-wf_vblank-interruptible - Failed assertion: timercmp(&es->last_received_ts, &es->current_ts, <)" href="https://bugs.freedesktop.org/show_bug.cgi?id=106087">bug 106087</a> from <a class="email" href="mailto:stanislav.lisovskiy@intel.com" title="Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>"> Stanislav Lisovskiy</a> <pre>According to the log and my investigations it looks like, for some reason vblank timestamp doesn't get updated in time, for the last 2 calls timestamp has exactly same number, while received timestamp value is correct. According to the information from Martin this looks like a regression since 4.16, I've noticed there were some vblank optimizations, which came with 4.17-rc1, for example like this one: commit 68036b08b91bc491ccc308f902616a570a49227c Author: Dhinakaran Pandiyan <<a href="mailto:dhinakaran.pandiyan@intel.com">dhinakaran.pandiyan@intel.com</a>> Date: Fri Feb 2 21:13:00 2018 -0800 drm/vblank: Do not update vblank count if interrupts are already disabled. Updating vblank counts requires register reads and these reads may not return meaningful values if the device was in a low power state after vblank interrupts were last disabled. So, update the count only if vblank interrupts are enabled. Secondly, this means the registers should be read before disabling vblank interrupts. v2: Don't check vblank->enabled outside it's lock (Chris) However currently this is only suspicion and I might be wrong, I have reverted this commit and now testing with my local machine, however as this issue doesn't always reproduce this might take a while.</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>