Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have an idle Linux centOS system and yet kswapd is using 100% cpu.

All I have running is a single bash session with top running.... I have 32G RAM and yet kswapd is constantly using 100% cpu for over 4 hours.

share|improve this question
1  
Can we get the output of top and ps -ef? Also, an output from /proc/cpuinfo would be nice. –  Rilindo Sep 29 '11 at 20:42
    
possible duplicate of How do I tell what process is causing kswapd to be in use? –  mailq Sep 29 '11 at 20:51
    
What kernel version do you have? And can you paste the output of free? –  David Schwartz Sep 30 '11 at 7:24
    
Linux version 2.6.18-164.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Thu Sep 3 03:28:30 EDT 2009 –  Deshawn Sep 30 '11 at 18:11
3  
Something, other than cache, is using most of your memory. You need to figure out what. Try ps axv --sort=-rss | head -10 and look at the RSS fields. –  David Schwartz Oct 1 '11 at 4:35

1 Answer 1

AFAICS this is neither related to free RAM nor SWAP. We have the same problem here which sometimes hits production machines and there is plenty of RAM free, quite often more than 700 MB with no dirty buffers to sync and 0 bytes SWAP used. It definitively looks like a severe Kernel BUG due to some unknown race condition.

Currently we run CentOS Kernel 2.6.18-194.el5 and will try to replace it by some newer kernel, because we think, this might help. (Perhaps I will find the time to report back if it worked.)

In the meanwhile there is a script, which is able to detect the 100% CPU situation quite well. It is called by our monitoring each minute to inform us about the situation. If the situation stays for too long, affected machines would lock up completely due to more and more unkillable processes using 100% CPU, until the machine becomes completely unmanageable.

Currently the only way known to solve the problem is to manually hard reboot the affected machine. /sbin/reboot fails, because the machine hangs on shutdown quite too often.

To hard-reboot a machine from any root shell commandline without direct access to Console do:

echo 10 > /proc/sys/kernel/panic
echo 1 > /proc/sys/kernel/sysrq
echo s > /proc/sysrq-trigger
sleep 5
echo s > /proc/sysrq-trigger
sleep 1
echo b > /proc/sysrq-trigger

Keep in mind, do this after quiescing the machine, such that there is no more process writing to the disks. This shall prevent that fsck runs in severe trouble after reboot.

Sorry, no real solution, but HTH. And keep in mind, perhaps there might be other things which cause a 100% CPU situation on kswapd than described here. So automating a reboot in this case perhaps is a bad idea.

share|improve this answer
    
Please note that the kswap hanging at 100% was confirmed being a Linux bug. It was fixed in mid/end 2012 kernels. –  Tino Jan 3 at 13:49

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.