From: Christian Kujau <lists@nerdbynature.de>
To: Maxim Uvarov <muvarov@gmail.com>
Cc: kexec@lists.infradead.org, uvarov@dev.rtsoft.ru,
linuxppc-dev@lists.ozlabs.org, horms@verge.net.au
Subject: Re: [PATCH 1/2] Fix kexec on powerpc32
Date: Wed, 12 May 2010 00:22:14 -0700 [thread overview]
Message-ID: <4BEA5726.50806@nerdbynature.de> (raw)
In-Reply-To: <20100511174749.19309.44615.stgit@muvarov>
On Tue, 11 May 2010 at 21:47, Maxim Uvarov wrote:
> This patch is required in case if you are using new toolchains.
After kexec-tools compiled, I actually tried it:
# kexec -l /boot/2.6/zImage --command-line="root=/dev/hda6 ro"
# echo $?
0
# kexec -e
Starting new kernel
Bye!
....but then the system just hung there, no more messages, I had to
powercycle it.
The --debug options is listed for "dol-ppc" systems (I have a PowerBook
G4, not sure if this falls into this category), when I use it the help
screen of kexec is displayed again and at the bottom:
Cannot load /boot/2.6/zImage
This is with 2.6.34-rc7 (today's git):
# file /boot/2.6/zImage
/boot/2.6/zImage: ELF 32-bit MSB executable, PowerPC or cisco 4500,
version 1 (SYSV), statically linked, with unknown capability 0x41000000
= 0x11676e75, with unknown capability 0x10000 = 0x90402, not stripped
.config and dmesg: http://nerdbynature.de/bits/2.6.34-rc7/kexec/
Christian.
--
make bzImage, not war
next prev parent reply other threads:[~2010-05-12 7:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 17:47 [PATCH 1/2] Fix kexec on powerpc32 Maxim Uvarov
2010-05-11 17:47 ` [PATCH 2/2] powerpc new toolchains fix (crt.S) Maxim Uvarov
2010-05-11 17:57 ` [PATCH 1/2] Fix kexec on powerpc32 Christian Kujau
2010-05-12 3:44 ` Christian Kujau
2010-05-12 6:31 ` Maxim Uvarov
2010-05-12 6:56 ` Christian Kujau
2010-05-12 13:19 ` Simon Horman
2010-05-12 7:22 ` Christian Kujau [this message]
2010-05-12 12:12 ` Maxim Uvarov
2010-05-13 11:19 ` Christian Kujau
2010-05-13 11:50 ` Maxim Uvarov
2010-05-14 0:43 ` Christian Kujau
2010-05-13 11:50 ` Michael Ellerman
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=4BEA5726.50806@nerdbynature.de \
--to=lists@nerdbynature.de \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=muvarov@gmail.com \
--cc=uvarov@dev.rtsoft.ru \
/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;
as well as URLs for NNTP newsgroup(s).