kdump failed because of hotplug memory adding in kdump kernel
bhe at redhat.com
Fri Jan 10 04:14:33 EST 2014
> >object tree, they are not treated as hotplug memory.
> They are treated as hotplug memory. But the memory cannot hot removed
> because the memory has kernel memory.
> >Otherwise, any hotplug memory which is not reserved for 2nd kernel can
> >be parsed and need be added as hotplug memory, and add them into movable
> The memory is allocated as normal zone and it is offline.
Thanks for answering.
I am confused. Now the fact is in 1st kernel memory is reserved for
crashkernel and passed to 2nd kernel by exactmap. Then in 2nd kernel,
reserved memory regions are added into e820. Later hotplug memory still
trigger add_memory, and cause bug I reported.
> >Am I right?
> >The other question, e820 reserve is done earlier than acpi
> >initialization, because acpi_early_init() invocation is very late in
> >start_kernel(). Does that means at the very beginning all memorys are in
> >e820, later when acpi_early_init is called, hotplug memory is detected,
> >they will be moved to different place or need be marked with a specific
> Yasuaki Ishimatsu
More information about the kexec