Bug 2952 - Random high CPU usage of X process (60%, 99%,...)
Summary: Random high CPU usage of X process (60%, 99%,...)
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/mga (show other bugs)
Version: 6.8.2
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-10 06:08 UTC by Jan Kundrát
Modified: 2010-11-19 17:05 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
2.6.11.4 vanilla kernel's config (28.45 KB, text/plain)
2005-04-10 06:09 UTC, Jan Kundrát
no flags Details
xorg.conf (4.00 KB, text/plain)
2005-04-10 06:09 UTC, Jan Kundrát
no flags Details
Xorg.0.log (32.57 KB, text/plain)
2005-04-10 06:10 UTC, Jan Kundrát
no flags Details
nvidia report during latest X lockup (108.04 KB, text/plain)
2006-10-30 07:32 UTC, gnuorder
no flags Details

Description Jan Kundrát 2005-04-10 06:08:10 UTC
Hi, using Gentoo, x11-base/xorg-x11-6.8.2-r1, USE flags are "-3dfx +3dnow   
+bitmap-fonts -cjk -debug -dlloader -dmx -doc -font-server* -hardened   
-insecure-drivers +ipv6 -minimal+mmx +nls +opengl +pam -sdk -sse -static   
+truetype-fonts +type1-fonts (-uclibc)-xprint +xv".   
   
Sometimes the CPU usage of process X goes too high - 99% as indicated by `top`,   
sometimes only to about 60%, and lasts on such values for some time. Chances 
for this to happen are higher if konqueror is running, especially with loaded 
"reply to thread" page of vBulettin forum (textarea, input boxes, animated 
GIFs).   
   
Vanilla 2.6.11.4 kernel, xorg 6.8.2, configs will follow. 
 
As the system is still usable, I think I can provide some debugging 
information, just ask.
Comment 1 Jan Kundrát 2005-04-10 06:09:08 UTC
Created attachment 2370 [details]
2.6.11.4 vanilla kernel's config
Comment 2 Jan Kundrát 2005-04-10 06:09:59 UTC
Created attachment 2371 [details]
xorg.conf
Comment 3 Jan Kundrát 2005-04-10 06:10:38 UTC
Created attachment 2372 [details]
Xorg.0.log
Comment 4 Jan Kundrát 2005-04-10 06:25:45 UTC
Oops, forgot to mention grpahic adapter model, altough it's in the log: 
 
Matrox G400, 32MB model 
Comment 5 Erik Andren 2006-04-23 18:34:37 UTC
Is this still an issue using a current version of xorg?
Comment 6 Jan Kundrát 2006-04-27 05:01:23 UTC
(In reply to comment #5)
> Is this still an issue using a current version of xorg?

Nope, it seems fixed. Thanks for the reminder :).
Comment 7 gnuorder 2006-10-29 18:22:39 UTC
(In reply to comment #5)
> Is this still an issue using a current version of xorg?

I'm having similar trouble quite often now with x11-base/xorg-x11-7.1,
x11-drivers/nvidia-legacy-drivers-1.0.7184 and the problems started when I
switched to x11-drivers/nvidia-legacy-drivers-1.0.7184.  X has locked up 4 or 5
times within a 2 week time with 99% CPU usage. 

Comment 8 gnuorder 2006-10-30 07:27:18 UTC
I meant to say the problems started when I upgraded to sys-devel/gcc-4.1.1 and
recompiled xorg.  That process upgraded xorg to 7.1 and switched me from
nvidia-kernel/glx to nvidia-drivers.  
Comment 9 gnuorder 2006-10-30 07:32:41 UTC
Created attachment 7594 [details]
nvidia report during latest X lockup

Ignore the old xfree86.log
Comment 10 Daniel Stone 2007-02-27 01:26:10 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 11 Jesse Adkins 2010-11-19 17:05:30 UTC
(In reply to comment #9)
> Created an attachment (id=7594) [details]
> nvidia report during latest X lockup
> 
> Ignore the old xfree86.log

I think your issue is caused by something else. I notice in your Xorg.0.log that ACPI fails to open, and then that APM is not even supported by your kernel. At the same time, I also see a lot of different issues relating to nvidia.

If you're still having problems with your setup, you might want to open a new bug against nv, nouveau, or whatever you might be using.

I'm closing this one.


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.