From: Michal Hocko <mhocko@suse.cz>
To: lkp@lists.01.org
Subject: Re: OOM in v4.8
Date: Thu, 13 Oct 2016 08:34:16 +0200 [thread overview]
Message-ID: <20161013063416.GD21678@dhcp22.suse.cz> (raw)
In-Reply-To: <519d7220-9750-7be7-436e-407d4dc95d67@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
On Thu 13-10-16 14:23:54, Aaron Lu wrote:
> On 10/12/2016 04:24 PM, Aaron Lu wrote:
> > On 10/12/2016 04:00 PM, Michal Hocko wrote:
[...]
> >> And I am obviously blind because you have already tested with
> >> 101105b1717f which contains the Andrew patchbomb and so all the relevant
> >> changes. Now that I am lookinig into your log for that kernel there
> >> doesn't seem to be any OOM killer invocation. There is only
> >> kern :warn : [ 177.175954] perf: page allocation failure: order:2, mode:0x208c020(GFP_ATOMIC|__GFP_COMP|__GFP_ZERO)
> >
> > Oh right, perf may fail but that shouldn't make the test be terminated.
> > I'll need to check why OOM is marked for that test.
>
> There is a monitor in our test infrastructure that periodically checks
> dmesg for messages like "out of memory", "page allocation failure", etc.
> And if those messages are found, the test is believed not trustworthy
> and killed since most of our tests are performance related.
>
> That is the reason why "perf page allocation failure" caused the test to
> be marked OOM. I tried to not start perf and with commit 101105b1717f,
> 10 tests finished without any OOM failures.
Thanks for double checking!
--
Michal Hocko
SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@suse.cz>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Linux MM <linux-mm@kvack.org>,
lkp@01.org, Huang Ying <ying.huang@intel.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: OOM in v4.8
Date: Thu, 13 Oct 2016 08:34:16 +0200 [thread overview]
Message-ID: <20161013063416.GD21678@dhcp22.suse.cz> (raw)
In-Reply-To: <519d7220-9750-7be7-436e-407d4dc95d67@intel.com>
On Thu 13-10-16 14:23:54, Aaron Lu wrote:
> On 10/12/2016 04:24 PM, Aaron Lu wrote:
> > On 10/12/2016 04:00 PM, Michal Hocko wrote:
[...]
> >> And I am obviously blind because you have already tested with
> >> 101105b1717f which contains the Andrew patchbomb and so all the relevant
> >> changes. Now that I am lookinig into your log for that kernel there
> >> doesn't seem to be any OOM killer invocation. There is only
> >> kern :warn : [ 177.175954] perf: page allocation failure: order:2, mode:0x208c020(GFP_ATOMIC|__GFP_COMP|__GFP_ZERO)
> >
> > Oh right, perf may fail but that shouldn't make the test be terminated.
> > I'll need to check why OOM is marked for that test.
>
> There is a monitor in our test infrastructure that periodically checks
> dmesg for messages like "out of memory", "page allocation failure", etc.
> And if those messages are found, the test is believed not trustworthy
> and killed since most of our tests are performance related.
>
> That is the reason why "perf page allocation failure" caused the test to
> be marked OOM. I tried to not start perf and with commit 101105b1717f,
> 10 tests finished without any OOM failures.
Thanks for double checking!
--
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-10-13 6:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 6:54 OOM in v4.8 Aaron Lu
2016-10-12 6:54 ` Aaron Lu
2016-10-12 7:44 ` Michal Hocko
2016-10-12 7:44 ` Michal Hocko
2016-10-12 8:00 ` Michal Hocko
2016-10-12 8:00 ` Michal Hocko
2016-10-12 8:24 ` Aaron Lu
2016-10-12 8:24 ` Aaron Lu
2016-10-12 8:43 ` Michal Hocko
2016-10-12 8:43 ` Michal Hocko
2016-10-12 13:38 ` Aaron Lu
2016-10-12 13:38 ` Aaron Lu
2016-10-13 6:23 ` Aaron Lu
2016-10-13 6:23 ` Aaron Lu
2016-10-13 6:34 ` Michal Hocko [this message]
2016-10-13 6:34 ` Michal Hocko
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=20161013063416.GD21678@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=lkp@lists.01.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.