I also tested it on 5.15.0-1031-bluefield and it also fails.
Configurations:
root@bu-oob:~# kdump-config show
DUMP_MODE: kdump
USE_KDUMP: 1
KDUMP_COREDIR: /var/crash
crashkernel addr: 0xbd00
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-1031-bluefield
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-5.15.0-1031-bluefield
current state:ready to kdump
kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-1031-bluefield
root=UUID=8e8b38a6-7d3d-4a29-b7a0-99761624f941 ro console=hvc0 console=ttyAMA0
earlycon=pl011,0x1301 fixrtc net.ifnames=0 biosdevname=0
iommu.passthrough=1 console=tty1 console=ttyS0 reset_devices
systemd.unit=kdump-tools-dump.service nr_cpus=1"
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@bu-lab60v3-oob:~#
###
root@bu-oob:~# dmesg |grep -i crash
[0.00] crashkernel reserved: 0xbd00 - 0xfd00
(1024 MB)
[0.00] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-5.15.0-1031-bluefield
root=UUID=8e8b38a6-7d3d-4a29-b7a0-99761624f941 ro console=hvc0 console=ttyAMA0
earlycon=pl011,0x1301 fixrtc net.ifnames=0 biosdevname=0
iommu.passthrough=1 console=tty1 console=ttyS0
crashkernel=2G-4G:320M,4G-32G:1024M,32G-64G:1536M,64G-128G:2048M,128G-:4096M
[5.230439] pstore: Using crash dump compression: deflate
root@bu-oob:~#
root@bu-oob:~# cat /etc/default/grub.d/kdump-tools.cfg
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT
crashkernel=2G-4G:320M,4G-32G:1024M,32G-64G:1536M,64G-128G:2048M,128G-:4096M"
root@bu-lab60v3-oob:~# grep -e "CRASH" -e "KEXEC"
/boot/config-5.15.0-1031-bluefield
CONFIG_KEXEC=y
CONFIG_KEXEC_FILE=y
CONFIG_KEXEC_SIG=y
CONFIG_KEXEC_IMAGE_VERIFY_SIG=y
CONFIG_CRASH_DUMP=y
CONFIG_CRASH_CORE=y
CONFIG_KEXEC_CORE=y
CONFIG_HAVE_IMA_KEXEC=y
CONFIG_IMA_KEXEC=y
*** How to reproduce ***
When manually triggers the crash "echo c > /proc/sysrq-trigger"
the system just hangs without showing any message/log.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2021930
Title:
kdump cannot generate coredump file on bluefield with 5.4 and 5.15
kernel
Status in linux-bluefield package in Ubuntu:
New
Bug description:
kdump cannot generate coredump file on bluefield with 5.4 kernel
Bug description:
Following the instruction in
https://ubuntu.com/server/docs/kernel-crash-dump, the coredump file cannot be
generated.
Bluefield is running 5.4 kernel
bf2:~$ uname -a
Linux sw-mtx-008-bf2 5.4.0-1060-bluefield #66-Ubuntu SMP PREEMPT Mon
Mar 27 15:52:50 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
crashkernel parameter is configured
bf2:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield
root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0
earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0
iommu.passthrough=1
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
bf2:~$ dmesg | grep -i crash
[0.00] crashkernel reserved: 0xcfe0 -
0xefe0 (512 MB)
[0.00] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield
root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0
earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0
iommu.passthrough=1
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
[8.070921] pstore: Using crash dump compression: deflate
kdump-config is as below:
bf2:~$ kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x
/var/lib/kdump/vmlinuz: symbolic link to
/boot/vmlinuz-5.4.0-1060-bluefield
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-5.4.0-1060-bluefield
current state:ready to kdump
kexec command:
/sbin/kexec -p
--command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1060-bluefield
root=UUID=52ddbe2c-ee4f-48d4-b7d4-ab76e264e438 ro console=hvc0 console=ttyAMA0
earlycon=pl011,0x0100 fixrtc net.ifnames=0 biosdevname=0
iommu.passthrough=1 reset_devices systemd.unit=kdump-tools-dump.service
nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
sysrq:
bf2:/# cat /proc/sys/kernel/sysrq
176
After trigged the crash manually with "echo c > /proc/sysrq-trigger", the
system could not come up because of OOM. And after change the crashkernel with
1024M memory it still hangs.
With default 512M, it hangs at "Killed process 674"
