jaunty xorg 100% cpu usage
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
after this week xorg driver update the xorg starts using 100% of one cpu core resources.
when i switch between text console (crtl+alt+f2) and back to X, the xorg load goes down.
then again some regular gnome activity causes Xorg load up.
I attached recordmydesktop video. I started recording terminal with top running.
After that i don't do anything. Suddenly xorg processor usage goes up.
And before the end i brought the load down switching display in text mode and back to X.
jaanusrk (jaanus-online) wrote : | #1 |
Cristian Barahona G. (cristianvirtual) wrote : | #2 |
jaanusrk (jaanus-online) wrote : | #3 |
jaanusrk (jaanus-online) wrote : | #4 |
jaanusrk (jaanus-online) wrote : | #5 |
jaanusrk (jaanus-online) wrote : | #6 |
- Xorg.0.log.old Edit (105.4 KiB, application/x-trash)
i installed weekend xorg updates, but they didn't help.
i'm testing the sytem with 2 displays at the moment.
in this setup, when Xorg load goes up, the second display goes black.
and at the end it logged me out, when i switched between text-mode console and back to graphical mode.
attached dualscreen xorg log
jaanusrk (jaanus-online) wrote : | #7 |
- Screenshot.png Edit (9.9 KiB, image/png)
additionally , when i open gnome menu, it adds sometimes icon from menu to panel background.
on attached screenshot is world clock menu item behind 4 applets from right.
it seems to choose latest menu item (i've noticed most often world clock from accessories menu and wireshark from internet menu)
this panel behaviour started at same time with the Xorg problem.
Pedro Villavicencio (pedro) wrote : | #8 |
I'm having a similar issue with my jaunty installation, the cpu usage goes to 100% with an intel card as well and the brightness goes also crazy, after a few minutes the cpu usage does down and everything is back to normal, could be this more like a driver issue?
Changed in xorg: | |
importance: | Undecided → Medium |
Changed in xorg: | |
status: | New → Confirmed |
jaanusrk (jaanus-online) wrote : | #9 |
probably, I installed Intrepid Ibex version of xserver-
its dependencies required other xorg packages downgrade too.
But at the moment the system works well.
Pedro Villavicencio (pedro) wrote : | #10 |
I'm not getting this behavior anymore after latest updates, could you confirm? thanks.
jaanusrk (jaanus-online) wrote : | #11 |
- Xorg.0.log Edit (81.9 KiB, text/plain)
In my computer X still uses 100% of one core.
i found additionally that i can trigger the behaviour when i increase screen backlight with keyboard keys.
i uploaded xorg.log too.
Isaac Clerencia (isaaccp) wrote : | #12 |
Same thing here with an Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller in a MacBook. After some (10 minutes) the CPU goes back to normal and I can use X without any problem.
Compositing seems to hang the machine so I have had to remove compiz though.
Changed in xorg: | |
status: | Confirmed → Triaged |
thedarkwinter (michael-thedarkwinter) wrote : | #13 |
- Xorg.0.log.diff Edit (1.5 KiB, text/x-diff)
Same thing here with Mobile GM965/GL960 on Sony Vaio; however, I have just cycled between Gnome and KDE a few times, and the problem only seems to exists in GNOME (every time).
My xorg.conf is clean (dpkg-reconfigure) and compiz is disabled, though it was working fine (didn't hang my machine)
Attached is a Diff between the Xorg.0.log between Gnome/Kde
Alberto Milone (albertomilone) wrote : | #14 |
Does it help if you kill both gnome-settings-
If yes, then it's a duplicate of this bug:
https:/
Isaac Clerencia (isaaccp) wrote : | #15 |
It sounds quite possible, I'll check it out later.
While Xorg was having high cpu usage, the screen brightness changed constantly, so I guess it might be related. I'll also try to install the new gnome-desktop package that allegedly fixes it.
thedarkwinter (michael-thedarkwinter) wrote : | #16 |
After a cold boot, it has cleared for a while. when it happens again i will try that too.
Alex Parker (bedside-clock) wrote : | #17 |
Yep, killing both gnome-settings-
Pedro Villavicencio (pedro) wrote : | #18 |
same here, marking this as duplicate of bug 307306. thanks you.
Changed in xorg: | |
status: | Triaged → Invalid |
jaanusrk (jaanus-online) wrote : | #19 |
Is it only gnome issue?
The gnome works well for me , when i'm using intrepid xorg packages.
I will upgrade xorg later today and try killing gnome-power-manager too.
Killing only gnome-settings-
Jorge Gustavo (jgr) wrote : | #20 |
- Xorg.0.log Edit (16.8 KiB, text/plain)
same problem here, with Xorg eating 100% of one of the cores
killing both gnome-settings-
2.6.28-4-server, nvidia 177.82, gnome 2.25.5 (Asus G70)
Still investigating the cause.
Attached is my Xorg.0.log
Jorge Gustavo (jgr) wrote : | #21 |
I also add a trace of the Xorg process, but is has almost no meaning to me :-(
(althought it seems stange so many calls to clock_gettime and setitimer, consuming almost 25% of the time)
$ sudo strace -v -f -p 5184 -c
Process 5184 attached - interrupt to quit
^CProcess 5184 detached
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
43.97 0.005542 15 369 ioctl
25.63 0.003231 0 395633 50 select
14.25 0.001796 0 804231 clock_gettime
11.42 0.001439 0 787366 setitimer
3.22 0.000406 6 69 munmap
1.09 0.000137 0 36300 gettimeofday
0.33 0.000041 0 7314 2886 read
0.10 0.000013 0 4013 writev
0.00 0.000000 0 1 close
0.00 0.000000 0 3 brk
0.00 0.000000 0 468 52 sigreturn
0.00 0.000000 0 50 poll
0.00 0.000000 0 415 rt_sigprocmask
0.00 0.000000 0 68 mmap2
0.00 0.000000 0 1 stat64
0.00 0.000000 0 1 geteuid32
0.00 0.000000 0 1 getegid32
0.00 0.000000 0 2 fcntl64
0.00 0.000000 0 1 accept
0.00 0.000000 0 1 shutdown
0.00 0.000000 0 1 getsockopt
0.00 0.000000 0 1 shmat
0.00 0.000000 0 1 shmdt
0.00 0.000000 0 1 shmctl
------ ----------- ----------- --------- --------- ----------------
100.00 0.012605 2036311 2988 total
Fabio M. Panico (fbugnon) wrote : | #22 |
Fabio M. Panico (fbugnon) wrote : | #23 |
- Xorg.0.log Edit (63.7 KiB, text/plain)
I'm having the same issue (Xorg consuming CPU) after upgraded from Interprid, but with a few differences:
- CPU usage is around 50% (average): one always on a 100% and the other very low, and I've notice that they keep alternating in a not constante time period.
- killing both gnome-settings-
MacBook Pro 1,1 Intel Dual Core 2Ghz, 2Gb RAM, Ubuntu 9.04, kernel linux 2.6.28-9-generic, Gnome 2.25.92.
=> xorg.conf already uploaded
=> Xorg.0.log uploading now
Thank you.
Fabio M. Panico (fbugnon) wrote : | #24 |
Just to add some information (might be irrelevant - sorry if this is the case):
I've just installed XFCE4 and I have no CPU usage problem with it :)
Fabio M. Panico (fbugnon) wrote : | #25 |
OK, so it was like I told in those upper lines: I run top from terminal and it didn't show any strange CPU usage under XFCE4.
But today, even under XFCE4 CPU consumption is as it was under Gnome (100% of one core - 50% average of processor dual)... so, I guess it really doesn't matter whether we use Gnome or XFCE.
caspar_wrede (caspar-wrede) wrote : | #26 |
I have the high CPU load problem on a thinkpad x31 with all the latest packages.
Killing both gnome-settings-
Vojtěch Procházka (v.proch) wrote : | #27 |
Same problem with Dell Latitude D600 (Intel Pentium M 1.6 MHz, ATI Mobility Radeon 9000).
With only one core is very difficult to do anything, everything is soooo slow. Killing anything causes no change.
Arthur Schiwon (blizzz) wrote : | #28 |
It affects me on an up to date Kubuntu Jaunty. Even with a dual core it is really nasty. Changing the Accel Mode (EXA or UXA) has no effect on this.
Max Bowsher (maxb) wrote : | #29 |
Commenters should take note that this bug report is marked as a duplicate, and moreover, the bug it is marked a duplicate of has been closed for some time. This means any comments made are unlikely to receive attention. Furthermore, unless you have specific evidence to the contrary, it is likely that whatever high load problem you are experiencing is a separate problem to the one addressed here. Please open a new bug, describing the symptoms you observe in as much detail as possible.
zokni (gyalog-versel) wrote : | #30 |
hi! i have the same problem with thinkpad x31.
killing gnome-settings-
maybe we shoud open a new thread.
Janusz (jledruide) wrote : | #31 |
Find a solution in deleting my home directory :
cd /home
sudo mv USER USER.bak
sudo mkdir USER
sudo chown USER:USER USER
It works now.
I think the problem is near the gnome parameters in .gconf, .gconfd or .gnome2, etc.
david.barbion (david-barbion) wrote : | #32 |
- Xorg.0.log Edit (21.7 KiB, text/plain)
I also have this issue here on an intel mobile 915GM/GMS/910GM.
I confirm that moving .gconf to .gconf.old solves partially this problem. Partially because when I scroll-down firefox is rather jerky and makes cpu fan speed-up (cpu intense task). Even when moving windows around.. Could this be to a missing 2D acceleration ?
In the xorg.log:
(II) intel(0): Kernel reported 489216 total, 1 used
(II) intel(0): I830CheckAvaila
(EE) intel(0): Cannot support DRI with frame buffer width > 2048.
(**) intel(0): Framebuffer compression enabled
(**) intel(0): Tiling enabled
(==) intel(0): VideoRam: 262144 KB
And I'm sure there is 256MB of video ram installed...
Arthur Schiwon (blizzz) wrote : | #33 |
David: you might want to take a look at https:/
david.barbion (david-barbion) wrote : | #34 |
Changing "Virtual" in display subsection solves the problem here...
Thanks very much..
david.barbion (david-barbion) wrote : | #35 |
Finally, I've found what consumes all my CPU. Long time ago, I activated the remote desktop viewer (the process is called vino-server) and I deactivated it and my CPU gets down to a few percents usage instantly !
I then understand why removing the .gconf* folders in my home directory solves the problem: vino-server was not set to start on log-on anymore...
elektrownia (piotr-kuna) wrote : | #36 |
Hi.
Upgraded to jauly today. After all the cpu usage was high from Xorg. Using a dualscreen setup.
After removing vino-server the problem stopped and the load goes down.
Hope it helps.
elektrownia (piotr-kuna) wrote : | #37 |
Thomas A. Gilchrist (tagilchrist) wrote : | #38 |
Same issue on Dell 6400 Inspiron (Intel Core 2 Duo)- Killing both gnome-settings-
chalkdust41485 (chalkdust41485) wrote : | #39 |
I can confirm that stopping the vino-server fixed my same exact issue.
Killing both gnome-settings-
musically_ut (musically-ut) wrote : | #40 |
Well, I can also confirm that killing vino-server fixed the problem, while killing gnome-settings-
This looks like an independent bug.
~
musically_ut
odaagan (teitur-arnarson) wrote : | #41 |
This comment is for those novise like me who mainly want a working system and are not primarilly looking to fix the bug.
I had the described problem after upgrading from Intrepid to Jaunty a couple of weeks ago. Xorg always over 30% CPU and often over 80%, even though I wasn't doing anything.
Running Dell Latitude E6400, 4 gig memory etc. I did try to kill power-manager and settings-daemon without any result. No vino-server running.
The behavior disappeared when I downgraded all xserver-
Since you who will go for this solution probably are as novice as me I will outline just how I did the downgrade (which might not be the standard way, I don't know).
edit the file /etc/apt/
Comment out all lines including the word 'jaunty' (put # in front of the line)
#deb http://
#deb-src http://
#deb http://
#deb-src http://
add the following line (probably overkill with multiverse universe etc., I don't know)
deb http://
save the file and do
sudo apt-get update
run aptitude (or your favourite package manager) and downgrade the following packages, including their dependencies (in my case 34 dependencies):
xserver-xorg
xserver-xorg-core
xserver-
xserver-
remember to uncomment the sources.list file and run 'sudo apt-get update' to reset jaunty repositories (and do not update xserver packages as suggested).
Stephen Burke (steve-burke-56) wrote : Re: [Bug 309776] Re: jaunty xorg 100% cpu usage | #42 |
What are your specs on the Dell E6400? I recently got one & it has
the Nvidia 160M video card in it. I've put Jaunty on that machine
with no problems. I did see this bug where the CPU goes to 100% very
quickly with my IBM T30.
Steve
On Wed, May 13, 2009 at 8:11 AM, odaagan <email address hidden> wrote:
>
> *** This bug is a duplicate of bug 307306 ***
> https:/
>
> This comment is for those novise like me who mainly want a working
> system and are not primarilly looking to fix the bug.
>
> I had the described problem after upgrading from Intrepid to Jaunty a
> couple of weeks ago. Xorg always over 30% CPU and often over 80%, even
> though I wasn't doing anything.
>
> Running Dell Latitude E6400, 4 gig memory etc. I did try to kill power-
> manager and settings-daemon without any result. No vino-server running.
>
> The behavior disappeared when I downgraded all xserver-
> packages back to the Intrepid version, and now the system is faster than
> ever:-)
>
> Since you who will go for this solution probably are as novice as me I
> will outline just how I did the downgrade (which might not be the
> standard way, I don't know).
>
> edit the file /etc/apt/
> Comment out all lines including the word 'jaunty' (put # in front of the line)
> #deb http://
> #deb-src http://
> #deb http://
> #deb-src http://
>
> add the following line (probably overkill with multiverse universe etc., I don't know)
> deb http://
>
> save the file and do
> sudo apt-get update
>
> run aptitude (or your favourite package manager) and downgrade the following packages, including their dependencies (in my case 34 dependencies):
> xserver-xorg
> xserver-xorg-core
> xserver-
> xserver-
>
> remember to uncomment the sources.list file and run 'sudo apt-get
> update' to reset jaunty repositories (and do not update xserver packages
> as suggested).
>
> --
> jaunty xorg 100% cpu usage
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug (via bug 307306).
>
> Status in “xorg” source package in Ubuntu: Invalid
>
> Bug description:
> after this week xorg driver update the xorg starts using 100% of one cpu core resources.
> when i switch between text console (crtl+alt+f2) and back to X, the xorg load goes down.
> then again some regular gnome activity causes Xorg load up.
> I attached recordmydesktop video. I started recording terminal with top running.
> After that i don't do anything. Suddenly xorg processor usage goes up.
> And before the end i brought the load down switching display in text mode and back to X.
odaagan (teitur-arnarson) wrote : | #43 |
Stephen: I'm sorry but I really don't know. Got computer from employer.
Here is the output when doing
sudo lshw -class display
*-display:0 UNCLAIMED
description: VGA compatible controller
product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 07
width: 64 bits
clock: 33MHz
*-display:1 UNCLAIMED
description: Display controller
product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2.1
bus info: pci@0000:00:02.1
version: 07
width: 64 bits
clock: 33MHz
and here is the /etc/X11/xorg.conf
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
SubSection "Display"
Virtual 2840 1050
EndSubSection
EndSection
Section "Device"
Identifier "Configured Video Device"
EndSection
I might add that I'm using dual screens. Using single and dual screens were both (more or less) equally slow with jaunty xorg packages, and are both equally fast with Intrepid packages.
Also, I was running the jaunty xorg packages since the jaunty release date without being too bothered about CPU usage. Today however it sacked down completely.
Since downgrading Xorg uses between 5-10% CPU when I'm running a few applications and doing nothing.
Pépou (yannickw24) wrote : | #44 |
Same problem for me. The only thing that solves the problem is reboot the computer.
maccus (maccus) wrote : | #45 |
Hi, I have just upgraded Intrepid to Jaunty. Now if I start the computer with kernel 2.6.28-11 the CPU usage is around 50% whilst doing nothing. If i start with the old kernel 2.6.27-14 everything is OK. My graphics card is an Nvidia.
maccus (maccus) wrote : | #46 |
I think the duplicate status is wrong because it has nothing to do with gnome-power-manager or gnome-settings daemon. Whether I kill gnome-settings-
AVS-PROS (avs-pros) wrote : | #47 |
Hello.
I have encountered the same problem after an upgrade from intrepid to jaunty. The solution is quite simple if vino causes the high cpu usage.
Delete "vino-server.
That shoudl fix the problem.
David Parker (davparker) wrote : | #48 |
I'm experiencing this bug after upgrading from 8.10 to 9.04 on a TP41.
Sandeep (sandybanger) wrote : | #49 |
Hi All,
I was facing the same issue with my Laptop Compaq - AMD-Athlon-X2 -QL-64, Nvidia 8200, 3GRam. I am running Ubuntu using Wubi.
"top" used to give Xorg as 100% of one of the cores if you move a window it simply shot up, and the other windows used to appear with a "curtain" effect!!.
Anyhoos, was able to solve it as below
I guess the problem was with the NVidia Drivers download the latest NVIDIA drivers from the Nvidia site(http://
Hope it helps
-
pengqingtao (qtpeng) wrote : | #50 |
Yes,it's due to the version of driver.
I met with the same problem that the xorg always consumes CPU nearby 100% when nvidia driver with version 180 was used.
I tried other versions, such as 185 or 190 ,and found the CPU usage dropped back to low level.
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.