Comment 22 for bug 1778844

------- Comment From <email address hidden> 2018-09-20 07:06 EDT-------
Hi,

We lost the old environment as jmet got returned.
Got a new Witherspoon jmet and retried the kdump scenario & issue recreated on latest ubuntu180401 kernel (4.15.0-34-generic) kernel.

> Triggered kdump with default crashkernel parameter and it went to initramfs state
root@wax:~# cat /proc/cmdline
root=UUID=38d0124f-14d8-4098-a746-03f9bda5c22e ro crashkernel=8192M splash quiet crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M

> Collected console & dmesg logs from same state
> Rebooted system & collected sosreport, tar czf lp1778844_sys.tar.gz /sys/
> Also tried comment#23 steps & collected /tmp/initrd.img

root@wax:~# cat /etc/initramfs-tools/initramfs.conf | grep MODULES
# MODULES: [ most | netboot | dep | list ]
MODULES=dep
root@wax:~# mkinitramfs -o /tmp/initrd.img
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
root@wax:~# uname -r
4.15.0-34-generic
root@wax:~# ls -l /tmp/initrd.img
-rw-r--r-- 1 root root 24128581 Sep 20 04:59 /tmp/initrd.img

> Attaching all above logs & if i am unable to attach any of the logs because of size issue. Logs are placed in the path

banner.isst.aus.stglabs.ibm.com [banner/don2rry ] : /home/banner/169067_sep20

> Attaching console logs from first step till last step ( starting from system booting with latest kernel level, trigger crash , initramfs state etc...)

Thanks & Regards,
Indira