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: Fri, 30 Dec 2016 12:11:36 +0100 [thread overview]
Message-ID: <20161230111135.GG13301@dhcp22.suse.cz> (raw)
In-Reply-To: <20161227112844.GG1308@dhcp22.suse.cz>
On Tue 27-12-16 12:28:44, Michal Hocko wrote:
> On Mon 26-12-16 12:00:53, Michal Hocko wrote:
> > [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)?
>
> If this turns out to be memory cgroup related then the patch from
> http://lkml.kernel.org/r/20161226124839.GB20715@dhcp22.suse.cz might
> help.
Did you get chance to test the above patch? I would like to send it for
merging and having it tested on another system would be really helpeful
and much appreciated.
Thanks!
--
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>
next prev parent reply other threads:[~2016-12-30 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161225205251.nny6k5wol2s4ufq7@ikki.ethgen.ch>
2016-12-26 11:00 ` Bug 4.9 and memorymanagement Michal Hocko
2016-12-27 11:28 ` Michal Hocko
2016-12-30 11:11 ` Michal Hocko [this message]
2016-12-30 16:52 ` [KERNEL] " Klaus Ethgen
2016-12-30 17:23 ` Michal Hocko
2017-01-04 8:06 ` Michal Hocko
2017-01-04 8:15 ` [KERNEL] " Klaus Ethgen
2017-01-04 8:31 ` Michal Hocko
2017-01-04 9:50 ` [KERNEL] " 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: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=20161230111135.GG13301@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).