[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 <[email protected]>
Newsgroups dev.linux.lists.oe-lkp
Message-ID <[email protected]>

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-rust
compiler: clang-20
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G

(please refer to attached dmesg/kmsg for entire log/backtrace)


+-----------------------------------------------------------------------------------------------------------+------------+------------+
|                                                                                                           | 71291215b3 | da80cfb7e2 |
+-----------------------------------------------------------------------------------------------------------+------------+------------+
| boot_successes                                                                                            | 15         | 0          |
| boot_failures                                                                                             | 0          | 15         |
| page_allocation_failure:order:#,mode:#(__GFP_ZERO|__GFP_COMP),nodemask=(null),cpuset=(null),mems_allowed= | 0          | 15         |
| Mem-Info                                                                                                  | 0          | 15         |
| BUG:kernel_NULL_pointer_dereference,address                                                               | 0          | 15         |
| Oops                                                                                                      | 0          | 15         |
| RIP:mem_cgroup_show_protected_memory                                                                      | 0          | 15         |
| Kernel_panic-not_syncing:Fatal_exception                                                                  | 0          | 15         |
+-----------------------------------------------------------------------------------------------------------+------------+------------+


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 <[email protected]>
| Closes: https://lore.kernel.org/oe-lkp/[email protected]


[    0.189983][    T0] software IO TLB: area num 2.
[    0.221422][    T0] Fallback order for Node 0: 0
[    0.221429][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 8388478
[    0.223346][    T0] Policy zone: Normal
[    0.223999][    T0] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.247639][    T0] swapper: page allocation failure: order:0, mode:0x40100(__GFP_ZERO|__GFP_COMP), nodemask=(null),cpuset=(null),mems_allowed=0-1023
[    0.250008][    T0] CPU: 0 UID: 0 PID: 0 Comm: swapper Not tainted 6.19.0-rc3-00002-gda80cfb7e23e #1 PREEMPT(undef)
[    0.250015][    T0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[    0.250019][    T0] Call Trace:
[    0.250024][    T0]  <TASK>
[    0.250029][    T0]  dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:123)
[    0.250040][    T0]  warn_alloc (kbuild/src/consumer/mm/page_alloc.c:4005)
[    0.250068][    T0]  __alloc_pages_slowpath (kbuild/src/consumer/mm/page_alloc.c:?)
[    0.250073][    T0]  __alloc_frozen_pages_noprof (kbuild/src/consumer/mm/page_alloc.c:?)


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260112/[email protected]



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.