From: yhlu <yinghailu@gmail.com>
To: Horms <horms@verge.net.au>
Cc: "Fastboot mailing list" <fastboot@lists.osdl.org>,
ebiederm@xmission.com,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Fastboot] Kexec with latest kernel fail
Date: Wed, 8 Nov 2006 22:03:17 -0800 [thread overview]
Message-ID: <2ea3fae10611082203s68454772l8970d180008dc246@mail.gmail.com> (raw)
In-Reply-To: <20061109054805.GA28415@verge.net.au>
2.6.19 AMD64
1. kexec 2.6.17 AMD64 bzImage ? elf32 ( made by mkelfImage 2.5)
2. kexec suse 10.0 amd64 vmlinuz and initrd.
YH
On 11/8/06, Horms <horms@verge.net.au> wrote:
> On Wed, Nov 08, 2006 at 08:07:22PM -0800, Lu, Yinghai wrote:
> > Eric,
> >
> > I got "Invalid memory segment 0x100000 - ..."
> > using kexec latest kernel...
>
> Which kernel? What config? What architecture? What hardware?
>
> > Do I need patch for kexec tools with latest kexec in kernel?
>
> Its largely dependant on what architecture you are using.
> But try out kexec-tools-testing if you are not already doing so.
> It is available via git from www.kernel.org/git
>
> --
> Horms
> H: http://www.vergenet.net/~horms/
> W: http://www.valinux.co.jp/en/
>
> _______________________________________________
> fastboot mailing list
> fastboot@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/fastboot
>
next prev parent reply other threads:[~2006-11-09 6:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 4:07 Lu, Yinghai
2006-11-09 5:48 ` [Fastboot] " Horms
2006-11-09 6:03 ` yhlu [this message]
2006-11-09 6:04 ` yhlu
2006-11-09 6:21 ` Horms
2006-11-09 7:36 ` Yinghai Lu
2006-11-10 0:47 ` Horms
2006-11-09 16:39 ` Don Zickus
2006-11-09 17:05 ` Yinghai Lu
2006-11-09 20:06 ` Jay Lan
2006-11-09 20:11 ` Vivek Goyal
2006-11-10 1:12 Lu, Yinghai
2006-11-10 1:27 ` Horms
2006-11-10 1:41 Lu, Yinghai
2006-11-10 5:24 ` Eric W. Biederman
2006-11-10 7:30 ` yhlu
2006-11-10 9:18 ` Yinghai Lu
2006-11-10 20:01 Lu, Yinghai
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=2ea3fae10611082203s68454772l8970d180008dc246@mail.gmail.com \
--to=yinghailu@gmail.com \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--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
all inboxes | Powered by JetHome®