<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - kms_frontbuffer_tracking - FBC disabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=105359#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - kms_frontbuffer_tracking - FBC disabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=105359">bug 105359</a> from <a class="email" href="mailto:marta.lofstedt@intel.com" title="Marta Löfstedt <marta.lofstedt@intel.com>"> Marta Löfstedt</a> <pre>I now found this to be even stranger than anticipated: checking the i915_FBC_state while running kms tests I have ended up way to many states for this to be sane: After reboot: FBC enabled Compressing: yes after killing lightdm: FBC disabled: framebuffer not tiled or fenced after running some kms tests: FBC disabled: frontbuffer write or FBC disabled: no suitable CRTC for FBC or FBC disabled: FBC enabled (active or scheduled) FBC worker scheduled on vblank 154675, now 154675 My recent idea was to set a warn on disabled: + if (strstr(buf, "FBC disabled: ")) + { + igt_warn("%s\n", buf); + igt_assert(true); + } This would result in the WARN result if FBC was disabled. This would not save any runtime, but it should stop the confusion if the test failed due to timeout or if due to FBC being disable. However, when testing above on a SKL NUCi5 system I always end up with WARN on all tests.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>