Bug 172721
Summary: | oom-killer invoked despite lots of swap and vm.overcommit_memory=1 | ||
---|---|---|---|
Product: | Memory Management | Reporter: | Walter Haidinger (walter.haidinger) |
Component: | Other | Assignee: | Andrew Morton (akpm) |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 4.7.3 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | monitoring graph: memory usage of the last days |
Description
Walter Haidinger
2016-09-22 16:10:19 UTC
Created attachment 239431 [details]
monitoring graph: memory usage of the last days
Additional note: with 4.4 and before, the system happily ran with 8GB RAM and 10GB swap-space (usually <10% in use).
fyi: I've switched from 4.4 to the 4.8 tree now (running 4.8.10 for a couple of days) and there haven't been any oom invocations yet. The machine workload hasn't changed so it seems the bug is fixed in 4.8 by now and/or the kernel adheres to the vm.overcommit_memory=1 setting. I'll fall back to vm.overcommit_memory=0 and see if this triggers oom. |