Re: [Xen-devel] Problems running Xen 4.4 on OMAP5432 evm

[Chen Baozi <baozich@xxxxxxxxx>]

On Apr 29, 2014, at 10:11, Kapania, Ashish <akapania@xxxxxx> wrote:

> Thanks Baozi, the printk patch helped. I am now able to see the kernel 
> printk's on the xen console.
> 
> The printk's show that the kernel panics while executing _clktrctrl_write(). 
> I believe clktrctrl is attempting to read from PRCM_MPU registers and that 
> address space is not mapped. Did you see a similar problem ?
> 
> The Kernel log I get:
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
> Xen)
> (XEN) Freed 264kB init memory.
> Booting Linux on physical CPU 0x0
> Linux version 3.11.0-rc3-dirty (a0273866@a0273866-VirtualBox) (gcc version 
> 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 
> - Linaro GCC 2013.03) ) #4 SMP Mon Apr 28 14:30:48 PD
> T 2014
> CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c53c7d
> CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
> Machine: Generic OMAP5 (Flattened Device Tree), model: TI OMAP5 uEVM board
> cma: CMA: reserved 16 MiB at ae800000
> Memory policy: ECC disabled, Data cache writealloc
> On node 0 totalpages: 32512
> free_area_init_node: node 0, pgdat c0833d00, node_mem_map c0da0000
>  Normal zone: 256 pages used for memmap
>  Normal zone: 0 pages reserved
>  Normal zone: 32512 pages, LIFO batch:7
> psci: probing function IDs from device-tree
> OMAP5432 ES2.0
> Unhandled fault: terminal exception (0x002) at 0xfc009300
> Internal error: : 2 [#1] SMP ARM
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper Not tainted 3.11.0-rc3-dirty #4
> task: c07a99c8 ti: c079e000 task.ti: c079e000
> PC is at _clktrctrl_write+0x1c/0x40
> LR is at omap4_clkdm_wakeup+0x18/0x20
> pc : [<c0035a88>]    lr : [<c0035ed8>]    psr: a00001d3
> sp : c079ff30  ip : c0839cd4  fp : c07ab060
> r10: c07ab060  r9 : c0801d90  r8 : c07a6ddc
> r7 : 00000002  r6 : c07b3020  r5 : c0839d1c  r4 : c07b4a00
> r3 : fc009300  r2 : 00001300  r1 : fc008000  r0 : 00000002
> Flags: NzCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment kernel
> Control: 10c53c7d  Table: a800406a  DAC: 00000017
> Process swapper (pid: 0, stack limit = 0xc079e240)
> Stack: (0xc079ff30 to 0xc07a0000)
> ff20:                                     c0035ec0 c0038a74 c07a99c8 c07b4a00
> ff40: c0839d1c c0038aac 0000000f c07b4a00 c0839d1c c0038c6c fc002000 c07a6490
> ff60: c078008c c07463d4 08000000 c074107c c079ff78 c079ff80 00000000 00000000
> ff80: 00000000 00000000 00000000 00000000 00000000 00000001 00000000 00000000
> ffa0: c0665f54 00000001 00000000 c07822ec c07ab188 a800406a 412fc0f2 00000000
> ffc0: 00000000 c073d58c 00000000 00000000 00000000 00000000 00000000 c07822f0
> ffe0: 00000000 10c53c7d c07a650c c07822ec c07ab188 a8008074 00000000 00000000
> [<c0035a88>] (_clktrctrl_write+0x1c/0x40) from [<c0035ed8>] 
> (omap4_clkdm_wakeup+0x18/0x20)
> [<c0035ed8>] (omap4_clkdm_wakeup+0x18/0x20) from [<c0038a74>] 
> (clkdm_wakeup_nolock+0x48/0x68)
> [<c0038a74>] (clkdm_wakeup_nolock+0x48/0x68) from [<c0038aac>] 
> (clkdm_wakeup+0x18/0x2c)
> [<c0038aac>] (clkdm_wakeup+0x18/0x2c) from [<c0038c6c>] 
> (clkdm_complete_init+0xb4/0xf8)
> [<c0038c6c>] (clkdm_complete_init+0xb4/0xf8) from [<c07463d4>] 
> (omap5_init_early+0x58/0x80)
> [<c07463d4>] (omap5_init_early+0x58/0x80) from [<c074107c>] 
> (setup_arch+0x8c8/0x9b8)
> [<c074107c>] (setup_arch+0x8c8/0x9b8) from [<c073d58c>] 
> (start_kernel+0x7c/0x320)
> [<c073d58c>] (start_kernel+0x7c/0x320) from [<a8008074>] (0xa8008074)
> Code: e59fc028 e79c1101 e3510000 0a000006 (e0833002) 
> ---[ end trace 1b75b31a2719ed1c ]---
> Kernel panic - not syncing: Attempted to kill the idle task!

looks like the hwmod & DT issues.

I post my recently boot steps on omap5 with upstream kernel on the wiki.
see: 
http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/OMAP5432_uEVM

Baozi


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