From: Vivek Goyal <vgoyal@redhat.com>
To: Soumendu Satapathy <soumendu.satapathy@reldata.com>
Cc: Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: problems in loading capture kernel
Date: Wed, 3 Feb 2010 15:25:11 -0500 [thread overview]
Message-ID: <20100203202510.GC17059@redhat.com> (raw)
In-Reply-To: <32AB6BC050DF9E4E91868C4C3B7B6ABBAE09A5@lion.reldatainc.local>
On Wed, Feb 03, 2010 at 02:46:53PM -0500, Soumendu Satapathy wrote:
> Hi Vivek ,
>
>
>
> I am having some problems to load the capture kernel.
>
>
>
> The following is the error. I am using a x86_64 box. I am using 2.6.27
> linux kernel for both the first kernel and the capture kernel. The
> capture kenel I have configured with CONFIG_SMP=n.
>
> maxcpus=1.
>
>
>
> kexec_load failed: Cannot assign requested address 99
>
This looks little odd. Where is this address "99" coming from?
Few things.
- Have you reserved the space for second kernel?
- Have you compiled kernel as relocatable one or built a second kernel
and trying to load vmlinux.
- What was the last working version or setup of kdump in your environment.
I would begin at running gdb at kexec to figure out where this seemingly
bad address "99" coming from.
CCing kexec mailing list, in case somebody has seen similar message.
Thanks
Vivek
> entry = 0x92550 flags = 1
>
> nr_segments = 4
>
> segment[0].buf = 0xb75b40
>
> segment[0].bufsz = 2e77
>
> segment[0].mem = 0x8f000
>
> segment[0].memsz = 3000
>
> segment[1].buf = 0xb6e8d0
>
> segment[1].bufsz = 7100
>
> segment[1].mem = 0x92000
>
> segment[1].memsz = 9000
>
> segment[2].buf = 0x7f5aab6c4e10
>
> segment[2].bufsz = 3159d0
>
> segment[2].mem = 0x100000
>
> segment[2].memsz = 316000
>
> segment[3].buf = 0x7f5aabd6c010
>
> segment[3].bufsz = 13b153
>
> segment[3].mem = 0x7fec4000
>
> segment[3].memsz = 13c000
>
>
>
>
>
> Can you please provide some inputs ?
>
>
>
> thanks
>
> Soumendu S Satapathy
>
> Senior Software Developer
>
> RELDATA Inc.
>
> 1719 Route 10, Suite 209
>
> Parsippany, NJ 07054
>
> (973) 644-2770 ext. 139 office
>
> 732-692-7230 mobile
>
> (973) 644-3385 fax
>
> soumendu.satapathy@reldata.com
>
> www.reldata.com <http://www.reldata.com/>
>
>
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next parent reply other threads:[~2010-02-03 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32AB6BC050DF9E4E91868C4C3B7B6ABBAE09A5@lion.reldatainc.local>
2010-02-03 20:25 ` Vivek Goyal [this message]
[not found] ` <32AB6BC050DF9E4E91868C4C3B7B6ABBAE09B6@lion.reldatainc.local>
2010-02-03 20:50 ` problems in loading capture kernel Vivek Goyal
2010-02-03 20:55 ` Soumendu Satapathy
2010-02-03 21:17 ` Vivek Goyal
2010-02-03 21:51 ` Soumendu Satapathy
2010-02-04 7:10 ` Chandan12 K
2010-02-04 16:27 ` Vivek Goyal
2010-02-12 16:04 ` Soumendu Satapathy
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=20100203202510.GC17059@redhat.com \
--to=vgoyal@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=soumendu.satapathy@reldata.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.