kdump failed because of hotplug memory adding in kdump kernel
vgoyal at redhat.com
Thu Jan 9 11:24:27 EST 2014
On Thu, Jan 09, 2014 at 09:03:59AM -0700, Toshi Kani wrote:
> > > > > So basically acpi thinks that some memory block is a hot plug memory
> > > > > and tries to add it. And that consumes lots of memory and we don't have
> > > > > that memory in second kernel.
> > > >
> > > > That's not exactly the case. What seems to happen is that there is an ACPI
> > > > memory object in the ACPI namespace and the ACPI memory hotplug driver
> > > > attempts to bind to it. That driver attempts to find removable memory blocks
> > > > associated with that object and to add them to the memory map.
> > > >
> > > > Why don't you simply append acpi=off to the kexec command line? That should
> > > > make the problem go away.
> > >
> > > Yes, that should work, but Baoquan's approach makes sense to me. When
> > > memmap=exactmap is specified, the kernel should ignore any memory
> > > information from the firmware.
> > memmap=exactmap is only for E820 map. It does not say that later memory
> > can not be hotplugged. So to me specifying exactmap does not imply that
> > memory hotplugging is disabled.
> There are multiple ways to describe memory range info in the firmware;
> e820, EFI memory descriptor table, and ACPI memory device objects. They
> basically provide the same info.
So ACPI memory device objects contain all the memory ranges as exported
> This problem happens when the firmware implements ACPI memory device
> objects, which are necessary to support memory hotplug, but do not mean
> that the system always supports hotplug when they exist. They are
> optional objects that firmware vendors may choose to implement.
This is confusing. So even if memory hotplug is not supported, ACPI memory
device objects might be present. What's the purpose? How do they help.
If they represent same info as firmware provided using a BIOS call early
(E820 map), then how does system later avoid adding same memory ranges.
IOW, in terms of design, what's the objective. Why to create this
additional path of getting memory information.
> While the exactmap option does not imply that memory hotplug is
But Bao's approach will disable memory hotplug on exactmap.
> it does require that the kernel only consumes user-supplied
> memory range information. Hence, Baoquan's approach makes sense to me.
I am fine with this as long as memmap=exactmap is not the only way to
disable memory hotplug. I need another way too so that users who are
not using exactmap can still disable memory hotplug.
> > IMO, it makes sense to have a separate knob to disable memory hotplug
> > behavior.
> Regular users do not know if their systems implement ACPI memory device
> objects or not. So, asking users to specify a separate option when
> their systems implement ACPI memory objects is tricky, IMO.
They can always specify no_memory_hotplug, irrespective of the fact that
kernel supports memory hotplug or not.
Anyway, I don't mind if one implicitly disables memory hotplug if
memmap=exactmap or mem=X is specified. It is just a matter of figuring
how what should be a more intutive behavior from user's point of view.
But I do want a separate path to disable memory hotplug so that even
if I am not using memmap=exactmap or mem=X, I should be able to disable
> > Also from kdump point of view, I don't want to rely on exactmap as in
> > new implementation I am planning to move away from exactmap. I will
> > pass new memory map in bootparams and stop passing it on command line.
> I think we still need a flag that indicates the kernel can only consume
> the new memory map in bootparams, and cannot to obtain from the
I think creating a new command line option is simpler as compared to
creating a new flag in bootparam which in turn disables memory hotplug.
More users can use that option. For example, if for some reason hotplug
code is crashing, one can just disable it on command line as work around
and move on.
More information about the kexec