Bug 103516 - [CI] igt@kms_frontbuffer_tracking@*fbc* - spurious skips - !fbc_not_enough_stolen()
Summary: [CI] igt@kms_frontbuffer_tracking@*fbc* - spurious skips - !fbc_not_enough_s...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-30 13:18 UTC by Marta Löfstedt
Modified: 2017-11-16 09:46 UTC (History)
1 user (show)

See Also:
i915 platform: SNB
i915 features: display/FBC

Attachments

Description Marta Löfstedt 2017-10-30 13:18:47 UTC 
This issue has been going on for a long time on SNB_shards:	

IGT-Version: 1.20-g9ba736ae (x86_64) (Linux: 4.14.0-rc5-CI-CI_DRM_3270+ x86_64)
Primary screen: VGA 1024x768, crtc 0
FBC last action not supported
Can't test PSR: no usable eDP screen.
Sink CRC not supported: primary screen is not eDP
Test requirement not met in function do_status_assertions, file kms_frontbuffer_tracking.c:1708:
Test requirement: !fbc_not_enough_stolen()
Subtest fbc-1p-primscrn-shrfb-msflip-blt: SKIP (0.639s)

This need to be fixed before we can release SNB to pre-merge.

Some examples:
skipped:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3270/shard-snb3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-msflip-blt.html
passed:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3278/shard-snb4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-msflip-blt.html
Comment 1 Marta Löfstedt 2017-10-30 13:53:06 UTC 
It looks like this is a regression that started on CI_DRM_3265.
Comment 2 Marta Löfstedt 2017-10-30 13:56:58 UTC 
I.e. there is a long sequence where all these test was skipped before CI_DRM_3265.
Comment 3 Jani Saarinen 2017-11-16 09:24:39 UTC 
Reference to Ville's patches https://patchwork.freedesktop.org/series/33060/
That re now merged.
Comment 5 Marta Löfstedt 2017-11-16 09:46:52 UTC 
Patch-set integrated to CI_DRM_3351.
The issue appear to be gone!

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.