From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64 crashkernel fails to boot on acpi-only machines due to ACPI regions being no longer mapped as NOMAP
Date: Mon, 13 Nov 2017 18:27:31 +0900 [thread overview]
Message-ID: <20171113092730.GA29552@linaro.org> (raw)
In-Reply-To: <CACi5LpNV_E9pvhTwLcy6vtEj9qbL1ZEHe-5sv=iiW0k9JxPD1Q@mail.gmail.com>
Hi,
On Fri, Nov 10, 2017 at 05:41:56PM +0530, Bhupesh Sharma wrote:
> Resent with Akashi's correct email address.
>
> On Fri, Nov 10, 2017 at 5:39 PM, Bhupesh Sharma <bhsharma@redhat.com> wrote:
> > Hi Ard, Akashi
> >
> > I have met an issue on an arm64 board using the latest master branch from Linus.
(snip)
> >
> > 8. Also, I think now the crashkernel handling changed by
> > e7cd190385d17790cc3eb3821b1094b00aacf325 (arm64: mark reserved
> > memblock regions explicitly in iomem), needs to be changed to handle
> > the change added by Ard to fix this issue on ACPI only machines.
> >
> > I have a dirty hack in place, but I would like to have your opinions
> > about what can be a more concrete fix to this issue (as we mark these
> > regions as System RAM now rather than NOMAP) and I don't have a DTB
> > based machine to test on currently.
I don't know much about acpi reclaim regions,
can you please tell me how your change affects your panic case?
Thanks,
-Takahiro AKASHI
> > Please share your views.
> >
> > Regards,
> > Bhupesh
next prev parent reply other threads:[~2017-11-13 9:27 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 12:09 arm64 crashkernel fails to boot on acpi-only machines due to ACPI regions being no longer mapped as NOMAP Bhupesh Sharma
2017-11-10 12:11 ` Bhupesh Sharma
2017-11-13 9:27 ` AKASHI Takahiro [this message]
2017-11-14 11:20 ` Ard Biesheuvel
2017-11-15 10:58 ` Bhupesh Sharma
2017-11-16 7:00 ` AKASHI Takahiro
2017-11-26 8:29 ` Bhupesh SHARMA
2017-12-04 14:02 ` Ard Biesheuvel
2017-12-12 21:51 ` Bhupesh Sharma
2017-12-13 10:26 ` AKASHI Takahiro
2017-12-13 10:49 ` Ard Biesheuvel
2017-12-13 12:16 ` AKASHI Takahiro
2017-12-13 12:17 ` Ard Biesheuvel
2017-12-13 19:22 ` Bhupesh SHARMA
2017-12-15 8:59 ` AKASHI Takahiro
2017-12-15 9:35 ` Ard Biesheuvel
2017-12-17 21:01 ` Bhupesh Sharma
2017-12-18 5:16 ` Dave Young
2017-12-18 5:54 ` AKASHI Takahiro
2017-12-18 8:59 ` Bhupesh SHARMA
2017-12-18 11:18 ` AKASHI Takahiro
2017-12-18 22:28 ` Bhupesh Sharma
2017-12-19 5:01 ` AKASHI Takahiro
2017-12-20 19:52 ` Bhupesh Sharma
2017-12-18 21:28 ` Bhupesh Sharma
2017-12-19 5:25 ` AKASHI Takahiro
2017-12-18 5:40 ` Dave Young
2017-12-18 5:43 ` Dave Young
2017-12-19 6:09 ` AKASHI Takahiro
2017-12-19 13:09 ` Ard Biesheuvel
2017-12-20 20:00 ` Bhupesh Sharma
2017-12-21 10:34 ` AKASHI Takahiro
2017-12-21 12:06 ` Bhupesh Sharma
2017-12-22 8:33 ` AKASHI Takahiro
2017-12-23 19:51 ` Bhupesh Sharma
2017-12-25 3:25 ` AKASHI Takahiro
2017-12-25 20:14 ` Bhupesh Sharma
2017-12-26 1:32 ` Dave Young
2017-12-26 1:35 ` Dave Young
2017-12-26 2:28 ` AKASHI Takahiro
2017-12-26 2:56 ` Bhupesh Sharma
2017-12-26 6:58 ` Dave Young
2018-01-09 5:22 ` AKASHI Takahiro
2018-01-08 20:00 ` Bhupesh Sharma
2018-01-09 4:42 ` AKASHI Takahiro
2018-01-09 11:46 ` Bhupesh Sharma
2017-12-26 6:56 ` Dave Young
2018-01-09 5:02 ` AKASHI Takahiro
2017-11-24 8:47 ` Dave Young
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=20171113092730.GA29552@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).