From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: linux-kernel@vger.kernel.org
Cc: ebiederm@xmission.com, horms@verge.net.au
Subject: [2.6.22-rc4] kexec failed: invalid argument
Date: Thu, 14 Jun 2007 21:09:41 +0300 [thread overview]
Message-ID: <200706142109.46027.caglar@pardus.org.tr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
Hi;
With current Linus's git tree + current kexec-tools-testing [1] (also with
kexec-tools-1.101) tree "kexec -e" call on reboot failed with following;
kexec failed: invalid argument
kexec document says its users responsibility to close running softwares,
mounting disks in read only mode etc. and it suggest calling "kexec -e" just
before the "reboot" call and talks about future merge with sysvinit's reboot
and kexec, and when i did it, it will not starts new kernel and instead gaves
that error.
But more supringuisly if i try to execute "kexec -e" directly (in init3 with
rw disks and lots of running software) it will starts new kernel without a
problem.
For reference im using following kexec line for loading the kernel
kexec -l /boot/kernel-2.6.22-rc4-CFS-v16 --append="root=/dev/sda3" --initrd=/boot/initramfs-2.6.22-rc4-CFS-v16
I'm not sure this is a regression or my(maybe me or kexec document misses some
point) mistake cause this is my first attempt to use kexec, but i want to
report the situation :)
[1]
http://git.kernel.org/?p=linux/kernel/git/horms/kexec-tools-testing.git;a=summary
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-06-14 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 18:09 S.Çağlar Onur [this message]
2007-06-14 23:49 ` [2.6.22-rc4] kexec failed: invalid argument Eric W. Biederman
2007-06-15 8:50 ` S.Çağlar Onur
2007-06-15 13:10 ` S.Çağlar Onur
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=200706142109.46027.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.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