I'm running an upgraded RedHat 6.2 system to get the
XFree86-4.0.1-30.i386.rpm to run. I don't remember how many packages I had
to upgrade to get it working. I have two graphics cards (matrox g400 sh,
guillemont riva tnt2 m64). I am not using the nvidia custom drivers, just
the nvidia drivers in the rpm. I am running in xinerama mode. My kernel
is 2.2.16-3 from rpm. I am also running enlightenment 16.4 from cvs. What
happens is that after my X session has been running a while, X will start
churning. It doesn't go into a "tight loop", but it does eat the cpu. It
typically stays around 50% cpu usage according to 'top'. The only solution
is to restart the X session. Of course, everything else seems to run slow
when X gets into this state.
Does this persist with the latest X packages?
I will check and post results. However, I upgraded my enlightenment to latest
cvs. I still have problem, but it doesn't occur as frequently. Please note
that 'top' reports that 'X' is eating up cpu. Of course, enlightenment works
closely with X.
I am unable to upgrade to XFree86-4.0.1-0.43.i386.rpm because I only have
rpm-3.0.5-0.5 installed on my system. I can't figure out how to upgrade to
rpm-4x without installing the beta RH7.0.
The -30 package was compiled by a compiler with
a bug that could cause strange X server behavior, that's
why I'm mentioning this.
You should be able to use the latest 3.0.5 RPM at
to install later X packages.
OK, I'm running XFree86-4.0.1-0.43 now. I'll post in another day to report if I
see the same behaviour or not.
I cam in this morning and found X running at 47% CPU. I leave X running for
several days. This particular session has been up since Aug 17 (when I
installed the -0.43 packages).
I just glanced over at top and found that X was only at 15%. I had an Eterm
running top covering an XEmacs window. I thought, "maybe XEmacs is what is
causing the problem." So, I exposed XEmacs and moved the window around with the
titlebar. Of course, X cpu usage went up while I was dragging the window
around. I actually got it as high as 80%. Now I've been waiting for about five
minutes and X has been steady around 50%.
I'm not sure what this points to; maybe the window manager (Enlightenment cvs)?
I will post to the enlightenment-devel mailing list and see what they think.
It does sound like an enlightenment problem; I haven't
heard any reports of this here with our enlightenment
packages, or with other window managers.