Red Hat Bugzilla – Bug 799685
oom-killer activates when plenty of RAM is still available
Last modified: 2012-03-14 10:43:30 EDT
Description of problem:
After updating to kernel 188.8.131.52-1.fc15.i686.PAE I'm getting oom-killer activated every few hours. I think this might be related to the bug 745241 or 735946 since I've been using fuse and rsync during that time (regression?).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
we can't do anything with this report without seeing logs from the oomkiller.
Created attachment 567529 [details]
Section of /var/log/messages
This shows what was logged to /var/log/messages when oom-killer activated.
Do you need any other logs?
Just got this again now with 184.108.40.206-3 PAE kernel. Attaching dmesg and /var/log/messages
Created attachment 569971 [details]
Created attachment 569972 [details]
Machine has 16 GB RAM and there's a few GB always free (or used by filesystem cache). Swap is either not used or barely (less than 100MB).
Any suggestions on how to debug this?
Is this due to PAE kernel?
Do you think changing value for vm.lowmem_reserve_ratio will help?
the real answer is to move to 64bit. Past 8GB, 32bit gets complicated because of so much low memory being used up by page tables. Once fragmentation starts to happen, this sort of thing is to be expected.
You might have memory free when the oom is triggering, but the problem is that you don't have any of the right 'type' of memory (the gfp mask) free.
You might make it perform a bit better by tweaking syscalls, but you're fundamentally in a losing battle just because you're pushing up against the architectural limits.