On Sun, Mar 25, 2007 at 06:12:40PM +0530, Rachita Kothiyal wrote:
> On Fri, Mar 23, 2007 at 10:23:13AM -0700, Judith Lebzelter wrote:
> > On Fri, Mar 23, 2007 at 09:45:04AM +0900, Horms wrote:
> > > On Thu, Mar 22, 2007 at 03:17:03PM -0700, Judith Lebzelter wrote:
> > > > Hi,
> > > >
> > > > I installed the kexec tools and was trying to load a newly built
> > > > 2.6.21-rc4 kernel using this command:
> > > >
> > > > kexec -p /boot/vmlinux-kdump --initrd=/boot/initrd-2.6.21-rc4-kdump.img
> > > > --args-linux --console-serial --elf32-core-headers --append="1
> > > > root=LABEL=/ irqpoll console=ttyS0,38400 , earlyprintk=ttyS0,38400
> > > > debug"
> > > >
> > > > but kexec gives an error: 'Cannot load /boot/vmlinux-kdump'
> > > >
> > > > However, when I load with -l:
> > > >
> > > > kexec -l /boot/vmlinux-kdump --initrd=/boot/initrd-2.6.21-rc4-kdump.img
> > > > --args-linux --console-serial --elf32-core-headers --append="1
> > > > root=LABEL=/ irqpoll console=ttyS0,38400 , earlyprintk=ttyS0,38400
> > > > debug"
> > > >
> > > > I do not see the error.
> > > >
> > > > Are these options all right for i686? (I've been doing mostly x86_64
> > > > with few problems)
> > >
> > > Which version of kexec-tools are you using?
> >
> > I was using the stable with the patch kexec-tools-1.101-kdump10.
> >
> > > Could you try kexec-tools-testing 20070319-rc?
> > > http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/testing/kexec-tools-testing-20070319-rc.tar.bz2
> >
> > I tried with this one and I get a better error message:
> >
> > Memory for crashkernel is not reserved
> > Please reserve memory by passing "[EMAIL PROTECTED]" parameter to the kernel
> > Then try loading kdump kernel
> >
> > But this is not true, as I see the crashkernel parameter passed correctly
> > on the
> > serial console log:
> >
> > Kernel command line: console=ttyS0,38400n8 console=tty1 ro [EMAIL
> > PROTECTED] root=LABEL=/ nmi_watchdog=1
>
> Hi
>
> Does /proc/iomem show the reserved region? Also for what physical location is
> the first kernel built?
/proc/iomem does _not_ show a reserved region. I guess the -l option must
be failing silently.
I have the configuration set to:
CONFIG_KEXEC=y
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_SYSFS=y
CONFIG_DEBUG_INFO=y
This is all that is required according to the Documentation. I am running FC5.
The grub options seem correct to me:
title 2.6.21-rc4-kexec
root (hd0,0)
kernel /vmlinuz-2.6.21-rc4-kexec console=ttyS0,38400n8 console=tty1 ro
[EMAIL PROTECTED] root=LABEL=/ nmi_watchdog=1
initrd /initrd-2.6.21-rc4-kexec.img
The machine is kind of old, a Pentium III/700.126MHz 8-way.
Am I missing something obvious?
Thanks,
Judith
>
> Thanks
> Rachita
>
> >
> > And it still seems to work with the '-l' option rather than '-p'.
> >
> > Judith
> >
> > >
> > > Thanks
> > >
> > > --
> > > Horms
> > > H: http://www.vergenet.net/~horms/
> > > W: http://www.valinux.co.jp/en/
> >
> > ----- End forwarded message -----
> > _______________________________________________
> > fastboot mailing list
> > fastboot@lists.linux-foundation.org
> > https://lists.linux-foundation.org/mailman/listinfo/fastboot
_______________________________________________
fastboot mailing list
fastboot@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/fastboot
