All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: hbabu@us.ibm.com, kexec@lists.infradead.org,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: kexec refuses to boot latest -mm
Date: Fri, 28 Dec 2007 09:27:39 -0500	[thread overview]
Message-ID: <20071228142739.GA4560@redhat.com> (raw)
In-Reply-To: <20071228124532.GB32643@linux.vnet.ibm.com>

On Fri, Dec 28, 2007 at 06:15:32PM +0530, Dhaval Giani wrote:
> Hi Vivek,
> 
> I can't seem to get the latest -mm (2.6.24-rc6-mm1) to boot with
> kexec. It just gets stuck at "Starting new kernel".
> 
> It does boot normally when booted as the first kernel.
> 
> Any hints debugging? (x86 architecture)

I generally try few things.

- Specify earlyprintk= parameter for second kernel and see if control
  is reaching to second kernel.

- Otherwise specify --console-serial parameter on "kexec -l" commandline
  and it should display a message "I am in purgatory" on serial console.
  This will just mean that control has reached at least till purgatory.

- If that also does not work, then most likely first kernel itself got
  stuck somewhere and we need to put some printks in first kernel
  to find out what's wrong.

Thanks
Vivek

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

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: hbabu@us.ibm.com, lkml <linux-kernel@vger.kernel.org>,
	kexec@lists.infradead.org
Subject: Re: kexec refuses to boot latest -mm
Date: Fri, 28 Dec 2007 09:27:39 -0500	[thread overview]
Message-ID: <20071228142739.GA4560@redhat.com> (raw)
In-Reply-To: <20071228124532.GB32643@linux.vnet.ibm.com>

On Fri, Dec 28, 2007 at 06:15:32PM +0530, Dhaval Giani wrote:
> Hi Vivek,
> 
> I can't seem to get the latest -mm (2.6.24-rc6-mm1) to boot with
> kexec. It just gets stuck at "Starting new kernel".
> 
> It does boot normally when booted as the first kernel.
> 
> Any hints debugging? (x86 architecture)

I generally try few things.

- Specify earlyprintk= parameter for second kernel and see if control
  is reaching to second kernel.

- Otherwise specify --console-serial parameter on "kexec -l" commandline
  and it should display a message "I am in purgatory" on serial console.
  This will just mean that control has reached at least till purgatory.

- If that also does not work, then most likely first kernel itself got
  stuck somewhere and we need to put some printks in first kernel
  to find out what's wrong.

Thanks
Vivek

  reply	other threads:[~2007-12-28 14:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 12:45 kexec refuses to boot latest -mm Dhaval Giani
2007-12-28 12:45 ` Dhaval Giani
2007-12-28 14:27 ` Vivek Goyal [this message]
2007-12-28 14:27   ` Vivek Goyal
2007-12-29  5:41   ` Dhaval Giani
2007-12-29  5:41     ` Dhaval Giani
2007-12-31 15:06     ` Vivek Goyal
2007-12-31 15:06       ` Vivek Goyal
2007-12-31 20:22       ` Dhaval Giani
2007-12-31 20:22         ` Dhaval Giani
2007-12-31 15:08     ` Vivek Goyal
2007-12-31 15:08       ` Vivek Goyal
2008-01-03 19:52       ` Dhaval Giani
2008-01-03 19:52         ` Dhaval Giani
2008-01-03 21:42         ` Rafael J. Wysocki
2008-01-03 21:42           ` Rafael J. Wysocki
2008-01-04 12:28           ` Dhaval Giani
2008-01-04 12:28             ` Dhaval Giani
2008-01-04 15:54             ` Dhaval Giani
2008-01-04 15:54               ` Dhaval Giani
2008-01-06  2:17               ` Andrew Morton
2008-01-06  2:17                 ` Andrew Morton
2008-01-06 13:37               ` Ingo Molnar
2008-01-06 13:37                 ` Ingo Molnar
2008-01-07  9:18                 ` Dhaval Giani
2008-01-07  9:18                   ` Dhaval Giani
2008-01-07 10:02                   ` Dhaval Giani
2008-01-07 10:02                     ` Dhaval Giani
2008-01-04 17:11             ` Rafael J. Wysocki
2008-01-04 17:11               ` Rafael J. Wysocki
2007-12-31 16:35     ` Vivek Goyal
2007-12-31 16:35       ` Vivek Goyal
2007-12-28 19:54 ` Neil Horman
2007-12-28 19:54   ` Neil Horman
2007-12-29  5:26   ` Dhaval Giani
2007-12-29  5:26     ` Dhaval Giani
2008-01-07 17:43 ` H. Peter Anvin
2008-01-07 17:43   ` H. Peter Anvin
2008-01-07 17:53   ` Dhaval Giani
2008-01-07 17:53     ` Dhaval Giani
2008-01-07 17:58     ` H. Peter Anvin
2008-01-07 17:58       ` H. Peter Anvin
2008-01-07 19:08     ` crashing on lowmem-only config (was: kexec refuses to boot latest -mm) H. Peter Anvin
2008-01-07 19:08       ` H. Peter Anvin

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=20071228142739.GA4560@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=hbabu@us.ibm.com \
    --cc=kexec@lists.infradead.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 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.