| Summary: | [r600g] xorg consumes 100% cpu and slows down desktop | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Moritz <software> | ||||||
| Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | ||||||||
| Version: | git | ||||||||
| Hardware: | x86-64 (AMD64) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
(In reply to comment #1) > I want to debug it but I do not know how. Please, could you tell me how to > get the relevant informations? When the problem occurs, capture a system profile for a couple of seconds of high CPU usage using perf, sysprof or oprofile, and attach the profile here. Make sure debugging symbols are available for the X server and the radeon driver. > Could it be possible that this problem is not due to x or radeon but another > application? That seems most likely at this point, but let's look at a profile. Created attachment 78641 [details]
perf profiles during high xorg cpu usage
I included a small readme file within the tar archive to clarify the meaning of the different profiles.
Thanks, but perf record without --call-graph only records that the Xorg process is using the CPU, not where exactly that is happening. I suspect you'll also need to run perf report on your end, as the symbols are probably only resolved at that point. It might be easier to use sysprof. I have not experienced problem within (say) the last year. The problem might be resolved. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 78314 [details] xorg logfile (Xorg.0.log) I am experiencing every day a very annoying problem. After some time of using the computer (KDE, Firefox, Thunderbird) the xorg process takes 100% cpu and only recovers after many minutes/hours (without guarantee). No error/warning in the log file, the desktop and all GUI apps just gets terribly slow such that I was instantly trying to install catalyst after recognizing that my card is not yet supported anymore by it. Sometimes the cpu usage is in the 20-50% range and the system only partially slows down. Sometimes the system is sacrified by 100% xorg cpu usage, which makes me think of buying a new GPU. I cannot understand the causes for these xorg cpu loads. The problem occurs with and without KDE desktop effects enabled. The problem started in 2013. I cannot determine the first day exactly. However, in 2012 where I used an old version of xorg (I guess 1.12 and smaller) with an according radeon driver version, the error did NOT show up. I cannot easily roll back because the old arch packages are compiled against library versions which do not exist anymore. Furthermore the problem indicates, that this is a bug in the recent versions of either xorg-server or the radeon driver and we should correct it. I want to debug it but I do not know how. Please, could you tell me how to get the relevant informations? While I am writting xorg is causing again 100% cpu. The xorg logfile is attached. My graphics card is according to lspci a "01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV730XT [Radeon HD 4670] (prog-if 00 [VGA controller])" I am using current archlinux with the following packages: xorg-server 1.14.1-1 xf86-video-ati 1:7.1.0-3 linux 3.8.7-1 (additionally I am using KDE 4.10.2, Firefox 20.0.1 and Thunderbird 17.0.5) The radeon driver (wihtout any xorg.conf file) is configured like this: # cat /sys/class/drm/card0/device/power_profile mid # cat /sys/class/drm/card0/device/power_method profile Please, could you give me hints how to come up with all necessary informations to understand and fix this issue? Could it be possible that this problem is not due to x or radeon but another application? What else can I do to fix this issue/to work around?