From: Pavel Machek <pavel@ucw.cz>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
nigel@nigel.suspend2.net, "Rafael J. Wysocki" <rjw@sisk.pl>,
Jeremy Maitin-Shepard <jbms@cmu.edu>,
Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@linux-foundation.org>,
david@lang.hm, linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATH 0/1] Kexec jump - v2 - the first step to kexec based hibernation
Date: Tue, 31 Jul 2007 13:04:58 +0200 [thread overview]
Message-ID: <20070731110458.GA1777@elf.ucw.cz> (raw)
In-Reply-To: <1184483593.1898.98.camel@caritas-dev.intel.com>
Hi!
> 3. Boot kernel compiled for normal usage, the reserved crash kernel
> memory region must be added to kernel command line as following:
>
> crashkernel=<XX>M@<XX>M
>
> Where, <XX> should be replaced by the real memory size and
> position.
I used crashkernel=64M@64M .
> 4. Load kernel compiled for hibernating usage as a crashdump kernel
> with kexec, the same kernel as that of 3 can be used if
> CONFIG_RELOCATABLE=y is selected. The kernel command line option as
> following must be appended to kernel command line.
>
> kexec_jump_buf_pfn=`cat /sys/kernel/kexec_jump_buf_pfn`
>
> For example, the shell command line can be as follow:
>
> kexec -p /boot/vmlinux --args-linux --append="root=/dev/hdb signal
> kexec_jump_buf_pfn=`cat /sys/kernel/kexec_jump_buf_pfn`"
I think I followed the instructions closely. Now I'm trying to do
kexec -p /data/l/linux/vmlinux --args-linux --append="init=/bin/bash
kexec_jump_buf_pfn=`cat /sys/kernel/kexec_jump_buf_pfn`"
but it tells me:
Invalid memory segment 0x100000 - 0x7a0fff
(and nothing in dmesg)
If I try to load bzImage (corresponding to vmlinux I tried to use), I
get:
root@amd:~# kexec -p /data/l/linux/arch/i386/boot/bzImage --append="init=/bin/bash kexec_jump_buf_pfn=`cat /sys/kernel/kexec_jump_buf_pfn`"
Could not find a free area of memory of 9000 bytes...
locate_hole failed
root@amd:~#
What am I doing wrong?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-07-31 11:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 7:13 [PATH 0/1] Kexec jump - v2 - the first step to kexec based hibernation Huang, Ying
2007-07-15 9:08 ` Nigel Cunningham
2007-07-15 10:09 ` Rafael J. Wysocki
2007-07-19 1:04 ` Andrew Morton
2007-07-19 2:15 ` Nigel Cunningham
2007-07-19 3:30 ` david
2007-07-19 6:43 ` Huang, Ying
2007-07-19 9:13 ` Rafael J. Wysocki
2007-07-31 9:10 ` Pavel Machek
2007-07-31 9:25 ` Huang, Ying
2007-07-31 10:52 ` Eric W. Biederman
2007-07-31 11:12 ` Pavel Machek
2007-08-01 1:16 ` Huang, Ying
2007-07-31 11:14 ` Pavel Machek
2007-07-31 11:04 ` Pavel Machek [this message]
2007-08-01 1:34 ` Huang, Ying
2007-08-05 18:55 ` Pavel Machek
2007-08-06 2:31 ` Huang, Ying
2007-08-06 9:02 ` Pavel Machek
2007-08-06 13:22 ` Huang, Ying
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=20070731110458.GA1777@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=david@lang.hm \
--cc=ebiederm@xmission.com \
--cc=jbms@cmu.edu \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nigel@nigel.suspend2.net \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
--cc=ying.huang@intel.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