On Fri, Jan 20, 2017 at 11:05:40AM +0900, AKASHI, Takahiro wrote:
I almost all the time test my kdump on fast model, but am also sure that it works on Hikey.
If you see any problems, I'm happy to help fix them with you.
Now have enabled kdump/kexec/crash tools on Hikey. So I can dump memory for panic (and hard/soft lock to trigger panic) and use crash to analyze panic context. Thanks a lot for AKASHI's great job and help!
I have two following questions:
- It takes long time to boot dump-capture kernel, I saw code just to use software method to trigger CPU reset; but looks like the time is a bit long, usually will take > 1 minute. So is this expected? sorry I have not investigate more detailed for the latency.
- If system is deadlock on the bus (e.g. AXI, or DDR port), so all CPUs will stall for this case. We can rely on watchdog to trigger SoC reset and preserve DDR contect. After watchdog reset system, what's the general method to boot dump-capture kernel?
Thanks, Leo Yan