Hi Jay,
On Tue, 27 Sep 2011 12:38:11 -0700
Jay Lan j...@sgi.com wrote:
I have a system running 2.6.18-238.12.1.el5 kernel.
The kexec version is kexec-tools-1.102pre-126.el5_6.6.
The kernel was booted OK. Then it ran /etc/init.d/kdump
and a new kdump initrd image was created.
A
On Tue, Sep 27, 2011 at 11:38:28AM -0700, Jay Lan wrote:
Hi all,
I have a system running 2.6.18-238.12.1.el5 kernel.
The kexec version is kexec-tools-1.102pre-126.el5_6.6.
The kernel was booted OK. Then it ran /etc/init.d/kdump
and a new kdump initrd image was created.
A kernel crash was
On Wed, Sep 28, 2011 at 09:08:42AM -0400, Don Zickus wrote:
On Tue, Sep 27, 2011 at 11:38:28AM -0700, Jay Lan wrote:
Hi all,
I have a system running 2.6.18-238.12.1.el5 kernel.
The kexec version is kexec-tools-1.102pre-126.el5_6.6.
The kernel was booted OK. Then it ran
Thanks to all who replied.
Our problem was resolved. It was caused by two different
configuration issues:
1) As Don and Neil said, the kdump initrd img should not be
in the menu.lst. Not sure why it was there at first place.
So we changed the boot line to use the orignial initrd img.
2)
On Mon, Sep 26, 2011 at 03:09:09PM +0200, Michael Holzheu wrote:
Hello Simon,
I think the --load-preserve-context and --load-jump-back-helper kexec
options are not working on s390 because we do not support
CONFIG_KEXEC_JUMP. I assume the same is true also on other
architectures. Correct me,
