From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Borislav Petkov <petkov@uni-muenster.de>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>,
linux-kernel@vger.kernel.org
Subject: Re: kexec?
Date: Tue, 10 May 2005 21:11:31 +0800 [thread overview]
Message-ID: <2cd57c9005051006117d0c343@mail.gmail.com> (raw)
In-Reply-To: <200505101215.48993.petkov@uni-muenster.de>
On 5/10/05, Borislav Petkov <petkov@uni-muenster.de> wrote:
> I've been doing some kexec tests (as described in Documentation/kdump.txt) too
> but can't get to load the image and get similar error messages. Let me know
> if you need more info about the hardware. The first_kernel was booted with
> "crashkernel=64M@16M" and the 16M value was configured into the second during
> kconfig in "Physical address where the kernel is loaded" as 0x1000000.
>
> [root@zmei]: kexec -p vmlinux --args-linux --append="root=/dev/hda1 maxcpus=1
> init 1"
kexec-tools-1.101 loads for me, but if cmdline is used, it hangs up
after "Starting new kernel"
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
next prev parent reply other threads:[~2005-05-10 13:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 20:20 kexec? Ralf Hildebrandt
2005-05-10 1:34 ` kexec? Randy.Dunlap
2005-05-10 7:00 ` kexec? Coywolf Qi Hunt
2005-05-10 10:15 ` kexec? Borislav Petkov
2005-05-10 13:11 ` Coywolf Qi Hunt [this message]
2005-05-11 6:04 ` kexec? Maneesh Soni
2005-05-11 11:51 ` kexec? Borislav Petkov
2005-05-11 14:39 ` kexec? Coywolf Qi Hunt
2005-05-12 6:41 ` kexec? Maneesh Soni
2005-05-16 22:11 ` kexec? Borislav Petkov
2005-05-17 10:02 ` kexec? Vivek Goyal
2005-05-18 7:58 ` kexec? Borislav Petkov
2005-05-20 10:52 ` kexec? Vivek Goyal
2005-05-21 8:20 ` kexec? Borislav Petkov
2005-05-23 6:42 ` kexec? Maneesh Soni
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=2cd57c9005051006117d0c343@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=Ralf.Hildebrandt@charite.de \
--cc=coywolf@lovecn.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkov@uni-muenster.de \
--cc=rddunlap@osdl.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