[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <551CD58E.60807@linaro.org>
Date: Thu, 02 Apr 2015 14:37:18 +0900
From: AKASHI Takahiro <takahiro.akashi@...aro.org>
To: Pratyush Anand <panand@...hat.com>, catalin.marinas@....com,
will.deacon@....com, vgoyal@...hat.com, hbabus@...ibm.com
CC: linaro-kernel@...ts.linaro.org, geoff@...radead.org,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
broonie@...nel.org, david.griego@...aro.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/5] arm64: add kdump support
Pratyush,
On 04/02/2015 01:58 PM, Pratyush Anand wrote:
>
>
> On Thursday 02 April 2015 04:57 AM, AKASHI Takahiro wrote:
>> Please try my latest kexec-tools in my linaro repo (branch name is
>> kdump/v0.11)
>> and let me know the result.
>
> Thanks a lot.. Just fetched your repo and found v.0.11.
>
> With this crash kernel loaded successfully, if I do not use initrd.
>
> With following I still see Overlapping memory segments
>
> kexec -p /home/panand/work/kernel/bsa2_kdump/vmlinux --initrd=/boot/initramfs-3.19.0.bz1198945+.img --append="$( cat
> /proc/cmdline ) maxcpus=1 mem=64M reset_devices"
How big is your initrd?
If it is good small, please tell me segments info, or messages from add_segment_phys_virt()
for all the segments.
FYI,
my latest kexec-tools, ie. v0.11, automatically appends "mem=".
Thanks,
-Takahiro AKASHI
> ~Pratyush
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists