From: "Magnus Damm" <magnus.damm@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: fastboot@lists.osdl.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Vivek Goyal" <vgoyal@in.ibm.com>, Horms <horms@verge.net.au>,
"Magnus Damm" <magnus@valinux.co.jp>
Subject: 2.6.19-rc1: kexec broken on x86_64
Date: Thu, 5 Oct 2006 19:28:35 +0900 [thread overview]
Message-ID: <aec7e5c30610050328i2bf9e3b6qcacc1873231ece28@mail.gmail.com> (raw)
Kexec is broken on x86_64 under 2.6.19-rc1.
Or rather - kexec works ok under 2.6.19-rc1, but something related to
the vmlinux format has probably changed and kexec-tools fails to load
a vmlinux from 2.6.19-rc1.
Loading bzImage works as usual, but vmlinux does not load properly.
The kexec binary fails with the following message:
Overlapping memory segments at 0x351000
sort_segments failed
/ #
Again, running kexec under 2.6.19-rc1 works ok. But rebooting into a
2.6.19-rc1 vmlinux does not work correctly. This is regardless of
which kexec-tools tree used.
A coarse-grained bisect says that the problem was introduced in 2.6.18-git7.
But maybe this is a kexec-tools issue?
I've used Horms testing tree as usual, tested the latest version
5aa1e11a27f1dc1ce96f850966e94f68c9cd8bce to be exact. Horms testing
tree that can be found here:
http://www.kernel.org/git/?p=linux/kernel/git/horms/kexec-tools-testing.git;a=summary
I've also tried version 71d2424c8ac4f93a60c3eee5c95df269f584a9da of
Eric's main tree:
http://www.kernel.org/git/?p=linux/kernel/git/ebiederm/kexec-tools.git;a=summary
That tree is unfortunately broken on x86_64. You need to apply the
follwing patch on x86_64 to be able to compile:
http://www.kernel.org/git/?p=linux/kernel/git/horms/kexec-tools-testing.git;a=commit;h=6492b850281a106c042221b836a693141fd9b49b
None of the kexec-tools trees can load a 2.6.19-rc1 vmlinux under
x86_64. i386 works fine.
/ magnus
next reply other threads:[~2006-10-05 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 10:28 Magnus Damm [this message]
2006-10-05 13:45 ` Vivek Goyal
2006-10-05 13:56 ` Magnus Damm
2006-10-05 14:24 ` Vivek Goyal
2006-10-05 15:17 ` Eric W. Biederman
2006-10-05 14:33 ` Eric W. Biederman
2006-10-05 16:33 ` Vivek Goyal
2006-10-06 2:28 ` Magnus Damm
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=aec7e5c30610050328i2bf9e3b6qcacc1873231ece28@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus@valinux.co.jp \
--cc=vgoyal@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®