Re: Help decoding oom-killer output

From: Aaron Sowry
Date: Wed Sep 08 2010 - 04:55:12 EST


On 08/09/10 10:09, Aaron Sowry wrote:
> Since this change, oom-killer seems to think we are running out of
> memory, and starts killing arbitrary processes. Output from 'free' does
> not indicate any lack of memory resource:

...however I have just noticed that low memory allocation appears to be
somewhat stingy, given the total amount of RAM available:

tle-thn18:~ # cat /proc/meminfo
MemTotal: 37115096 kB
MemFree: 34528308 kB
Buffers: 49356 kB
Cached: 861024 kB
SwapCached: 0 kB
Active: 1830136 kB
Inactive: 549420 kB
Active(anon): 1442900 kB
Inactive(anon): 73056 kB
Active(file): 387236 kB
Inactive(file): 476364 kB
Unevictable: 0 kB
Mlocked: 0 kB
HighTotal: 36931780 kB
HighFree: 34520552 kB
LowTotal: 183316 kB
LowFree: 7756 kB
SwapTotal: 4200988 kB
SwapFree: 4200988 kB
Dirty: 2624 kB
Writeback: 0 kB
AnonPages: 1469264 kB
Mapped: 203692 kB
Shmem: 46780 kB
Slab: 95460 kB
SReclaimable: 31968 kB
SUnreclaim: 63492 kB
KernelStack: 9952 kB
PageTables: 31660 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 22758536 kB
Committed_AS: 4689664 kB
VmallocTotal: 524288 kB
VmallocUsed: 34520 kB
VmallocChunk: 311868 kB
HardwareCorrupted: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 8184 kB
DirectMap2M: 491520 kB

--
Aaron Sowry
Developer / Technical Sales
Cendio AB
Wallenbergs Gata 4
583 30 LINKÖPING
Sweden
aaron@xxxxxxxxx
Tel + 46 13 29 08 54
Fax + 46 13 21 47 00

Attachment: signature.asc
Description: OpenPGP digital signature