<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT][BYT,BSW] WARN_ON(dev_priv->uncore.funcs.mmio_readl(dev_priv, (((const i915_reg_t){ .reg = (0x180000 + 0x650C) })), true) & (1 << 27))" href="https://bugs.freedesktop.org/show_bug.cgi?id=101517#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT][BYT,BSW] WARN_ON(dev_priv->uncore.funcs.mmio_readl(dev_priv, (((const i915_reg_t){ .reg = (0x180000 + 0x650C) })), true) & (1 << 27))" href="https://bugs.freedesktop.org/show_bug.cgi?id=101517">bug 101517</a> from <a class="email" href="mailto:krisman@collabora.co.uk" title="krisman@collabora.co.uk">krisman@collabora.co.uk</a> <pre>(In reply to Martin Peres from <a href="show_bug.cgi?id=101517#c0">comment #0</a>) > Starting from CI_DRM_2743, executing the tests > igt@kms_pipe_crc_basic@suspend-read-crc-pipe-[ac] on our baytrails and > braswells may lead to the following WARNING: > > [ 579.071526] [drm:chv_set_cdclk [i915]] *ERROR* timed out waiting for > CDclk change > [ 579.071942] WARN_ON(dev_priv->uncore.funcs.mmio_readl(dev_priv, (((const In the code, this WARN_ON carries the following comment: /* * FIXME is this guaranteed to clear * immediately or should we poll for it? */ WARN_ON(I915_READ(GCI_CONTROL) & PFI_CREDIT_RESEND); Maybe we should consider polling? :-) Anyway, that WARN_ON can be a side effect of the *ERROR* right before it. I'm Looking into that. Also, I don't see much change in the commit log between CI_DRM_2742 and CI_DRM_2743 that would explain it, but I will take a deeper look.</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>