<br><font size=2 face="sans-serif">Hi Soumendu,</font>
<br>
<br>
<br><font size=2 face="sans-serif">I also had similar issue, but my problem
got solved once I looked across the memory layout of the BIOS. example
you may have 8G of memory on system but there exists some memory area where
can't be user by the kernel (they are generally reserved for some ACPI
data or some other firmware data).</font>
<br>
<br><font size=2 face="sans-serif">So, kindly do check that BIOS memory
layout and allocate the memory address for capture kernel from the available
memory.</font>
<br>
<br><font size=2 face="sans-serif">For example in my system it looks like
</font>
<br>
<br><font size=2 face="sans-serif">BIOS-provided physical RAM map:</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 0000000000000000 -
000000000009c000 (usable)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 000000000009c000 -
00000000000a0000 (reserved)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000000e0000 -
0000000000100000 (reserved)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 0000000000100000 -
00000000bf3a1000 (usable)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf3a1000 -
00000000bf3c2000 (ACPI NVS)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf3c2000 -
00000000bf3c3000 (ACPI data)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf3c3000 -
00000000bf3d6000 (reserved)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf3d6000 -
00000000bf3d7000 (ACPI NVS)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf3d7000 -
00000000bf3e8000 (reserved)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf3e8000 -
00000000bf3eb000 (ACPI NVS)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf3eb000 -
00000000bf449000 (reserved)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf449000 -
00000000bf44b000 (ACPI data)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf44b000 -
00000000bf44c000 (ACPI NVS)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf44c000 -
00000000bf456000 (ACPI data)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf456000 -
00000000bf45f000 (ACPI NVS)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf45f000 -
00000000bf47e000 (reserved)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf47e000 -
00000000bf681000 (ACPI NVS)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000bf681000 -
00000000bf800000 (usable)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000c0000000 -
00000000d0000000 (reserved)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000fed1c000 -
00000000fed20000 (reserved)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 00000000ff000000 -
0000000100000000 (reserved)</font>
<br><font size=2 face="sans-serif"> BIOS-e820: 0000000100000000 -
0000000240000000 (usable)</font>
<br>
<br><font size=2 face="sans-serif">Here I can see various memory areas
which are already reserved and can't be used. So, if you can get similar
memory map (during bootup) and allocate the address to the "usable"
one, probably it may help you to jettison your capture kernel loading issue.
</font>
<br>
<br><font size=2 face="sans-serif">Thanks<br>
Chandan <br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">"Soumendu Satapathy" <soumendu.satapathy@reldata.com></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">"Vivek Goyal" <vgoyal@redhat.com></font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">Kexec Mailing List <kexec@lists.infradead.org></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">02/04/2010 03:38 AM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">RE: problems in loading capture kernel</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">kexec-bounces@lists.infradead.org</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>cat /proc/iomem | grep -i crash<br>
02000000-05ffffff : Crash kernel<br>
<br>
I reserve memory now at 32M. I can see the entry in /proc/iomem.
But<br>
the problem still persists. Perhaps kexec_load() is not loading into the<br>
<br>
available reserved memory somehow.<br>
<br>
kexec_load failed: Cannot assign requested address<br>
entry = 0x92550 flags = 1<br>
nr_segments = 4<br>
segment[0].buf = 0x8eeb40<br>
segment[0].bufsz = 2e4d<br>
segment[0].mem = 0x8f000<br>
segment[0].memsz = 3000<br>
segment[1].buf = 0x8e78d0<br>
segment[1].bufsz = 7100<br>
segment[1].mem = 0x92000<br>
segment[1].memsz = 9000<br>
segment[2].buf = 0x7f7d32395e10<br>
segment[2].bufsz = 3159f0<br>
segment[2].mem = 0x100000<br>
segment[2].memsz = 316000<br>
segment[3].buf = 0x7f7d32a3d010<br>
segment[3].bufsz = 13b165<br>
segment[3].mem = 0x7fec4000<br>
segment[3].memsz = 13c000<br>
<br>
<br>
Thanks<br>
Soumendu<br>
<br>
-----Original Message-----<br>
From: Vivek Goyal [</font></tt><a href=mailto:vgoyal@redhat.com><tt><font size=2>mailto:vgoyal@redhat.com</font></tt></a><tt><font size=2>]
<br>
Sent: Wednesday, February 03, 2010 4:18 PM<br>
To: Soumendu Satapathy<br>
Cc: Kexec Mailing List<br>
Subject: Re: problems in loading capture kernel<br>
<br>
On Wed, Feb 03, 2010 at 03:55:40PM -0500, Soumendu Satapathy wrote:<br>
> cat /proc/iomem<br>
> <br>
> 00000000-0009b3ff : System RAM<br>
> 0009b400-0009ffff : reserved<br>
> 000e4000-000fffff : reserved<br>
> 00100000-cff6ffff : System RAM<br>
> 00200000-006f0557 : Kernel code<br>
> 006f0558-009b9b3f : Kernel data<br>
> 00be2000-01219ea7 : Kernel bss<br>
<br>
[..]<br>
> 100000000-22fffffff : System RAM<br>
> <br>
> I don't see a crashkernel entry in the above. Perhaps that might be<br>
the<br>
> issue.<br>
<br>
Yes.<br>
<br>
00be2000-01219ea7 : Kernel bss<br>
<br>
You are trying to reserve memory starting at 16MB (0x1000000) and that<br>
area has been claimed by kernel bss reigon. Try reserving memory at<br>
some other address, say 32MB (crashkernel=64M@32M).<br>
<br>
Vivek<br>
<br>
> <br>
> <br>
> Thanks<br>
> Soumendu<br>
> <br>
> -----Original Message-----<br>
> From: Vivek Goyal [</font></tt><a href=mailto:vgoyal@redhat.com><tt><font size=2>mailto:vgoyal@redhat.com</font></tt></a><tt><font size=2>]
<br>
> Sent: Wednesday, February 03, 2010 3:50 PM<br>
> To: Soumendu Satapathy<br>
> Cc: Kexec Mailing List<br>
> Subject: Re: problems in loading capture kernel<br>
> <br>
> On Wed, Feb 03, 2010 at 03:41:25PM -0500, Soumendu Satapathy wrote:<br>
> <br>
> > Oh! I am sorry. That's not an issue, I just did some trace to
check<br>
> the<br>
> > errno. The errno = 99 which is invalid address.<br>
> > <br>
> > <br>
> > - Have you reserved the space for second kernel?<br>
> > <br>
> > Yes, I have reserved with the boot parameters. crashkernel=64M@16M<br>
> > <br>
> > <br>
> > - Have you compiled kernel as relocatable one or built a second<br>
kernel<br>
> > and trying to load vmlinux.<br>
> > CONFIG_KEXEC=y<br>
> > CONFIG_CRASH_DUMP=y<br>
> > CONFIG_PHYSICAL_START=0x1000000<br>
> > CONFIG_RELOCATABLE=y<br>
> > CONFIG_PHYSICAL_ALIGN=0x200000<br>
> > <br>
> <br>
> Please do not exclude kexec mailing list from CC. Adding it again.<br>
> <br>
> Can you paste your `cat /proc/iomem` output and make sure space for<br>
> crash<br>
> kernel has been reserved.<br>
> <br>
> Thanks<br>
> Vivek<br>
> <br>
> > I have used the above config option for the capture kernel .<br>
Compiled<br>
> > and build it. And was trying to pre-load it using the following<br>
> command.<br>
> > kexec -p /boot/vmlinuz-2.6.27_capturekernel03feb<br>
> > --initrd=/boot/initrd-2.6.27.img --append="root=/dev/nfs<br>
> > nfsroot=192.168.101.3:/FILESYSTEMS/nfs-roots/root-55 ip=dhcp<br>
selinux=0<br>
> > 1 irqpoll maxcpus=1 reset_devices"<br>
> > <br>
> > <br>
> > - What was the last working version or setup of kdump in your<br>
> > environment.<br>
> > <br>
> > Kdump worked well in my environment with a vanilla kernel (2.6.18).<br>
> The<br>
> > one that I am using now is a Fedora core 2.6.27 and it is somehow<br>
> > failing with it.<br>
> > <br>
> > <br>
> > Thanks<br>
> > Soumendu<br>
> > <br>
> > -----Original Message-----<br>
> > From: Vivek Goyal [</font></tt><a href=mailto:vgoyal@redhat.com><tt><font size=2>mailto:vgoyal@redhat.com</font></tt></a><tt><font size=2>]
<br>
> > Sent: Wednesday, February 03, 2010 3:25 PM<br>
> > To: Soumendu Satapathy<br>
> > Cc: Kexec Mailing List<br>
> > Subject: Re: problems in loading capture kernel<br>
> > <br>
> > On Wed, Feb 03, 2010 at 02:46:53PM -0500, Soumendu Satapathy
wrote:<br>
> > > Hi Vivek ,<br>
> > > <br>
> > > <br>
> > > <br>
> > > I am having some problems to load the capture kernel.<br>
> > > <br>
> > > <br>
> > > <br>
> > > The following is the error. I am using a x86_64 box. I am
using<br>
> 2.6.27<br>
> > > linux kernel for both the first kernel and the capture kernel.
The<br>
> > > capture kenel I have configured with CONFIG_SMP=n.<br>
> > > <br>
> > > maxcpus=1.<br>
> > > <br>
> > > <br>
> > > <br>
> > > kexec_load failed: Cannot assign requested address 99<br>
> > > <br>
> > <br>
> > This looks little odd. Where is this address "99" coming
from?<br>
> > <br>
> > Few things.<br>
> > <br>
> > - Have you reserved the space for second kernel?<br>
> > - Have you compiled kernel as relocatable one or built a second<br>
kernel<br>
> > and trying to load vmlinux.<br>
> > - What was the last working version or setup of kdump in your<br>
> > environment.<br>
> > <br>
> > I would begin at running gdb at kexec to figure out where this<br>
> seemingly<br>
> > bad address "99" coming from.<br>
> > <br>
> > CCing kexec mailing list, in case somebody has seen similar message.<br>
> > <br>
> > Thanks<br>
> > Vivek<br>
> > <br>
> > > entry = 0x92550 flags = 1<br>
> > > <br>
> > > nr_segments = 4<br>
> > > <br>
> > > segment[0].buf = 0xb75b40<br>
> > > <br>
> > > segment[0].bufsz = 2e77<br>
> > > <br>
> > > segment[0].mem = 0x8f000<br>
> > > <br>
> > > segment[0].memsz = 3000<br>
> > > <br>
> > > segment[1].buf = 0xb6e8d0<br>
> > > <br>
> > > segment[1].bufsz = 7100<br>
> > > <br>
> > > segment[1].mem = 0x92000<br>
> > > <br>
> > > segment[1].memsz = 9000<br>
> > > <br>
> > > segment[2].buf = 0x7f5aab6c4e10<br>
> > > <br>
> > > segment[2].bufsz = 3159d0<br>
> > > <br>
> > > segment[2].mem = 0x100000<br>
> > > <br>
> > > segment[2].memsz = 316000<br>
> > > <br>
> > > segment[3].buf = 0x7f5aabd6c010<br>
> > > <br>
> > > segment[3].bufsz = 13b153<br>
> > > <br>
> > > segment[3].mem = 0x7fec4000<br>
> > > <br>
> > > segment[3].memsz = 13c000<br>
> > > <br>
> > > <br>
> > > <br>
> > > <br>
> > > <br>
> > > Can you please provide some inputs ?<br>
> > > <br>
> > > <br>
> > > <br>
> > > thanks<br>
> > > <br>
> > > Soumendu S Satapathy<br>
> > > <br>
> > > Senior Software Developer<br>
> > > <br>
> > > RELDATA Inc.<br>
> > > <br>
> > > 1719 Route 10, Suite 209<br>
> > > <br>
> > > Parsippany, NJ 07054<br>
> > > <br>
> > > (973) 644-2770 ext. 139 office<br>
> > > <br>
> > > 732-692-7230 mobile<br>
> > > <br>
> > > (973) 644-3385 fax<br>
> > > <br>
> > > soumendu.satapathy@reldata.com<br>
> > > <br>
> > > </font></tt><a href=www.reldata.com><tt><font size=2>www.reldata.com</font></tt></a><tt><font size=2>
<</font></tt><a href=http://www.reldata.com/><tt><font size=2>http://www.reldata.com/</font></tt></a><tt><font size=2>>
<br>
> > > <br>
> > > <br>
> > > <br>
<br>
_______________________________________________<br>
kexec mailing list<br>
kexec@lists.infradead.org<br>
</font></tt><a href=http://lists.infradead.org/mailman/listinfo/kexec><tt><font size=2>http://lists.infradead.org/mailman/listinfo/kexec</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><pre>=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
</pre>