From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "linux- stable" <stable@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Roman Gushchin" <guro@fb.com>,
"Michal Hocko" <mhocko@kernel.org>,
lkft-triage@lists.linaro.org, "Chris Down" <chris@chrisdown.name>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Michel Lespinasse" <walken@google.com>,
Fan_Yang@sjtu.edu.cn, bgeffon@google.com,
"Anshuman Khandual" <anshuman.khandual@arm.com>,
"Will Deacon" <will@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
pugaowei@gmail.com, "Jérôme Glisse" <jglisse@redhat.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Mel Gorman" <mgorman@techsingularity.net>,
"Hugh Dickins" <hughd@google.com>,
"Al Viro" <viro@zeniv.linux.org.uk>, "Tejun Heo" <tj@kernel.org>,
"Sasha Levin" <sashal@kernel.org>
Subject: Re: WARNING: at mm/mremap.c:211 move_page_tables in i386
Date: Fri, 10 Jul 2020 09:47:35 +0530 [thread overview]
Message-ID: <CA+G9fYsoEiQ-8ECKxMqQqPZKUbTQStp6wZi7ZiJDyi0YahFAvg@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a0ii1Z-UG8NpwTvkmOEcOvvTo4+m9xjW0JqR6LPvUZ4=g@mail.gmail.com>
On Thu, 9 Jul 2020 at 13:55, Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Thu, Jul 9, 2020 at 7:28 AM Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > While running LTP mm test suite on i386 or qemu_i386 this kernel warning
> > has been noticed from stable 5.4 to stable 5.7 branches and mainline 5.8.0-rc4
> > and linux next.
>
> Are you able to correlate this with any particular test case in LTP, or does
> it happen for random processes?
>
> In the log you linked to, it happens once for ksm05.c and multiple times for
> thp01.c, sources here:
>
> https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/mem/ksm/ksm05.c
> https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/mem/thp/thp01.c
>
> Is it always these tests that trigger the warning, or sometimes others?
These two test cases are causing this warning multiple times on i386.
>
> When you say it happens with linux-5.4 stable, does that mean you don't see
> it with older versions? What is the last known working version?
I do not notice on stable-4.19 and below versions.
Sorry i did not get the known working commit id or version.
It started happening from stable-rc 5.0 first release.
I have evidence [1] showing it on 5.0.1
>
> I also see that you give the virtual machine 16GB of RAM, but as you are
> running a 32-bit kernel without PAE, only 2.3GB end up being available,
> and some other LTP tests in the log run out of memory.
>
> You could check if the behavior changes if you give the kernel less memory,
> e.g. 768MB (lowmem only), or enable CONFIG_X86_PAE to let it use the
> entire 16GB.
Warning is still happening after enabling PAE config.
But the oom-killer messages are gone. Thank you.
CONFIG_HIGHMEM=y
CONFIG_X86_PAE=y
full test log oom-killer messages are gone and kernel warning is still there,
https://lkft.validation.linaro.org/scheduler/job/1552606#L10357
build location:
https://builds.tuxbuild.com/puilcMcGVwzFMN5fDUhY4g/
[1] https://qa-reports.linaro.org/lkft/linux-stable-rc-5.0-oe/build/v5.0.1/testrun/1324990/suite/ltp-mm-tests/test/ksm02/log
---
[ 775.646689] WARNING: CPU: 3 PID: 10858 at
/srv/oe/build/tmp-lkft-glibc/work-shared/intel-core2-32/kernel-source/mm/mremap.c:211
move_page_tables+0x553/0x570
[ 775.647006] Modules linked in: fuse
[ 775.647006] CPU: 3 PID: 10858 Comm: true Not tainted 5.0.1 #1
[ 775.647006] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.10.2-1 04/01/2014
[ 775.647006] EIP: move_page_tables+0x553/0x570
- Naresh
next prev parent reply other threads:[~2020-07-10 4:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 5:28 WARNING: at mm/mremap.c:211 move_page_tables in i386 Naresh Kamboju
2020-07-09 8:25 ` Arnd Bergmann
2020-07-10 4:17 ` Naresh Kamboju [this message]
2020-07-09 19:12 ` Linus Torvalds
2020-07-10 4:28 ` Naresh Kamboju
2020-07-10 5:22 ` Linus Torvalds
2020-07-10 17:48 ` Naresh Kamboju
2020-07-10 20:05 ` Linus Torvalds
2020-07-11 17:27 ` Naresh Kamboju
2020-07-11 18:12 ` Linus Torvalds
2020-07-11 18:21 ` Linus Torvalds
2020-07-11 23:33 ` Joel Fernandes
2020-07-12 17:30 ` Matthew Wilcox
2020-07-12 20:38 ` Linus Torvalds
2020-07-12 21:50 ` Joel Fernandes
2020-07-12 22:58 ` Linus Torvalds
2020-07-13 2:53 ` Joel Fernandes
2020-07-13 3:51 ` Linus Torvalds
2020-07-13 12:12 ` Joel Fernandes
2020-07-14 7:33 ` Kirill A. Shutemov
2020-07-14 11:27 ` Naresh Kamboju
2020-07-14 16:08 ` Joel Fernandes
2020-07-14 16:10 ` Linus Torvalds
2020-07-14 18:12 ` Joel Fernandes
2020-07-14 18:49 ` Linus Torvalds
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=CA+G9fYsoEiQ-8ECKxMqQqPZKUbTQStp6wZi7ZiJDyi0YahFAvg@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=Fan_Yang@sjtu.edu.cn \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=bgeffon@google.com \
--cc=catalin.marinas@arm.com \
--cc=chris@chrisdown.name \
--cc=gregkh@linuxfoundation.org \
--cc=guro@fb.com \
--cc=hughd@google.com \
--cc=jglisse@redhat.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=pugaowei@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=walken@google.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).