From: panand@redhat.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: kexec crash kernel boot failure on arm64
Date: Mon, 27 Jul 2015 10:48:35 +0530 [thread overview]
Message-ID: <20150727051835.GF31919@dhcppc13.redhat.com> (raw)
In-Reply-To: <20150724092934.GA23074@leverpostej>
On 24/07/2015:10:29:34 AM, Mark Rutland wrote:
> On Fri, Jul 24, 2015 at 03:07:24AM +0100, Anurup m wrote:
> > Hi All,
> >
> > There is a problem observed with crash kernel boot in kdump on arm64.
>
> With which kernel? Mainline doesn't have kexec or kdump support for
> arm64.
>
> > On arm64 hardware board, when I enable the purgatory segment, the crash kernel doesnot boot.
> > When checked with trace32, it is observed that the control comes to purgatory_start routine,
> > but the instructions are seen as UNDEF and the boot hangs. But when I took the memory dump, the
> > contents were seen as proper(matching with the purgatory_start code).
> >
> > I did some experiments to analyze this issue. Tried changing the Load order of kexec segments and
> > observed results as below
As Mark asked, its important to know, which kernel and which
kexec-tools you are using. I guess, you would be using either Geoff's
[1] master branch or Akashi's [2] kdump/v0.12 branch for kexec-tools.
Can you try to increase your crashkernel(=xM) size and use mem=
parameter appropriately for the primary kernel commandline and see if
it improves.
~Pratyush
[1] git://git.kernel.org/pub/scm/linux/kernel/git/geoff/kexec-tools.git
[2] https://git.linaro.org/people/takahiro.akashi/kexec-tools.git
next prev parent reply other threads:[~2015-07-27 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 2:07 kexec crash kernel boot failure on arm64 Anurup m
2015-07-24 9:29 ` Mark Rutland
2015-07-27 5:18 ` Pratyush Anand [this message]
2015-07-27 6:24 ` Anurup M
2015-07-27 5:33 ` Anurup M
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=20150727051835.GF31919@dhcppc13.redhat.com \
--to=panand@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.