From: kernel test robot <yi1.lai@intel.com>
To: Dmitry Ilvokhin <d@ilvokhin.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Michal Hocko <mhocko@suse.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Kiryl Shutsemau <kas@kernel.org>,
David Hildenbrand <david@redhat.com>,
Hugh Dickins <hughd@google.com>,
Liam Howlett <liam.howlett@oracle.com>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, yi1.lai@intel.com
Subject: [linus:master] [mm] e97d7c5165: trinity.invoked oom-killer
Date: Sun, 8 Nov 2026 16:14:08 +0800 [thread overview]
Message-ID: <202611081559.ec60e6e4-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "trinity.invoked oom-killer" on:
commit: e97d7c5165227e6e4423b4a869d7805b01706392 ("mm: shmem/tmpfs hugepage defaults config choice") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linux-next/master ddfe51b0a0f5dc9e415cc2c8ad8db17532dd426b]
in testcase: trinity
version: trinity-i386-abe9de86-1_20230429 with following parameters:
runtime: 300s
group: group-01
nr_groups: 5
config: x86_64-randconfig-1008-20261105
compiler: clang-22
test machine: qemu-system-x86_64 -enable-kvm -cpu Icelake-Server-noTSX,enforce -smp 4 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
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 <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202611081559.ec60e6e4-lkp@intel.com
[ 147.803560][ T3738] trinity-c3 invoked oom-killer: gfp_mask=0x440dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO|__GFP_COMP), order=0, oom_score_adj=500
[ 147.808170][ T3738] CPU: 0 UID: 65534 PID: 3738 Comm: trinity-c3 Not tainted 6.18.0-rc5-00155-ge97d7c516522 #1 PREEMPT(lazy)
[ 147.808179][ T3738] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 147.808182][ T3738] Call Trace:
[ 147.808186][ T3738] <TASK>
[ 147.808190][ T3738] dump_stack_lvl+0xc0/0x138
[ 147.808212][ T3738] dump_header+0xd3/0x440
[ 147.808225][ T3738] oom_kill_process+0x107/0xf00
[ 147.808240][ T3738] ? out_of_memory+0x897/0x12f0
[ 147.808252][ T3738] out_of_memory+0xeaa/0x12f0
[ 147.808265][ T3738] ? out_of_memory+0x897/0x12f0
[ 147.808278][ T3738] __alloc_pages_may_oom+0x1a5/0x2c0
[ 147.808295][ T3738] __alloc_pages_slowpath+0x6d7/0xe00
[ 147.808316][ T3738] __alloc_frozen_pages_noprof+0x1fb/0x270
[ 147.808330][ T3738] alloc_pages_mpol+0x16f/0x340
[ 147.808340][ T3738] alloc_pages_noprof+0x95/0x1b0
[ 147.808349][ T3738] pte_alloc_one+0x23/0x2f0
[ 147.808357][ T3738] ? __pte_alloc+0x1a/0x170
[ 147.808367][ T3738] __pte_alloc+0x22/0x170
[ 147.808378][ T3738] do_pte_missing+0x2500/0x3180
[ 147.808401][ T3738] handle_mm_fault+0x1061/0x36b0
[ 147.808409][ T3738] ? handle_mm_fault+0x41/0x36b0
[ 147.808435][ T3738] do_user_addr_fault+0xa18/0x1030
[ 147.808447][ T3738] ? rcu_is_watching+0x15/0xb0
[ 147.808459][ T3738] exc_page_fault+0x6d/0xf0
[ 147.808474][ T3738] asm_exc_page_fault+0x26/0x30
[ 147.808480][ T3738] RIP: 0023:0xf7e1d80e
[ 147.808486][ T3738] Code: c6 44 24 28 00 8b 7c 24 14 89 bd 4c 01 00 00 e9 ca fe ff ff 8d b4 26 00 00 00 00 90 ba 10 00 00 00 29 ca 8d 3c 10 89 f0 29 d0 <89> 17 83 c7 08 83 c8 02 89 47 fc e9 b9 fd ff ff 66 90 89 4c 24 14
[ 147.808490][ T3738] RSP: 002b:00000000ffe58f80 EFLAGS: 00010212
[ 147.808497][ T3738] RAX: 0000000000200ff8 RBX: 00000000f7f84740 RCX: 0000000000000008
[ 147.808501][ T3738] RDX: 0000000000000008 RSI: 0000000000201000 RDI: 00000000f58b3008
[ 147.808505][ T3738] RBP: 00000000f7f84000 R08: 0000000000000000 R09: 0000000000000000
[ 147.808508][ T3738] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 147.808511][ T3738] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 147.808529][ T3738] </TASK>
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20261108/202611081559.ec60e6e4-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-08 8:14 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=202611081559.ec60e6e4-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=d@ilvokhin.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=kas@kernel.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=oe-lkp@lists.linux.dev \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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
all inboxes | Powered by JetHome®