You are not logged in.
New update fixed the cpu usage for me
Offline
@ eidgeare
Which update do you mean?
Kernel26 2.6.30.4 in testing?
Offline
New update fixed the cpu usage for me
Bah! New updates *fixed* me too... Now in addition to X taking 100% CPU, when I login to KDM it restarts X and spits me back to KDM login screen. I've had to disable KDM just to get into X.
I'm in the middle of re-compiling certain packages for downgrade to make KDM work again...
Funny as I only have "core" and "extra" in pacman, but I swear I must have "testing" enabled somehow?!??
Jacob
Last edited by Jacob (2009-10-13 21:00:32)
Offline
I've just updated my system. The problem is solved... Maybe it's the new version of the kernel (2.6.31.4). Now my server X doesn't take 100% of my CPU.
Offline
Nope.... The updated kernel 2.6.31.4 doesn't solve the problem. The CPU activity on idle has decreased from 30%-50% to 2.7%-12%. Yet under load (scrolling, yakuake menu slide, background auto-change) it still spikes. To contrast that to kernel 2.6.30.6, CPU activity on idle is 0.0% to 2.7%, and everything is smooth under load.
I wonder what shiny untested bobble has worked it's way into the Linux kernel to cause this, and I wonder how to disable it?
Note: If it is KMS it would be very hard to disable, and even though I've tested 2.6.31.4 with KMS blacklisted, when I start X, modules (radeon, ttm, a few others) get loaded into the kernel, not by my doing.
Offline
I updated my system to a custom kernel 2.6.31.4 (with arch linux patchset) and the 100% X CPU bug still exists... It's horrible...
Offline
Its here too...
Cant use my system basicly...
What should i do?
I dont use testing repostory....
Offline
I think there are some issues with the new kernel that are causing various problems for users. If you can find an older kernel, like 2.6.30.x, try it and see if the problems go away. They did for me.
You can find some older kernels here:
oz
Offline
Here i disabled KMS and the 100% usage is gonne...
Offline
The 100% X load problem still exists on my system. I'm using kernel 2.6.31.4 without KMS and a closed source nvidia driver.
Last edited by Flasher (2009-10-15 18:09:33)
Offline
Something new for me:
As i mentioned here one week before the reason for my high Xorg cpu usage was KDM.
Same problem here and in my case it is kdm at vanilla.
I removed it from deamons and cpu seems to act normal.
Until today i had no problems with Xorg. But one hour ago Xorg started to use high CPU again, although KDM was not activated.
Causation this time: It was my systray with Kalarm. I removed Kalarm from autostart and cpu stays at normal level.
I found the solution in this post:
http://forum.kde.org/viewtopic.php?f=20&t=82416#p130587
This bug started after reboot but without any relevant updates or changes to Plasma or Kontact. The interesting thing is that the cpu acts normal even with KDM at deamons now.
I'm kinda confused right now!
P.S.: Sorry, english is only my third language
Last edited by Angry (2009-10-20 15:55:04)
Offline
Hello!
I found the problem. It's a flashplugin bug....
After "pacman -Rs flashplugin" my cpu usage is normal.
There's only one problem left: Inet without flash is boring..
Last edited by Flasher (2009-10-21 20:15:47)
Offline
Hello!
I found the problem. It's a flashplugin bug....
After "pacman -Rs flashplugin" my cpu usage is normal.
There's only one problem left: Inet without flash is boring..
Thats weird, there seems to be many people with a Xorg CPU in KDE but the causations are different.
Offline
AHHHHH!!!!
It wasn't the flashplugin. After removing the flashplugin-package the error comes again..............
Offline
I had the same issue. I have done the following:
I removed kdm from the DAEMONS list in rc.conf. In order to start KDM on boot up, I have enabled it in /etc/inittab
I have uncommented the following line:
x:5:respawn:/usr/bin/kdm -nodaemon
and commented out
#x:5:respawn:/usr/bin/xdm -nodaemon
Right now my cpu usage for X is fine.
2735 root 20 0 124m 57m 8756 S 6.0 3.8 0:33.41 X
Will let you know if the symptoms come back.
(side note, for some reason I already had it enabled in inittab and also loading in DAEMONS....weird)
Offline
Just performed a cold boot to test and my cpu usage for X is 2.0%
looks promissing.
Offline
I did the following:
rc.conf:
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
DAEMONS=(location syslog-ng acpid hal wicd avahi-daemon netfs crond sshd alsa cups)
/etc/inittab:
# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >& /dev/null
# End of file
But after these changes kdm doesn't start anymore. I get a console login (without X)
Offline
Forgot to change the following:
id:3:initdefault:
to
id:5:initdefault:
Now, kdm is starting. I hope this is the solution. I'm testing it
Offline
Until now ist looks great
Do you have a bug report for this error? Maybe at kde.org? I don't found any matching bug report.
Last edited by Flasher (2009-10-24 12:43:39)
Offline
oops, yeah forgot to mention that obviously your default runlevel needs to be 5. If 3 starts with just a console, it means it's working properly
I haven't filed a bug report yet. You think it's a KDE bug or more an Arch bug since I don't think most distros use rc.conf to start daemons?
Offline
Ok, after hours of testing: the X-server works with normal cpu usage. Tomorrow I open a bug report at archlinux.org. Maybe it's a kde-bug, but this should decide the kdm maintainer of our distro
Offline
oh, yeah I thought it sounds more like an Arch bug to me so I went and filed the bug. FS#16827. If the Arch devs decide it's more of a KDE bug, I'll go ahead and create the required KDE bug.
I'm glad to hear that this fixed the issue for you as well.
w00t! my first ever bug report!
Offline
I don't know if it is the same bug, but with or without compositing (KWin or Compiz) the CPU usage from Xorg is high.
But the problem seems to be Konsole, as running top on it is *very* sluggish and I see a high CPU usage from Xorg. Running top from xterm shows normal values. Actually everything running under Konsole is sluggish and shows artifacts. It's not a compositing problem as I do not experience any other issue with any other application.
no masters to rule us, no gods to fool us
Offline
To anyone experiencing my issue above, here's the relevant thread: http://www.nvnews.net/vbulletin/showthread.php?t=125111
I confirm that switching Konsole to antialiased fonts (I was using Terminus before) restores the smoothness.
no masters to rule us, no gods to fool us
Offline