Red Hat Bugzilla – Bug 477969
Xorg CPU percentage is unusually high
Last modified: 2009-12-18 02:24:39 EST
Description of problem: On an otherwise idle Fedora 10 system, when a terminal window is opened and "top" run, Xorg shows a CPU usage of at least 10%. This percentage increases or decreases if I increase or decrease (respectively) the size of the terminal window. Also, other actions that change the screen display (such as mouse movements, opening or scrolling a browser window) make the CPU percentage of Xorg jump abnormally high (sometimes up to 80% in my observations). This is on a system with 4GB of RAM and a dual-core processor (2 x 2.4GHz).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot system into X Windows
2. Open terminal window and run top command
Xorg shows in top as constantly taking up 10% or more of CPU. This percentage increases if the terminal window size is increased.
Xorg should take 1-3% of CPU resources, as seen on other F10 machines.
I get the same results whether I use an ATI driver or the generic VESA driver.
Today (1/5/2009) our computer was updated with the latest ATI driver (xorg-x11-drv-ati-18.104.22.168.fc10.i386.rpm) and we get the same results as detailed above. None of our Fedora 9 machines have this problem.
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) 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.
Could you please also try to run with "nomodeset" string on the kernel command line (press any Ctrl on startup to get grub menu and then "a" on the chosen kernel to get kernel command line editor)? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 328482 [details]
xorg.conf from affected system
I am attaching 6 files: xorg.conf, Xorg.0.log, Xorg.1.log, Xorg.2.log, Xorg.3.log, and Xorg.0.log.nomodeset. The last one is the Xorg.0.log when booting using the nomodeset option as was requested. The other Xorg.*.log files are with a normal boot.
Thanks for looking into this issue.
Created attachment 328483 [details]
Xorg.0.log from affected system
Created attachment 328484 [details]
Xorg.1.log from affected system
Created attachment 328485 [details]
Xorg.2.log from affected system
Created attachment 328486 [details]
Xorg.3.log from affected system
Created attachment 328487 [details]
Xorg.0.log from affected system (using nomodeset kernel parameter)
Normally I use Feodra on my laptop to diminish the system resource usage. But today I got a new desktop PC, I installed fedora on that one. I found the fans is very loud when I run firefox to browse with some images or videos, it's extremely loud, not normal. But this doesn't happen when I switch to Windows XP on the same machine.
I compared the cpu usage, apparently, the reason why the machine becomes loud is the cpu usage within Fedora. Xorg is always the top 1, at least 10% usage if there is any images on the webpages.
I did a good amount of research for the entire day on Sunday May 10, 2009
Finally on 12th May I referred the following link.
http://www.bramschoenmakers.nl/en/node/549 ( Fixing Plasma performance with the open source Radeon driver )
I implemented the solution provided in the above link on my IBM Thinkpad R40, with ATI Mobility Radeon R40 ( R100 based chip )
i am running Fedora 10
Earlier I used to have a Xorg CPU percentage unusually high
Mostly above 90 % always
I had a slow response especially using Firefox tabbing ( a delay of about 2 seconds )
Also, the response was slow using Dolphin file manager and doing all such tasks
But now after implementing the solution provided in http://www.bramschoenmakers.nl/en/node/549
THE CPU percentage for Xorg process has considerably reduced.
I can use Firefox tabs with ease ( almost immediate response to mouse click )
Also when I click any icon in Dolphin, it opens up almost immediately
I hope my inputs will help in speedy resolution of this bug
I am thankful to Bram Schoenmakers for his valuable solution at http://www.bramschoenmakers.nl/en/node/549
Use the following two options in Xorg.conf under Device section
Option "AccelMethod" "EXA"
Option "AccelDFS" "true"
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.