Bug 102410 - [BAT][BDW] igt@kms_frontbuffer_tracking@basic - *ERROR* vblank not available for FBC on pipe X
Summary: [BAT][BDW] igt@kms_frontbuffer_tracking@basic - *ERROR* vblank not available ...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: highest critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-25 14:14 UTC by Martin Peres
Modified: 2017-10-05 19:18 UTC (History)
1 user (show)

See Also:
i915 platform: BDW
i915 features: display/Other

Attachments

Description Martin Peres 2017-08-25 14:14:36 UTC 
On CI_DRM_3003, the machine fi-bdw-5557u generated the following error when running the test igt@kms_frontbuffer_tracking@basic:

[  364.202246] [drm:intel_fbc_work_fn [i915]] *ERROR* vblank not available for FBC on pipe A

Full logs: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3003/fi-bdw-5557u/igt@kms_frontbuffer_tracking@basic.html
Comment 1 Chris Wilson 2017-08-26 11:42:39 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>
Comment 2 Elizabeth 2017-10-04 19:52:02 UTC 
So far, only a dmesg warning on 9/20. Can we close/verify this case?
Comment 3 Elizabeth 2017-10-04 19:53:05 UTC 
(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
Comment 4 Martin Peres 2017-10-04 20:01:56 UTC 
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
Comment 5 Elizabeth 2017-10-05 19:18:24 UTC 
(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.