Initial implementation of kdump for ARM
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 8 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 8 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/8] Initial implementation of kdump for ARM
These are some other hard code address in some boards.
For example, beagle board boot_params is 0x80000100.
I guest nokia's Nseris does not use atags for transfering params.
When I test my relocated kernel, it blocks at machinee initialization.
Maybe there is other address mapping issue. I will look it tomorrow.
Janboe
Quoted 33 lines · Mika Westerberg
Quoted 2 lines · ext Janboe Ye
I am trying this. But it seems need to do a lot work to make kdump to work on other omap3 board.
You need to have userspace tools (in this case kexec-tools) which load the crashkernel into the running kernel. I'm planning to send my kexec-tools patches to upstream after the kernel part is accepted (so that they can be in sync) but I can provide you the patches if needed.
For kernel part, I believe only thing that needs to be done is to make sure that
PHYS_OFFSETof the crashkernel is configured correctly.For example in my platform (and I guess all OMAP3s) physical memory starts at
0x80000000and this is thePHYS_OFFSETused by the primary kernel. I decided to load crashkernel at physical address0x84000000.So I boot the primary kernel with 'crashkernel=32M at
0x84000000'. Now memory for crashkernel is reserved.Only thing left is to load the craskernel itself which is done like (with patched kexec-tools):
# kexec -p /boot/zImage.crash --command-line="..."What kind of problems you are having?
Thanks,
MW_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel