On Fri, Apr 28, 2017 at 09:05:07AM -0400, Dave Anderson wrote:
>
> > Hello,
> >
> > Is there arm64 big endian support in crash utility? And when it appears?
> >
> > Best regards,
> > Denys
> >
>
> What happens when you rebuild the crash package from scratch on a
> big-endian arm64 host?
I gave it a spin with my kdump patch on ARM's fast model.
* Crash utility can compile natively.
* Kdump works, of course, and crash seems to cope with vmcore correctly
as follows:
===8<===
sys
KERNEL: ./vmlinux.0511
DUMPFILE: vmcore.0511
CPUS: 8
DATE: Thu May 11 00:29:29 2017
UPTIME: 00:04:23
LOAD AVERAGE: 0.10, 0.07, 0.02
TASKS: 109
NODENAME: 192.168.10.11
RELEASE: 4.11.0-rc3-00041-g9cb987c300d2
VERSION: #6 SMP PREEMPT Thu May 11 09:16:54 JST 2017
MACHINE: aarch64_be (unknown Mhz)
MEMORY: 512 MB
PANIC: "sysrq: SysRq : Trigger a crash"
bt
PID: 1 TASK: ffff80000d900000 CPU: 2 COMMAND: "bash"
#0 [ffff80000d8f7a30] crash_kexec at ffff000008143e1c
#1 [ffff80000d8f7a60] die at ffff00000808884c
#2 [ffff80000d8f7aa0] __do_kernel_fault at ffff00000809b5a8
#3 [ffff80000d8f7ad0] do_page_fault at ffff000008098628
#4 [ffff80000d8f7b40] do_translation_fault at ffff000008098718
#5 [ffff80000d8f7b50] do_mem_abort at ffff000008080aa4
#6 [ffff80000d8f7d30] el1_ia at ffff000008082600
PC: ffff00000850f7d8 [sysrq_handle_crash+32]
LR: ffff00000850f7c4 [sysrq_handle_crash+12]
SP: ffff80000d8f7d30 PSTATE: 60000145
X29: ffff80000d8f7d30 X28: ffff80000d900000 X27: ffff000008932000
X26: 0000000000000040 X25: 0000000000000123 X24: 0000000000000015
X23: 0000000000000000 X22: 0000000000000009 X21: ffff000008ebe810
X20: 0000000000000063 X19: ffff000008e31000 X18: 0000000000000010
X17: 0000ffffac312290 X16: ffff0000081fd378 X15: ffff000088f2c057
X14: 0000000000000006 X13: ffff000008f2c065 X12: ffff000008e31dc0
X11: ffff000008e31000 X10: 0000000005f5e0ff X9: ffff80000d8f7a40
X8: 79735271203a2054 X7: ffff000008530ed0 X6: 00000000000000f7
X5: 0000000000000000 X4: 0000000000000000 X3: ffffffffffffffff
X2: ffff000008e31df0 X1: 0000000000000000 X0: 0000000000000001
#7 [ffff80000d8f7d40] __handle_sysrq at ffff00000850fe60
#8 [ffff80000d8f7d80] write_sysrq_trigger at ffff0000085102e4
#9 [ffff80000d8f7da0] proc_reg_write at ffff000008262478
#10 [ffff80000d8f7dc0] __vfs_write at ffff0000081fac20
#11 [ffff80000d8f7e40] vfs_write at ffff0000081fbf34
#12 [ffff80000d8f7e80] sys_write at ffff0000081fd3b8
#13 [ffff80000d8f7ed0] el0_svc_naked at ffff000008082f2c
PC: 0000000000000001 LR: 0000ffffac366998 SP: 0000000020000000
X29: 0000ffffde54d1b0 X28: 0000ffffac315450 X27: 0000ffffde54d1b0
X26: 0000000013fc6850 X25: 0000000000000000 X24: 00000000004e3000
X23: 00000000004e6000 X22: 00000000004c5460 X21: 0000000000000002
X20: 0000000000000002 X19: 0000ffffac3ee488 X18: 0000000013fc55e0
X17: 0000000000000002 X16: 0000000000000000 X15: 0000ffffac312290
X14: 0000000000000000 X13: 0000000000000000 X12: 0000000000000000
X11: 0000000000000000 X10: 0000000000000000 X9: 0000000000000020
X8: 0000000000000001 X7: ffffffc8ffffff80 X6: 0000000000000040
X5: 0000000000000063 X4: 0000000000000063 X3: 0000000000000001
X2: 00000000fbad2a84 X1: 0000000000000000 X0: 0000000000000002
ORIG_X0: 0000000000000000 SYSCALLNO: 0 PSTATE: 00000040
===>8===
-Takahiro AKASHI
> Dave
>
> --
> Crash-utility mailing list
> Crash-utility@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/crash-utility
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
