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

Re: [Xen-devel] unable start xen in hikey



Hi Konrad,

I have already specified that in my xen.cfg :

options=console=dtuart dom0_mem=512M dom0_max_vcpus=4 conswitch=x dtuart=/smb/uart@f7113000
kernel=Image console=hvc0 root=/dev/mmcblk1p4 rootwait rw
dtb=hi6220-hikey.dtb

Chen,

I am using linux kernel from 96 boards repo:  https://github.com/96boards/linux.git and I compile using this command as below:

make Image -j24 arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts 

There was no dtb file produced after the compilation finished. But i saw a trace log mentioning , make: Nothing to be done for `arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts'.

 Correct me if the make command above is wrong?


Thanks,
Kamenee

On Thu, Aug 18, 2016 at 3:46 PM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
On Wed, Aug 17, 2016 at 06:30:23PM -0400, Kamenee Arumugam wrote:
> Hi Chen,
>
> My previous issue was resolved when i used hi6220-hikey.dtb from this
> source: https://github.com/kuscsik/device-linaro-hikey-kernel. When I
> download linux kernel, there doesn't seems to contain hi6220-hikey.dtb.
>
> But now it got stuck while loading Dom0 and below are log traces:
>
>
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Loading kernel from boot module @ 000000007a037000
> (XEN) Loading ramdisk from boot module @ 000000000ae00000
> (XEN) Allocating 1:1 mappings totalling 512MB for dom0:
> (XEN) BANK[0] 0x00000040000000-0x00000060000000 (512MB)
> (XEN) Grant table range: 0x00000005c00000-0x00000005c54000
> (XEN) Loading zImage from 000000007a037000 to
> 0000000040080000-0000000040ce8c00
> (XEN) Loading dom0 initrd from 000000000ae00000 to
> 0x0000000048200000-0x0000000048a00000
> (XEN) Allocating PPI 16 for event channel interrupt
> (XEN) Loading dom0 DTB to 0x0000000048000000-0x000000004800af11
> (XEN) Scrubbing Free RAM on 1 nodes using 8 CPUs
> (XEN) ..done.
> (XEN) Initial low memory virq threshold set at 0x4000 pages.
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) *** Serial input -> DOM0 (type 'CTRL-x' three times to switch input
> to Xen)
> (XEN) Freed 284kB init memory.
> (XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER4
> (XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER8
> (XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER12
> (XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER16
> (XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> (XEN) d0v1: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> (XEN) d0v2: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> (XEN) d0v3: vGICD: unhandled word write 0xffffffff to ICACTIVER0
>
> It just hang there after the last line above.
> I have looked into those messages " d0v3: vGICD: unhandled word write
> 0xffffffff to ICACTIVER0"  and linux kernel already taking care to ignore
> it. Therefore, I believe this is not contributing to there hang here. Any
> idea on this issue?

It looks like you did not let the kernel use the console so nothing
was printed.

Make sure you have 'console=hvc0' on your Linux line.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.