From: Baoquan He <bhe@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, pifang@redhat.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
aarcange@redhat.com
Subject: Re: Memory hotplug softlock issue
Date: Thu, 15 Nov 2018 21:38:40 +0800 [thread overview]
Message-ID: <20181115133840.GR2653@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20181115131927.GT23831@dhcp22.suse.cz>
On 11/15/18 at 02:19pm, Michal Hocko wrote:
> On Thu 15-11-18 21:12:11, Baoquan He wrote:
> > On 11/15/18 at 09:30am, Michal Hocko wrote:
> [...]
> > > It would be also good to find out whether this is fs specific. E.g. does
> > > it make any difference if you use a different one for your stress
> > > testing?
> >
> > Created a ramdisk and put stress bin there, then run stress -m 200, now
> > seems it's stuck in libc-2.28.so migrating. And it's still xfs. So now xfs
> > is a big suspect. At bottom I paste numactl printing, you can see that it's
> > the last 4G.
> >
> > Seems it's trying to migrate libc-2.28.so, but stress program keeps trying to
> > access and activate it.
>
> Is this still with faultaround disabled? I have seen exactly same
> pattern in the bug I am working on. It was ext4 though.
After a long time struggling, the last 2nd block where libc-2.28.so is
located is reclaimed, now it comes to the last memory block, still
stress program itself. swap migration entry has been made and trying to
unmap, now it's looping there.
[ +0.004445] migrating pfn 190ff2bb0 failed
[ +0.000013] page:ffffea643fcaec00 count:203 mapcount:201 mapping:ffff888dfb268f48 index:0x0
[ +0.012809] shmem_aops
[ +0.000011] name:"stress"
[ +0.002550] flags: 0x1dfffffc008004e(referenced|uptodate|dirty|workingset|swapbacked)
[ +0.010715] raw: 01dfffffc008004e ffffea643fcaec48 ffffea643fc714c8 ffff888dfb268f48
[ +0.007828] raw: 0000000000000000 0000000000000000 000000cb000000c8 ffff888e72e92000
[ +0.007810] page->mem_cgroup:ffff888e72e92000
[ +0.004466] migrating pfn 190ff2bb1 failed
[ +0.000013] page:ffffea643fcaec40 count:203 mapcount:201 mapping:ffff888dfb268f48 index:0x2
[ +0.014321] shmem_aops
[ +0.000024] name:"stress"
[ +0.002535] flags: 0x1dfffffc008004e(referenced|uptodate|dirty|workingset|swapbacked)
[ +0.010680] raw: 01dfffffc008004e ffffc900000e3d80 ffffea643fcaec08 ffff888dfb268f48
[ +0.007863] raw: 0000000000000002 0000000000000000 000000cb000000c8 ffff888e72e92000
[ +0.007828] page->mem_cgroup:ffff888e72e92000
[ +1.357302] migrating pfn 190ff1c53 failed
[ +0.000011] page:ffffea643fc714c0 count:202 mapcount:201 mapping:ffff888e5e395109 index:0x28
[ +0.012756] anon
[ +0.000024] flags: 0x1dfffffc008004c(uptodate|dirty|workingset|swapbacked)
[ +0.008961] raw: 01dfffffc008004c ffffea643fcaec08 ffffc900000e3d80 ffff888e5e395109
[ +0.007847] raw: 0000000000000028 0000000000000000 000000ca000000c8 ffff888e72e92000
[ +0.007844] page->mem_cgroup:ffff888e72e92000
[ +0.004455] migrating pfn 190ff2bb0 failed
[ +0.000018] page:ffffea643fcaec00 count:203 mapcount:201 mapping:ffff888dfb268f48 index:0x0
[ +0.014392] shmem_aops
[ +0.000010] name:"stress"
[ +0.002565] flags: 0x1dfffffc008004e(referenced|uptodate|dirty|workingset|swapbacked)
[ +0.010675] raw: 01dfffffc008004e ffffea643fcaec48 ffffea643fc714c8 ffff888dfb268f48
[ +0.007819] raw: 0000000000000000 0000000000000000 000000cb000000c8 ffff888e72e92000
[ +0.007808] page->mem_cgroup:ffff888e72e92000
[ +0.004431] migrating pfn 190ff2bb1 failed
[ +0.000019] page:ffffea643fcaec40 count:203 mapcount:201 mapping:ffff888dfb268f48 index:0x2
[ +0.012688] shmem_aops
[ +0.000012] name:"stress"
[ +0.002525] flags: 0x1dfffffc008004e(referenced|uptodate|dirty|workingset|swapbacked)
[ +0.012385] raw: 01dfffffc008004e ffffc900000e3d80 ffffea643fcaec08 ffff888dfb268f48
[ +0.007840] raw: 0000000000000002 0000000000000000 000000cb000000c8 ffff888e72e92000
[ +0.007832] page->mem_cgroup:ffff888e72e92000
next prev parent reply other threads:[~2018-11-15 13:38 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 7:09 Memory hotplug softlock issue Baoquan He
2018-11-14 7:16 ` Baoquan He
2018-11-14 8:18 ` David Hildenbrand
2018-11-14 9:00 ` Baoquan He
2018-11-14 9:25 ` David Hildenbrand
2018-11-14 9:41 ` Michal Hocko
2018-11-14 9:48 ` David Hildenbrand
2018-11-14 10:04 ` Michal Hocko
2018-11-14 9:01 ` Michal Hocko
2018-11-14 9:22 ` David Hildenbrand
2018-11-14 9:37 ` Michal Hocko
2018-11-14 9:39 ` David Hildenbrand
2018-11-14 14:52 ` Baoquan He
2018-11-14 15:00 ` Michal Hocko
2018-11-15 5:10 ` Baoquan He
2018-11-15 7:30 ` Michal Hocko
2018-11-15 7:53 ` Baoquan He
2018-11-15 8:30 ` Michal Hocko
2018-11-15 9:42 ` David Hildenbrand
2018-11-15 9:52 ` Baoquan He
2018-11-15 9:53 ` David Hildenbrand
2018-11-15 13:12 ` Baoquan He
2018-11-15 13:19 ` Michal Hocko
2018-11-15 13:23 ` Baoquan He
2018-11-15 14:25 ` Michal Hocko
2018-11-15 13:38 ` Baoquan He [this message]
2018-11-15 14:32 ` Michal Hocko
2018-11-15 14:34 ` Baoquan He
2018-11-16 1:24 ` Baoquan He
2018-11-16 9:14 ` Michal Hocko
2018-11-17 4:22 ` Baoquan He
[not found] ` <20181119105202.GE18471@MiWiFi-R3L-srv>
2018-11-19 12:40 ` Michal Hocko
2018-11-19 12:51 ` Michal Hocko
2018-11-19 14:10 ` Michal Hocko
2018-11-19 16:36 ` Vlastimil Babka
2018-11-19 16:46 ` Michal Hocko
2018-11-19 16:46 ` Vlastimil Babka
2018-11-19 16:48 ` Vlastimil Babka
2018-11-19 17:01 ` Michal Hocko
2018-11-19 17:33 ` Michal Hocko
2018-11-19 20:34 ` Hugh Dickins
2018-11-19 20:59 ` Michal Hocko
2018-11-20 1:56 ` Baoquan He
2018-11-20 5:44 ` Hugh Dickins
2018-11-20 13:38 ` Vlastimil Babka
2018-11-20 13:58 ` Baoquan He
2018-11-20 14:05 ` Michal Hocko
2018-11-20 14:12 ` Baoquan He
2018-11-21 1:21 ` Hugh Dickins
2018-11-21 1:08 ` Hugh Dickins
2018-11-21 3:20 ` Hugh Dickins
2018-11-21 17:31 ` Michal Hocko
2018-11-22 1:53 ` Hugh Dickins
2018-11-14 10:00 ` 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=20181115133840.GR2653@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=pifang@redhat.com \
/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).