From: dwmw2@infradead.org (David Woodhouse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v33 00/14] add kdump support
Date: Fri, 17 Mar 2017 11:43:11 +0000 [thread overview]
Message-ID: <1489750991.17202.40.camel@infradead.org> (raw)
In-Reply-To: <20170315095656.24992-1-takahiro.akashi@linaro.org>
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.
Is this one going to be be my fault too?
[???38.947305] SMP: stopping secondary CPUs
[???38.951291] Starting crashdump kernel...
[???38.955207] ------------[ cut here ]------------
[???38.959818] WARNING: CPU: 0 PID: 312 at arch/arm64/kernel/machine_kexec.c:169 machine_kexec+0x220/0x298
That's the cpus_are_stuck_in_kernel() || num_online_cpus() one. Again,
v32 applied to a 4.9 kernel. With the stray __init removed this time ;)
Taking secondary CPUs down for a normal kexec does work via PSCI.
I'll see if I can enable enough hardware support to let me test a newer
kernel...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4938 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170317/d019a5cd/attachment.bin>
next prev parent reply other threads:[~2017-03-17 11:43 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
2017-03-16 10:29 ` David Woodhouse
2017-03-17 11:43 ` David Woodhouse [this message]
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=1489750991.17202.40.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).