Using 'sys' command, we can view the panic message with general system information. If we run RISCV64-based vmcore, PANIC message is not properly displayed. The reason is that "Unable to handle kernel" is first printed in the kernel log when exception occurs in the RISC-V based Linux kernel. The corresponding kernel commit is 21733cb518471. Without the patch: crash> sys KERNEL: vmlinux [TAINTED] DUMPFILE: vmcore CPUS: 4 DATE: Thu Aug 22 16:13:08 KST 2024 UPTIME: 00:33:25 LOAD AVERAGE: 0.07, 0.07, 0.02 TASKS: 385 NODENAME: starfive RELEASE: 6.6.20+ VERSION: #13 SMP Mon Aug 19 12:58:52 KST 2024 MACHINE: riscv64 (unknown Mhz) MEMORY: 4 GB PANIC: "" With the patch: crash> sys KERNEL: vmlinux [TAINTED] DUMPFILE: vmcore CPUS: 4 DATE: Thu Aug 22 16:13:08 KST 2024 UPTIME: 00:33:25 LOAD AVERAGE: 0.07, 0.07, 0.02 TASKS: 385 NODENAME: starfive RELEASE: 6.6.20+ VERSION: #13 SMP Mon Aug 19 12:58:52 KST 2024 MACHINE: riscv64 (unknown Mhz) MEMORY: 4 GB PANIC: "Unable to handle kernel access to user memory without uaccess routines at virtual address 0000000000000000" Signed-off-by: Austin Kim <austindh.kim(a)gmail.com&gt; --- task.c | 1 + 1 file changed, 1 insertion(+) diff --git a/task.c b/task.c index d52ce0b..443f488 100644 --- a/task.c +++ b/task.c @@ -6330,6 +6330,7 @@ static const char* panic_msg[] = { "[Hardware Error]: ", "Bad mode in ", "Oops: ", + "Unable to handle kernel access ", }; #define ARRAY_SIZE(a) (sizeof (a) / sizeof ((a)[0])) -- 2.17.1