[intrepid] high cpu usage after boot

[Lacyc3]

Binary package hint: xorg

After boot, X uses 5-60% CPU, after start any programs, its became 80% and higher. Computer became instable.

Description: Ubuntu intrepid (development branch)
Release: 8.10
X Version: 1:7.4~0ubuntu2

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/Xorg
Package: xserver-xorg 1:7.4~0ubuntu2
ProcAttrCurrent: unconfined
ProcEnviron:
 PATH=/sbin:/bin:/usr/sbin:/usr/bin
 LANG=C
SourcePackage: xorg
Uname: Linux 2.6.26-5-generic i686

[Marlon Cisternas Milla (mcisternas-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please attach your X server configuration file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the bug report as individual uncompressed file attachments using the "Attachment:" box below. Could you please also try to run without any /etc/X11/xorg.conf and let Xorg autodetect your display and video card? Please also attach the /var/log/Xorg.0.log from this attempt. Thanks in advance.

[Lacyc3 (lacyc3)]

After autodetect, xorg started, but only blank black picture on the monitor. The gdm started, becouse i heard the sound, but nothing on the monitor and i can't switch to tty1 - tty2..etc and nothing changed if i restart X.

[Bastian Doetsch (bastian-doetsch)]

I see this problem as well - although I can't determine how the effect is triggered. All of a sudden, xorg uses 100% CPU for minutes although I do nothing special causing lots of compiz effects to kick in.

[Bastian Doetsch (bastian-doetsch)]

Here's another log (autodetect, using radeon driver). My xorg.conf is as follows:

Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

[Giorgio Stefanoni (giorgio-stefanoni-deactivatedaccount)]

I can confirm that this problem exists:

Description: Ubuntu intrepid Beta (development branch)
Release: 8.10
X Version: 1:7.4~2ubuntu5
Architecture: x86_64
Uname: Linux callisto 2.6.27-4-generic #1 SMP Wed Sep 24 01:29:06 UTC 2008 x86_64 GNU/Linux

Xorg starts eating up the CPU for several minutes and all in a sudden it returns to work smoothly.

[Bastian Doetsch (bastian-doetsch)]

It seems to be related to Firefox, possibly Flash. The CPU usage goes back to normal when I close Firefox.

[Giorgio Stefanoni (giorgio-stefanoni-deactivatedaccount)]

It seems to be definitely related to Flash, Xorg starts eating up the CPU just when I am on a flash-site, when I close the single tab having flash everything returns to work fine.

[Bastian Doetsch (bastian-doetsch)]

This bug might be related to https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/113184

[Riccardo 'c10ud' (c10ud)]

$ sudo X -version

X.Org X Server 1.5.1
Release Date: 23 September 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-16-server i686 Ubuntu
Current Operating System: Linux rubuntu 2.6.27-5-generic #1 SMP Fri Oct 3 00:38:23 UTC 2008 i686
Build Date: 06 October 2008 03:13:08PM
xorg-server 2:1.5.1-1ubuntu2 (<email address hidden>)
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present

with this update launching/using xawtv sucks a lot of cpu - usually i could watch tv staying @750mhz, now frequency is bumped and xorg uses > 30% of cpu

commands used:
xawtv -device /dev/video1 -vbidev /dev/vbi0 -nodga
or
xawtv -device /dev/video1 -vbidev /dev/vbi0 -nodga -noxv

doesn't matter - prior to upgrading today, everything was working with no so much cpu load.

[Riccardo 'c10ud' (c10ud)]

ok found where the problem was.

xorg (wrongly) chose radeonhd driver instead of radeon one :)

i solved explicity choosing Driver "radeon" in xorg.conf

lspci:
01:00.0 VGA compatible controller: ATI Technologies Inc RV530 [Radeon X1600]
01:00.1 Display controller: ATI Technologies Inc RV530 [Radeon X1600] (Secondary)

[Bob/Paul (ubuntu-launchpad-bobpaul)]

This bug does not appear to be a duplicate on my system. I've tried ati, radeon, and fglrx drivers in Xorg.conf, and X continues to take high CPU load. This happens as soon as X loads, whether or not Firefox is open. Perhaps there is a different but, unrelated to flash, on 64bit systems? I'm running the 64bit Intrepid and rather wish I could turn back to a week or two ago. Attached is the xorg.conf I'm currently using. Here is my lspci related to graphics:

01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M]

[Bob/Paul (ubuntu-launchpad-bobpaul)]

On my system it's definitely related to gnome-settings-daemon somehow. As soon as I log into gnome, even on a newly created test account, /usr/lib/gnome-settings-daemon/gnome-settings-daemon jumps to 20% cpu with X at 60% cpu. Killing gnome-settings-daemon stops the problem, but, of course, gnome doesn't look as pretty. Re-launching the program crashes X. I have no issues with unusually high CPU usage when using flash (it's high when playing flash videos, but that's always been the case and drops when the video is done.)

$ X -version

X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-16-server x86_64 Ubuntu
Current Operating System: Linux Lappy486 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64
Build Date: 24 October 2008 09:06:49AM

$ apt-cache show gnome-settings-daemon

Package: gnome-settings-daemon
Priority: extra
Section: gnome
Installed-Size: 3448
Maintainer: Ubuntu Desktop Team <email address hidden>
Original-Maintainer: Debian GNOME Maintainers <email address hidden>
Architecture: amd64
Version: 2.24.0-0ubuntu3

[Colin (colinnc)]

I was able to get the CPU usage to go down by killing the gnome-settings-daemon as well.

After some investigation I found continuous wabcom errors in the xorg log file.

I commented out all of the wabcom entries in the xorg.conf file, restarted GDM and the problem went away. Make sure you look for wabcom entries in section "ServerLayout" in addition to "InputDevice" sections.

[Bob/Paul (ubuntu-launchpad-bobpaul)]

Work around confirmed. Removing wacom from the xorg.conf works for me, as well.

[Daniel Bonniot de Ruisselet (bonniot-users)]

I have the same 60% X / 20% gnome-settings-daemon bug, and removing wacom from x.org fixes it as well. That one is definitely NOT a duplicate of bug #113184. But is this the original reporter's bug, or should a new one be opened?