From: Vlastimil Babka <vbabka@suse.cz>
To: E V <eliventer@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
Michal Hocko <mhocko@kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [Bug 186671] New: OOM on system with just rsync running 32GB of ram 30GB of pagecache
Date: Thu, 17 Nov 2016 22:49:54 +0100 [thread overview]
Message-ID: <4c85dfa5-9dbe-ea3c-7816-1ab321931e1c@suse.cz> (raw)
In-Reply-To: <CAJtFHUTn9Ejvyj3vJkqnsLoa6gci104-TPu5viG=epfJ9Rk_qg@mail.gmail.com>
On 11/16/2016 02:39 PM, E V wrote:
> System panic'd overnight running 4.9rc5 & rsync. Attached a photo of
> the stack trace, and the 38 call traces in a 2 minute window shortly
> before, to the bugzilla case for those not on it's e-mail list:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=186671
The panic screenshot has only the last part, but the end marker says
it's OOM with no killable processes. The DEBUG_VM config thus didn't
trigger anything, and still there's tons of pagecache, mostly clean,
that's not being reclaimed.
Could you now try this?
- enable CONFIG_PAGE_OWNER
- boot with kernel option: page_owner=on
- after the first oom, "cat /sys/kernel/debug/page_owner > file"
- provide the file (compressed, it will be quite large)
Vlastimil
--
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-11-17 21:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-186671-27@https.bugzilla.kernel.org/>
2016-11-03 18:53 ` Andrew Morton
2016-11-03 23:58 ` Vlastimil Babka
2016-11-04 14:13 ` E V
2016-11-04 21:00 ` Vlastimil Babka
2016-11-14 13:27 ` E V
2016-11-14 17:04 ` Vlastimil Babka
2016-11-14 20:56 ` E V
2016-11-16 13:39 ` E V
2016-11-17 21:49 ` Vlastimil Babka [this message]
2016-11-18 11:54 ` Tetsuo Handa
2016-11-18 15:02 ` E V
2016-11-22 13:58 ` E V
2016-11-22 14:48 ` Vlastimil Babka
2016-11-25 14:06 ` E V
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=4c85dfa5-9dbe-ea3c-7816-1ab321931e1c@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=eliventer@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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