Hello, On Mon, Mar 25, 2013 at 10:45:25AM +0100, Romeyke, Andreas wrote: > Package: ike
your problem is probably not related to ike: > [159293.425658] iked.real invoked oom-killer: gfp_mask=0x201da, order=0, > oom_adj=0, oom_score_adj=0 This only states, that iked.real was one of the running processes, when the kernel needed additional memory to handle a sys call. The process wanted to do something, but couldn't, because the ressources were depleted. > [159293.469869] [ pid ] uid tgid total_vm rss cpu oom_adj > oom_score_adj name ... > [159293.470044] [ 3014] 0 3014 13878 0 1 0 > 0 iked.real As you can see, iked itself used very little memory. > [159293.470244] [ 5182] 1000 5182 2807853 829398 2 0 > 0 clementine "clementine" on the other hand was hogging most of the RAM ... > [159293.470393] Out of memory: Kill process 5182 (clementine) score 973 or > sacrifice child > [159293.470407] Killed process 5182 (clementine) total-vm:11231412kB, > anon-rss:3317592kB, file-rss:0kB ... which made is a perfect candidate to be killed by the kernel to free some memory fast. Please have a look at "iked.real" after it was freshly started. If its vm_site is not much lower that the value above, it was not a memory lead in iked, but in some other application: grep VmSize /proc/`pidof iked.real`/status > [159293.426192] Free swap = 0kB > [159293.426196] Total swap = 6923260kB There is not enough information to diagnose, who's using your 7 GiB swap space. The total_vm column only sums up to your 4 GiB of RAM. Run "top" and press 'O' followed by 'p' to get your processes sorted by swap usage, which might get your some insight when you next encounter such a problem. You should probably setup a cron job to dump that information to some files, so you have some more usable data. Sincerely Philipp -- Philipp Matthias Hahn <pmh...@debian.org> GPG/PGP: 9A540E39 @ keyrings.debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
