Bug 892302

Summary: kms radeon DisplayPort gives no signal error in X but works in console
Product: [Fedora] Fedora Reporter: Juha Heljoranta <juha.heljoranta>
Component: xorg-x11-drv-atiAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 14:53:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg output when no signal (step 6)
none
dmesg output when DP works correctly (step 10)
none
DisplayPort-0 section output from xrandr --verbose none

Description Juha Heljoranta 2013-01-06 13:23:52 UTC
Created attachment 673348 [details]
dmesg output when no signal (step 6)

Description of problem:
Monitor DP connection fails to detect signal in X but works in console. Curiously precondition for this bug is that there is an other device connected to the same monitor via DVI.

Version-Release number of selected component (if applicable):
kernel-3.6.11-1.fc17.x86_64
xorg-x11-server-Xorg-1.12.4-2.fc17.x86_64

Steps to Reproduce:
1. Connect monitor DP to laptop
1. Connect monitor DVI to other computer
2. Power on all devices and login to standard fedora graphical session
3. From laptop toggle output to all monitors (tap twice fn-f4)
4. Verify that xrandr shows monitor DP with status "connected"
5. Select DisplayPort from monitor
6. Wait few seconds and monitor says "no signal" (BUG)
7. Verify that xrandr still shows monitor DP with status "connected"
8. Switch to console (ctrl-alt-f2)
9. Select DisplayPort from monitor
10. Wait few seconds and monitor hows the same console as LVDS (SUCCESS)
11. Switch back to X (ctrl-alt-f1)
10. Wait few seconds and monitor now hows the X session (SUCCESS)

So the bug is in step 6. rest of the steps provide a workaround.

Actual results:
DP connection fails to work in X if there is DVI connection to monitor (but works in console).

Expected results:
DP connection should work in X.

Additional info:
# lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] [1002:6760]
Monitor model: ASUS PB278Q

Attaching dmesg output (drm.debug=0xe) from steps 6 and 11 plus relevant output from xrandr.

Comment 1 Juha Heljoranta 2013-01-06 13:26:06 UTC
Created attachment 673349 [details]
dmesg output when DP works correctly (step 10)

Comment 2 Juha Heljoranta 2013-01-06 13:28:02 UTC
Created attachment 673350 [details]
DisplayPort-0 section output from xrandr --verbose

Comment 3 Fedora End Of Life 2013-07-04 04:48:48 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2013-08-01 14:53:34 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.