From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mark.rutland@arm.com, 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@lists.infradead.org
Subject: Re: [PATCH v33 00/14] add kdump support
Date: Thu, 16 Mar 2017 09:23:48 +0900 [thread overview]
Message-ID: <20170316002347.GA11935@linaro.org> (raw)
In-Reply-To: <1489578078.4195.113.camel@infradead.org>
On Wed, Mar 15, 2017 at 11:41:18AM +0000, David Woodhouse wrote:
> On Wed, 2017-03-15 at 18:56 +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[1] are also needed. Please use the latest one, v6 [2].
> > For your convinience, you can pick them up from:
> > https://git.linaro.org/people/takahiro.akashi/linux-aarch64.git arm64/kdump
> > https://git.linaro.org/people/takahiro.akashi/kexec-tools.git arm64/kdump
> >
> > To examine vmcore (/proc/vmcore) on a crash-dump kernel, you can use
> > - crash utility (v7.1.8 or later) [3]
> >
> > I tested this patchset on fast model and hikey.
>
> Please build with CONFIG_DEBUG_SECTION_MISMATCH=y.
>
> It might be because I'm using your v32 patchset, hacked late at night
> to apply to a 4.9 kernel, but I see this:
>
> WARNING: vmlinux.o(.text+0x10240): Section mismatch in reference from the function arch_kexec_protect_crashkres() to the function .init.text:create_pgd_mapping()
> The function arch_kexec_protect_crashkres() references
> the function __init create_pgd_mapping().
> This is often because arch_kexec_protect_crashkres lacks a __init
> annotation or the annotation of create_pgd_mapping is wrong.
>
> WARNING: vmlinux.o(.text+0x102b0): Section mismatch in reference from the function arch_kexec_unprotect_crashkres() to the function .init.text:create_pgd_mapping()
> The function arch_kexec_unprotect_crashkres() references
> the function __init create_pgd_mapping().
> This is often because arch_kexec_unprotect_crashkres lacks a __init
> annotation or the annotation of create_pgd_mapping is wrong.
I double-checked but saw no warnings like these neither for v32 nor v33.
I'm afraid that you might have done something wrong in backporting,
particularly patch#5.
Thanks,
-Takahiro AKASHI
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2017-03-16 0:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 9:56 [PATCH v33 00/14] add kdump support AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 01/14] memblock: add memblock_clear_nomap() AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 02/14] memblock: add memblock_cap_memory_range() AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 03/14] arm64: limit memory regions based on DT property, usable-memory-range AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 04/14] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2017-03-17 10:46 ` David Woodhouse
2017-03-17 11:31 ` AKASHI Takahiro
2017-03-17 11:32 ` David Woodhouse
2017-03-15 9:59 ` [PATCH v33 05/14] arm64: mm: allow for unmapping part of kernel mapping AKASHI Takahiro
2017-03-21 10:35 ` James Morse
2017-03-23 11:43 ` AKASHI Takahiro
2017-03-24 10:57 ` Ard Biesheuvel
2017-03-27 13:49 ` AKASHI Takahiro
2017-03-21 11:16 ` Ard Biesheuvel
2017-03-23 10:56 ` AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 06/14] arm64: kdump: protect crash dump kernel memory AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 07/14] arm64: hibernate: preserve kdump image around hibernation AKASHI Takahiro
2017-03-21 18:25 ` James Morse
2017-03-23 11:29 ` AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 08/14] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 09/14] arm64: kdump: add VMCOREINFO's for user-space tools AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 10/14] arm64: kdump: provide /proc/vmcore file AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 11/14] arm64: kdump: enable kdump in defconfig AKASHI Takahiro
2017-03-15 9:59 ` [PATCH v33 12/14] Documentation: kdump: describe arm64 port AKASHI Takahiro
2017-03-15 10:00 ` [PATCH v33 13/14] Documentation: dt: chosen properties for arm64 kdump AKASHI Takahiro
2017-03-15 10:01 ` [PATCH v33 14/14] efi/libstub/arm*: Set default address and size cells values for an empty dtb AKASHI Takahiro
2017-03-15 11:41 ` [PATCH v33 00/14] add kdump support David Woodhouse
2017-03-16 0:23 ` AKASHI Takahiro [this message]
2017-03-16 10:29 ` David Woodhouse
2017-03-17 11:43 ` David Woodhouse
2017-03-17 14:02 ` David Woodhouse
2017-03-17 15:04 ` Mark Rutland
2017-03-17 15:33 ` Mark Rutland
2017-03-17 15:47 ` David Woodhouse
2017-03-17 16:24 ` Mark Rutland
2017-03-17 16:59 ` Marc Zyngier
2017-03-17 17:10 ` Marc Zyngier
2017-03-17 20:03 ` David Woodhouse
2017-03-21 7:34 ` AKASHI Takahiro
2017-03-21 9:42 ` David Woodhouse
2017-03-20 12:42 ` Pratyush Anand
2017-03-22 16:55 ` Goel, Sameer
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=20170316002347.GA11935@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=bauerman@linux.vnet.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=dwmw2@infradead.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox