From: kernel test robot <oliver.sang@intel.com>
To: Aristeu Rozanski <aris@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Muchun Song <muchun.song@linux.dev>,
Aristeu Rozanski <aris@ruivo.org>,
David Hildenbrand <david@redhat.com>,
Vishal Moola <vishal.moola@gmail.com>, <oliver.sang@intel.com>
Subject: [linux-next:master] [hugetlb] 003af997c8: libhugetlbfs-test.32/64bit.counters_sh.fail
Date: Tue, 16 Jul 2024 21:30:39 +0800 [thread overview]
Message-ID: <202407162105.5eab5c8f-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "libhugetlbfs-test.32/64bit.counters_sh.fail" on:
commit: 003af997c8a945493859dd1a2d015cc9387ff27a ("hugetlb: force allocating surplus hugepages on mempolicy allowed nodes")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: libhugetlbfs-test
version: libhugetlbfs-test-x86_64-1bb2d54-1_20240614
with following parameters:
pagesize: 2MB
compiler: gcc-13
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480+ (Sapphire Rapids) with 256G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
the issues are random in our tests, but keep clean on parent:
64548bc5347bd051 003af997c8a945493859dd1a2d0
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:20 55% 11:20 libhugetlbfs-test.32bit.counters_sh.fail
:20 65% 13:20 libhugetlbfs-test.64bit.counters_sh.fail
If you fix the issue in a separate patch/commit (i.e. not just a new version 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/202407162105.5eab5c8f-oliver.sang@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240716/202407162105.5eab5c8f-oliver.sang@intel.com
counters.sh (2M: 32): FAIL Line 349: Bad HugePages_Total: expected 1, actual 2
counters.sh (2M: 64): FAIL Line 349: Bad HugePages_Total: expected 1, actual 2
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-07-16 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 13:30 kernel test robot [this message]
2024-07-16 15:44 ` Aristeu Rozanski
2024-07-17 20:45 ` Aristeu Rozanski
2024-07-24 19:48 ` Aristeu Rozanski
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=202407162105.5eab5c8f-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aris@redhat.com \
--cc=aris@ruivo.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=muchun.song@linux.dev \
--cc=oe-lkp@lists.linux.dev \
--cc=vishal.moola@gmail.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