Hi,
I am using fsl sdk v2.0's kernel, devicetree and hypervisor on t2080qds devkit. Everything is in 64 bit mode. But, I am getting following crash when I boot hypervisor. Without using the hypervisor my kernel boots without any error.
Kernel config : corenet64_fmanv3h_smp (Default from kernel)
Kernel Device tree : t2080qds.dts (Default from kernel)
Hypervisor config : t2080qds/RR_PNNPPH_66_16/hv-2p-lnx-lnx (From hv-config.git)
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at ec700000 ...
Image Name:
Image Type: PowerPC Linux Kernel Image (uncompressed)
Data Size: 551040 Bytes = 538.1 KiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at ec800000
Booting using the fdt blob at 0xec800000
Loading Kernel Image ... OK
Loading Device Tree to 03fe3000, end 03fffb28 ... OK
[0] =======================================
[0] Freescale Hypervisor 1.3-012 ppc64
[0] Hypervisor command line: config-addr=0xfec900000 console=ttyS0,115200
[0] malloc_init: using 12357 KiB at 0x7f2e3af0 - 0x7fef4fff
[0] malloc_init: using 1060 KiB at 0x7fef6000 - 0x7fffefff
[0] dt_read_aliases: Alias pci2 points to non-existent /pcie@ffe260000
[0] assign_callback: device buffer-pool@7 in buffer-pool@7 not found
[0] assign_callback: device buffer-pool@8 in buffer-pool@8 not found
[0] assign_callback: device buffer-pool@9 in buffer-pool@9 not found
[0] assign_callback: device buffer-pool@16 in buffer-pool@16 not found
[0] assign_callback: device buffer-pool@17 in buffer-pool@17 not found
[0] assign_callback: device pci2 in pci2 not found
[0] assign_callback: device rman in rman not found
[0] assign_callback: device /fsl,dpaa/ethernet@16 in dpa-ethernet@16 not found
[0] assign_callback: device /fsl,dpaa/dpa-fman0-oh@1 in dpa-fman0-oh@1 not found
HV> [0] unexpected trap in hypervisor
[0] data tlb miss
[0] NIP 0x004093c8 MSR 0x80001002 LR 0x0040a6c4 ESR 0x00000000 EXC 13
CTR 0x0040a480 CR 0x28424022 XER 0x20000000 DEAR 0x00000000 PIR 0
Prev trap level 0
r00 0x004309c0 r01 0x006e3190 r02 0x0048e880 r03 0x0048ffc0
r04 0x00000005 r05 0x00000004 r06 0x0000003f r07 0x00000008
r08 0x004594a0 r09 0x00000000 r10 0x00007000 r11 0x00000000
r12 0x48424022 r13 0x00479b40 r14 0x0045e5d0 r15 0x0045f220
r16 0x7f30b450 r17 0x80029002 r18 0x14318000 r19 0x00000002
r20 0x7f979510 r21 0x0045cc90 r22 0x00000000 r23 0x00001000
r24 0x0048f8b8 r25 0x0048ffc0 r26 0x004888b8 r27 0x80001002
r28 0x00008000 r29 0x0048ffc0 r30 0x7f326f10 r31 0x00000100
[0] sp 6e3190 6e3250 12 6e3240 1000000deadbeef
[0] Traceback: 0x7f2e3e9c 0x48424022006824c0 0x0045f21c 0x4842402200685abc 0x284220440047e87c 0x220020820047325c
0x0045da24 0x24002023fffffffc 0xfffffffffffffffc
Hello Ronak Desai,
According to the log, it seems that you didn't deploy images and configure Hypervisor command line correctly, please refer to the following.
uImage(linux):0xE8020000-0xE87FFFFF
fsl-image-core-t2080qds.ext2.gz.u-boot(rootfs): 0xE9300000-0xEBEFFFFF
hv.uImage: 0xE8700000-0xE87FFFFF
uImage-t2080qds.dtb(linux dtb):0xE8800000-0xE92FFFFF
hv-2p-lnx-lnx.dtb(hv dtb): 0xE8900000-0xE89FFFFF
=>setenv bootargs config-addr=0xfe8900000 console=ttyS0,115200
=>setenv bootcmd 'bootm 0xfe8700000 - 0xfe8800000'
Have a great day,
Yiping
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------