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@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec