I cannot suggest you a solution, but just a test to see what's happening. Look at the following quote from a post of mine in a similar thread.
--------------------- Re: Xorg freezes, crashes, locks, shoots and leaves Dear Gene,
I know your problem very well! Anyway, after having X freezing the system for several months, at present it doesn't happen any more. It's hard to say way.
I only can suggest you to add the following lines to xorg.conf:
Section "ServerFlags" Option "AllowDeactivateGrabs" "true" Option "AllowClosedownGrabs" "true" EndSection
They allow you to use C-A-K-* and C-A-K-/ to try to unlock X in some situations (see man xorg.conf for a few detail). To avoid misunderstandings, please note that C-A-K-* means "Control, Alt, Keypad *" pressed together.
This could be a start to investigate what is happening to your system. I would not be very optimistic, but at least you can try, it's very easy. Remember to restart your X server after the changes above.
Best regards... and good luck!!! -------------------------------
Christophe Lambert wrote:
Hi,
I am running the RedHat Fedora core 2 on an Athlon computer. The computer ran without any problem since the Fedora core 2 release. Since the following updates, the X windows system freezes after a random amount of time.
Package Installed: kernel 2.6.8-1.521.i686
Package Dependency Installed: kdebase-devel 6:3.2.2-6.FC2.i386 kdelibs-devel 6:3.2.2-8.FC2.i386 samba-common 3.0.7-2.FC2.i386 samba-client 3.0.7-2.FC2.i386
Package Updated: imlib 1:1.9.13-19.i386 lha 1.14i-14.1.i386 kdebase 6:3.2.2-6.FC2.i386 cdda2wav 8:2.01-0.a27.4.FC2.3.i386 cdrecord 8:2.01-0.a27.4.FC2.3.i386 mkisofs 8:2.01-0.a27.4.FC2.3.i386 kdelibs 6:3.2.2-8.FC2.i386 kudzu 1.1.68.2-1.i386 samba 3.0.7-2.FC2.i386
Characteristics:
- The X process is running at 99% of CPU.
- There is no related lines in log files
- It seems to be not dependent on the kernel (I tried under 2.6.7 and
2.6.8).
- It appears under Gnome as well as under KDE
- It seems independently related to applications I used (Evolution,
Emacs, Mozilla, Terminal or ... nothing)
- It seems to be not related to the screen saver: it does not matter if
it is activated or not.
The only thing I can do is to log in from another computer, kill the X process, go to telinit 3 and then telinit 5. The problem happens about 10 times per day.
If somebody has any idea to solve/find the problem, he is welcome.
Thanks, Christophe