Xorg gets into a 100%-cpu-consumption but usable state if its initial controlling tty is somehow detached or made unavailable. strace indicates a tight loop including select([...]) => returning fd5 ioctl(5, TCFLSH, 0x2) => EIO, on a filehandle /dev/tty1, with no other processes with that tty open. systemtap indicates the kernel is treating the filehandle with the hung_up_tty* group of functions. See also https://bugs.launchpad.net/xorg-server/+bug/60487 https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/439138?comments=all where these guys work around the problem by arranging to keep the tty open. Nevertheless, it seems to me that xorg should adapt to the loss of the tty (which it can determine from the EIO error return code), and stop polling it. xorg-x11-server-Xorg-1.6.4-0.1-fc11.x86_64
See also bug #475890 and bug #490829, except in this case, there appears to be no mingetty or whatever else also hammering on tty1.
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 attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 365071 [details] dmesg
Created attachment 365072 [details] Xorg.0.log
Created attachment 365073 [details] Xorg.1.log
Created attachment 365074 [details] Xorg.2.log
Created attachment 365075 [details] Xorg.3.log
Created attachment 365076 [details] Xorg.4.log
Created attachment 365077 [details] Xorg.5.log I logged out and logged back in since this has happened, FYI. There is no xorg.conf file.
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command yum upgrade --enablerepo='*-updates-testing' Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD . Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Matej, information has been provided, including strace logs. It would be rather unfortunate if the only diagnosis / response that we received in exchange is automatic notification about 'please try the new version'. Can you do any level of examination of the new source code, in order to see whether any *relevant* areas have been changed?
I took a brief looks. For starters, this is definitely nothing to do with nouveau. I'd say it belongs on xorg-x11-server. If this is still an issue for you, can you please reassign.
Ben, thanks for taking a look. I agree, the -server seems like the most appropriate component (and the one we initially selected for this bugzilla report). Jeff, can you reproduce this problem still?
No, I can't reproduce the problem.
OK, let's close this then. I hope next time we can nab the bug in flight.