From: kernel test robot <oliver.sang@intel.com>
To: Breno Leitao <leitao@debian.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@surriel.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Muchun Song <muchun.song@linux.dev>, <oliver.sang@intel.com>
Subject: [linux-next:master] [selftests/mm] 116d57303a: kernel-selftests.mm.run_vmtests.sh../uffd_stress_hugetlb_private_128_32.fail
Date: Mon, 30 Oct 2023 22:30:18 +0800 [thread overview]
Message-ID: <202310302121.d628ff69-oliver.sang@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2221 bytes --]
Hello,
kernel test robot noticed "kernel-selftests.mm.run_vmtests.sh../uffd_stress_hugetlb_private_128_32.fail" on:
commit: 116d57303a051bb2c7939a5026e441d8a7845db2 ("selftests/mm: add a new test for madv and hugetlb")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 66f1e1ea3548378ff6387b1ce0b40955d54e86aa]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
sc_nr_hugepages: 2
group: mm
compiler: gcc-12
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (Cascade Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
besides, also see another test always fails upon this commit but pass on parent.
c8b90731427814b1 116d57303a051bb2c7939a5026
---------------- --------------------------
fail:runs %reproduction fail:runs
| | |
:6 100% 6:6 kernel-selftests.mm.run_vmtests.sh../uffd_stress_hugetlb_128_32.fail
:6 100% 6:6 kernel-selftests.mm.run_vmtests.sh../uffd_stress_hugetlb_private_128_32.fail
If you fix the issue in a separate patch/commit (i.e. not just a new vursion of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202310302121.d628ff69-oliver.sang@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231030/202310302121.d628ff69-oliver.sang@intel.com
full test log is attached.
# ------------------------------------
# running ./uffd-stress hugetlb 128 32
# ------------------------------------
# nr_pages: 36, nr_pages_per_cpu: 1
# ERROR: context init failed (errno=12, @uffd-stress.c:254)
# [FAIL]
# --------------------------------------------
# running ./uffd-stress hugetlb-private 128 32
# --------------------------------------------
# nr_pages: 36, nr_pages_per_cpu: 1
# ERROR: context init failed (errno=12, @uffd-stress.c:254)
# [FAIL]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[-- Attachment #2: kernel-selftests.xz --]
[-- Type: application/x-xz, Size: 13952 bytes --]
reply other threads:[~2023-10-30 14:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202310302121.d628ff69-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=leitao@debian.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=oe-lkp@lists.linux.dev \
--cc=riel@surriel.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).