Re: problems in loading capture kernel

Re: problems in loading capture kernel

[Vivek Goyal]

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

Re: problems in loading capture kernel

[Vivek Goyal]

On Wed, Feb 03, 2010 at 03:41:25PM -0500, Soumendu Satapathy wrote:

> Oh! I am sorry. That's not an issue, I just did some trace to check the
> errno. The errno = 99 which is invalid address.
> 
> 
> - Have you reserved the space for second kernel?
> 
> Yes, I have reserved with the boot parameters. crashkernel=64M@16M
> 
> 
> - Have you compiled kernel as relocatable one or built a second kernel
>   and trying to load vmlinux.
> CONFIG_KEXEC=y
> CONFIG_CRASH_DUMP=y
> CONFIG_PHYSICAL_START=0x1000000
> CONFIG_RELOCATABLE=y
> CONFIG_PHYSICAL_ALIGN=0x200000
> 

Please do not exclude kexec mailing list from CC. Adding it again.

Can you paste your `cat /proc/iomem` output and make sure space for crash
kernel has been reserved.

Thanks
Vivek

> I have used the above config option for the capture kernel . Compiled
> and build it. And was trying to pre-load it using the following command.
> kexec -p  /boot/vmlinuz-2.6.27_capturekernel03feb
> --initrd=/boot/initrd-2.6.27.img  --append="root=/dev/nfs
> nfsroot=192.168.101.3:/FILESYSTEMS/nfs-roots/root-55 ip=dhcp selinux=0
> 1  irqpoll  maxcpus=1  reset_devices"
> 
> 
> - What was the last working version or setup of kdump in your
> environment.
> 
> Kdump worked well in my environment with a vanilla kernel (2.6.18). The
> one that I am using now is a Fedora core 2.6.27 and it is somehow
> failing with it.
> 
> 
> Thanks
> Soumendu
> 
> -----Original Message-----
> From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> Sent: Wednesday, February 03, 2010 3:25 PM
> To: Soumendu Satapathy
> Cc: Kexec Mailing List
> Subject: Re: problems in loading capture kernel
> 
> 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

RE: problems in loading capture kernel

[Soumendu Satapathy]

cat /proc/iomem

00000000-0009b3ff : System RAM
0009b400-0009ffff : reserved
000e4000-000fffff : reserved
00100000-cff6ffff : System RAM
  00200000-006f0557 : Kernel code
  006f0558-009b9b3f : Kernel data
  00be2000-01219ea7 : Kernel bss
cff70000-cff77fff : ACPI Tables
cff78000-cff7ffff : ACPI Non-volatile Storage
cff80000-cfffffff : reserved
d1000000-d11fffff : PCI Bus 0000:01
  d1000000-d10fffff : PCI Bus 0000:02
    d1000000-d107ffff : 0000:02:03.0
    d1080000-d10fffff : 0000:02:03.1
  d1100000-d11fffff : PCI Bus 0000:03
    d1100000-d113ffff : 0000:03:02.0
    d1140000-d117ffff : 0000:03:02.1
d1200000-d12fffff : PCI Bus 0000:04
  d1200000-d12fffff : PCI Bus 0000:05
    d1200000-d120ffff : 0000:05:04.0
d1300000-d13fffff : PCI Bus 0000:06
  d1300000-d13fffff : PCI Bus 0000:07
    d1300000-d130ffff : 0000:07:04.0
d1400000-d14fffff : PCI Bus 0000:09
  d1400000-d141ffff : 0000:09:01.0
d1500000-d15003ff : 0000:00:1f.1
dd000000-dd000fff : 0000:00:01.0
dd001000-dd00100f : 0000:00:1d.4
dd001400-dd0017ff : 0000:00:1d.7
  dd001400-dd0017ff : ehci_hcd
dd100000-dd3fffff : PCI Bus 0000:01
  dd100000-dd100fff : 0000:01:00.1
  dd101000-dd101fff : 0000:01:00.3
  dd200000-dd2fffff : PCI Bus 0000:02
    dd200000-dd201fff : 0000:02:03.0
    dd202000-dd203fff : 0000:02:03.1
  dd300000-dd3fffff : PCI Bus 0000:03
    dd300000-dd300fff : 0000:03:02.0
    dd301000-dd301fff : 0000:03:02.1
dd400000-dd4fffff : PCI Bus 0000:04
  dd400000-dd4fffff : PCI Bus 0000:05
    dd400000-dd40ffff : 0000:05:04.0
      dd400000-dd40ffff : tg3
    dd410000-dd41ffff : 0000:05:04.0
      dd410000-dd41ffff : tg3
    dd420000-dd42ffff : 0000:05:04.1
      dd420000-dd42ffff : tg3
    dd430000-dd43ffff : 0000:05:04.1
      dd430000-dd43ffff : tg3
dd500000-dd5fffff : PCI Bus 0000:06
  dd500000-dd5fffff : PCI Bus 0000:07
    dd500000-dd50ffff : 0000:07:04.0
      dd500000-dd50ffff : tg3
    dd510000-dd51ffff : 0000:07:04.0
      dd510000-dd51ffff : tg3
    dd520000-dd52ffff : 0000:07:04.1
      dd520000-dd52ffff : tg3
    dd530000-dd53ffff : 0000:07:04.1
      dd530000-dd53ffff : tg3
dd600000-dd6fffff : PCI Bus 0000:08
  dd600000-dd61ffff : 0000:08:01.0
    dd600000-dd61ffff : e1000
  dd620000-dd63ffff : 0000:08:02.0
    dd620000-dd63ffff : e1000
dd700000-deffffff : PCI Bus 0000:09
  dd700000-dd700fff : 0000:09:01.0
  de000000-deffffff : 0000:09:01.0
e0000000-efffffff : PCI MMCONFIG 0
  e0000000-efffffff : reserved
fec00000-fec0ffff : reserved
  fec00000-fec00fff : IOAPIC 0
fec10000-fec10fff : IOAPIC 1
fec80000-fec80fff : IOAPIC 2
fee00000-fee00fff : Local APIC
  fee00000-fee00fff : reserved
ff800000-ffbfffff : reserved
fffffc00-ffffffff : reserved
100000000-22fffffff : System RAM

I don't see a crashkernel entry in the above. Perhaps that might be the
issue.


Thanks
Soumendu

-----Original Message-----
From: Vivek Goyal [mailto:vgoyal@redhat.com] 
Sent: Wednesday, February 03, 2010 3:50 PM
To: Soumendu Satapathy
Cc: Kexec Mailing List
Subject: Re: problems in loading capture kernel

On Wed, Feb 03, 2010 at 03:41:25PM -0500, Soumendu Satapathy wrote:

> Oh! I am sorry. That's not an issue, I just did some trace to check
the
> errno. The errno = 99 which is invalid address.
> 
> 
> - Have you reserved the space for second kernel?
> 
> Yes, I have reserved with the boot parameters. crashkernel=64M@16M
> 
> 
> - Have you compiled kernel as relocatable one or built a second kernel
>   and trying to load vmlinux.
> CONFIG_KEXEC=y
> CONFIG_CRASH_DUMP=y
> CONFIG_PHYSICAL_START=0x1000000
> CONFIG_RELOCATABLE=y
> CONFIG_PHYSICAL_ALIGN=0x200000
> 

Please do not exclude kexec mailing list from CC. Adding it again.

Can you paste your `cat /proc/iomem` output and make sure space for
crash
kernel has been reserved.

Thanks
Vivek

> I have used the above config option for the capture kernel . Compiled
> and build it. And was trying to pre-load it using the following
command.
> kexec -p  /boot/vmlinuz-2.6.27_capturekernel03feb
> --initrd=/boot/initrd-2.6.27.img  --append="root=/dev/nfs
> nfsroot=192.168.101.3:/FILESYSTEMS/nfs-roots/root-55 ip=dhcp selinux=0
> 1  irqpoll  maxcpus=1  reset_devices"
> 
> 
> - What was the last working version or setup of kdump in your
> environment.
> 
> Kdump worked well in my environment with a vanilla kernel (2.6.18).
The
> one that I am using now is a Fedora core 2.6.27 and it is somehow
> failing with it.
> 
> 
> Thanks
> Soumendu
> 
> -----Original Message-----
> From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> Sent: Wednesday, February 03, 2010 3:25 PM
> To: Soumendu Satapathy
> Cc: Kexec Mailing List
> Subject: Re: problems in loading capture kernel
> 
> 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

Re: problems in loading capture kernel

[Vivek Goyal]

On Wed, Feb 03, 2010 at 03:55:40PM -0500, Soumendu Satapathy wrote:
> cat /proc/iomem
> 
> 00000000-0009b3ff : System RAM
> 0009b400-0009ffff : reserved
> 000e4000-000fffff : reserved
> 00100000-cff6ffff : System RAM
>   00200000-006f0557 : Kernel code
>   006f0558-009b9b3f : Kernel data
>   00be2000-01219ea7 : Kernel bss

[..]
> 100000000-22fffffff : System RAM
> 
> I don't see a crashkernel entry in the above. Perhaps that might be the
> issue.

Yes.

00be2000-01219ea7 : Kernel bss

You are trying to reserve memory starting at 16MB (0x1000000) and that
area has been claimed by kernel bss reigon. Try reserving memory at
some other address, say 32MB (crashkernel=64M@32M).

Vivek

> 
> 
> Thanks
> Soumendu
> 
> -----Original Message-----
> From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> Sent: Wednesday, February 03, 2010 3:50 PM
> To: Soumendu Satapathy
> Cc: Kexec Mailing List
> Subject: Re: problems in loading capture kernel
> 
> On Wed, Feb 03, 2010 at 03:41:25PM -0500, Soumendu Satapathy wrote:
> 
> > Oh! I am sorry. That's not an issue, I just did some trace to check
> the
> > errno. The errno = 99 which is invalid address.
> > 
> > 
> > - Have you reserved the space for second kernel?
> > 
> > Yes, I have reserved with the boot parameters. crashkernel=64M@16M
> > 
> > 
> > - Have you compiled kernel as relocatable one or built a second kernel
> >   and trying to load vmlinux.
> > CONFIG_KEXEC=y
> > CONFIG_CRASH_DUMP=y
> > CONFIG_PHYSICAL_START=0x1000000
> > CONFIG_RELOCATABLE=y
> > CONFIG_PHYSICAL_ALIGN=0x200000
> > 
> 
> Please do not exclude kexec mailing list from CC. Adding it again.
> 
> Can you paste your `cat /proc/iomem` output and make sure space for
> crash
> kernel has been reserved.
> 
> Thanks
> Vivek
> 
> > I have used the above config option for the capture kernel . Compiled
> > and build it. And was trying to pre-load it using the following
> command.
> > kexec -p  /boot/vmlinuz-2.6.27_capturekernel03feb
> > --initrd=/boot/initrd-2.6.27.img  --append="root=/dev/nfs
> > nfsroot=192.168.101.3:/FILESYSTEMS/nfs-roots/root-55 ip=dhcp selinux=0
> > 1  irqpoll  maxcpus=1  reset_devices"
> > 
> > 
> > - What was the last working version or setup of kdump in your
> > environment.
> > 
> > Kdump worked well in my environment with a vanilla kernel (2.6.18).
> The
> > one that I am using now is a Fedora core 2.6.27 and it is somehow
> > failing with it.
> > 
> > 
> > Thanks
> > Soumendu
> > 
> > -----Original Message-----
> > From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> > Sent: Wednesday, February 03, 2010 3:25 PM
> > To: Soumendu Satapathy
> > Cc: Kexec Mailing List
> > Subject: Re: problems in loading capture kernel
> > 
> > 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

RE: problems in loading capture kernel

[Soumendu Satapathy]

cat /proc/iomem | grep -i crash
  02000000-05ffffff : Crash kernel

I reserve memory now at 32M.  I can see the entry in /proc/iomem. But
the problem still persists. Perhaps kexec_load() is not loading into the

available reserved memory somehow.

kexec_load failed: Cannot assign requested address
entry       = 0x92550 flags = 1
nr_segments = 4
segment[0].buf   = 0x8eeb40
segment[0].bufsz = 2e4d
segment[0].mem   = 0x8f000
segment[0].memsz = 3000
segment[1].buf   = 0x8e78d0
segment[1].bufsz = 7100
segment[1].mem   = 0x92000
segment[1].memsz = 9000
segment[2].buf   = 0x7f7d32395e10
segment[2].bufsz = 3159f0
segment[2].mem   = 0x100000
segment[2].memsz = 316000
segment[3].buf   = 0x7f7d32a3d010
segment[3].bufsz = 13b165
segment[3].mem   = 0x7fec4000
segment[3].memsz = 13c000


Thanks
Soumendu

-----Original Message-----
From: Vivek Goyal [mailto:vgoyal@redhat.com] 
Sent: Wednesday, February 03, 2010 4:18 PM
To: Soumendu Satapathy
Cc: Kexec Mailing List
Subject: Re: problems in loading capture kernel

On Wed, Feb 03, 2010 at 03:55:40PM -0500, Soumendu Satapathy wrote:
> cat /proc/iomem
> 
> 00000000-0009b3ff : System RAM
> 0009b400-0009ffff : reserved
> 000e4000-000fffff : reserved
> 00100000-cff6ffff : System RAM
>   00200000-006f0557 : Kernel code
>   006f0558-009b9b3f : Kernel data
>   00be2000-01219ea7 : Kernel bss

[..]
> 100000000-22fffffff : System RAM
> 
> I don't see a crashkernel entry in the above. Perhaps that might be
the
> issue.

Yes.

00be2000-01219ea7 : Kernel bss

You are trying to reserve memory starting at 16MB (0x1000000) and that
area has been claimed by kernel bss reigon. Try reserving memory at
some other address, say 32MB (crashkernel=64M@32M).

Vivek

> 
> 
> Thanks
> Soumendu
> 
> -----Original Message-----
> From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> Sent: Wednesday, February 03, 2010 3:50 PM
> To: Soumendu Satapathy
> Cc: Kexec Mailing List
> Subject: Re: problems in loading capture kernel
> 
> On Wed, Feb 03, 2010 at 03:41:25PM -0500, Soumendu Satapathy wrote:
> 
> > Oh! I am sorry. That's not an issue, I just did some trace to check
> the
> > errno. The errno = 99 which is invalid address.
> > 
> > 
> > - Have you reserved the space for second kernel?
> > 
> > Yes, I have reserved with the boot parameters. crashkernel=64M@16M
> > 
> > 
> > - Have you compiled kernel as relocatable one or built a second
kernel
> >   and trying to load vmlinux.
> > CONFIG_KEXEC=y
> > CONFIG_CRASH_DUMP=y
> > CONFIG_PHYSICAL_START=0x1000000
> > CONFIG_RELOCATABLE=y
> > CONFIG_PHYSICAL_ALIGN=0x200000
> > 
> 
> Please do not exclude kexec mailing list from CC. Adding it again.
> 
> Can you paste your `cat /proc/iomem` output and make sure space for
> crash
> kernel has been reserved.
> 
> Thanks
> Vivek
> 
> > I have used the above config option for the capture kernel .
Compiled
> > and build it. And was trying to pre-load it using the following
> command.
> > kexec -p  /boot/vmlinuz-2.6.27_capturekernel03feb
> > --initrd=/boot/initrd-2.6.27.img  --append="root=/dev/nfs
> > nfsroot=192.168.101.3:/FILESYSTEMS/nfs-roots/root-55 ip=dhcp
selinux=0
> > 1  irqpoll  maxcpus=1  reset_devices"
> > 
> > 
> > - What was the last working version or setup of kdump in your
> > environment.
> > 
> > Kdump worked well in my environment with a vanilla kernel (2.6.18).
> The
> > one that I am using now is a Fedora core 2.6.27 and it is somehow
> > failing with it.
> > 
> > 
> > Thanks
> > Soumendu
> > 
> > -----Original Message-----
> > From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> > Sent: Wednesday, February 03, 2010 3:25 PM
> > To: Soumendu Satapathy
> > Cc: Kexec Mailing List
> > Subject: Re: problems in loading capture kernel
> > 
> > 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

RE: problems in loading capture kernel

[Chandan12 K]

[-- Attachment #1.1: Type: text/plain, Size: 9059 bytes --]

Hi Soumendu,


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).

So, kindly do check that BIOS memory layout and allocate the memory 
address for capture kernel from the available memory.

For example in my system it looks like 

BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009c000 (usable)
 BIOS-e820: 000000000009c000 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bf3a1000 (usable)
 BIOS-e820: 00000000bf3a1000 - 00000000bf3c2000 (ACPI NVS)
 BIOS-e820: 00000000bf3c2000 - 00000000bf3c3000 (ACPI data)
 BIOS-e820: 00000000bf3c3000 - 00000000bf3d6000 (reserved)
 BIOS-e820: 00000000bf3d6000 - 00000000bf3d7000 (ACPI NVS)
 BIOS-e820: 00000000bf3d7000 - 00000000bf3e8000 (reserved)
 BIOS-e820: 00000000bf3e8000 - 00000000bf3eb000 (ACPI NVS)
 BIOS-e820: 00000000bf3eb000 - 00000000bf449000 (reserved)
 BIOS-e820: 00000000bf449000 - 00000000bf44b000 (ACPI data)
 BIOS-e820: 00000000bf44b000 - 00000000bf44c000 (ACPI NVS)
 BIOS-e820: 00000000bf44c000 - 00000000bf456000 (ACPI data)
 BIOS-e820: 00000000bf456000 - 00000000bf45f000 (ACPI NVS)
 BIOS-e820: 00000000bf45f000 - 00000000bf47e000 (reserved)
 BIOS-e820: 00000000bf47e000 - 00000000bf681000 (ACPI NVS)
 BIOS-e820: 00000000bf681000 - 00000000bf800000 (usable)
 BIOS-e820: 00000000c0000000 - 00000000d0000000 (reserved)
 BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
 BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 0000000240000000 (usable)

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. 

Thanks
Chandan 




From:
"Soumendu Satapathy" <soumendu.satapathy@reldata.com>
To:
"Vivek Goyal" <vgoyal@redhat.com>
Cc:
Kexec Mailing List <kexec@lists.infradead.org>
Date:
02/04/2010 03:38 AM
Subject:
RE: problems in loading capture kernel
Sent by:
kexec-bounces@lists.infradead.org



cat /proc/iomem | grep -i crash
  02000000-05ffffff : Crash kernel

I reserve memory now at 32M.  I can see the entry in /proc/iomem. But
the problem still persists. Perhaps kexec_load() is not loading into the

available reserved memory somehow.

kexec_load failed: Cannot assign requested address
entry       = 0x92550 flags = 1
nr_segments = 4
segment[0].buf   = 0x8eeb40
segment[0].bufsz = 2e4d
segment[0].mem   = 0x8f000
segment[0].memsz = 3000
segment[1].buf   = 0x8e78d0
segment[1].bufsz = 7100
segment[1].mem   = 0x92000
segment[1].memsz = 9000
segment[2].buf   = 0x7f7d32395e10
segment[2].bufsz = 3159f0
segment[2].mem   = 0x100000
segment[2].memsz = 316000
segment[3].buf   = 0x7f7d32a3d010
segment[3].bufsz = 13b165
segment[3].mem   = 0x7fec4000
segment[3].memsz = 13c000


Thanks
Soumendu

-----Original Message-----
From: Vivek Goyal [mailto:vgoyal@redhat.com] 
Sent: Wednesday, February 03, 2010 4:18 PM
To: Soumendu Satapathy
Cc: Kexec Mailing List
Subject: Re: problems in loading capture kernel

On Wed, Feb 03, 2010 at 03:55:40PM -0500, Soumendu Satapathy wrote:
> cat /proc/iomem
> 
> 00000000-0009b3ff : System RAM
> 0009b400-0009ffff : reserved
> 000e4000-000fffff : reserved
> 00100000-cff6ffff : System RAM
>   00200000-006f0557 : Kernel code
>   006f0558-009b9b3f : Kernel data
>   00be2000-01219ea7 : Kernel bss

[..]
> 100000000-22fffffff : System RAM
> 
> I don't see a crashkernel entry in the above. Perhaps that might be
the
> issue.

Yes.

00be2000-01219ea7 : Kernel bss

You are trying to reserve memory starting at 16MB (0x1000000) and that
area has been claimed by kernel bss reigon. Try reserving memory at
some other address, say 32MB (crashkernel=64M@32M).

Vivek

> 
> 
> Thanks
> Soumendu
> 
> -----Original Message-----
> From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> Sent: Wednesday, February 03, 2010 3:50 PM
> To: Soumendu Satapathy
> Cc: Kexec Mailing List
> Subject: Re: problems in loading capture kernel
> 
> On Wed, Feb 03, 2010 at 03:41:25PM -0500, Soumendu Satapathy wrote:
> 
> > Oh! I am sorry. That's not an issue, I just did some trace to check
> the
> > errno. The errno = 99 which is invalid address.
> > 
> > 
> > - Have you reserved the space for second kernel?
> > 
> > Yes, I have reserved with the boot parameters. crashkernel=64M@16M
> > 
> > 
> > - Have you compiled kernel as relocatable one or built a second
kernel
> >   and trying to load vmlinux.
> > CONFIG_KEXEC=y
> > CONFIG_CRASH_DUMP=y
> > CONFIG_PHYSICAL_START=0x1000000
> > CONFIG_RELOCATABLE=y
> > CONFIG_PHYSICAL_ALIGN=0x200000
> > 
> 
> Please do not exclude kexec mailing list from CC. Adding it again.
> 
> Can you paste your `cat /proc/iomem` output and make sure space for
> crash
> kernel has been reserved.
> 
> Thanks
> Vivek
> 
> > I have used the above config option for the capture kernel .
Compiled
> > and build it. And was trying to pre-load it using the following
> command.
> > kexec -p  /boot/vmlinuz-2.6.27_capturekernel03feb
> > --initrd=/boot/initrd-2.6.27.img  --append="root=/dev/nfs
> > nfsroot=192.168.101.3:/FILESYSTEMS/nfs-roots/root-55 ip=dhcp
selinux=0
> > 1  irqpoll  maxcpus=1  reset_devices"
> > 
> > 
> > - What was the last working version or setup of kdump in your
> > environment.
> > 
> > Kdump worked well in my environment with a vanilla kernel (2.6.18).
> The
> > one that I am using now is a Fedora core 2.6.27 and it is somehow
> > failing with it.
> > 
> > 
> > Thanks
> > Soumendu
> > 
> > -----Original Message-----
> > From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> > Sent: Wednesday, February 03, 2010 3:25 PM
> > To: Soumendu Satapathy
> > Cc: Kexec Mailing List
> > Subject: Re: problems in loading capture kernel
> > 
> > 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


=====-----=====-----=====
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



[-- Attachment #1.2: Type: text/html, Size: 14407 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

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

Re: problems in loading capture kernel

[Vivek Goyal]

On Wed, Feb 03, 2010 at 04:51:33PM -0500, Soumendu Satapathy wrote:
> cat /proc/iomem | grep -i crash
>   02000000-05ffffff : Crash kernel
> 
> I reserve memory now at 32M.  I can see the entry in /proc/iomem. But
> the problem still persists. Perhaps kexec_load() is not loading into the
> 
> available reserved memory somehow.
> 
> kexec_load failed: Cannot assign requested address
> entry       = 0x92550 flags = 1

Which kexec-tools are you using. Can you try using the latest one.

http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/

> nr_segments = 4
> segment[0].buf   = 0x8eeb40
> segment[0].bufsz = 2e4d
> segment[0].mem   = 0x8f000
> segment[0].memsz = 3000
> segment[1].buf   = 0x8e78d0
> segment[1].bufsz = 7100
> segment[1].mem   = 0x92000
> segment[1].memsz = 9000
> segment[2].buf   = 0x7f7d32395e10
> segment[2].bufsz = 3159f0
> segment[2].mem   = 0x100000

Looking at this address, kexec is still trying to load a memory segemnt
at address 1MB. I think with kexec -p and relocatable bzImage, it should
have loaded the segment with-in reserved area. (IIRC). Slowly memory is
fading. Long time since I touched kexec now. :-)

Trying using latest kexec-tools and see what happens.

Vivek

> segment[2].memsz = 316000
> segment[3].buf   = 0x7f7d32a3d010
> segment[3].bufsz = 13b165
> segment[3].mem   = 0x7fec4000
> segment[3].memsz = 13c000
> 
> 
> Thanks
> Soumendu
> 
> -----Original Message-----
> From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> Sent: Wednesday, February 03, 2010 4:18 PM
> To: Soumendu Satapathy
> Cc: Kexec Mailing List
> Subject: Re: problems in loading capture kernel
> 
> On Wed, Feb 03, 2010 at 03:55:40PM -0500, Soumendu Satapathy wrote:
> > cat /proc/iomem
> > 
> > 00000000-0009b3ff : System RAM
> > 0009b400-0009ffff : reserved
> > 000e4000-000fffff : reserved
> > 00100000-cff6ffff : System RAM
> >   00200000-006f0557 : Kernel code
> >   006f0558-009b9b3f : Kernel data
> >   00be2000-01219ea7 : Kernel bss
> 
> [..]
> > 100000000-22fffffff : System RAM
> > 
> > I don't see a crashkernel entry in the above. Perhaps that might be
> the
> > issue.
> 
> Yes.
> 
> 00be2000-01219ea7 : Kernel bss
> 
> You are trying to reserve memory starting at 16MB (0x1000000) and that
> area has been claimed by kernel bss reigon. Try reserving memory at
> some other address, say 32MB (crashkernel=64M@32M).
> 
> Vivek
> 
> > 
> > 
> > Thanks
> > Soumendu
> > 
> > -----Original Message-----
> > From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> > Sent: Wednesday, February 03, 2010 3:50 PM
> > To: Soumendu Satapathy
> > Cc: Kexec Mailing List
> > Subject: Re: problems in loading capture kernel
> > 
> > On Wed, Feb 03, 2010 at 03:41:25PM -0500, Soumendu Satapathy wrote:
> > 
> > > Oh! I am sorry. That's not an issue, I just did some trace to check
> > the
> > > errno. The errno = 99 which is invalid address.
> > > 
> > > 
> > > - Have you reserved the space for second kernel?
> > > 
> > > Yes, I have reserved with the boot parameters. crashkernel=64M@16M
> > > 
> > > 
> > > - Have you compiled kernel as relocatable one or built a second
> kernel
> > >   and trying to load vmlinux.
> > > CONFIG_KEXEC=y
> > > CONFIG_CRASH_DUMP=y
> > > CONFIG_PHYSICAL_START=0x1000000
> > > CONFIG_RELOCATABLE=y
> > > CONFIG_PHYSICAL_ALIGN=0x200000
> > > 
> > 
> > Please do not exclude kexec mailing list from CC. Adding it again.
> > 
> > Can you paste your `cat /proc/iomem` output and make sure space for
> > crash
> > kernel has been reserved.
> > 
> > Thanks
> > Vivek
> > 
> > > I have used the above config option for the capture kernel .
> Compiled
> > > and build it. And was trying to pre-load it using the following
> > command.
> > > kexec -p  /boot/vmlinuz-2.6.27_capturekernel03feb
> > > --initrd=/boot/initrd-2.6.27.img  --append="root=/dev/nfs
> > > nfsroot=192.168.101.3:/FILESYSTEMS/nfs-roots/root-55 ip=dhcp
> selinux=0
> > > 1  irqpoll  maxcpus=1  reset_devices"
> > > 
> > > 
> > > - What was the last working version or setup of kdump in your
> > > environment.
> > > 
> > > Kdump worked well in my environment with a vanilla kernel (2.6.18).
> > The
> > > one that I am using now is a Fedora core 2.6.27 and it is somehow
> > > failing with it.
> > > 
> > > 
> > > Thanks
> > > Soumendu
> > > 
> > > -----Original Message-----
> > > From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> > > Sent: Wednesday, February 03, 2010 3:25 PM
> > > To: Soumendu Satapathy
> > > Cc: Kexec Mailing List
> > > Subject: Re: problems in loading capture kernel
> > > 
> > > 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

RE: problems in loading capture kernel

[Soumendu Satapathy]

Sorry I am posting the results very late. As per Vivek's suggestions, I
used the latest kexec-tools i.e version kexec-tools-2.0.1
and I was successfully able to load the capture kernel.  I had problems
with kexec-tools-2.0.0 and kexec-tools-1.101.

Thanks for your suggestions Vivek.

Regards
Soumendu

-----Original Message-----
From: Vivek Goyal [mailto:vgoyal@redhat.com] 
Sent: Thursday, February 04, 2010 11:28 AM
To: Soumendu Satapathy
Cc: Kexec Mailing List
Subject: Re: problems in loading capture kernel

On Wed, Feb 03, 2010 at 04:51:33PM -0500, Soumendu Satapathy wrote:
> cat /proc/iomem | grep -i crash
>   02000000-05ffffff : Crash kernel
> 
> I reserve memory now at 32M.  I can see the entry in /proc/iomem. But
> the problem still persists. Perhaps kexec_load() is not loading into
the
> 
> available reserved memory somehow.
> 
> kexec_load failed: Cannot assign requested address
> entry       = 0x92550 flags = 1

Which kexec-tools are you using. Can you try using the latest one.

http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/

> nr_segments = 4
> segment[0].buf   = 0x8eeb40
> segment[0].bufsz = 2e4d
> segment[0].mem   = 0x8f000
> segment[0].memsz = 3000
> segment[1].buf   = 0x8e78d0
> segment[1].bufsz = 7100
> segment[1].mem   = 0x92000
> segment[1].memsz = 9000
> segment[2].buf   = 0x7f7d32395e10
> segment[2].bufsz = 3159f0
> segment[2].mem   = 0x100000

Looking at this address, kexec is still trying to load a memory segemnt
at address 1MB. I think with kexec -p and relocatable bzImage, it should
have loaded the segment with-in reserved area. (IIRC). Slowly memory is
fading. Long time since I touched kexec now. :-)

Trying using latest kexec-tools and see what happens.

Vivek

> segment[2].memsz = 316000
> segment[3].buf   = 0x7f7d32a3d010
> segment[3].bufsz = 13b165
> segment[3].mem   = 0x7fec4000
> segment[3].memsz = 13c000
> 
> 
> Thanks
> Soumendu
> 
> -----Original Message-----
> From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> Sent: Wednesday, February 03, 2010 4:18 PM
> To: Soumendu Satapathy
> Cc: Kexec Mailing List
> Subject: Re: problems in loading capture kernel
> 
> On Wed, Feb 03, 2010 at 03:55:40PM -0500, Soumendu Satapathy wrote:
> > cat /proc/iomem
> > 
> > 00000000-0009b3ff : System RAM
> > 0009b400-0009ffff : reserved
> > 000e4000-000fffff : reserved
> > 00100000-cff6ffff : System RAM
> >   00200000-006f0557 : Kernel code
> >   006f0558-009b9b3f : Kernel data
> >   00be2000-01219ea7 : Kernel bss
> 
> [..]
> > 100000000-22fffffff : System RAM
> > 
> > I don't see a crashkernel entry in the above. Perhaps that might be
> the
> > issue.
> 
> Yes.
> 
> 00be2000-01219ea7 : Kernel bss
> 
> You are trying to reserve memory starting at 16MB (0x1000000) and that
> area has been claimed by kernel bss reigon. Try reserving memory at
> some other address, say 32MB (crashkernel=64M@32M).
> 
> Vivek
> 
> > 
> > 
> > Thanks
> > Soumendu
> > 
> > -----Original Message-----
> > From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> > Sent: Wednesday, February 03, 2010 3:50 PM
> > To: Soumendu Satapathy
> > Cc: Kexec Mailing List
> > Subject: Re: problems in loading capture kernel
> > 
> > On Wed, Feb 03, 2010 at 03:41:25PM -0500, Soumendu Satapathy wrote:
> > 
> > > Oh! I am sorry. That's not an issue, I just did some trace to
check
> > the
> > > errno. The errno = 99 which is invalid address.
> > > 
> > > 
> > > - Have you reserved the space for second kernel?
> > > 
> > > Yes, I have reserved with the boot parameters. crashkernel=64M@16M
> > > 
> > > 
> > > - Have you compiled kernel as relocatable one or built a second
> kernel
> > >   and trying to load vmlinux.
> > > CONFIG_KEXEC=y
> > > CONFIG_CRASH_DUMP=y
> > > CONFIG_PHYSICAL_START=0x1000000
> > > CONFIG_RELOCATABLE=y
> > > CONFIG_PHYSICAL_ALIGN=0x200000
> > > 
> > 
> > Please do not exclude kexec mailing list from CC. Adding it again.
> > 
> > Can you paste your `cat /proc/iomem` output and make sure space for
> > crash
> > kernel has been reserved.
> > 
> > Thanks
> > Vivek
> > 
> > > I have used the above config option for the capture kernel .
> Compiled
> > > and build it. And was trying to pre-load it using the following
> > command.
> > > kexec -p  /boot/vmlinuz-2.6.27_capturekernel03feb
> > > --initrd=/boot/initrd-2.6.27.img  --append="root=/dev/nfs
> > > nfsroot=192.168.101.3:/FILESYSTEMS/nfs-roots/root-55 ip=dhcp
> selinux=0
> > > 1  irqpoll  maxcpus=1  reset_devices"
> > > 
> > > 
> > > - What was the last working version or setup of kdump in your
> > > environment.
> > > 
> > > Kdump worked well in my environment with a vanilla kernel
(2.6.18).
> > The
> > > one that I am using now is a Fedora core 2.6.27 and it is somehow
> > > failing with it.
> > > 
> > > 
> > > Thanks
> > > Soumendu
> > > 
> > > -----Original Message-----
> > > From: Vivek Goyal [mailto:vgoyal@redhat.com] 
> > > Sent: Wednesday, February 03, 2010 3:25 PM
> > > To: Soumendu Satapathy
> > > Cc: Kexec Mailing List
> > > Subject: Re: problems in loading capture kernel
> > > 
> > > 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