Bug 736859

Created attachment 522207 [details]
intel_reg_dumper output, 2 screens active

intel_reg_dumper output, 2 screens active. Small screen (main) is now on the left, I want it on the right.

Created attachment 522208 [details]
intel_reg_dumper output, 2 screens active, small on the right

Created attachment 522209 [details]
intel_reg_dumper output, re-arrange: big screen now off

re-arranged the screen so big one on the left and small on the right. Big screen turned off after switching.

found some messages in the kernel log which might be related:

[ 1462.198454] [drm:intel_disable_transcoder] *ERROR* failed to disable transcoder
[ 1697.377116] [drm:intel_disable_transcoder] *ERROR* failed to disable transcoder
[ 1878.172624] [drm:intel_disable_transcoder] *ERROR* failed to disable transcoder
[ 1942.191463] HDMI hot plug event: Codec=3 Pin=5 Presence_Detect=1 ELD_Valid=0
[ 1942.191507] HDMI status: Codec=3 Pin=5 Presence_Detect=1 ELD_Valid=0
[ 2031.088363] [drm:intel_disable_transcoder] *ERROR* failed to disable transcoder
[ 2155.331793] [drm:intel_disable_transcoder] *ERROR* failed to disable transcoder
[ 2355.297291] gnome-control-c[3063] general protection ip:7f17d0d3e6fc sp:7fffd611be90 error:0 in libdisplay.so[7f17d0d35000+10000]
[ 2379.001163] gnome-control-c[3208] general protection ip:7f9e53a896fc sp:7fffe68a7360 error:0 in libdisplay.so[7f9e53a80000+10000]
[ 2575.523784] [drm:intel_disable_transcoder] *ERROR* failed to disable transcoder

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

OK, attaching file for various tested scenario's.
There is no /etc/X11/xorg.conf and there are no backtraces in the Xorg.*.log* files.

*scenario 1*
Booted with only 1 screen attached. 
Files:
dmesg-`uname -r`-drm.debug-single-screen.txt
messages-drm.debug-single-screen.txt
Xorg.0.log-drm-debug-booted-with-single-screen

Attached 2nd screen. The 2nd screen only turn on when I start System Settings->Displays.

Files:
dmesg-`uname -r`-drm.debug-attached-2nd-screen.txt
messages-drm.debug-attached-2nd-screen.txt

Switched screens (first time it worked):
dmesg-`uname -r`-drm.debug-switched-screens.txt
More switching (stays black):
dmesg-`uname -r`-drm.debug-switched-screens-stayed-black.txt
Some more switching:
dmesg-`uname -r`-drm.debug-switched-screens-few-times-stayed-black.txt

*scenario 2*
Booted with 2 screens attached. Things of interest. The login screen came up on the bigger screen (on the left). After login in gnome-panel came up on the smaller screen (on the right) (??).

Files:
dmesg-`uname -r`-booted-with-2screens.txt
messages-drm.debug-booted-with-2screens.txt
Xorg.0.log-booted-with-2screens

Did some switching, 1 screen stayed black:
messages-drm.debug-booted-with-2screens-switched-black.txt

Thing of interest: sometimes the Displays app goes to the black screen only to return when the timeout runs out.

If you need more info, just let me know.

Created attachment 522463 [details]
see comment

Created attachment 522464 [details]
see comment

Created attachment 522465 [details]
see comment

Created attachment 522466 [details]
see comment

Created attachment 522467 [details]
see comment #6

Created attachment 522468 [details]
see comment #6

Created attachment 522469 [details]
see comment #6

Created attachment 522470 [details]
see comment #6

Created attachment 522471 [details]
see comment #6

Created attachment 522472 [details]
see comment #6

Created attachment 522473 [details]
see comment #6

Created attachment 522474 [details]
see comment #6

Created attachment 522475 [details]
see comment #6

Created attachment 522476 [details]
see comment #6

Created attachment 522477 [details]
see comment #6

Bugzilla is now probably out of diskspace ;-)

Any progress on this?

Haven't heard back since I submitted megabytes of logs files. Is this still under investigation? If not, I will close this bug.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.