KDump&Kexec

[D Srinivasa Reddy]

Hi Anil,

How are you?.

I'm srinivas, trying to generate vmcore crash dump upon triggering crash,but I'm getting size 0, seems ram contents not copied to vmcore file. crashkernel=1G-:512M given on uboot cmdline as grub.conf is not there. This is for armv8.

I've few doubts related to kdump-config.

1.along with vmlinuz -> /boot/vmlinuz, do we need to take initrd.img/initramfs in /var/lib/kdump path.

2./etc/kdump.conf is not there, I've /etc/default/kdump-tools. do we need to create /etc/kdump.conf from /etc/default/kdump-tools

3./etc/grub.conf is not there. uboot cmdline I'm giving crashkernel=1G-:512M

4.do we need to generate two kernels or one kernel enabled with KEXEC,CRASH DUMP, SYSRQ, VMCORE is sufficient?.

5. current state of kdump showing not ready to dump?. any issue in kdump configuration?.

any proper link,videos available?

root@localhost:~# kdump-config show
DUMP_MODE:        kdump
USE_KDUMP:        1
KDUMP_SYSCTL:     kernel.panic_on_oops=1
KDUMP_COREDIR:    /home/tetra/cores
crashkernel addr: 0xdbe00000
   /var/lib/kdump/vmlinuz
kdump initrd:
   /var/lib/kdump/initrd.img
current state:    Not ready to kdump

kexec command:
  no kexec command recorded

[real time]

Hi Srinivas , 

Please check in this link , are you missing anything?

Oops! Debugging Kernel Panics | Linux Journal

Regards,

Mehul

--
You received this message because you are subscribed to the Google Groups "SysPlay's Inside Linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/inside_linux/CAOKcRMsRG4JnJnoc0gtvheshVX0ypr58XhuoMDRoV2B9J2XJYQ%40mail.gmail.com.