some questions about elf_ppc64_load

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/01/2015 07:44, liu.song11 at 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 at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
> 




[Index of Archives]     [LM Sensors]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux