Bug 475158 - Xorg is using 100% cpu
Summary: Xorg is using 100% cpu
Status: CLOSED DUPLICATE of bug 474586
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-12-08 08:55 UTC by Steve
Modified: 2008-12-09 18:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-12-09 18:04:03 UTC
Type: ---

Attachments (Terms of Use)
Xorg.0.log (171.22 KB, application/octet-stream)
2008-12-08 09:01 UTC, Steve
no flags Details
Xorg log (251.31 KB, text/plain)
2008-12-08 09:19 UTC, Alex Dutton
no flags Details

Description Steve 2008-12-08 08:55:44 UTC
Description of problem:
Since the update from F10 to Rawhide, the xserver is using 100% of cpu.

Version-Release number of selected component (if applicable):

How reproducible:
When the screensaver goes on, cpu goes to normal state, but the screensaver does present a black screen.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Steve 2008-12-08 09:01:24 UTC
Created attachment 326102 [details]

Comment 2 Alex Dutton 2008-12-08 09:19:55 UTC
Created attachment 326104 [details]
Xorg log

I'd like to second this one. Same circumstances (well, was on rawhide before the F10 release).

Xorg acts normally at GDM and then hits 100% on one core after login.

xorg-x11-server-Xorg.x86_64         1.5.3-5.fc10          installed
xorg-x11-drv-i810.x86_64            2.5.0-3.fc11          installed

Comment 3 John Ellson 2008-12-08 12:58:22 UTC
I'm seeing this one too, in my case with the Nvidia 180.11 driver.

However, this only happens with the Gnome desktop, if I log in with KDE then Xorg cpu usage is normal.


Comment 4 John Ellson 2008-12-08 13:07:00 UTC
Something to do with gnome-screensaver maybe?    I just switched to xscreensaver and the Xorg cpu usage dropped to normal.   I tried to switch back to gnome-screensaver, but I don't seem to be able to recreate the problem.

Comment 5 Steve 2008-12-08 13:50:08 UTC
Yes, it has something to do with gnome-screensaver. By killing it, the high cpu-usage is gone. Should i switch bug to gnome-screensaver?

Comment 6 Steve 2008-12-09 18:04:03 UTC

*** This bug has been marked as a duplicate of bug 474586 ***

Note You need to log in before you can comment on or make changes to this bug.