From: "Randy.Dunlap" <rddunlap@osdl.org>
To: vgoyal@in.ibm.com
Cc: akpm@osdl.org, sharyathi@in.ibm.com, fastboot@lists.osdl.org,
linux-kernel@vger.kernel.org, ebiederm@xmission.com
Subject: Re: [Fastboot] Re: [PATCH] Kdump docs.
Date: Fri, 29 Apr 2005 07:26:00 -0700 [thread overview]
Message-ID: <20050429072600.67851fde.rddunlap@osdl.org> (raw)
In-Reply-To: <20050429050729.GB3636@in.ibm.com>
On Fri, 29 Apr 2005 10:37:29 +0530 Vivek Goyal wrote:
| Hi Randy,
|
| > + A) First kernel:
| > + a) Enable "kexec system call" feature (in Processor type and features).
| > + CONFIG_KEXEC=y
| > + b) This kernel's physical load address should be the default value of
| > + 0x100000 (0x100000, 1 MB) (in Processor type and features).
| > + CONFIG_PHYSICAL_START=0x100000
| > + c) Enable "sysfs file system support" (in Pseudo filesystems).
| > + CONFIG_SYSFS=y
| > + d) Boot into first kernel with the command line parameter "crashkernel=Y@X".
| > + Use appropriate values for X and Y. Y denotes how much memory to reserve
| > + for the second kernel, and X denotes at what physical address the reserved
| > + memory section starts. For example: "crashkernel=64M@16M".
| > +
| > + B) Second kernel:
| > + a) Enable "kernel crash dumps" feature (in Processor type and features).
| > + CONFIG_CRASH_DUMP=y
| > + b) Specify a suitable value for "Physical address where the kernel is
| > + loaded" (in Processor type and features). Typically this value
| > + should be same as X (See option b) above, e.g., 16 MB or 0x1000000.
|
| Should above line be as follows.
| "should be same as X (See option d) above."
Yes, thanks for catching that. Now how to update it....?
| This will make clear what is X and what should be the new value of
| CONFIG_PHYSICAL_START.
---
~Randy
next prev parent reply other threads:[~2005-04-29 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 3:30 [Fastboot] Re: Kdump Testing Vivek Goyal
2005-04-25 12:15 ` Nagesh Sharyathi
2005-04-25 23:09 ` Randy.Dunlap
2005-04-26 8:54 ` Vivek Goyal
2005-04-27 16:46 ` Randy.Dunlap
2005-04-27 19:23 ` Randy.Dunlap
2005-04-28 11:44 ` Vivek Goyal
2005-04-28 16:11 ` Randy.Dunlap
2005-04-28 19:08 ` Eric W. Biederman
2005-04-29 3:08 ` [PATCH] Kdump docs Randy.Dunlap
2005-04-29 5:07 ` Vivek Goyal
2005-04-29 14:26 ` Randy.Dunlap [this message]
2005-04-30 3:04 ` [PATCH] Kdump doc. fix option typo Randy.Dunlap
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=20050429072600.67851fde.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sharyathi@in.ibm.com \
--cc=vgoyal@in.ibm.com \
/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
all inboxes | Powered by JetHome®