On Thu, Sep 12, 2019 at 03:55:39PM +0200, Thomas Bogendoerfer wrote: > - reserved[0xd] [0x000000035bff8000-0x000000035bffffff], > 0x0000000000008000 bytes flags: 0x0 > > I have no idea which reservation this is, but it's not from one of the > node data.
that's sparsemem's mem_section. And free_bootmem_with_active_regions(node, end_pfn); on the last node will free this reserved memory, when memory is added node by node. This explains it. So when resending the patch add my Tested-by: Thomas Bogendoerfer <tbogendoer...@suse.de> Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]
