From: Jay Lan <jlan@sgi.com>
To: Neil Horman <nhorman@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>, kexec@lists.infradead.org
Subject: Re: rhel5.6 kdump initrd problem?
Date: Wed, 28 Sep 2011 13:57:00 -0700 [thread overview]
Message-ID: <4E838A1C.4010308@sgi.com> (raw)
In-Reply-To: <20110928143008.GD15446@hmsreliant.think-freely.org>
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) We had multiple lines of "ext3 LABEL=xxx" and it
guarantees at least one of them fail during mkdumprd
and kdump not started properly.
All is fine now. Thanks to all who replied!
Jay
On 09/28/2011 07:30 AM, Neil Horman wrote:
> 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 /etc/init.d/kdump
>>> and a new kdump initrd image was created.
>>> A kernel crash was triggered. The kdump kernel was booted
>>> alright. However, it failed to boot when it tried to boot
>>> back the regular kernel (now with the kdump initrd image
>>> specified in the menu.lst.)
>> Not sure why you would see the kdump initrd image in the menu.lst, it is
>> just a parameter sent to kexec.
>>
> Its actually not even passed to kexec, we build the initrd using the output of
> uname -a, or override it manually with an option in /etc/sysconfig/kdump. We
> don't ever mount the /boot partition, so /boot/grub/menu.lst shouldn't be
> accessible for re-writing.
>
>> You might have more success filing a Red Hat bz (bugzilla.redhat.com), as
>> the RHEL-5 kernel and kexec-tools are probably too old for discussion on
>> this list.
>>
> Agreed, initramfs construction is a distro specific operation, the upstream
> project doesn't contain bits on how to do that.
> Neil
>
>> Cheers,
>> Don
>>
>> _______________________________________________
>> kexec mailing list
>> kexec@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2011-09-28 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 18:38 rhel5.6 kdump initrd problem? Jay Lan
2011-09-27 19:38 ` Jay Lan
2011-09-28 6:26 ` Ken'ichi Ohmichi
2011-09-28 13:08 ` Don Zickus
2011-09-28 14:30 ` Neil Horman
2011-09-28 20:57 ` Jay Lan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E838A1C.4010308@sgi.com \
--to=jlan@sgi.com \
--cc=dzickus@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=nhorman@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.