How to see extra hardware dump in vmcore

[Tirtsah]

Hi,
I'm enabling core dump flow on my Linux, using Linux kexec mechanism. This flow ends with vmcore elf image reflecting the full memory situation at the crash moment. The vmcore driver in kernel that outputs the vmcore elf image has vmcore_add_device_dump API that's used for pushing some extra hardware memory sections into the ELF.

However, After vmcore file is generated, I want to see this data, but don't know how to do that. I'm using crash-utility for the core analysis, so I wonder - maybe there is an option to see also this extra data using crash-utility?

[crash-utility]

Can you post your question to the [email protected] mailing list? There was a discussion about CONFIG_PROC_VMCORE_DEVICE_DUMP on the list a while back, where the author of the kernel patch said the he was going to post a crash utility patch to dump the data. But I can't find the thread. The data is contained within an ELF note, and you may be able to see a raw dump of the note's contents using the "help -D" option -- but only if your vmcore is an ELF vmcore. If the vmcore has been transformed into a compressed kdump dumpfile via the makedumpfile command, then the data will not be dumped with that option. As I recall, the author posted a shell script that dug the data out of a compressed kdump. Anyway, put CONFIG_PROC_VMCORE_DEVICE_DUMP in the subject line of the crash-utility post, and maybe it will get the author's attention. Thanks, Dave

…

----- Original Message -----

Hi, I'm enabling core dump flow on my Linux, using Linux kexec mechanism. This flow ends with vmcore elf image reflecting the full memory situation at the crash moment. The vmcore driver in kernel that outputs the vmcore elf image has vmcore_add_device_dump API that's used for pushing some extra hardware memory sections into the ELF. However, After vmcore file is generated, I want to see this data, but don't know how to do that. I'm using crash-utility for the core analysis, so I wonder - maybe there is an option to see also this extra data using crash-utility? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #32