Messages in this thread | | | Date | Tue, 19 Jun 2012 14:09:45 +0800 | From | Gavin Shan <> | Subject | Re: Early boot panic on machine with lots of memory |
| |
>> : >> [ 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |