public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Fix for kexec reboot failing after multiple continued kexec reboots
Date: Wed, 17 Nov 2004 23:44:39 +0000	[thread overview]
Message-ID: <200411171544.39448.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <1100633878.21234.15.camel@lyra.fc.hp.com>

On Wednesday, November 17, 2004 2:45 pm, Jesse Barnes wrote:
> This is really neat!  It patched pretty cleanly against the latest bk (this
> stuff should get into -mm asap to help prevent it from getting stale) and
> my new boot got this far:
>
> [root@flatearth ~]# kexec -e
> Starting new kernel
> Linux version 2.6.10-rc2 (jbarnes@tomahawk.engr.sgi.com) (gcc version
> 3.4.1) #1SMP Wed Nov 17 14:34:56 PST 2004
> EFI v1.02 by SGI: SALsystab=0x3002514a60 ACPI 2.0=0x3002514b60
> kexec'd kernel: Not virtualizing EFI
> Number of logical nodes in system = 1
> Number of memory chunks in system = 1
>
> This may be due to the lack of args though, I'll fix it up so that the
> console= stuff is passed in correctly and then debug it further.

It's dying in find_pernode_space.  The efi memmap, though trimmed, should be 
ok at this point, so I'm still trying to figure out what's going on in that 
routine.

Jesse

  parent reply	other threads:[~2004-11-17 23:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 19:37 [PATCH] Fix for kexec reboot failing after multiple continued Khalid Aziz
2004-11-17 22:45 ` [PATCH] Fix for kexec reboot failing after multiple continued kexec reboots Jesse Barnes
2004-11-17 23:44 ` Jesse Barnes [this message]
2004-11-18  0:08 ` Jesse Barnes
2004-11-22 19:10 ` [PATCH] Fix for kexec reboot failing after multiple continued Khalid Aziz

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=200411171544.39448.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=linux-ia64@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