From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: Help needed with kexec on arm64
Date: Thu, 19 May 2016 20:03:09 +0900 [thread overview]
Message-ID: <20160519110307.GA4941@linaro.org> (raw)
In-Reply-To: <DB5PR04MB1688C3F122091109E6BD9B68E6740@DB5PR04MB1688.eurprd04.prod.outlook.com>
On Fri, May 13, 2016 at 12:45:04PM +0000, Harninder Rai wrote:
> Hello Takahiro Akashi,
>
> >
> > Apparently lack of memory is a cause of OOM killer, but the core file has
> > nothing to do with this issue.
> > I think that you don't have enough memory for the system yet.
> >
> > -Takahiro AKASHI
>
>
> I moved to SD card based rootfs for booting the crash kernel but when I try to load the dump kernel, I get the following message
> Is there limitation with kexec that the crash kernel cannot be booted from anything apart from RAM?
I don't know what you did here exactly, but I don't think that
there is such a limitation.
> kexec -p ./vmlinux --initrd=./ramdisk_ls1012_openwrt.cpio.gz --append='console=ttyS1,115200 root=/dev/mmcblk0p1 earlycon=uart8250,mmio,0x21c0600ramdisk_size=0x2000000 default_hugepagesz=2m hugepagesz=2m hugepages=256 crashkernel=64M at 2240M memblock=debug'
> Memory for crashkernel is not reserved
This message is a hint. You have got the same one before, right?
Please check /proc/iomem and a dmesg log from the first kernel
with memblock=debug.
-Takahiro AKASHI
> Please reserve memory by passing"crashkernel=X at Y" parameter to kernel
> Then try to loading kdump kernel
>
> Regards
> Harry++
--
Thanks,
-Takahiro AKASHI
next prev parent reply other threads:[~2016-05-19 11:03 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 [this message]
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
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=20160519110307.GA4941@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).