Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: liu.song11@zte.com.cn
Cc: kexec@lists.infradead.org
Subject: Re: some questions about elf_ppc64_load
Date: Tue, 06 Jan 2015 09:37:03 +0100	[thread overview]
Message-ID: <54AB9EAF.2020004@linux.vnet.ibm.com> (raw)
In-Reply-To: <OF9C6CA8A8.9D7923CD-ON48257DC5.0023F61F-48257DC5.0024E800@zte.com.cn>

On 06/01/2015 07:44, liu.song11@zte.com.cn wrote:
> 
> hi all,
> 
> I use kexec-tools-2.0.8 for ppc64, in fuction elf_ppc64_load prompt "Can't use ramdisk with device tree blob input".
> 
> I don't know why here ramdisk can't together with dtb,and need some help.

The device tree is also specifying initrd (see kexec/fs2dt.c putnode),
so there is 2 initrd specify in that case. The code is a bit rough here,
but I guess this is because there is not yet a valid use case.

> I also have some questions, when I just ./kexe -l vmlinux then ./kexec -e, will jump to second kernel sucessfully,
> 
> but without useful dtb, then device can't init correct. But, when I input ./kexec -l vmlinux --dtb=my.dtb , then
> 
> ./kexec -e, the kernel couldn't work and crash in head_64.S, this problem also make me confused.

It's hard to state with no more details. I guess the device tree blob
you're using is not valid, or contain bad data.

Cheers,
Laurent.

> Thanks
> Regards
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
> 


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2015-01-06  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06  6:44 some questions about elf_ppc64_load liu.song11
2015-01-06  8:37 ` Laurent Dufour [this message]
2015-01-06  9:20   ` liu.song11
2015-01-06 10:00     ` Laurent Dufour
2015-01-08  4:21       ` liu.song11

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=54AB9EAF.2020004@linux.vnet.ibm.com \
    --to=ldufour@linux.vnet.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=liu.song11@zte.com.cn \
    /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