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
