linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: Help needed with kexec on arm64
Date: Tue, 31 May 2016 09:34:27 +0900	[thread overview]
Message-ID: <574CDC13.9090709@linaro.org> (raw)
In-Reply-To: <DB5PR04MB16887FF10CEA6AA9BF990F0DE6420@DB5PR04MB1688.eurprd04.prod.outlook.com>

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++
>

  parent reply	other threads:[~2016-05-31  0:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DB5PR04MB168845795D86B4CE5BA5656FE68B0@DB5PR04MB1688.eurprd04.prod.outlook.com>
     [not found] ` <1458230896.3391.18.camel@infradead.org>
     [not found]   ` <CAB5YjtBEO=efjhcFdVOaZqG13qK3uzCbS5SFym5hhw-n+_QLhw@mail.gmail.com>
     [not found]     ` <DB5PR04MB1688A6D4385B76DAFF71D364E68C0@DB5PR04MB1688.eurprd04.prod.outlook.com>
     [not found]       ` <CAB5YjtAqjL8LMvNPbxwVWe+Zhi5rFkz_X7rti9wSrXQ7Y_2kOA@mail.gmail.com>
     [not found]         ` <DB5PR04MB16880834700413C3B80194B5E68C0@DB5PR04MB1688.eurprd04.prod.outlook.com>
     [not found]           ` <CAB5YjtCP6M9=ESJhfxyyYKSGTg8s3Y83qp8RS_oyYkUqcqYcCw@mail.gmail.com>
2016-03-21 10:27             ` Help needed with kexec on arm64 Harninder Rai
     [not found]               ` <CAB5YjtCoX5FoRbOYTPCETbbBGmEvs=1Xm6Giho78TH_a7u=eXw@mail.gmail.com>
2016-03-22 17:49                 ` Harninder Rai
2016-04-04 10:49             ` Harninder Rai
2016-04-05  5:23               ` AKASHI Takahiro
2016-04-05 10:42                 ` Harninder Rai
2016-05-10 12:32                 ` Harninder Rai
2016-05-11  0:53                   ` AKASHI Takahiro
2016-05-11 11:06                     ` Harninder Rai
2016-05-13 12:45                     ` Harninder Rai
2016-05-19 11:03                       ` AKASHI Takahiro
2016-05-19 13:53                         ` Harninder Rai
2016-05-27 11:51                         ` Harninder Rai
2016-05-27 13:58                           ` Russell King - ARM Linux
2016-05-27 19:19                             ` Geoff Levand
2016-05-30 11:10                               ` Harninder Rai
2016-05-30 11:07                             ` Harninder Rai
2016-05-31  0:34                           ` AKASHI Takahiro [this message]
2016-05-19 10:48                 ` Harninder Rai
2016-03-17 16:57 Harninder Rai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=574CDC13.9090709@linaro.org \
    --to=takahiro.akashi@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).