Re: [Xen-devel] Boot Xen on Jetson TX2

[Andrii Anisov <andrii_anisov@xxxxxxxx>]

Hello Baoqian,


It looks like vcpu0 of dom0 was not scheduled to run. But I can't 
imagine why this happened.

Please do not miss CC'ing xen-devel mailing list. This will increase a 
probability to get proper suggestions.

On 22.12.17 05:53, Wang, Baoqian wrote:
> I also dumped domain0 info, it shows :
>
>
> VCPU information and callbacks for domain 0:
> (XEN)     VCPU0: CPU0 [has=F] poll=0 upcall_pend=00 upcall_mask=01 
> dirty_cpus={}
> (XEN)     cpu_hard_affinity={0} cpu_soft_affinity={0}
> (XEN)     pause_count=0 pause_flags=0
> (XEN) GICH_LRs (vcpu 0) mask=0
> (XEN) VCPU_LR[0]=0
> (XEN) VCPU_LR[1]=0
> (XEN) VCPU_LR[2]=0
> (XEN) VCPU_LR[3]=0
> (XEN)     No periodic timer
>
>
> There is not periodic timer and the CPU0[has=F], is this the problem?
>
>
> ------------------------------------------------------------------------
> *From:* Wang, Baoqian
> *Sent:* Thursday, December 21, 2017 7:24:02 PM
> *To:* Andrii Anisov
> *Subject:* Re: [Xen-devel] Boot Xen on Jetson TX2
>
> Hi Andrii,
>
>
> Thanks for your reply. I tried your suggestions and got the following 
> messages.  The PC is a0080000 where the kernel image is loaded.  The 
> X0 is a8000000 where dtb is loaded. It seems that vcpu did not even 
> execute the zImage.  Other things looks normal. is it possible 
> something wrong  with the domain0 kernel or the memory address where 
> it is loaded. Any other suggestions? Thank you!
> Baoqian Wang
>
>
> (XEN) *** Dumping Dom0 vcpu#0 state: ***
> (XEN) ----[ Xen-4.9.0  arm64  debug=y   Not tainted ]----
> (XEN) CPU:    0
> (XEN) PC:     00000000a0080000
> (XEN) LR:     0000000000000000
> (XEN) SP_EL0: 0000000000000000
> (XEN) SP_EL1: 0000000000000000
> (XEN) CPSR:   000001c5 MODE:64-bit EL1h (Guest Kernel, handler)
> (XEN)      X0: 00000000a8000000  X1: 0000000000000000  X2: 
> 0000000000000000
> (XEN)      X3: 0000000000000000  X4: 0000000000000000  X5: 
> 0000000000000000
> (XEN)      X6: 0000000000000000  X7: 0000000000000000  X8: 
> 0000000000000000
> (XEN)      X9: 0000000000000000 X10: 0000000000000000 X11: 
> 0000000000000000
> (XEN)     X12: 0000000000000000 X13: 0000000000000000 X14: 
> 0000000000000000
> (XEN)     X15: 0000000000000000 X16: 0000000000000000 X17: 
> 0000000000000000
> (XEN)     X18: 0000000000000000 X19: 0000000000000000 X20: 
> 0000000000000000
> (XEN)     X21: 0000000000000000 X22: 0000000000000000 X23: 
> 0000000000000000
> (XEN)     X24: 0000000000000000 X25: 0000000000000000 X26: 
> 0000000000000000
> (XEN)     X27: 0000000000000000 X28: 0000000000000000  FP: 
> 0000000000000000
> (XEN)
> (XEN)    ELR_EL1: 0000000000000000
> (XEN)    ESR_EL1: 00000000
> (XEN)    FAR_EL1: 0000000000000000
> (XEN)
> (XEN)  SCTLR_EL1: 00c50838
> (XEN)    TCR_EL1: 00000000
> (XEN)  TTBR0_EL1: 0000000000000000
> (XEN)  TTBR1_EL1: 0000000000000000
> (XEN)
> (XEN)   VTCR_EL2: 80043594
> (XEN)  VTTBR_EL2: 0001000275d33000
> (XEN)
> (XEN)  SCTLR_EL2: 30cd183d
> (XEN)    HCR_EL2: 000000008038663f
> (XEN)  TTBR0_EL2: 0000000275cfe000
>
> (XEN)    ESR_EL2: 8200000d
> (XEN)  HPFAR_EL2: 0000000000000000
> (XEN)    FAR_EL2: 00000000a0080000
> (XEN)
> (XEN) Guest stack trace from sp=0:
> (XEN)   Failed to convert stack to physical address
> (XEN) '0' pressed -> dumping Dom0's registers
--

*Andrii Anisov*



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel