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:~#
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?
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: 350002ac01d6314 e1-part1 on / type ext4 (rw,errors= remount- ro) nosuid, nodev) nosuid, nodev) fuse/connection s type fusectl (rw) security type securityfs (rw) nosuid, gid=5,mode= 0620) nosuid, size=10% ,mode=0755) nosuid, nodev,size= 5242880) nosuid, nodev,size= 104857600, mode=0755) cgroup/ systemd type cgroup (rw,noexec, nosuid, nodev,none, name=systemd)
root@ubuntu:~# mount
/dev/mapper/
proc on /proc type proc (rw,noexec,
sysfs on /sys type sysfs (rw,noexec,
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,
tmpfs on /run type tmpfs (rw,noexec,
none on /run/lock type tmpfs (rw,noexec,
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,
none on /sys/fs/pstore type pstore (rw)
systemd on /sys/fs/
root@ubuntu:~#
hbauser@ubuntu:~$ ls /boot/ 0-24-generic grub memtest86+.bin memtest86+ _multiboot. bin vmlinuz- 3.13.0- 24-generic 3.13.0- 24-generic initrd. img-3.13. 0-24-generic memtest86+.elf System. map-3.13. 0-24-generic
abi-3.13.
config-
hbauser@ubuntu:~$
hbauser@ubuntu:~$ cat /proc/cmdline /boot/vmlinuz- 3.13.0- 24-generic root=UUID= 0503c0b3- 1acd-4e11- a60a-f5f2618fdb 6c ro crashkernel= 384M-:128M /boot/vmlinuz- 3.13.0- 24-generic root=UUID= 0503c0b3- 1acd-4e11- a60a-f5f2618fdb 6c ro crashkernel= 384M-:128M /boot/vmlinuz- 3.13.0- 24-generic root=UUID= 0503c0b3- 1acd-4e11- a60a-f5f2618fdb 6c ro crashkernel= 384M-:128M
BOOT_IMAGE=
hbauser@ubuntu:~$ dmesg | grep -i crash
[ 0.000000] Command line: BOOT_IMAGE=
[ 0.000000] Reserving 128MB of memory at 720MB for crashkernel (System RAM: 32733MB)
[ 0.000000] Kernel command line: BOOT_IMAGE=
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?