Hello guys,

Any Ideas? I got this problem, my redhat stop and cannot continue after this "Freeing unused kernel Memory: 156K free"....

I don't change anything in my box. Any help.

TY

So your saying this just started randomly happening? No appernt reason? Did you reconfigure your kernel at all, hardware changes, etc...? You said you didn't change anything.. but something must have been changed for random problems like this to occure (to the best of my recolection anyways).

Thanks for the reply,

Actyually, I don't change anything. No hardware or software upgrade has been done. Yesterday it was working fine. This is the only problem I encountered in my box after several months.

This is rather strange.. I have never seen anything like this before :S. Is this before or after init has started? If it is after, you can try going directly into a root shell via boot params

linux init=/bin/bash

and from there can try and move around and see if anything is wrong.

I have read some articles from the net, they saying that it might be the swap. So how can I rebuild my swap under linux rescue mode? My swap was mounted on /dev/hda6

Ty

mkswap -v1 /dev/hda6

Thanks

I did rebuiilding my swap, but still i can't get thru. Stil have other ideas?

check your filesystem for errors, and maybe even rebuild your kernel. Both random idea's, but its worth a try .

Thought I would add my plea for help. Seems like this happens often, and doesn't have much hope. I actually did move my hard drive from an older AMD K-6 to an AMD Athon 900 Mhz board and get this error now. I reinstalled over the last one, but did not reformat as I have some info I don't want to lose. Could this be the prob? I am wondering that the kernel is configured wrong, but I thought by reinstalling it would be configured right? How can I insure that it is configured right for the new board? Is it a question of swamp memory? Any ideas?

--Hmm I also have 3 sticks of 128 RAM in for 384, a weird number for RAM, could this be another reason?

Thanks for help, I need it:

This happened to me a while ago. I remember finding a solution by searching Google but it was a while ago. I do remember the solution involving an additional parameter passed to the kernel through grub.conf. A new search suggests the solution may have been to add "apm=off" or "vsdo=0". My search was '"freeing unused kernel memory" fedora'. I believe it happened after upgrading my FC1 system to a 2.6 kernel.

Ktvoelker:
I saw those also, but didn't think they would for my system. I tried them anyway, and it looks like it worked
Thanks!

Hehe, okay, as usual I get ahead of myself. While using those commands helped continue the boot process, when it tries to 'startx' , the screen goes bonkers and I can't see anything. Do those commands have anything to do with startx or GUI? If not, what else might be causing the problem?

Which of those commands did you use? apm=off is related to power management and I don't see any obvious problems this could cause with X. The other option I don't know anything about. Maybe you could give the output from the X error log?

I used both actually. When booting into X the graphics are all skewed, like the monitor is fried. When I disabled this and was able to get into a text mode, I typed startx. There it just says XIO: fatal IO error 104 (Connections reset by peer) on X server. Also, having Redhat 8.0, i tried to reinstall using redhat-config-xfree86. That tries to load but then gives: xconf.py: Fatal IO error 2 (Connection reset by peer) on X server. The vid card is the same one I used in the previous machine, but maybe the new mobo is causing compat issues?

I can't help much directly about X, but try removing the other option besides "apm=off". I'm pretty sure "apm=off" was all that I needed to fix the lockup.