Mohan Kumar M wrote: > Haren Myneni wrote: > >> >> We are already looking for crashkernel segment before loading the >> kdump image - crashdump-<arch>.c. Ex: for ppc64, reading >> linux,crashkernel-size property and for i386/x86_64, from /proc/iomem. >> >> Why do not we display the error message and exit from here? >> > The issue is when memory for crashkernel is not reserved, the error > message is not displayed properly. > > For eg, in PPC64, the error message will be: > /proc/device-tree/chosen/linux,crashkernel-base: No such file or > directory > get memory ranges:0 > Warning: append= option is not passed. Using the first kernel root > partition > /proc/device-tree/chosen/linux,crashkernel-base: No such file or > directory > Could not find a free area of memory of 74ac00 bytes... > Base address: ffffffff is not page aligned > > i386 kexec tool also does not clearly report the error. > > The tool has to inform the user about what exactly happened and what > should be done in order to successfully load the kdump kernel.
Yes, kexec tool has to report proper error message when crashkernel is not reserved in the first kernel. What I am saying is, when the kexec tool tries to read the crashkernel locations, report an error if not found and exit. In the case of ppc64, if the linux,crashkernel-base property is not found, means memory is not reserved for the kdump kernel. This property is created and exported only when the crashkernel= option is passed. Similarly, for i386, the kexec tool reads /proc/iomem for the "crash kernel". Thanks Haren > >> Thanks >> Haren >> >>> _______________________________________________ >>> fastboot mailing list >>> [email protected] >>> https://lists.osdl.org/mailman/listinfo/fastboot >>> >>> >> > _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
