Re: Xen on (RELEASE-4.4.0) crashed when booting on Cubieboard2

[Julien Grall <julien.grall@linaro.org>]

Hello,

On 06/04/14 03:44, duqi wrote:
>> Why do you compile the DTB into Xen? I guess you have hardcoded the
>> chosen node... if so can you paste the content here?
>
> We are worried about our memory layout when loading xen and dom0 kernel.

The memory layout on the wiki page is working on the cubieboard with 
128Mb, so you don't have to worry.

> For simplicity, we compiled dtb into xen. Also we compiled ramdisk into kernel image for the same reason.

I still don't get why you are compiling the DTB into Xen ... it's 
error-prone as you have to hardcode Xen nodes in the device-tree.

> We will test the stand alone dtb load progress soon.

Please try the instructions on the wiki page before trying fancy things...

> / {
> 	model = "Cubietech Cubieboard2";
> 	compatible = "cubietech,cubieboard2", "allwinner,sun7i-a20";
> 	
>      chosen {
>          bootargs = "dom0_mem=128M sync_console console=dtuart dtuart=serial0";
>          xen,dom0-bootargs = "console=hvc0,115200n8 debug ignore_loglevel rw earlyprintk=xen clk_ignore_unused init=/init";
>          modules {
>              module@0 {
>                  compatible = "xen,linux-zimage", "xen,multiboot-module";
>                  reg = <0x7f600000 0xf00000>;
>              };
>              module@1 {
>                  compatible = "xen,linux-initrd", "xen,multiboot-module";
>                  reg = <0x60000000 0x6000000>;
>                  linux,initrd-start = <0x60000000>;
>                  linux,initrd-end = <0x66000000>;

This properties should not be there ... and I though you compiled your 
ramdisk with the kernel, right?

>              };
>          };
>      };
>
>          hypervisor {
>                  compatible = "xen,xen-4.2", "xen,xen";
>                  reg = <0xb0000000 0x20000>;
>                  interrupts = <1 15 0xf08>;
>          };

This node is not necessary.

To repeat what I said at the beginning of the mail, compiling the DTB in 
Xen is *NOT* the solution for debugging. The modules nodes may differ 
because you didn't load you kernel in the right place ... or the initrd 
is not loaded.

Regards,

-- 
Julien Grall