Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: kexec@lists.infradead.org
Subject: /sbin/kexec became zero size... Anyone else?
Date: Wed, 17 Sep 2008 14:07:15 -0700	[thread overview]
Message-ID: <48D17183.7030002@sgi.com> (raw)

Hi,

My root disk was populated with sles10sp2, but the kernel was
2.6.27-rc5 and /sbin/kexec was built from 2.0.0 version.

Many times when kdump kernel failed early i found  after reboot that
/sbin/kexec became zero size. There was no warning on executing
'/etc/init.d/kdump start' when /sbin/kexec is zero size. I have
no idea when and how that happened.

Has anyone else seen this problem?

Thanks,
jay


a4700rac:/sbin # ll kexec*
-rwxr-xr-x 1 root root      0 2008-09-17 12:41 kexec
-rwxr-xr-x 1 root root 387635 2008-07-23 07:25 kexec-2.0.0
-r-xr-xr-x 1 root root 320632 2008-04-21 17:31 kexec-sles10sp2
a4700rac:/sbin # /etc/init.d/kdump start
Loading kdump Loading kdump kernel: /sbin/kexec -p
/boot/vmlinuz-2.6.27-rc5-default --append="CRASH=1  root=/dev/sda8
shub2 console=ttySG0,115200  thash_entries=2097152  ro elevator=deadline
sysrq=1 reset_devices irqpoll maxcpus=1  3"
--initrd=/boot/initrd-2.6.27-rc5-default --noio
                                                                     done
a4700rac:/sbin #


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

             reply	other threads:[~2008-09-17 21:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 21:07 Jay Lan [this message]
2008-09-23  7:52 ` /sbin/kexec became zero size... Anyone else? Simon Horman
2008-09-23 16:41   ` Jay Lan
2008-09-23 17:41     ` Neil Horman
2008-09-23 20:32       ` Jay Lan
2008-09-23 20:41         ` Neil Horman
2010-04-08 16:54         ` Neil Horman

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=48D17183.7030002@sgi.com \
    --to=jlan@sgi.com \
    --cc=kexec@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox