All of lore.kernel.org
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Ruslan Bilovol <ruslan.bilovol@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Geoff Levand <geoff@infradead.org>,
	catalin.marinas@arm.com, will.deacon@arm.com,
	james.morse@arm.com, bauerman@linux.vnet.ibm.com,
	dyoung@redhat.com, kexec@lists.infradead.org,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v23 0/9] arm64: add kdump support
Date: Thu, 4 Aug 2016 14:20:49 +0900	[thread overview]
Message-ID: <20160804052048.GL7995@linaro.org> (raw)
In-Reply-To: <CAB=otbTODnOwFiLZT7bm1_MLyORQ1cx-gaeg7bm+bReaMRhYwg@mail.gmail.com>

Ruslan,

On Fri, Jul 29, 2016 at 07:26:03PM +0300, Ruslan Bilovol wrote:
> Hi,
> 
> On Tue, Jul 26, 2016 at 11:09 AM, AKASHI Takahiro
> <takahiro.akashi@linaro.org> 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 upstream, are needed.
> >> Please pick Geoff's kexec patches [1] and my kdump patches [2].
> >>
> >> To examine vmcore (/proc/vmcore) on a crash-dump kernel, you can use
> >>   - crash utility (coming v7.1.6 or later) [3]
> >>     (Necessary patches have already been queued in the master.)
> >>
> >> [1]  http://lists.infradead.org/pipermail/kexec/2016-July/016532.html
> >> [2]  TBD
> >
> > See my kexec-tools patches in:
> > http://lists.infradead.org/pipermail/kexec/2016-July/016642.html
> 
> I tired this patch series with mentioned Geoff's kexec patches and
> your kdump patches, but unfortunately it doesn't work for me.
> 
> While I can successfully load and kexec the kernel ('kexec --load' +
> 'kexec -e'), same combination of kernel+ramdisk+dtb doesn't boot
> if I do kdump combination ('kexec -p' + sysrq crash), there is no
> any output after sysrq crash trace.
> Unfortunately I don't have any debugger here for deep investigation
> of this issue.

- Can you try to do kdump without ramdisk?
- Show me
    - kernel boot log, particularly, "Virtual kernel memory layout:"
    - cat /proc/iomem
    - log from kexec command

> Also for some reason in case of 'load and kexec the kernel' it
> takes 1-2 minutes to start booting after I do kexec -e, need to
> investigate it further.
> 
> Which hardware do you use for validating your patches?

I always test my patches on ARM fast model.

Thanks,
-Takahiro AKASHI

> Also, could you please share exact commands you use for
> kdump validation?
>
> Best regaerds,
> Ruslan

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v23 0/9] arm64: add kdump support
Date: Thu, 4 Aug 2016 14:20:49 +0900	[thread overview]
Message-ID: <20160804052048.GL7995@linaro.org> (raw)
In-Reply-To: <CAB=otbTODnOwFiLZT7bm1_MLyORQ1cx-gaeg7bm+bReaMRhYwg@mail.gmail.com>

Ruslan,

On Fri, Jul 29, 2016 at 07:26:03PM +0300, Ruslan Bilovol wrote:
> Hi,
> 
> On Tue, Jul 26, 2016 at 11:09 AM, AKASHI Takahiro
> <takahiro.akashi@linaro.org> 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 upstream, are needed.
> >> Please pick Geoff's kexec patches [1] and my kdump patches [2].
> >>
> >> To examine vmcore (/proc/vmcore) on a crash-dump kernel, you can use
> >>   - crash utility (coming v7.1.6 or later) [3]
> >>     (Necessary patches have already been queued in the master.)
> >>
> >> [1]  http://lists.infradead.org/pipermail/kexec/2016-July/016532.html
> >> [2]  TBD
> >
> > See my kexec-tools patches in:
> > http://lists.infradead.org/pipermail/kexec/2016-July/016642.html
> 
> I tired this patch series with mentioned Geoff's kexec patches and
> your kdump patches, but unfortunately it doesn't work for me.
> 
> While I can successfully load and kexec the kernel ('kexec --load' +
> 'kexec -e'), same combination of kernel+ramdisk+dtb doesn't boot
> if I do kdump combination ('kexec -p' + sysrq crash), there is no
> any output after sysrq crash trace.
> Unfortunately I don't have any debugger here for deep investigation
> of this issue.

- Can you try to do kdump without ramdisk?
- Show me
    - kernel boot log, particularly, "Virtual kernel memory layout:"
    - cat /proc/iomem
    - log from kexec command

> Also for some reason in case of 'load and kexec the kernel' it
> takes 1-2 minutes to start booting after I do kexec -e, need to
> investigate it further.
> 
> Which hardware do you use for validating your patches?

I always test my patches on ARM fast model.

Thanks,
-Takahiro AKASHI

> Also, could you please share exact commands you use for
> kdump validation?
>
> Best regaerds,
> Ruslan

  parent reply	other threads:[~2016-08-04  5:15 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26  7:56 [PATCH v23 0/9] arm64: add kdump support AKASHI Takahiro
2016-07-26  7:56 ` AKASHI Takahiro
2016-07-26  7:56 ` [PATCH v23 1/9] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2016-07-26  7:56   ` AKASHI Takahiro
2016-07-26  7:56 ` [PATCH v23 2/9] memblock: add memblock_cap_memory_range() AKASHI Takahiro
2016-07-26  7:56   ` AKASHI Takahiro
2016-07-26  7:56 ` [PATCH v23 3/9] arm64: limit memory regions based on DT property, usable-memory-range AKASHI Takahiro
2016-07-26  7:56   ` AKASHI Takahiro
2016-07-26  7:56 ` [PATCH v23 4/9] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2016-07-26  7:56   ` AKASHI Takahiro
2016-07-26  7:56 ` [PATCH v23 5/9] arm64: kdump: add kdump support AKASHI Takahiro
2016-07-26  7:56   ` AKASHI Takahiro
2016-07-26  7:56 ` [PATCH v23 6/9] arm64: kdump: add VMCOREINFO's for user-space coredump tools AKASHI Takahiro
2016-07-26  7:56   ` AKASHI Takahiro
2016-07-26  7:56 ` [PATCH v23 7/9] arm64: kdump: enable kdump in the arm64 defconfig AKASHI Takahiro
2016-07-26  7:56   ` AKASHI Takahiro
2016-07-26  7:56 ` [PATCH v23 8/9] arm64: kdump: update a kernel doc AKASHI Takahiro
2016-07-26  7:56   ` AKASHI Takahiro
2016-07-26  8:02 ` [PATCH v23 9/9] Documentation: dt: chosen properties for arm64 kdump AKASHI Takahiro
2016-07-26  8:02   ` AKASHI Takahiro
2016-07-26  8:02   ` AKASHI Takahiro
2016-07-27 15:09   ` Rob Herring
2016-07-27 15:09     ` Rob Herring
2016-07-27 15:09     ` Rob Herring
     [not found]     ` <20160728075511.GA7995@linaro.org>
2016-08-04  5:10       ` AKASHI Takahiro
2016-08-04  5:10         ` AKASHI Takahiro
2016-08-04  5:10         ` AKASHI Takahiro
2016-07-26  8:09 ` [PATCH v23 0/9] arm64: add kdump support AKASHI Takahiro
2016-07-26  8:09   ` AKASHI Takahiro
2016-07-29 16:26   ` Ruslan Bilovol
2016-07-29 16:26     ` Ruslan Bilovol
2016-07-29 17:08     ` Geoff Levand
2016-07-29 17:08       ` Geoff Levand
2016-07-29 17:17       ` Pratyush Anand
2016-07-29 17:17         ` Pratyush Anand
2016-07-29 17:13     ` Pratyush Anand
2016-07-29 17:13       ` Pratyush Anand
2016-08-01  4:37       ` AKASHI Takahiro
2016-08-01  4:37         ` AKASHI Takahiro
2016-08-01  6:21         ` Pratyush Anand
2016-08-01  6:21           ` Pratyush Anand
2016-08-01  6:46           ` AKASHI Takahiro
2016-08-01  6:46             ` AKASHI Takahiro
2016-08-04  5:20     ` AKASHI Takahiro [this message]
2016-08-04  5:20       ` 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=20160804052048.GL7995@linaro.org \
    --to=takahiro.akashi@linaro.org \
    --cc=bauerman@linux.vnet.ibm.com \
    --cc=catalin.marinas@arm.com \
    --cc=dyoung@redhat.com \
    --cc=geoff@infradead.org \
    --cc=james.morse@arm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=ruslan.bilovol@gmail.com \
    --cc=will.deacon@arm.com \
    /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.