FYI, we noticed the following commit: commit: cc4a913fa513cdac8777c2714e6388465691faf8 ("mm/memblock: switch to use NUMA_NO_NODE instead of MAX_NUMNODES in for_each_mem_pfn_range()") url: https://github.com/0day-ci/linux/commits/Wei-Yang/mm-memblock-use-NUMA_NO... in testcase: trinity with following parameters: runtime: 300s test-description: Trinity is a linux system call fuzz tester. test-url: http://codemonkey.org.uk/projects/trinity/ on test machine: qemu-system-i386 -enable-kvm -m 256M caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace): +------------------------------------------------+------------+------------+ | | 2d1ec173d5 | cc4a913fa5 | +------------------------------------------------+------------+------------+ | boot_successes | 6 | 0 | | boot_failures | 0 | 8 | | WARNING:at_mm/memblock.c:#__next_mem_pfn_range | 0 | 8 | | calltrace:SyS_open | 0 | 8 | +------------------------------------------------+------------+------------+ [ 0.000000] initial memory mapped: [mem 0x00000000-0x083fffff] [ 0.000000] Base memory trampoline at [8009b000] 9b000 size 16384 [ 0.000000] ------------[ cut here ]------------ [ 0.000000] WARNING: CPU: 0 PID: 0 at mm/memblock.c:1088 __next_mem_pfn_range+0x5e/0x16e [ 0.000000] Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead [ 0.000000] Modules linked in: [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.9.0-rc6-00135-gcc4a913 #1 [ 0.000000] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.3-20161025_171302-gandalf 04/01/2014 [ 0.000000] 87511ec0 86e241ad 8743bde0 8743bde0 87511ed8 86c48c2a 00000440 11a426ae [ 0.000000] 87511f5c 87511f54 87511ef4 86c48c68 00000009 00000000 87511eec 8743bde0 [ 0.000000] 87511f08 87511f1c 875eadb9 8743bd80 00000440 8743bde0 87511f5c 87511f54 [ 0.000000] Call Trace: [ 0.000000] [<86e241ad>] dump_stack+0x76/0xa9 [ 0.000000] [<86c48c2a>] __warn+0xba/0xd0 [ 0.000000] [<86c48c68>] warn_slowpath_fmt+0x28/0x30 [ 0.000000] [<875eadb9>] __next_mem_pfn_range+0x5e/0x16e [ 0.000000] [<875a84e6>] init_range_memory_mapping+0x3e/0x177 [ 0.000000] [<875e9fea>] ? memblock_find_in_range+0x3c/0x95 [ 0.000000] [<875a87c4>] init_mem_mapping+0x1a5/0x260 [ 0.000000] [<87594e3a>] setup_arch+0x7c0/0xb82 [ 0.000000] [<86c973b2>] ? vprintk_default+0x12/0x20 [ 0.000000] [<8758dcd8>] start_kernel+0x5b/0x40f [ 0.000000] [<8758d2c8>] i386_start_kernel+0xaf/0xc7 [ 0.000000] ---[ end trace 0000000000000000 ]--- [ 0.000000] BRK [0x07ea3000, 0x07ea3fff] PGTABLE [ 0.000000] RAMDISK: [mem 0x0f4f1000-0x0ffcffff] To reproduce: git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git cd lkp-tests bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email Thanks, Xiaolong