Hello. Goldwyn Rodrigues wrote: > > This would be a bug of "depmod", It wasn't a bug. It was my mistake. > > but the reason I post to this ML is that I want to know > > "What will happen to OOM-killer if no RAM is freeable?" > > OOM killer constantly runs in the background and I suppose it is not > swappable (I am not sure of this). OOM Killer tries to kill the > "naughty" processes, to free some RAM. > > > > > I once encountered a case that OOM-killer attempts to free > > RAM but unable to find any RAM, resulting infinite loop > > showing noisy messages rather than killing "depmod" itself. > > Can OOM-killer always return if OOM is caused by "depmod"? > > Yes, I have seen such cases. > > > I couldn't trace what system call was executing at that time, > > but I think the kernel was processing something that are related > > to kernel module functions such as init_module() because the > > process that caused OOM is "depmod". > > I think your swap space is not up (probably because of incorrect > configuration in /etc/fstab). Please check this. This is a common > mistake people do. Yeah. I didn't assign swap partition (because I'm running inside VMware). I assigned 256MB of RAM and no swap partition. It worked for many months. But now, only 256MB of memory seems to be insufficient for compiling kernel 2.6.15-1.2054_FC5 on FC5 environment. I assigned 1536MB of RAM, and "depmod" ran successfully. Thank you! -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
