From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from pandora.armlinux.org.uk ([2001:4d48:ad52:3201:214:fdff:fe10:1be6]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1f8Q5a-0007kd-2J for kexec@lists.infradead.org; Tue, 17 Apr 2018 12:52:07 +0000 Date: Tue, 17 Apr 2018 13:51:35 +0100 From: Russell King Subject: Re: kdump in upstream kexec-tools Message-ID: <20180417125134.GF23531@flint.armlinux.org.uk> References: <20180417090113.GA19564@flint.armlinux.org.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Bhupesh Sharma Cc: khalid.aziz@hp.com, kexec@lists.infradead.org, AKASHI Takahiro , Simon Horman , ebiederm@xmission.com, Bhupesh SHARMA , Dave Young , Vivek Goyal 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@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec