[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#699277: linux-image-3.6-trunk-amd64: OOM killer running loose on system with lots of memory



On Thu, 2013-02-07 at 17:53 +0100, Michal Suchanek wrote:
> Package: src:linux
> Version: 3.7.3-1~experimental.1
> Followup-For: Bug #699277
> 
> I have vm.swappiness = 0.
> 
> As far as I understand this should prevent swapping when not needed but
> not prevent sawpping altogether. It did not cause any trouble in the
> past with *less* RAM.
> 
> Either way I think I have enough memory to run cp(1).

vm.swappiness = 0 is slightly more effective than it used to be.  It
might delay swapping for too long.

It seems like a bug in writeback - cp (or whatever program) should be
throttled rather than being able to fill up memory with buffered writes.
This was supposed to have been improved around Linux 3.2.

This sounds a bit like <http://bugs.debian.org/695182>, though that
discussion has mostly turned up bugs specific to i386 or to older kernel
versions.

Please report the bug to linux-mm@kvack.org, cc'ing this bug address and
including the OOM kernel log and any VM sysctls that you have changed.

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: