Re: More OOM problems

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

 



On Mon 19-09-16 09:42:37, Lorenzo Stoakes wrote:
> On Mon, Sep 19, 2016 at 10:32:15AM +0200, Michal Hocko wrote:
> >
> > so this is the same thing as in Linus case. All the zones are hitting
> > min wmark so the should_compact_retry() gave up. As mentioned in other
> > email [1] this is inherent limitation of the workaround. Your system is
> > swapless but there is a lot of the reclaimable page cache so Vlastimil's
> > patches should help.
> 
> I will experiment with a linux-next kernel and see if the problem
> recurs. I've attempted to see if there is a way to manually reproduce
> on the mainline kernel by performing workloads that triggered the
> OOM (loading google sheets tabs, compiling a kernel, playing a video
> on youtube), but to no avail - it seems the system needs to be
> sufficiently fragmented first before it'll trigger.
>
> Given that's the case, I'll just have to try using the linux-next
> kernel and if you don't hear from me you can assume it did not repro
> again :)

OK, fair deal ;)

> I actually have a whole bunch of other OOM kill logs that I saved
> from previous occurrences of this issue, would it be useful for me to
> pastebin them, or would they not add anything of use beyond what's
> been shown in this thread?

If they are from before the workaround then it probably won't be that
useful.

-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]