Originally posted by akaBeaVis
What about the (*dreaded*) acpi business? is this machine new enough to have acpi? is acpid running now and not before? or, even more *dreaded*, are apmd and acpid running at the same time?
I am in agreement with akaBeaVis on this one. I have heard (many times) of acpi and apm causing problems such as you describe (although this might not, obviously, be your actual problem).
As for APM, if you examine your /etc/rc.d/rc.modules file, you may see a line such as:
If this line is not commented out (with '#') then you may wish to do so as a test. That is, make the above line look like:
Additionally, as to ACPI, you may find that you have a file such as /etc/rc.d/rc.acpid. You may wish to do a:
ls -al /etc/rc.d/rc.acpid
and see if the file is listed as executable. If it is, then it will be loaded at startup.
In my case, I get:
sh-2.05b$ ls -al /etc/rc.d/rc.acpid
-rwxr-xr-x 1 root root 466 Aug 28 02:57 /etc/rc.d/rc.acpid
indicating that this acpid script is run at boot. You may (as root)
chmod 644 /etc/rc.d/rc.acpid
In my case this results in:
bash-2.05b# ls -al /etc/rc.d/rc.acpid
-rw-r--r-- 1 root root 466 Aug 28 02:57 /etc/rc.d/rc.acpid
which indicates this script will not be run at boot.
Reboot and see if it helps your freezing.
Note than I am a newb at this linux stuff, so I mean not to offend you if my comments seem elementary to you. Just trying to help with what I have learned.