Thread (41 messages) flat view 41 messages, 8 authors, 2017-03-27
STALE3421d

Revision v33 of 7 in this series.

Revisions (7)
  1. v33 [diff vs current]
  2. v33 [diff vs current]
  3. v33 current
  4. v33 [diff vs current]
  5. v33 [diff vs current]
  6. v33 [diff vs current]
  7. v33 [diff vs current]

[PATCH v33 00/14] add kdump support

From: dwmw2@infradead.org (David Woodhouse)
Date: 2017-03-17 11:43:11
Also in: kexec

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>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help