MIPS issue with crash utility

[rwiner]

Hi,
I'm Intel employee, having a MIPS Platform running Linux OS.
I enabled the kexec\kdump flow in Linux version we use and now I have vmcore memory dump, and now I'm getting into troubles....
I'm running the crash utility compiled with "target=MIPS" and getting the output:

crash: read error: kernel virtual address: xxxx30fc type: "possible"
WARNING: cannot read cpu_possible_map
crash: read error: kernel virtual address: xxxx30f4 type: "present"
WARNING: cannot read cpu_present_map
crash: read error: kernel virtual address: xxxx30f8 type: "online"
WARNING: cannot read cpu_online_map
crash: read error: kernel virtual address: xxxx30f0 type: "active"
WARNING: cannot read cpu_active_map
crash: read error: kernel virtual address:xxxx0a48 type: "shadow_timekeeper xtime_sec"
crash: read error: kernel virtual address: xxxxa444 type: "init_uts_ns"
crash: linux/vmlinux and vmcore do not match!

As you see the tool claims that the vmlinux doesn't match to the vmcore although the vmcore captured from the given vmlinux.
When I open the vmcore with gdb from our toolchain provided by MIPS, it's successfully opened and I see that the init_uts_ns is in offset xxxxa440 instead of xxxxa444 it looks for in the crash utility.

I thought that maybe the issue is we use a propriety toolchain provided by Codescape (the next link) and tried to replace the gdb packet in the Makefile - but then the tool wasn't compile, it fails in the gdb_merge step:
http://codescape-mips-sdk.imgtec.com/components/toolchain/2017.10-05/downloads.html

Can you help us to understand how to overcome this issue? is there any easy way to replace the gdb binary the tool uses?

we'll very appreciate your help.

[crash-utility]

Hi,
I'm Intel employee, having a MIPS Platform running Linux OS.

Unfortunately I'm a Red Hat employee, and I know pretty much nothing about MIPS.

The patches for the support of the 32-MIPS architecture were posted externally on
the crash-utility mailing list, and I accepted it, and all subsequent patches posted
there:

https://www.redhat.com/mailman/listinfo/crash-utility

You may be able to get some help by posting your query there.

What I can say, though, is that replacing the embedded gdb-7.6 version built
into the crash utility is a major task, and certainly not anything that can be
done by tinkering with the Makefile. So absolutely no, there is no easy way.

It would be interesting if you were to take the gdb-7.6.tar.gz package and
build it standalone, and then run "gdb vmlinux". Are you saying that the
symbol values shown by gdb-7.6 are off-by-4 from what you see when you
run "nm -Bn vmlinux"? Seems strange to me.

Anyway, sorry, I can be of much help.

[shengduiliang]

Hello,I got the same problem on MIPS platform running linux-5.4.May I ask you that if you have solved this problem?

[crash-utility]

Sorry no. As I mentioned above, I have no way to investigate issues on that architecture,
and nobody has brought it up on the mailing list.