Created attachment 599564 [details] Xorg.1.log Segfault in Xorg when trying to use VGASWITCHEROO on Lenovo ThinkPad E520. I have set up my Thinkpad E520 in the BIOS to use the swithcalble graphics and it all wors up to the point of trying to switch to the discrete graphics card, when I get a segfault in xorg and the system freezes. To reproduce : 1/ Blacklist radeon in /etc/modprobe.d/blacklist.conf (otherwise the system sill not boot) 2/ Set BIOS to use Switchable Graphics 3/ Reboot 4/ modprobe radeon 5/ as root "# cat /sys/kernel/debug/vgaswitcheroo/switch" to see the state 6/ as root "# echo DDIS > /sys/kernel/debug/vgaswitcheroo/switch" to set up to use discrete graphics 7/ restart X. Logging out in Gnome 3.4 seems to be enough to cause X to restart. For me this causes a hard freeze, but Xorg.1.log contains fault info after restarting
I'm experiencing this too with exactly the same errors in Xorg.[0-9]+.log. Also, the frozen state can be fixed by pressing Alt-F2, then blindly logging in as root and typing: echo IGD > /sys/kernel/debug/vgaswitcheroo/switch I wonder if these lines in the log mean anything: [ 77.309] (WW) RADEON(0): No outputs definitely connected, trying again... [ 77.309] (WW) RADEON(0): Unable to find connected outputs - setting 1024x768 initial framebuffer Apparently, Xorg doesn't know that all outputs are really connected to IGD. As long as framebuffer consoles are also frozen, neither does the kernel.
Oh, forgot to mention that my laptop is Lenovo ThinkPad G570. (Lenovo-specific issue?)
Created attachment 673992 [details] a part of dmesg output with commands executed from console Here's a part of dmesg output interleaved with commands (starting with '#') typed in the virtual console as root. The video froze after prefdm service restart.
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.
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.