Subject: Help needed with kexec on arm64

From: [email-masked] (AKASHI Takahiro)
Date: Tue, 31 May 2016 09:34:27 +0900

On 05/27/2016 08:51 PM, Harninder Rai wrote:
> Hello Takahiro Akashi,
>
> Please see the following log which I was talking about in my last communication
> Any idea as to what could be wrong just when I move from RAM based rootfs to SD based rootfs?
>
>> I did check /proc/iomem and everything looks there. This is very strange
>> since if I keep everything same and just move the rootfs from RAM based to
>> SD based, I start getting this issue.
>
> root at ls2085ardb:/# kexec -p ./vmlinux.wor --initrd=./initramfs_arm64_busybox1_22_1_with_coremark.cpio.gz --append='console=ttyS1,115200 root=/dev/ram0 earlycon=uart8250,mmio,0x21c0600ramdisk_size=0x2000000 default_hugepagesz=2m hugepagesz=2m hugepages=256 memblock=debug maxcpus=1'
> Memory for crashkernel is not reserved
> Please reserve memory by passing"crashkernel=X at Y" parameter to kernel
> Then try to loading kdump kernel
> root at ls2085ardb:/# cat /proc/iomem
> 02000000-0200ffff : /i2c at 2000000
> 02140000-0214ffff : mmc0
> 021c0500-021c05ff : serial
> 021c0600-021c06ff : serial
> 03100000-03107fff : /usb3 at 3100000
> 0310c100-0310ffff : /usb3 at 3100000
> 03110000-03117fff : /usb3 at 3110000
> 0311c100-0311ffff : /usb3 at 3110000
> 05000000-057fffff : /iommu at 5000000
> 80000000-ffffffff : System RAM
>    80080000-80a39333 : Kernel code
>    80af5000-80bd4fff : Kernel data
>    8c000000-8fffffff : Crash kernel
> 80c000000-80c00003f : mc_portal

Please trace is_crashkernel_mem_reserved() and kexec_iomem_for_each_line().

-Takahiro AKASHI

> Regards
> Harry++