All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Mike Snitzer <snitzer@gmail.com>
Cc: Simon Horman <horms@verge.net.au>, kexec@lists.infradead.org
Subject: Re: kexec won't --load-panic a 2.6.22 relocatable kernel?
Date: Wed, 2 Apr 2008 13:26:57 -0400	[thread overview]
Message-ID: <20080402172657.GJ668@redhat.com> (raw)
In-Reply-To: <170fa0d20803240822j1bf02aeer7471651b6ec7e321@mail.gmail.com>

On Mon, Mar 24, 2008 at 11:22:59AM -0400, Mike Snitzer wrote:
> On Mon, Mar 24, 2008 at 10:18 AM, Mike Snitzer <snitzer@gmail.com> wrote:
> >
> > On Mon, Mar 24, 2008 at 4:29 AM, Simon Horman <horms@verge.net.au> wrote:
> >  >
> >  > On Fri, Mar 21, 2008 at 02:32:36PM +0900, Simon Horman wrote:
> >  >  > 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.
> >  >
> >  >  Sorry for being a bit slow, I have managed to reproduce the problem,
> >  >  which is that --args-linux can't be used if the image is a bzImage.
> >  >  Could you try with a vmlinux image instead?
> >
> >  Interesting, makes sense.
> >
> >  Sure enough RedHat's image is a "ELF 64-bit LSB shared object" and a
> >  vmlinux is "ELF 64-bit LSB executable".
> >
> >  I wonder how RedHat gets their kernel image to be an ELF image?
> 
> RedHat includes the following (which never made it upstream):
> http://lkml.org/lkml/2006/8/14/203
> 

Yep. Andrew Morton's one machine with lilo boot-loader did not
boot with ELF header for bzImage and we did not know what was
wrong. So above patch never made upstream.

Anyway, it was not a necessary patch though..

Thanks
Vivek


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2008-04-02 17:27 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
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 [this message]

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=20080402172657.GJ668@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=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.