public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Fastboot mailing list <fastboot@lists.osdl.org>
Subject: Re: Current kexec status?
Date: Thu, 14 Jul 2005 11:23:02 +0530	[thread overview]
Message-ID: <20050714055301.GA4133@in.ibm.com> (raw)
In-Reply-To: <20050713123239.GT4561@charite.de>

On Wed, Jul 13, 2005 at 02:32:39PM +0200, Ralf Hildebrandt wrote:
> * Vivek Goyal <vgoyal@in.ibm.com>:
> 
> > Can you give more details like
> > - Which distro release you are running.
> 
> Debian unstable; since it has no kexec-tools, I built those from source.
> 
> > - Exactly what changes did you do to /etc/init.d/reboot and what steps
> > did you follow to load the kernel (command line options).
> 
> /etc/init.d/reboot:
> ===================
> 
> echo -n "Rebooting... "
> #reboot -d -f -i
> /usr/local/sbin/kexec -f --exec --debug
> 
> Loading the Kernel in /etc/init.d/umountfs, before umount'ing /boot:
> ====================================================================
> 
> echo -n "Loading kernel for kexec()..."
> /usr/local/sbin/kexec --load /vmlinuz
> echo "done."
> 

Please copy all the mails related to kexec and kdump problems to
fastboot mailing list also (fastboot@lists.osdl.org).

Instead of modifying reboot scripts, first can you try following simple 
steps from shell.

1. Load the kernel.
#kexec -l <kernel-image> --append=<boot time options>

2. Drop to run level 3 
# init 3

3. Exec into second kernel
# kexec -e


Thanks
Vivek

      parent reply	other threads:[~2005-07-14  5:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-13 10:48 Current kexec status? Ralf Hildebrandt
2005-07-13 12:22 ` Vivek Goyal
2005-07-13 12:32   ` Ralf Hildebrandt
2005-07-13 12:47     ` Ralf Hildebrandt
2005-07-14  5:53     ` 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=20050714055301.GA4133@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=Ralf.Hildebrandt@charite.de \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.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