Bug 104312

Summary: [CI] igt@kms_setmode@* - WARN - no modes for connector 48
Product: DRI Reporter: Marta Löfstedt <marta.lofstedt>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED WORKSFORME QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: SNB i915 features: display/Other

Description Marta Löfstedt 2017-12-18 08:00:48 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3537/shard-snb3/igt@kms_setmode@clone-exclusive-crtc.html

WARN:
	
(kms_setmode:1418) igt-kms-WARNING: no modes for connector 48

How could this have happened this is all in dmesg before:
<5>[   15.353989] owatch: Using watchdog device /dev/watchdog0
<5>[   15.354163] owatch: Watchdog /dev/watchdog0 is a software watchdog
<5>[   15.355089] owatch: timeout for /dev/watchdog0 set to 370 (requested 370)
<7>[   19.916161] [IGT] kms_chamelium: executing
<7>[   19.964709] [IGT] kms_chamelium: exiting, ret=77
<7>[   20.083697] [IGT] gem_exec_blt: executing
<7>[   20.112074] [IGT] gem_exec_blt: starting subtest cold
<7>[   20.121827] [drm:intel_power_well_enable [i915]] enabling always-on
<7>[   21.520843] [IGT] gem_exec_blt: exiting, ret=0
<7>[   21.521573] [drm:intel_power_well_disable [i915]] disabling always-on
<7>[   21.621926] [IGT] kms_setmode: executing
<7>[   21.653445] [IGT] kms_setmode: starting subtest clone-exclusive-crtc
<7>[   21.653702] [IGT] kms_setmode: exiting, ret=0
<7>[   21.761562] [IGT] kms_flip: executing

nothing suspicious in boot log.
Comment 1 Marta Löfstedt 2018-01-19 08:22:07 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3648/shard-snb2/igt@kms_setmode@invalid-clone-single-crtc-stealing.html

(kms_setmode:1486) igt-kms-WARNING: no modes for connector 48
Comment 2 Marta Löfstedt 2018-02-23 08:09:49 UTC 
Last seen: CI_DRM_3648: 2018-01-19 / 284 runs ago

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.