I have a setup with Ubuntu 14.04 LTS server. The /boot is not on a separate partition. I followed the kdump setup as mentioned in https://help.ubuntu.com/14.04/serverguide/kernel-crash-dump.html
After triggering the kdump, system panics but system never comeup/reboot. It get stuck at the call trace of the panic. Some of the commands output is below it might help to understand the issue: root@ubuntu:~# mount /dev/mapper/350002ac01d6314e1-part1 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) root@ubuntu:~# hbauser@ubuntu:~$ ls /boot/ abi-3.13.0-24-generic grub memtest86+.bin memtest86+_multiboot.bin vmlinuz-3.13.0-24-generic config-3.13.0-24-generic initrd.img-3.13.0-24-generic memtest86+.elf System.map-3.13.0-24-generic hbauser@ubuntu:~$ hbauser@ubuntu:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=0503c0b3-1acd-4e11-a60a-f5f2618fdb6c ro crashkernel=384M-:128M hbauser@ubuntu:~$ dmesg | grep -i crash [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=0503c0b3-1acd-4e11-a60a-f5f2618fdb6c ro crashkernel=384M-:128M [ 0.000000] Reserving 128MB of memory at 720MB for crashkernel (System RAM: 32733MB) [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=0503c0b3-1acd-4e11-a60a-f5f2618fdb6c ro crashkernel=384M-:128M hbauser@ubuntu:~$ In another configuration where I have installed OS with LVM and /boot on separate partition. The workaround suggested in this bug also didn't work. Am I missing something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828731 Title: kdump functionality not working as expected when /boot is a separate partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/828731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
