From: james.morse@arm•com (James Morse)
To: linux-arm-kernel@lists•infradead.org
Subject: kdump: need help with kexec -p
Date: Mon, 23 Oct 2017 10:33:03 +0100 [thread overview]
Message-ID: <59EDB74F.4070302@arm.com> (raw)
In-Reply-To: <HE1PR04MB12413AEF2BF54623027FD22A97460@HE1PR04MB1241.eurprd04.prod.outlook.com>
Hi Prabhakar, Akashi,
On 23/10/17 06:37, Prabhakar Kushwaha wrote:
> After further analysis, it is figured out to be a data cache flush issue.
>
> After trying below patch(suggested by Takahiro). This problem looks to be resolved for now.
>
> ===
> commit 9b492cf58077
> Author: Xunlei Pang <xlpang@redhat•com>
> Date: Mon May 23 16:24:10 2016 -0700
>
> kexec: introduce a protection mechanism for the crashkernel reserved memory
> ===
/me winces.
Yes, without the protection mechanism the code will still compile, and still
work, but be missing the kexec_segment_flush() calls.
This is the problem with backporting stuff. Glad you got it fixed!
Thanks,
James
prev parent reply other threads:[~2017-10-23 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 9:11 kdump: need help with kexec -p Prabhakar Kushwaha
2017-10-12 11:40 ` James Morse
2017-10-13 8:36 ` AKASHI Takahiro
2017-10-13 9:41 ` Prabhakar Kushwaha
2017-10-13 10:30 ` James Morse
2017-10-13 11:23 ` Prabhakar Kushwaha
2017-10-23 5:37 ` Prabhakar Kushwaha
2017-10-23 9:33 ` James Morse [this message]
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=59EDB74F.4070302@arm.com \
--to=james.morse@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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