Re: kexec?

[Maneesh Soni <maneesh@in.ibm.com>]

On Wed, May 11, 2005 at 01:51:41PM +0200, Borislav Petkov wrote:
> On Wednesday 11 May 2005 08:04, Maneesh Soni wrote:
> <snip>
> > > > [root@zmei]: kexec -p vmlinux --args-linux --append="root=/dev/hda1
> > > > maxcpus=1 init 1"
> > >
> > >  kexec-tools-1.101 loads for me, but if cmdline is used, it hangs up
> > > after "Starting new kernel"
> >
> > Thanks for trying this out. As Vivek mentioned can you please try with
> > bulding second or dump capture kernel with CONFIG_SMP=N and _without_
> > maxcpus= option. Basically the second kernel's job is just to save the dump
> > and it doesnot need to be a SMP kernel. There are some issues with booting
> > SMP kernel as dump capture kernel.
> 
> Hm, without 'maxcpus' seems to work. However, when booting into the new 
> kernel, the rootfs had to be fsck'ed due to "/ was not cleanly unmounted, 
> check forced." and then was forced to reboot linux due to inconsistency in 
> the fs. I simply did kexec -l <vmlinux> --args-linux --append="root=/dev/hda1 
> init 1" and then kexec -e to execute the loaded image. It seems that the 
> filesystems are not unmounted properly before loading the second kernel, (or 
> I am missing something..., which is more likely :))
> 
> > Also, it would be great help if you can also send us some hardware details
> > about the system you are trying, like lspci, 
> [root@zmei] lspci -vv

Thanks Boris, I have updated the kdump test page with details you provided. 

http://lse.sourceforge.net/kdump/kdump-test.html

It will be nice if you could try kdump also on the similar lines. 

Thanks
Maneesh

-- 
Maneesh Soni
Linux Technology Center, 
IBM India Software Labs,
Bangalore, India
email: maneesh@in.ibm.com
Phone: 91-80-25044990
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/