Created attachment 434396 [details] xorg log Description of problem: 100% cpu usage from Xorg Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.8.99.905-2.20100716.fc14.x86_64 How reproducible: always Steps to Reproduce: n/a Actual results: Expected results: Additional info:
Created attachment 434737 [details] Xorg.0.log when Xorg is consuming 100% of CPU I'm seeing this as well. System is Thinkpad X200, Intel graphics. No xorg.conf.
A bit more information on this. I downgraded back to xorg-x11-server-common-1.8.99.904-6.20100702.fc14.x86_64.rpm xorg-x11-server-debuginfo-1.8.99.904-6.20100702.fc14.x86_64.rpm xorg-x11-server-devel-1.8.99.904-6.20100702.fc14.x86_64.rpm xorg-x11-server-Xorg-1.8.99.904-6.20100702.fc14.x86_64.rpm And the problem remained: 100% Xorg cpu utilization. I then noticed this in /var/log/messages: Jul 27 09:17:05 tlondon /sbin/mingetty[1691]: tty1: invalid character 0x1c in login name Jul 27 09:17:10 tlondon systemd[1]: getty holdoff time over, scheduling restart. Jul 27 09:17:10 tlondon kernel: systemd[1]: getty holdoff time over, scheduling restart. Jul 27 09:17:10 tlondon systemd[1]: Unit getty entered maintenance state. Jul 27 09:17:10 tlondon kernel: systemd[1]: Unit getty entered maintenance state. Jul 27 09:17:10 tlondon systemd[1]: getty holdoff time over, scheduling restart. Jul 27 09:17:10 tlondon kernel: systemd[1]: getty holdoff time over, scheduling restart. Jul 27 09:17:11 tlondon systemd[1]: getty holdoff time over, scheduling restart. Jul 27 09:17:11 tlondon systemd[1]: Unit getty entered maintenance state. Jul 27 09:17:11 tlondon kernel: systemd[1]: getty holdoff time over, scheduling restart. <<<SNIP>>> etc. So, two things: 1. logging off and logging back in (not shutting down and rebooting) seems to "fix this for me". 2. Could this be an issue with systemd? I haven't tried this with upstart.
(In reply to comment #0) > Created an attachment (id=434396) [details] > xorg log > > Description of problem: > 100% cpu usage from Xorg How did you achieve this interesting result? Also, 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), * 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.
For me, this seems to be a systemd issue. Following the workaround in https://bugzilla.redhat.com/show_bug.cgi?id=614454#c7 appears to "make this work for me". Not sure this is the same issue as originally posted.
Reporter, does the workaround in bug 614454 comment 7 work for you?
@Matej Seems to work. I need to pay more attention to syslog. Cheers, Ritesh
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Thank you for letting us know.