linux-kernel - WARNING: CPU: 0 PID: 0 at mm/memblock.c:789 __next_free_mem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140106133600.GA18624@localhost>
Date:	Mon, 6 Jan 2014 21:36:00 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Grygorii Strashko <grygorii.strashko@...com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: WARNING: CPU: 0 PID: 0 at mm/memblock.c:789 __next_free_mem_range()

Greetings,

I got the below dmesg and the error is exposed by

commit 68abcdf54742a06de9ec52cbb05b6bdd27e6bdab
Author:     Grygorii Strashko <grygorii.strashko@...com>
AuthorDate: Fri Jan 3 14:09:57 2014 +1100
Commit:     Stephen Rothwell <sfr@...b.auug.org.au>
CommitDate: Fri Jan 3 14:09:57 2014 +1100

    mm/memblock: use WARN_ONCE when MAX_NUMNODES passed as input parameter
    
    Check nid parameter and produce warning if it has deprecated MAX_NUMNODES
    value.  Also re-assign NUMA_NO_NODE value to the nid parameter in this
    case.
    
    These will help to identify the wrong API usage (the caller) and make code
    simpler.
    
    Signed-off-by: Grygorii Strashko <grygorii.strashko@...com>
    Signed-off-by: Santosh Shilimkar <santosh.shilimkar@...com>
    Cc: Yinghai Lu <yinghai@...nel.org>
    Cc: Tejun Heo <tj@...nel.org>
    Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>


[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] mapped APIC to ffffffffff57b000 (        fee00000)
[    0.000000] ------------[ cut here ]------------
[    0.000000] WARNING: CPU: 0 PID: 0 at mm/memblock.c:789 __next_free_mem_range+0xc7/0x29c()
[    0.000000] Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead
[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.13.0-rc7-next-20140106-07462-gb4a839b #455
[    0.000000] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[    0.000000]  0000000000000009 ffffffff82201d70 ffffffff81986d81 ffffffff82201db8
[    0.000000]  ffffffff82201da8 ffffffff810da9a8 0000000000000000 0000000000000001
[    0.000000]  0000000000000001 0000000000000001 0000000000000001 ffffffff82201e08
[    0.000000] Call Trace:
[    0.000000]  [<ffffffff81986d81>] dump_stack+0x85/0xba
[    0.000000]  [<ffffffff810da9a8>] warn_slowpath_common+0xa8/0xe0
[    0.000000]  [<ffffffff810daa7c>] warn_slowpath_fmt+0x5c/0x70
[    0.000000]  [<ffffffff8115b745>] ? vprintk_emit+0x465/0x950
[    0.000000]  [<ffffffff827139cd>] __next_free_mem_range+0xc7/0x29c
[    0.000000]  [<ffffffff826ab120>] ? early_idt_handlers+0x120/0x120
[    0.000000]  [<ffffffff826ab120>] ? early_idt_handlers+0x120/0x120
[    0.000000]  [<ffffffff826b3da3>] memblock_find_dma_reserve+0xca/0x163
[    0.000000]  [<ffffffff826b09c9>] setup_arch+0x1086/0x11f9
[    0.000000]  [<ffffffff826ab120>] ? early_idt_handlers+0x120/0x120
[    0.000000]  [<ffffffff826ab120>] ? early_idt_handlers+0x120/0x120
[    0.000000]  [<ffffffff826abeb7>] start_kernel+0xe4/0x6fc
[    0.000000]  [<ffffffff826ab120>] ? early_idt_handlers+0x120/0x120
[    0.000000]  [<ffffffff826ab637>] x86_64_start_reservations+0x46/0x4f
[    0.000000]  [<ffffffff826ab7c9>] x86_64_start_kernel+0x189/0x19f
[    0.000000] ---[ end trace 8fe5782a70405023 ]---
[    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00

Thanks,
Fengguang

View attachment "dmesg-yocto-xgwo-5:20140106180919:x86_64-randconfig-c0-0106:3.13.0-rc7-next-20140106-07462-gb4a839b:455" of type "text/plain" (45139 bytes)

View attachment "config-3.13.0-rc7-next-20140106-07462-gb4a839b" of type "text/plain" (75658 bytes)