From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v22 2/8] arm64: limit memory regions based on DT property, usable-memory-range
Date: Tue, 09 Aug 2016 17:22:57 +0100 [thread overview]
Message-ID: <57AA0361.6030505@arm.com> (raw)
In-Reply-To: <20160804062131.GM7995@linaro.org>
Hi Akashi,
Sorry for the late response, (I was on holiday last week...)
On 04/08/16 07:21, AKASHI Takahiro wrote:
> On Mon, Jul 25, 2016 at 02:27:55PM +0900, AKASHI Takahiro wrote:
>> On Fri, Jul 22, 2016 at 02:55:02PM +0100, James Morse wrote:
>>> On 21/07/16 01:57, AKASHI Takahiro wrote:
>>>> Could you please apply the diff attached below and confirm that
>>>> kdump works in your environment?
>>>> I can't test it by myself since my hikey board seems to be broken now.
>>>
>>> With this I get a failure even earlier, even with 'acpi=off'.
>>> With this patch, on boot of the kdump kernel I get:
>>
>> I think you ran into the problem that I mentioned in:
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2016-July/444500.html
>>
>> You may want to
>> - apply the change stated above, or
>> (Given that we don't know about the configuration of crash dump kernel,
>> checking for CONFIG_ZONE_DMA doesn't make sense. Instead, we'd better
>> always enforce ARCH_LOW_ADDRESS_LIMIT.)
>> - explicitly specify the start address (Y) below ARCH_LOW_ADDRESS_LIMIT
>> at "crashkernel=X at Y"
>> Either would work.
>
> Have these methods fixed your problem in the end?
The change you made in v23 to use ARCH_LOW_ADDRESS_LIMIT fixed the problem with
juno and acpi. I will retest it with v24 and using Seattle too...
Thanks,
James
WARNING: multiple messages have this Message-ID (diff)
From: James Morse <james.morse@arm.com>
To: AKASHI Takahiro <takahiro.akashi@linaro.org>
Cc: mark.rutland@arm.com, geoff@infradead.org,
catalin.marinas@arm.com, will.deacon@arm.com, robh+dt@kernel.org,
bauerman@linux.vnet.ibm.com, dennis.chen@arm.com,
dyoung@redhat.com, kexec@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v22 2/8] arm64: limit memory regions based on DT property, usable-memory-range
Date: Tue, 09 Aug 2016 17:22:57 +0100 [thread overview]
Message-ID: <57AA0361.6030505@arm.com> (raw)
In-Reply-To: <20160804062131.GM7995@linaro.org>
Hi Akashi,
Sorry for the late response, (I was on holiday last week...)
On 04/08/16 07:21, AKASHI Takahiro wrote:
> On Mon, Jul 25, 2016 at 02:27:55PM +0900, AKASHI Takahiro wrote:
>> On Fri, Jul 22, 2016 at 02:55:02PM +0100, James Morse wrote:
>>> On 21/07/16 01:57, AKASHI Takahiro wrote:
>>>> Could you please apply the diff attached below and confirm that
>>>> kdump works in your environment?
>>>> I can't test it by myself since my hikey board seems to be broken now.
>>>
>>> With this I get a failure even earlier, even with 'acpi=off'.
>>> With this patch, on boot of the kdump kernel I get:
>>
>> I think you ran into the problem that I mentioned in:
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2016-July/444500.html
>>
>> You may want to
>> - apply the change stated above, or
>> (Given that we don't know about the configuration of crash dump kernel,
>> checking for CONFIG_ZONE_DMA doesn't make sense. Instead, we'd better
>> always enforce ARCH_LOW_ADDRESS_LIMIT.)
>> - explicitly specify the start address (Y) below ARCH_LOW_ADDRESS_LIMIT
>> at "crashkernel=X@Y"
>> Either would work.
>
> Have these methods fixed your problem in the end?
The change you made in v23 to use ARCH_LOW_ADDRESS_LIMIT fixed the problem with
juno and acpi. I will retest it with v24 and using Seattle too...
Thanks,
James
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-08-09 16:22 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 5:05 [PATCH v22 0/8] arm64: add kdump support AKASHI Takahiro
2016-07-12 5:05 ` AKASHI Takahiro
2016-07-12 5:05 ` [PATCH v22 1/8] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2016-07-12 5:05 ` AKASHI Takahiro
2016-07-13 9:12 ` Suzuki K Poulose
2016-07-13 9:12 ` Suzuki K Poulose
2016-07-13 15:42 ` AKASHI Takahiro
2016-07-13 15:42 ` AKASHI Takahiro
2016-07-19 9:39 ` Dennis Chen
2016-07-19 9:39 ` Dennis Chen
2016-07-19 10:28 ` AKASHI Takahiro
2016-07-19 10:28 ` AKASHI Takahiro
2016-07-19 10:41 ` Dennis Chen
2016-07-19 10:41 ` Dennis Chen
2016-07-19 12:48 ` Mark Salter
2016-07-19 12:48 ` Mark Salter
2016-07-19 13:27 ` Mark Rutland
2016-07-19 13:27 ` Mark Rutland
2016-07-20 2:17 ` AKASHI Takahiro
2016-07-20 2:17 ` AKASHI Takahiro
2016-07-20 3:48 ` Dennis Chen
2016-07-20 3:48 ` Dennis Chen
2016-07-19 23:34 ` AKASHI Takahiro
2016-07-19 23:34 ` AKASHI Takahiro
2016-07-12 5:05 ` [PATCH v22 2/8] arm64: limit memory regions based on DT property, usable-memory-range AKASHI Takahiro
2016-07-12 5:05 ` AKASHI Takahiro
2016-07-18 18:04 ` James Morse
2016-07-18 18:04 ` James Morse
2016-07-19 8:35 ` AKASHI Takahiro
2016-07-19 8:35 ` AKASHI Takahiro
2016-07-19 10:06 ` Dennis Chen
2016-07-19 10:06 ` Dennis Chen
2016-07-19 11:01 ` AKASHI Takahiro
2016-07-19 11:01 ` AKASHI Takahiro
2016-07-20 3:39 ` Dennis Chen
2016-07-20 3:39 ` Dennis Chen
2016-07-20 4:22 ` AKASHI Takahiro
2016-07-20 4:22 ` AKASHI Takahiro
2016-07-20 4:36 ` Dennis Chen
2016-07-20 4:36 ` Dennis Chen
2016-07-21 0:57 ` AKASHI Takahiro
2016-07-21 0:57 ` AKASHI Takahiro
2016-07-22 13:55 ` James Morse
2016-07-22 13:55 ` James Morse
2016-07-25 5:27 ` AKASHI Takahiro
2016-07-25 5:27 ` AKASHI Takahiro
2016-08-04 6:21 ` AKASHI Takahiro
2016-08-04 6:21 ` AKASHI Takahiro
2016-08-09 16:22 ` James Morse [this message]
2016-08-09 16:22 ` James Morse
2016-07-12 5:05 ` [PATCH v22 3/8] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2016-07-12 5:05 ` AKASHI Takahiro
2016-07-13 9:32 ` Suzuki K Poulose
2016-07-13 9:32 ` Suzuki K Poulose
2016-07-13 16:00 ` AKASHI Takahiro
2016-07-13 16:00 ` AKASHI Takahiro
2016-07-12 5:05 ` [PATCH v22 4/8] arm64: kdump: add kdump support AKASHI Takahiro
2016-07-12 5:05 ` AKASHI Takahiro
2016-07-12 5:05 ` [PATCH v22 5/8] arm64: kdump: add VMCOREINFO's for user-space coredump tools AKASHI Takahiro
2016-07-12 5:05 ` AKASHI Takahiro
2016-07-12 5:05 ` [PATCH v22 6/8] arm64: kdump: enable kdump in the arm64 defconfig AKASHI Takahiro
2016-07-12 5:05 ` AKASHI Takahiro
2016-07-12 5:05 ` [PATCH v22 7/8] arm64: kdump: update a kernel doc AKASHI Takahiro
2016-07-12 5:05 ` AKASHI Takahiro
2016-07-12 5:05 ` [PATCH v22 8/8] Documentation: dt: chosen properties for arm64 kdump AKASHI Takahiro
2016-07-12 5:05 ` AKASHI Takahiro
2016-07-12 10:07 ` Mark Rutland
2016-07-12 10:07 ` Mark Rutland
2016-07-13 15:14 ` AKASHI Takahiro
2016-07-13 15:14 ` AKASHI Takahiro
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=57AA0361.6030505@arm.com \
--to=james.morse@arm.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.