[Crash-utility] [Question] crash-8.0.5 invalid to parse the assembly code by dis cmd for ARM64 crash dump
Dear sirs,
I found a bug for crash-8.0.5 that I failed to parse the assembly code by dis cmd for
ARM64 crash dump:
$ crash vmlinux dump.202403061305 -d 1
KERNEL: vmlinux [TAINTED]
DUMPFILE: dump.202403061305 [PARTIAL DUMP]
CPUS: 4crash: get_cpus_online: online: 4
DATE: Wed Mar 6 21:04:30 CST 2024
UPTIME: 2135039823346 days, 00:18:07
LOAD AVERAGE: 0.32, 0.40, 0.17
TASKS: 93
NODENAME: benshushu
RELEASE: 5.15.0+
VERSION: #1 SMP Tue Mar 5 16:54:41 CST 2024
MACHINE: aarch64 (unknown Mhz)
MEMORY: 1 GB
PANIC: "Unable to handle kernel paging request at virtual address
ffff800809102430"
PID: 494
COMMAND: "bash"
TASK: ffff000007d11a80 [THREAD_INFO: ffff000007d11a80]
CPU: 0
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 494 TASK: ffff000007d11a80 CPU: 0 COMMAND: "bash"
0: ffff80001022400c (crash_kexec)
#0 [ffff000007ce34d0] crash_kexec at ffff800010224008
#1 [ffff000007ce3570] die at ffff800010030038
#2 [ffff000007ce35e0] die_kernel_fault at ffff80001005d8e8
#3 [ffff000007ce3610] __do_kernel_fault at ffff80001005dbf4
#4 [ffff000007ce3650] do_bad_area at ffff80001005de14
#5 [ffff000007ce36b0] do_translation_fault at ffff800011172f84
#6 [ffff000007ce3700] do_mem_abort at ffff80001005e220
#7 [ffff000007ce3760] el1_abort at ffff800011162210
#8 [ffff000007ce3790] el1h_64_sync_handler at ffff80001116243c
#9 [ffff000007ce38f0] el1h_64_sync at ffff8000100111dc
......
crash> dis do_mem_abort
crash> dis -x ffff80001005e220 -r 8
0xffff80001005e184 <do_mem_abort>:
crash> dis do_mem_abort
0xffff80001005e184 <do_mem_abort>:
crash> dis do_translation_fault
0xffff800011172ed4 <do_translation_fault>:
There is no problem for crash-8.0.4:
crash> dis do_mem_abort
0xffff80001005e184 <do_mem_abort>: mov x9, x30
0xffff80001005e188 <do_mem_abort+4>: nop
0xffff80001005e18c <do_mem_abort+8>: stp x29, x30, [sp, #-96]!
0xffff80001005e190 <do_mem_abort+12>: mov x29, sp
......
There must be some change corrupted the ARM64 dis function. Please help look at the
issue.
Thanks