slow down,beep of death..etc
i am using an IBM ThiunkCentrer A50 series Pintum 4 3.00 GHz (2CPU)
intel 82865G with 64MB.
I started to have the symptomps as soon as i installed FC6 on top of the existing windows overwrting the recovery partition of IBM(that didn't seem to cause a problem when i did the same thing but with redhat 9 3 years ago).
The only thing that seem to fix it was a loop job to direct /proc/meminfo into a file to possiblly monitor memory use as the syomptoms were consistint with memmory leak.
The system went on runnign like charm with both runlelevs 3 and 5 for about 3 weeks till 2 days ago wehn i decided to have another X session run from tty1 using statrtx -- :1 which started a session on tty8 and everything seemed to be wroking fine until i decided i wanted to log off the second x session (tty8) that when everything froze. Tired to kill the bash that i started the x session from (tty1) but to no avail, and so reboot i did and to my amazment and disappointment i was presented again with the inital symptomps of slow down command retrun with the famous beep of death!!! after couple boot up atempts the system seems to be stable again with the command top returning result rather promptly (yes the "top" command slow down was one of the symptomps).
i'll monitor this thread and update accordingly when anything new happens with me
p.s: since i didn't have acip=off noacip option from the beigning i assume this might not be the cause
welcoming your inputs guys
Maybe It's Not LVM ... sigh
Well, I thought getting rid of LVM had cured my lock-ups, but when I went to the system this AM it was back into molasses mode (funny, I don't recall seeing molassesd in the services list, either!). The system would respond, eventually, until I started shutting it down. That took forever, and I actually started getting the continuous beeping others have reported, so it was power-off time.
However, to muddy the waters, I did start updating the system yesterday (hey, everything seemed to be fixed, remember), including the kernel, so I rebooted with the original kernel after the hangup the morning and I'll try to leave everything else the same for the next few hours and see if it might be the kernel update that caused the problem.