Bug 105724 - [IGT][BAT] igt@kms_busy@basic-flip-[a|b] warn igt-kms-WARNING: Output DP-2 could not be assigned to a pipe
Summary: [IGT][BAT] igt@kms_busy@basic-flip-[a|b] warn igt-kms-WARNING: Output DP-2 co...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-23 22:47 UTC by Elizabeth
Modified: 2018-06-04 09:54 UTC (History)
1 user (show)

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

Attachments
dmesg log (55.18 KB, text/plain)
2018-03-23 22:47 UTC, Elizabeth 		no flags Details
kern_log (424.65 KB, text/plain)
2018-03-23 22:48 UTC, Elizabeth 		no flags Details
View All

Description Elizabeth 2018-03-23 22:47:19 UTC 
Created attachment 138327 [details]
dmesg log

Since 4.16.0-rc6 commit-141def2+ we are seeing this igt warn with test:

igt@kms_busy@basic-flip-a
igt@kms_busy@basic-flip-b

Stdout	
IGT-Version: 1.22-g94e8862 (x86_64) (Linux: 4.16.0-rc6-drm-intel-qa-ww12-commit-9d737ce+ x86_64)
Subtest basic-flip-A: SUCCESS (1.221s)
Test requirement not met in function igt_display_require_output_on_pipe, file igt_kms.c:2014:
Test requirement: !(pipe >= igt_display_get_n_pipes(display))
Pipe C does not exist.
Test requirement not met in function igt_display_require_output_on_pipe, file igt_kms.c:2014:
Test requirement: !(pipe >= igt_display_get_n_pipes(display))
Pipe D does not exist.
Test requirement not met in function igt_display_require_output_on_pipe, file igt_kms.c:2014:
Test requirement: !(pipe >= igt_display_get_n_pipes(display))
Pipe E does not exist.
Test requirement not met in function igt_display_require_output_on_pipe, file igt_kms.c:2014:
Test requirement: !(pipe >= igt_display_get_n_pipes(display))
Pipe F does not exist.
Stderr	
(kms_busy:3713) igt-kms-WARNING: Output DP-2 could not be assigned to a pipe
Comment 1 Elizabeth 2018-03-23 22:48:13 UTC 
Created attachment 138328 [details]
kern_log
Comment 2 Jani Saarinen 2018-03-29 07:11:33 UTC 
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 3 Elizabeth 2018-04-03 21:17:15 UTC 
Still reproducible for both tests:

igt@kms_busy@basic-flip-a
igt@kms_busy@basic-flip-b

Results for igt@kms_busy@basic-flip-a
Result: warn
Out	
IGT-Version: 1.22-gda00bf8 (x86_64) (Linux: 4.16.0-rc7-drm-intel-qa-ww14-commit-29940f1+ x86_64)
Subtest basic-flip-A: SUCCESS (2.407s)
Test requirement not met in function igt_display_require_output_on_pipe, file igt_kms.c:2022:
Test requirement: !(pipe >= igt_display_get_n_pipes(display))
Pipe C does not exist.
Test requirement not met in function igt_display_require_output_on_pipe, file igt_kms.c:2022:
Test requirement: !(pipe >= igt_display_get_n_pipes(display))
Pipe D does not exist.
Test requirement not met in function igt_display_require_output_on_pipe, file igt_kms.c:2022:
Test requirement: !(pipe >= igt_display_get_n_pipes(display))
Pipe E does not exist.
Test requirement not met in function igt_display_require_output_on_pipe, file igt_kms.c:2022:
Test requirement: !(pipe >= igt_display_get_n_pipes(display))
Pipe F does not exist.
Err	
(kms_busy:13776) igt-kms-WARNING: Output DP-2 could not be assigned to a pipe
Comment 4 Francesco Balestrieri 2018-06-01 07:45:25 UTC 
Not seen in new CI buglogger. Closing.
Comment 5 Francesco Balestrieri 2018-06-01 07:48:29 UTC 
Actually passing on CI

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.