Red Hat Bugzilla – Bug 815427
xrandr locks up Xorg (CPU ~ 100%)
Last modified: 2013-07-31 21:10:59 EDT
Description of problem:
On friday I upgraded my system to Fedora 17 using preupgrade. When logging into gnome3, the system freezes: the mouse cursor is suddenly pinned on the left side of the screen, top shows Xorg as taking just under 100% of the CPU, and login fails to progress. I have to remotely "killall -9 Xorg" to return to the login screen. The gdm login screen does seem to be responsive, though, so Xorg isn't entirely broken.
I also have notion (the current incarnation of the ion3 WM) on this machine, and I couldn't log into a notion session, either. I could log into a fluxbox session, however. I started commenting out lines in my .xsession file (that I use to log into notion), and I found that the line causing the problem is:
xrandr --output DVI-0 --left-of VGA-0
Once I commented out that line, I could log into a notion session just fine. My gnome3 session also has the monitors "switched", and I assume that gnome3 uses xrandr to do that at startup, which is why I couldn't log into gnome3 either.
I've no idea if the problem is xorg, xrandr, or the radeon driver I'm using.
Version-Release number of selected component (if applicable):
Locks up every time.
Steps to Reproduce:
1. xrandr --output DVI-0 --left-of VGA-0
100% CPU usage, Xorg locks up, mouse cursor pinned to left side of screen.
None of the above.
Created attachment 579596 [details]
Xorg.0.log (no xorg.conf file)
Created attachment 579599 [details]
Xorg.0.log (no xorg.conf file)
Created attachment 579605 [details]
Created attachment 579622 [details]
dmesg w/ drm.debug=14 log_buf_len=16M
Booting w/ "nomodeset" breaks xrandr (as far as I can tell), so I can't test w/ nomodeset on the boot line.
Probably a radeon driver bug (either userspace or kernel).
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.