From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, horms@verge.net.au
Subject: Re: [2.6.22-rc4] kexec failed: invalid argument
Date: Fri, 15 Jun 2007 11:50:19 +0300 [thread overview]
Message-ID: <200706151150.19605.caglar@pardus.org.tr> (raw)
In-Reply-To: <m1hcpanlkw.fsf@ebiederm.dsl.xmission.com>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
15 Haz 2007 Cum tarihinde, Eric W. Biederman şunları yazmıştı:
> Sight unseen I'm guessing that you have a kexec aware distro that is doing
> something in the runlevel change scripts and thus unloading the kernel.
> What do: /sys/kernel/kexec_loaded and /sys/kernel/kexec_crash_loaded say?
Not sure, here is the pseudo output what our init system does;
- Stop running services
- Save random seed, sync clock
- Unmount mounted fs's (this includes proc/sysfs etc.)
- Call kexec -e
- Call reboot
> kexec -e at any point should start a loaded kernel without problems, but it
> is a lot like pressing the reset button. Nothing is guaranteed to be
> shutdown cleanly. Now that journalling filesystems are the norm it is
> quite possible nothing bad will happen to you.
zangetsu ~ #
kexec -l /boot/kernel-2.6.22-rc4-CFS-v16 --append="root=/dev/sda3" --initrd=/boot/initramfs-2.6.22-rc4-CFS-v16
setup_linux_vesafb: 1024x768x16 @ c0000000 +300000
zangetsu ~ # cat /sys/kernel/kexec_loaded
1
zangetsu ~ # cat /sys/kernel/kexec_crash_loaded
0
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 prev parent reply other threads:[~2007-06-15 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 18:09 [2.6.22-rc4] kexec failed: invalid argument S.Çağlar Onur
2007-06-14 23:49 ` Eric W. Biederman
2007-06-15 8:50 ` S.Çağlar Onur [this message]
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=200706151150.19605.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