o kernel
| Then try to loading kdump kernel
My system already has reserved region for crashkernel:
~# cat /proc/iomem | grep Crash
7f00-7fff : Crash kernel
And I use kexec next way:
kexec --type Image -p /Image --ramdisk=/ramdisk.cpio.gz
--dtb=dtb-arm64.dtb --append="
Hi Geoff,
On Mon, Jul 25, 2016 at 11:50 PM, Geoff Levand wrote:
> Hi Ruslan,
>
> On Mon, 2016-07-25 at 17:28 +0300, Ruslan Bilovol wrote:
>> And I use kexec next way:
>> kexec --type Image -p /Image --ramdisk=/ramdisk.cpio.gz
>> --dtb=dtb-arm64.dtb --append=
Hi,
On Tue, Jul 26, 2016 at 11:16 AM, AKASHI Takahiro
wrote:
> On Tue, Jul 26, 2016 at 04:36:01AM +0300, Ruslan Bilovol wrote:
>> Hi Geoff,
>>
>> On Mon, Jul 25, 2016 at 11:50 PM, Geoff Levand wrote:
>> > Hi Ruslan,
>> >
>> > On Mon, 2016-07-25 a
Hi,
On Tue, Jul 26, 2016 at 11:09 AM, AKASHI Takahiro
wrote:
> On Tue, Jul 26, 2016 at 04:56:51PM +0900, AKASHI Takahiro wrote:
>> This patch series adds kdump support on arm64.
>>
>> To load a crash-dump kernel to the systems, a series of patches to
>> kexec-tools, which have not yet been merged
Hi,
On 09/07/2016 07:29 AM, AKASHI Takahiro wrote:
v26-specific note: After a comment from Rob[0], an idea of adding
"linux,usable-memory-range" was dropped. Instead, an existing
"reserved-memory" node will be used to limit usable memory ranges
on crash dump kernel.
This
On 10/18/2016 09:26 AM, AKASHI Takahiro wrote:
Ruslan,
On Mon, Oct 17, 2016 at 06:41:01PM +0300, Ruslan Bilovol wrote:
Hi,
On 09/07/2016 07:29 AM, AKASHI Takahiro wrote:
v26-specific note: After a comment from Rob[0], an idea of adding
"linux,usable-memory-range" w
