From: Simon Horman <horms@verge.net.au>
To: Mike Snitzer <snitzer@gmail.com>
Cc: kexec@lists.infradead.org
Subject: Re: kexec won't --load-panic a 2.6.22 relocatable kernel?
Date: Fri, 21 Mar 2008 14:32:36 +0900 [thread overview]
Message-ID: <20080321053236.GA29330@verge.net.au> (raw)
In-Reply-To: <170fa0d20803182305x3b16f7bt198d767a53553c8e@mail.gmail.com>
On Wed, Mar 19, 2008 at 02:05:46AM -0400, Mike Snitzer wrote:
> I'm building a x86_64 2.6.22 kernel with the following options set:
>
> CONFIG_KEXEC=y
> CONFIG_CRASH_DUMP=y
> CONFIG_RELOCATABLE=y
> CONFIG_PHYSICAL_START=0x200000
>
> If I try to load the kernel with the following I get:
>
> ./kexec --args-linux -p '--command-line=ro root=LABEL=/1 rhgb quiet
> irqpoll maxcpus=1' --initrd=/boot/initrd-2.6.22.19.img
> /boot/vmlinuz-2.6.22.19
>
> ./kexec: unrecognized option `--args-linux'
> kexec-tools-testing 20080318-rc released 18th March 2008
> Usage: kexec [OPTION]... [kernel]
> ...
> Cannot load /boot/vmlinuz-2.6.22.19
Hi Mike,
that looks a lot like a problem with kexec-tools parsing command line
arguments to me. However I'm not having much luck reproducing it here.
I'll poke a bit more.
Did you get kexec-tools-testing 20080318-rc as a tarball from
kernel.org? I just want to make sure we are looking at the same code.
--
Horms
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-03-21 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 6:05 kexec won't --load-panic a 2.6.22 relocatable kernel? Mike Snitzer
2008-03-21 5:32 ` Simon Horman [this message]
2008-03-21 23:54 ` Mike Snitzer
2008-03-24 8:29 ` Simon Horman
2008-03-24 14:18 ` Mike Snitzer
2008-03-24 15:22 ` Mike Snitzer
2008-04-02 17:26 ` Vivek Goyal
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=20080321053236.GA29330@verge.net.au \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=snitzer@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.