On 20/12/2022 02:51, Baoquan He wrote: > On 12/20/22 at 01:41pm, Baoquan He wrote: >> On one intel bare metal system, I can randomly reproduce the kdump hang >> as below with tick_periodic call trace. Attach the kernel config for >> reference. > > Forgot mentioning this random hang is also caused by adding > 'nr_cpus=2' into normal kernel's cmdline, then triggering crash will get > kdump kernel hang as below kdump log shown. > The weird thing is that you seem to be using "nr_cpus=1" instead - this is the cmdline from the log: "nr_cpus=2 irqpoll nr_cpus=1 reset_devices cgroup_disable=memory mce=off numa=off udev.children-max=2 panic=10 acpi_no_memhotplug transparent_hugepage=never nokaslr hest_disable novmcoredd cma=0 hugetlb_cma=0 disable_cpu_apicid=16 [...]" You seems to pass twice the "nr_cpus" thing, and I guess kernel pick the last one? Also, what is "disable_cpu_apicid=16"? Could this be related? Thanks for the report! Cheers, Guilherme _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
