From: Baoquan He <bhe@redhat.com>
To: Michal Hocko <mhocko@kernel.org>, pifang@redhat.com
Cc: David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, aarcange@redhat.com
Subject: Re: Memory hotplug softlock issue
Date: Thu, 15 Nov 2018 21:23:42 +0800 [thread overview]
Message-ID: <20181115132342.GQ2653@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.
No, forgot disabling faultround after reboot. Do we need to disable it and
retest?
>
> > [ 5055.461652] migrating pfn 190f4fb3e failed
> > [ 5055.461671] page:ffffea643d3ecf80 count:257 mapcount:251 mapping:ffff888e7a6ac528 index:0x85
> > [ 5055.474734] xfs_address_space_operations [xfs]
> > [ 5055.474742] name:"libc-2.28.so"
> > [ 5055.481070] flags: 0x1dfffffc0000026(referenced|uptodate|active)
> > [ 5055.490329] raw: 01dfffffc0000026 ffffc900000e3d80 ffffc900000e3d80 ffff888e7a6ac528
> > [ 5055.498080] raw: 0000000000000085 0000000000000000 000000fc000000f9 ffff88810a8f2000
> > [ 5055.505823] page->mem_cgroup:ffff88810a8f2000
> > [ 5056.335970] migrating pfn 190f4fb3e failed
> > [ 5056.335990] page:ffffea643d3ecf80 count:255 mapcount:250 mapping:ffff888e7a6ac528 index:0x85
> > [ 5056.348994] xfs_address_space_operations [xfs]
> > [ 5056.348998] name:"libc-2.28.so"
> > [ 5056.353555] flags: 0x1dfffffc0000026(referenced|uptodate|active)
> > [ 5056.364680] raw: 01dfffffc0000026 ffffc900000e3d80 ffffc900000e3d80 ffff888e7a6ac528
> > [ 5056.372428] raw: 0000000000000085 0000000000000000 000000fc000000f9 ffff88810a8f2000
> > [ 5056.380172] page->mem_cgroup:ffff88810a8f2000
> > [ 5057.332806] migrating pfn 190f4fb3e failed
> > [ 5057.332821] page:ffffea643d3ecf80 count:261 mapcount:250 mapping:ffff888e7a6ac528 index:0x85
> > [ 5057.345889] xfs_address_space_operations [xfs]
> > [ 5057.345900] name:"libc-2.28.so"
> > [ 5057.350451] flags: 0x1dfffffc0000026(referenced|uptodate|active)
> > [ 5057.359707] raw: 01dfffffc0000026 ffffc900000e3d80 ffffc900000e3d80 ffff888e7a6ac528
> > [ 5057.369285] raw: 0000000000000085 0000000000000000 000000fc000000f9 ffff88810a8f2000
> > [ 5057.377030] page->mem_cgroup:ffff88810a8f2000
> > [ 5058.285457] migrating pfn 190f4fb3e failed
> > [ 5058.285489] page:ffffea643d3ecf80 count:257 mapcount:250 mapping:ffff888e7a6ac528 index:0x85
> > [ 5058.298544] xfs_address_space_operations [xfs]
> > [ 5058.298556] name:"libc-2.28.so"
> > [ 5058.303092] flags: 0x1dfffffc0000026(referenced|uptodate|active)
> > [ 5058.314358] raw: 01dfffffc0000026 ffffc900000e3d80 ffffc900000e3d80 ffff888e7a6ac528
> > [ 5058.322109] raw: 0000000000000085 0000000000000000 000000fc000000f9 ffff88810a8f2000
> > [ 5058.329848] page->mem_cgroup:ffff88810a8f2000
> --
> Michal Hocko
> SUSE Labs
next prev parent reply other threads:[~2018-11-15 13:23 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 [this message]
2018-11-15 14:25 ` Michal Hocko
2018-11-15 13:38 ` Baoquan He
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=20181115132342.GQ2653@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).