Re: kdump in upstream kexec-tools

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 17, 2018 at 04:20:00PM +0530, Bhupesh Sharma wrote:
> For e.g I use this tool on my arm64 board as follows:
> 
> a. Read out the 'elfcorehdr' env variable passed to the crash kernel
> and pass the same as an argument to the tool:
> 
> Assuming that the 'elfcorehdr' spans the range ->
> 0xffdf0000-0xffdf13ff, launch the tool as -
> 
> # kdump
> Cannot find the start of the core dump
> 
> # kdump 0xffdf0000 >> output_elf_file
> 
> # file output_elf_file
> output: ELF 64-bit LSB core file ARM aarch64, version 1 (SYSV)

The contents should basically be the same (possibly with a different
section ordering) as /proc/vmcore in the crashdump kernel.  If so,
kdump serves no useful purpose, and ends up confusing the situation
due to its inability to handle 32-bit ELF coredump files.

It seems to me that the presence of /proc/vmcore obsoletes the kdump
tool.

-- 
Russell King

_______________________________________________
kexec mailing list
kexec@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/kexec



[Index of Archives]     [LM Sensors]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux