From: Michal Hocko <mhocko@kernel.org>
To: Klaus Ethgen <Klaus+lkml@ethgen.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Bug 4.9 and memorymanagement
Date: Mon, 26 Dec 2016 12:00:53 +0100 [thread overview]
Message-ID: <20161226110053.GA16042@dhcp22.suse.cz> (raw)
In-Reply-To: <20161225205251.nny6k5wol2s4ufq7@ikki.ethgen.ch>
[CCing linux-mm]
On Sun 25-12-16 21:52:52, Klaus Ethgen wrote:
> Hello,
>
> The last days I compiled version 4.9 for my i386 laptop. (Lenovo x61s)
Do you have memory cgroups enabled in runtime (aka does the same happen
with cgroup_disable=memory)?
> First, everything seems to be sane but after some sleep and awake
> (suspend to ram) cycles I seen some really weird behaviour ending in OOM
> or even complete freeze of the laptop.
>
> What I was able to see is that it went to swap even if there is plenty
> of memory left. The OOMs was also with many memory left.
Could you paste those OOM reports from the kernel log?
> Once I also catched kswapd0 with running insane with 100% CPU
> utilization.
>
> I first had in mind the CONFIG_SLAB_FREELIST_RANDOM setting and disabled
> it. This didn't made the problem to go away but it helped a little.
> Nevertheless, further OOM or other strange behaviour happened.
>
> I went back to 4.8.15 now with the same config from 4.9 and everything
> gets back to normal.
>
> So it seems for me that there are some really strange memory leaks in
> 4.9. The biggest problem is, that I do not know how to reproduce it
> reliable. The only what I know is that it happened after several
> suspends. (Not necessarily the first.)
>
> Am I the only one seeing that behavior or do anybody have an idea what
> could went wrong?
no there were some reports recently and 32b with memory cgroups are
broken since 4.8 when the zone LRU's were moved to nodes.
>x
> For the reference I put the .configs of the two compilings as attachment
> to this mail.
>
> Please keep me in CC as I am not subscribed to LKML.
>
> Regards
> Klaus
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: Klaus Ethgen <Klaus+lkml@ethgen.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Bug 4.9 and memorymanagement
Date: Mon, 26 Dec 2016 12:00:53 +0100 [thread overview]
Message-ID: <20161226110053.GA16042@dhcp22.suse.cz> (raw)
In-Reply-To: <20161225205251.nny6k5wol2s4ufq7@ikki.ethgen.ch>
[CCing linux-mm]
On Sun 25-12-16 21:52:52, Klaus Ethgen wrote:
> Hello,
>
> The last days I compiled version 4.9 for my i386 laptop. (Lenovo x61s)
Do you have memory cgroups enabled in runtime (aka does the same happen
with cgroup_disable=memory)?
> First, everything seems to be sane but after some sleep and awake
> (suspend to ram) cycles I seen some really weird behaviour ending in OOM
> or even complete freeze of the laptop.
>
> What I was able to see is that it went to swap even if there is plenty
> of memory left. The OOMs was also with many memory left.
Could you paste those OOM reports from the kernel log?
> Once I also catched kswapd0 with running insane with 100% CPU
> utilization.
>
> I first had in mind the CONFIG_SLAB_FREELIST_RANDOM setting and disabled
> it. This didn't made the problem to go away but it helped a little.
> Nevertheless, further OOM or other strange behaviour happened.
>
> I went back to 4.8.15 now with the same config from 4.9 and everything
> gets back to normal.
>
> So it seems for me that there are some really strange memory leaks in
> 4.9. The biggest problem is, that I do not know how to reproduce it
> reliable. The only what I know is that it happened after several
> suspends. (Not necessarily the first.)
>
> Am I the only one seeing that behavior or do anybody have an idea what
> could went wrong?
no there were some reports recently and 32b with memory cgroups are
broken since 4.8 when the zone LRU's were moved to nodes.
>x
> For the reference I put the .configs of the two compilings as attachment
> to this mail.
>
> Please keep me in CC as I am not subscribed to LKML.
>
> Regards
> Klaus
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2016-12-26 11:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 20:52 Bug 4.9 and memorymanagement Klaus Ethgen
2016-12-26 11:00 ` Michal Hocko [this message]
2016-12-26 11:00 ` Michal Hocko
2016-12-27 11:28 ` Michal Hocko
2016-12-27 11:28 ` Michal Hocko
2016-12-30 11:11 ` Michal Hocko
2016-12-30 11:11 ` Michal Hocko
2016-12-30 16:52 ` [KERNEL] " Klaus Ethgen
2016-12-30 16:52 ` Klaus Ethgen
2016-12-30 17:23 ` Michal Hocko
2016-12-30 17:23 ` Michal Hocko
2017-01-04 8:06 ` Michal Hocko
2017-01-04 8:06 ` Michal Hocko
2017-01-04 8:15 ` [KERNEL] " Klaus Ethgen
2017-01-04 8:15 ` Klaus Ethgen
2017-01-04 8:31 ` Michal Hocko
2017-01-04 8:31 ` Michal Hocko
2017-01-04 9:50 ` [KERNEL] " Klaus Ethgen
2017-01-04 9:50 ` Klaus Ethgen
[not found] ` <66baf7dd-c5e3-e11c-092f-3a642c306e63@I-love.SAKURA.ne.jp>
2016-12-27 11:48 ` Klaus Ethgen
2016-12-27 12:05 ` Michal Hocko
2016-12-27 12:05 ` Michal Hocko
2016-12-27 12:14 ` Klaus Ethgen
2016-12-27 12:14 ` Klaus Ethgen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161226110053.GA16042@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=Klaus+lkml@ethgen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.