From: janboe.ye@gmail.com (Janboe Ye)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Initial implementation of kdump for ARM
Date: Fri, 23 Apr 2010 12:26:26 +0800 [thread overview]
Message-ID: <20100423042626.GA2997@localhost.localdomain> (raw)
In-Reply-To: <20100423041106.GG3028@esdhcp04058.research.nokia.com>
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
On Fri, Apr 23, 2010 at 07:11:06AM +0300, Mika Westerberg wrote:
> On Fri, Apr 23, 2010 at 05:05:56AM +0200, ext Janboe Ye wrote:
> > 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_OFFSET of the crashkernel is configured correctly.
>
> For example in my platform (and I guess all OMAP3s) physical memory starts
> at 0x80000000 and this is the PHYS_OFFSET used by the primary kernel. I decided
> to load crashkernel at physical address 0x84000000.
>
> 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
next prev parent reply other threads:[~2010-04-23 4:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 8:50 [PATCH 0/8] Initial implementation of kdump for ARM Mika Westerberg
2010-04-20 8:50 ` [PATCH 1/8] arm: kdump: reserve memory for crashkernel Mika Westerberg
2010-04-20 8:50 ` [PATCH 2/8] arm: kdump: implement crash_setup_regs() Mika Westerberg
2010-04-20 8:50 ` [PATCH 3/8] arm: kdump: implement machine_crash_shutdown() Mika Westerberg
2010-04-20 8:50 ` [PATCH 4/8] arm: kdump: skip indirection page when crashing Mika Westerberg
2010-04-20 8:50 ` [PATCH 5/8] arm: kdump: implement copy_oldmem_page() Mika Westerberg
2010-04-20 8:50 ` [PATCH 6/8] arm: allow passing an ELF64 header to elf_check_arch() Mika Westerberg
2010-04-20 8:50 ` [PATCH 7/8] arm: kdump: add support for elfcorehdr= parameter Mika Westerberg
2010-04-20 8:50 ` [PATCH 8/8] arm: kdump: add CONFIG_CRASH_DUMP Kconfig option Mika Westerberg
2010-04-22 12:03 ` [PATCH 0/8] Initial implementation of kdump for ARM Mika Westerberg
2010-04-23 3:05 ` Janboe Ye
2010-04-23 4:11 ` Mika Westerberg
2010-04-23 4:26 ` Janboe Ye [this message]
2010-04-23 4:53 ` Mika Westerberg
2010-04-27 10:05 ` Mika Westerberg
2010-04-26 1:26 ` Joonyoung Shim
2010-04-26 9:16 ` Mika Westerberg
2010-05-03 8:28 ` Mika Westerberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100423042626.GA2997@localhost.localdomain \
--to=janboe.ye@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).