Hi James,

I will be happy to ginea pig your work regarding kexec/kdump, as soon as you got something testable let me know.

I guess the first validation step will be kexec so we can boot the 2nd kernel and have kcore at hand.

Good luck with this new challenge :)

On the side of this, do you think getting a guest dump from qemu is worth a trail to investigate. (I am iliterate here dunno if this is doable or not)

Cheers Phi

On Tue, Jun 4, 2013 at 1:05 PM, James King james.king@linaro.org wrote:

Hi Phi,

As part of my Linaro assignee role, I am working on implementation of kexec/crashdump for armv8. Only recently started so no significant progress yet, but will sync up over what you want to do and how I can help.

Cheers, James

On 3 June 2013 08:16, phi debian phi.debian@gmail.com wrote:

...

Hi All,

I'd like to investigate kernel crashdump debuging for armv8.

For this I need a crashdump, basically I would be happy with a vmlinux with debuginfos (-g compiled) either as 1 a.out or a splitted a.out ( ala suse) a save state of some sort (a crash notes records) and a vmcore that could be a simple raw file, a core file, an elf file, a kdump format.

I am not to picky on the crashdump format for the time being.

What would be my best bet?

• Does someone as a crashdump at hand, I would simply download the

vmlinux/vmcore/crashnotes.

• Make it myself as a qemu guest crash.

If qemu is able to produce a guest core dump, I could build a kernel -g then trig a guest dump (if someone did this any receipe would be appreciated :) )

• Make it myself with a manual kdump (ideal) or kexec phases.

I would then have to install linaro, get the source, build the -g vmlinux, then try some kexec sequence and catch the kcore, or better if available I could do a makedumpfile to get a kdump. Again if one did this, any help appreciated.

Cheers, Phi

---

linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev