Bug 44304

Summary: [ivb 3pipe] "*ERROR* failed to set mode on [CRTC:5]" while plug in the 3rd monitor
Product: DRI Reporter: Yi Sun <yi.sun>
Component: DRM/IntelAssignee: Jesse Barnes <jbarnes>
Status: CLOSED FIXED QA Contact:
Severity: major    
Priority: high CC: ben, chris, daniel, guang.a.yang, jbarnes
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 44622    
Attachments:
Description Flags
dmesg file
none
The dmesg when the 3 displays work well. none

Description Yi Sun 2011-12-29 22:54:46 UTC 
System Environment:
--------------------------
Arch:           x86_64
Platform:       IvyBridge
Libdrm: Libdrm: (master)2.4.29-3-gef20301a11afae50bfe127002913dbd0b81ddccc
Mesa:           (master)ec4851253bbf7fd7d11c5570f19f9733a885e471
Xserver:       
(master)xorg-server-1.11.99.1-56-gfb22a408c69a84f81905147de9e82cf66ffb6eb2
Kernel:    (drm-intel-next)097354eb14fa94d31a09c64d640643f58e4a5a9a

Bug detailed description:
-------------------------
If we boot machine with only one monitor after that plug in another two monitors, one of the 3 monitor doesn't come up, and the error information "*ERROR* failed to set mode on [CRTC:5]". In that case, all the 3 monitors would get the normal pictures while running "testdisplay -m".

But if we boot machine with two or even three monitors, the issue doesn't occurs. 
The issue exists on both mobile and desktop platform.
Comment 1 Yi Sun 2011-12-29 22:58:51 UTC 
Created attachment 54967 [details]
dmesg file
Comment 2 Daniel Vetter 2012-01-28 13:44:39 UTC 
Can you please also append the dmesg (with drm.debug setting) of the working 3 monitor configuration?
Comment 3 Yi Sun 2012-02-07 18:45:47 UTC 
Created attachment 56732 [details]
The dmesg when the 3 displays work well.
Comment 4 Yi Sun 2012-02-20 23:11:36 UTC 
I think the latest -testing branch has the fix of this issue.
Comment 5 Daniel Vetter 2012-02-21 00:22:32 UTC 
> --- Comment #4 from sunyi <yi.sun@intel.com> 2012-02-20 23:11:36 PST ---
> I think the latest -testing branch has the fix of this issue.

I'm a bit confused: Does this mean latest -testing works and we can
close this? Or do you still need to test & confirm?
Comment 6 Yi Sun 2012-02-21 00:30:15 UTC 
(In reply to comment #5)
Oh, I meant the the latest -testing works, and we could close this.


> > --- Comment #4 from sunyi <yi.sun@intel.com> 2012-02-20 23:11:36 PST ---
> > I think the latest -testing branch has the fix of this issue.
> 
> I'm a bit confused: Does this mean latest -testing works and we can
> close this? Or do you still need to test & confirm?
Comment 7 Elizabeth 2017-10-06 14:51:16 UTC 
Closing old verified.

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.