From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.skyhub.de ([5.9.137.197]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hZYF8-0001kc-GC for kexec@lists.infradead.org; Sat, 08 Jun 2019 10:06:35 +0000 Date: Sat, 8 Jun 2019 12:06:23 +0200 From: Borislav Petkov Subject: Re: [PATCH 0/3 v11] add reserved e820 ranges to the kdump kernel e820 table Message-ID: <20190608100623.GA9138@zn.tnic> References: <20190423013007.17838-1-lijiang@redhat.com> <12847a03-3226-0b29-97b5-04d404410147@redhat.com> <20190607174211.GN20269@zn.tnic> <20190608035451.GB26148@MiWiFi-R3L-srv> <20190608091030.GB32464@zn.tnic> <20190608100139.GC26148@MiWiFi-R3L-srv> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20190608100139.GC26148@MiWiFi-R3L-srv> 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: Baoquan He Cc: Thomas.Lendacky@amd.com, x86@kernel.org, lijiang , peterz@infradead.org, dave.hansen@linux.intel.com, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, mingo@redhat.com, luto@kernel.org, hpa@zytor.com, tglx@linutronix.de, dyoung@redhat.com, akpm@linux-foundation.org On Sat, Jun 08, 2019 at 06:01:39PM +0800, Baoquan He wrote: > OK, it may be different with the case we met, if panic happened when > load a kdump kernel. > > We can load with 'kexec -l' or 'kexec -p', but can't boot after triggering > crash or execute 'kexec -e' to do kexec jumping. No, I load a kdump kernel properly with this command: kexec -s -p /boot/vmlinuz-5.2.0-rc3+ --initrd=/boot/initrd.img-5.2.0-rc3+ --command-line="maxcpus=1 root=/dev/sda5 ro debug ignore_loglevel log_buf_len=16M no_console_suspend net.ifnames=0 systemd.log_target=null mem_encrypt=on kvm_amd.sev=1 nr_cpus=1 irqpoll reset_devices vga=normal LANG=en_US.UTF-8 earlyprintk=serial cgroup_disable=memory mce=off numa=off udev.children-max=2 panic=10 rootflags=nofail acpi_no_memhotplug transparent_hugepage=never disable_cpu_apicid=0" And that succeeds judging from $ grep . /sys/kernel/kexec_* Then I trigger a panic with echo c > /proc/sysrq-trigger and this is where it hangs and doesn't load the kdump kernel. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec