Description of problem: gdm/xorg crash occurs on boot with Nouveau drivers and GTX 570 card. The monitor is connected to the HDMI port on the card (not the DVI port). Boot messages disappear and the display goes dead (no signal). If fbcon=map:1 is not set, then the display is dead (no signal) throughout the entire boot process. Version-Release number of selected component: xorg-x11-server-Xorg-1.14.4-9.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-mFfvOm/database -seat seat0 -nolisten tcp vt1 executable: /usr/bin/Xorg kernel: 3.14.8-200.fc20.x86_64 open_fds: runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (5 frames) #9 RRSetChanged at randr.c:558 #10 RRScreenSetSizeRange at rrinfo.c:228 #11 xf86RandR12CreateScreenResources12 at xf86RandR12.c:1593 #12 xf86RandR12CreateScreenResources at xf86RandR12.c:842 #13 xf86CrtcCreateScreenResources at xf86Crtc.c:710
Created attachment 913534 [details] File: backtrace
Created attachment 913535 [details] File: cgroup
Created attachment 913536 [details] File: core_backtrace
Created attachment 913537 [details] File: dso_list
Created attachment 913538 [details] File: environ
Created attachment 913539 [details] File: limits
Created attachment 913540 [details] File: maps
Created attachment 913541 [details] File: proc_pid_status
Created attachment 913542 [details] File: var_log_messages
Created attachment 913550 [details] disregard this attachment /var/log/Xorg.0.log
Problem also occurs in the following kernel/xorg combinations: kernel 3.14.8-200.fc20.x86_64 + xorg-x11-server 1.14.4-11.fc20 kernel 3.14.9-200.fc20.x86_64 + xorg-x11-server 1.14.4-11.fc20
Created attachment 913583 [details] another /var/log/Xorg.0.log Removed second unused GPU (AMD 7870) which was previously stubbed out with the pci-stub kernel module, and a change in behavior was observed. With fbcon=map:1 set, and the second GPU physically removed, the display does not go dead, instead it just seems to stop printing console messages and gets stuck at the systemd graphical.target. After reviewing the logs via SSH, it seems that ABRT did not detect a crash this time. Unfortunately there is still no graphical environment. The behavior is similar when the system is booted without fbcon=map:1, except that the display is dead the whole time. If I use the AMD card as the primary card (with the free radeon driver) and use the Nvidia card with the pci-stub driver, the system boots normally with a graphical environment. I'm starting to think that this might be some kind of issue with nouveau, rather than xorg. kernel 3.14.9-200.fc20.x86_64 + xorg-x11-server 1.14.4-11.fc20
Comment on attachment 913550 [details] disregard this attachment disregard this attachment, it is incorrect
Created attachment 913584 [details] Xorg.0.log when crash was occurring initially These are the logs from when the crash was occurring initially
Another user experienced a similar problem: no comments. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /bin/Xorg :9 -ac -nolisten tcp executable: /usr/bin/Xorg kernel: 3.18.6-100.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-14.fc20 reason: Xorg killed by SIGABRT runlevel: unknown type: CCpp uid: 0
Another user experienced a similar problem: I have tried to use the vgaswitcheroo for use the discrete card instead of the integrated reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/X :0 vt1 -background none -nolisten tcp -seat seat0 -auth /var/run/kdm/A:0-XDIVga executable: /usr/bin/Xorg kernel: 3.18.7-100.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-14.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.