>> : >> [ 0.000000] memblock_free: [0x0000102febc080-0x0000102febf080] memblock_free_reserved_regions+0x37/0x39 >> >> Here, [0x0000102febc080-0x0000102febf080] was released to available memory block >> by function free_low_memory_core_early(). I'm not sure the release memblock might >> be taken by bootmem, but I think it's worthy to have a try of removing following >> 2 lines: memblock_free_reserved_regions() and memblock_reserve_reserved_regions() > >if it was taken, should have print out about that. > Yinghai, it's possible the memory block returned to bootmem and get used/corrupted by other CPU cores? Thanks, Gavin -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>