From: kernel test robot <oliver.sang@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Gregory Price <gourry@gourry.net>, <oliver.sang@intel.com>
Subject: [gourryinverse:scratch/gourry/isolation/v2] [mm] da80cfb7e2: page_allocation_failure:order:#,mode:#(__GFP_ZERO|__GFP_COMP),nodemask=(null),cpuset=(null),mems_allowed=
Date: Wed, 7 Jan 2026 14:55:27 +0800 [thread overview]
Message-ID: <202601070744.b186a98d-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "page_allocation_failure:order:#,mode:#(__GFP_ZERO|__GFP_COMP),nodemask=(null),cpuset=(null),mems_allowed=" on:
commit: da80cfb7e23e7d84297f9d24a2a70a014daa0a0c ("mm: restrict slub, compaction, and page_alloc to sysram")
https://github.com/gourryinverse/linux scratch/gourry/isolation/v2
in testcase: boot
config: x86_64-rhel-9.4-ltp
compiler: gcc-14
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G
(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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202601070744.b186a98d-lkp@intel.com
[ 1.571716][ T0] Policy zone: Normal
[ 1.572090][ T0] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 1.572767][ T0] stackdepot: allocating hash table via alloc_large_system_hash
[ 1.573496][ T0] stackdepot hash table entries: 1048576 (order: 12, 16777216 bytes, linear)
[ 1.579058][ T0] stackdepot: allocating space for 8192 stack pools via memblock
[ 1.665046][ T0] swapper: page allocation failure: order:0, mode:0x40100(__GFP_ZERO|__GFP_COMP), nodemask=(null),cpuset=(null),mems_allowed=0-1023
[ 1.666481][ T0] CPU: 0 UID: 0 PID: 0 Comm: swapper Not tainted 6.19.0-rc3-00002-gda80cfb7e23e #1 PREEMPT(undef)
[ 1.666487][ T0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 1.666490][ T0] Call Trace:
[ 1.666497][ T0] <TASK>
[ 1.666503][ T0] dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:122)
[ 1.666514][ T0] warn_alloc.cold (kbuild/src/consumer/mm/page_alloc.c:4005)
[ 1.666520][ T0] ? __pfx_warn_alloc (kbuild/src/consumer/mm/page_alloc.c:3984)
[ 1.666525][ T0] ? __asan_memcpy (kbuild/src/consumer/mm/kasan/shadow.c:105 (discriminator 1))
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260107/202601070744.b186a98d-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-07 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 6:55 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 7:48 [gourryinverse:scratch/gourry/isolation/v2] [mm] da80cfb7e2: page_allocation_failure:order:#,mode:#(__GFP_ZERO|__GFP_COMP),nodemask=(null),cpuset=(null),mems_allowed= kernel test robot
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=202601070744.b186a98d-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=gourry@gourry.net \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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