From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] ??? FAIL: Test report for kernel 5.4.13-rc1-7f1b863.cki (stable)
Date: Fri, 17 Jan 2020 03:35:11 -0500 (EST) [thread overview]
Message-ID: <1477632721.2420697.1579250111441.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200116153741.GA558@rei>
----- Original Message -----
> Hi!
> > > One or more kernel tests failed:
> > >
> > > ppc64le:
> > > ??? LTP
> >
> > Hi, I see max_map_count failed on ppc64le:
> > https://artifacts.cki-project.org/pipelines/385189/logs/ppc64le_host_2_LTP_mm.run.log
>
> That's strange, we do attempt to map 65536 mappings but we do not touch
> them, so these shouldn't be faulted in, so there is no real reason why
> mmap() in the child process should stop prematurely at 65532.
>
> I guess that we cannot do much here, unless it's reproducible, because
> there is not much information there.
max_map_count.c:205: FAIL: 64882 map entries in total, but expected 65536 entries
I can reproduce it by running it in loop for couple hours. Though no idea
why we started seeing it only in 5.4.13 rc kernels, as there doesn't seem
to be any significant mm changes.
I'll try some older kernels.
WARNING: multiple messages have this Message-ID (diff)
From: Jan Stancek <jstancek@redhat.com>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Rachel Sibley <rasibley@redhat.com>, Jianwen Ji <jiji@redhat.com>,
Hangbin Liu <haliu@redhat.com>,
Memory Management <mm-qe@redhat.com>,
Linux Stable maillist <stable@vger.kernel.org>,
Jianlin Shi <jishi@redhat.com>,
CKI Project <cki-project@redhat.com>,
LTP Mailing List <ltp@lists.linux.it>
Subject: Re: [LTP] ??? FAIL: Test report for kernel 5.4.13-rc1-7f1b863.cki (stable)
Date: Fri, 17 Jan 2020 03:35:11 -0500 (EST) [thread overview]
Message-ID: <1477632721.2420697.1579250111441.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200116153741.GA558@rei>
----- Original Message -----
> Hi!
> > > One or more kernel tests failed:
> > >
> > > ppc64le:
> > > ??? LTP
> >
> > Hi, I see max_map_count failed on ppc64le:
> > https://artifacts.cki-project.org/pipelines/385189/logs/ppc64le_host_2_LTP_mm.run.log
>
> That's strange, we do attempt to map 65536 mappings but we do not touch
> them, so these shouldn't be faulted in, so there is no real reason why
> mmap() in the child process should stop prematurely at 65532.
>
> I guess that we cannot do much here, unless it's reproducible, because
> there is not much information there.
max_map_count.c:205: FAIL: 64882 map entries in total, but expected 65536 entries
I can reproduce it by running it in loop for couple hours. Though no idea
why we started seeing it only in 5.4.13 rc kernels, as there doesn't seem
to be any significant mm changes.
I'll try some older kernels.
next prev parent reply other threads:[~2020-01-17 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 12:13 [LTP] ❌ FAIL: Test report for kernel 5.4.13-rc1-7f1b863.cki (stable) CKI Project
2020-01-16 12:13 ` CKI Project
2020-01-16 13:41 ` [LTP] " Rachel Sibley
2020-01-16 13:41 ` Rachel Sibley
2020-01-16 15:37 ` [LTP] ??? " Cyril Hrubis
2020-01-16 15:37 ` Cyril Hrubis
2020-01-17 8:35 ` Jan Stancek [this message]
2020-01-17 8:35 ` Jan Stancek
2020-01-17 16:44 ` Naresh Kamboju
2020-01-17 16:44 ` Naresh Kamboju
2020-01-20 20:55 ` Jan Stancek
2020-01-20 20:55 ` Jan Stancek
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=1477632721.2420697.1579250111441.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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.