Summary: | [BAT][BDW] igt@kms_frontbuffer_tracking@basic - *ERROR* vblank not available for FBC on pipe X | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | critical | ||
Priority: | highest | CC: | intel-gfx-bugs |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | BDW | i915 features: | display/Other |
Description
Martin Peres
2017-08-25 14:14:36 UTC
commit 908b6e6e8ab4c1e0c3783be4c4b437ac6fa374ea Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Aug 25 16:02:15 2017 +0100 drm/i915: Quietly cancel FBC activation if CRTC is turned off before worker Since we use a worker to enable FBC on the CRTC, it is possible for the CRTC to be switched off before we run. In this case, the CRTC will not allow us to wait upon a vblank, so remove the DRM_ERROR as this is very much expected. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=102410 Fixes: ca18d51d77eb ("drm/i915/fbc: wait for a vblank instead of 50ms when enabling") Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20170825150215.19236-1-chris@chris-wilson.co.uk Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> So far, only a dmesg warning on 9/20. Can we close/verify this case? (In reply to Elizabeth from comment #2) > So far, only a dmesg warning on 9/20. Can we close/verify this case? Or would be better wait a little more? https://intel-gfx-ci.01.org/tree/drm-tip/fi-bdw-5557u.html For devs and CI in general. FIXED == done. I guess someone forgot to move change it to CLOSED. Sorry about that! PS: When looking at the history of a bug, I would suggest you check what cibuglog has to say as it has a much longer history: https://intel-gfx-ci.01.org/cibuglog/index.html%3Faction_failures_history=-1&failures_test=igt@kms_frontbuffer_tracking@basic&failures_machine=fi-bdw-5557u.html (In reply to Martin Peres from comment #4) > ... > PS: When looking at the history of a bug, I would suggest you check what > cibuglog has to say as it has a much longer history: > https://intel-gfx-ci.01.org/cibuglog/index.html%3Faction_failures_history=- > 1&failures_test=igt@kms_frontbuffer_tracking@basic&failures_machine=fi-bdw- > 5557u.html Understood. Thanks for the information. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.