* Problem bringing up Xen 4.4 on omap5432
@ 2014-05-14 2:49 bibin c
2014-05-14 13:54 ` Julien Grall
2014-05-19 10:41 ` bibin c
0 siblings, 2 replies; 3+ messages in thread
From: bibin c @ 2014-05-14 2:49 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 6101 bytes --]
Hello,
I have been trying to bring up xen 4.4 with Linux DOM0 on omap5432, but
have been facing
issue with the same.
I have followed the instructions as mentioned in xen wiki:
http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/OMAP5432_uEVM
Linux kernel 3.12 was used with dtb patched as per the wiki.
With debug enabled, i could see that DOM0 boot fails with Data abort
(Unexpected trap),
What could be going wrong, mentioned below is the UART log:
---------------------------------------------------------------------------------------------------------------------
## Booting kernel from Legacy Image at 90000000 ...
Image Name:
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 688912 Bytes = 672.8 KiB
Load Address: 80200000
Entry Point: 80200000
Verifying Checksum ... OK
## Flattened Device Tree blob at 825f0000
Booting using the fdt blob at 0x825f0000
Loading Kernel Image ... OK
OK
reserving fdt memory region: addr=825f0000 size=5000
Loading Device Tree to feef7000, end feefefff ... OK
Starting kernel ...
- UART enabled -
- CPU 00000000 booting -
- Xen starting in Hyp mode -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
Checking for initrd in /chosen
RAM: 0000000080000000 - 00000000feffffff
MODULE[1]: 00000000feef7000 - 00000000feeff000
MODULE[2]: 00000000a0000000 - 00000000a0a00000
RESVD[0]: 00000000825f0000 - 00000000825f5000
Command line: sync_console console=dtuart dtuart=serial2 debug
Placing Xen at 0x00000000fec00000-0x00000000fee00000
Xen heap: 00000000ee000000-00000000fe000000 (65536 pages)
Dom heap: 454656 pages
Looking for UART console serial2
Xen 4.4.0
(XEN) Xen version 4.4.0 (ubuntu@) (arm-linux-gnueabihf-gcc (crosstool-NG
linaro-1.13.1-4.8-2014.04 - Linaro GCC 4.8-2014.04) 4.8.3 20140401 (pr4
(XEN) Latest ChangeSet:
(XEN) Console output is synchronous.
(XEN) Processor: 412fc0f2: "ARM Limited", variant: 0x2, part 0xc0f, rev 0x2
(XEN) 32-bit Execution:
(XEN) Processor Features: 00001131:00011011
(XEN) Instruction Sets: AArch32 Thumb Thumb-2 ThumbEE Jazelle
(XEN) Extensions: GenericTimer Security
(XEN) Debug Features: 02010555
(XEN) Auxiliary Features: 00000000
(XEN) Memory Model Features: 10201105 20000000 01240000 02102211
(XEN) ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
(XEN) Platform: TI OMAP5
(XEN) Set AuxCoreBoot1 to 00000000fec0004c (0020004c)
(XEN) Set AuxCoreBoot0 to 0x20
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27
(XEN) Using generic timer at 6144 KHz
(XEN) GIC initialization:
(XEN) gic_dist_addr=0000000048211000
(XEN) gic_cpu_addr=0000000048212000
(XEN) gic_hyp_addr=0000000048214000
(XEN) gic_vcpu_addr=0000000048216000
(XEN) gic_maintenance_irq=25
(XEN) GIC: 192 lines, 2 cpus, secure (IID 0000043b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 16 KiB.
(XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
(XEN) Bringing up CPU1
- CPU 00000001 booting -
- Xen starting in Hyp mode -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 1 booted.
(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Populate P2M 0xa8000000->0xb0000000 (1:1 mapping for dom0)
(XEN) Loading kernel from boot module 2
(XEN) CPU0: Unexpected Trap: Data Abort
(XEN) ----[ Xen-4.4.0 arm32 debug=n Tainted: C ]----
(XEN) CPU: 0
(XEN) PC: 0024cb04 gic_route_irq_to_guest+0x144/0x16c
(XEN) CPSR: 600000da MODE:Hypervisor
(XEN) R0: 00000001 R1: 00000029 R2: 00403c08 R3: ffffffff
(XEN) R4: 002bc580 R5: 00000000 R6: 002a7a20 R7: 002bc594
(XEN) R8: 40012000 R9: 2000005a R10:00000001 R11:002a7a7c R12:00000001
(XEN) HYP: SP: 002a799c LR: 0024bb14
(XEN)
(XEN) VTCR_EL2: 80002558
(XEN) VTTBR_EL2: 00010000feef4000
(XEN)
(XEN) SCTLR_EL2: 30cd187f
(XEN) HCR_EL2: 0000000000282835
(XEN) TTBR0_EL2: 00000000fece7000
(XEN)
(XEN) ESR_EL2: 94000021
(XEN) HPFAR_EL2: 0000000000000000
(XEN) HDFAR: ffffffff
(XEN) HIFAR: 00000000
(XEN)
(XEN) Xen stack trace from sp=002a799c:
(XEN) 0024ca98 00000000 002b0054 00000002 002a7ba0 40008698 400086c4
40012000
(XEN) 0024a504 00002000 00000000 002be600 002be614 002bb51c 0024d0b4
002badd0
(XEN) 00000000 40012000 00000000 002602c8 002602d4 00000003 00266d48
002a7a20
(XEN) 0024cb78 00000000 0026a6dc 002badd0 0000000a 00000010 00262e2c
002a7a74
(XEN) 00255950 00000029 00000004 00000001 00267254 400084f0 00000003
00000000
(XEN) 00000009 00000004 080f0000 01000000 0b000000 080f0000 ffffffc3
40020000
(XEN) 00000000 40008698 4fff80b0 002a7ba0 40008000 002602b8 40012000
002a7b3c
(XEN) 0024a8ec 002b1118 00000000 00000000 00000020 00000000 0026b020
00000000
(XEN) 00000000 40012000 00000000 002602c8 002602d4 002601e0 00260198
00000004
(XEN) 00000004 00000030 00000004 00000002 02dc0580 002a7afc 002186cc
00000000
(XEN) 00000004 00000002 0000908f 00004000 4002c000 00001000 40020000
002a7b0c
(XEN) 00219908 00000004 002a7b2c 00000000 00000000 002a7ba0 00000000
0000000f
(XEN) 002a7ba0 00000000 0000000f 000a8000 a8000000 00000000 40012000
002a7eb4
(XEN) 0024b384 00000001 00000000 00000000 00000000 00000000 40037f58
00000000
(XEN) 4003e000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 40020000 00000000 00000000 00000000 00000001 00000000
a8000000
(XEN) 00000000 08000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) Xen call trace:
(XEN) [<0024cb04>] gic_route_irq_to_guest+0x144/0x16c (PC)
(XEN) [<0024bb14>] gic_cpu_mask+0x88/0xc0 (LR)
(XEN) [<0024a8ec>] handle_node+0x8d4/0xe70
(XEN) [<0024b384>] construct_dom0+0x4fc/0x9a8
(XEN) [<00278380>] start_xen+0xba0/0xde4
(XEN) [<0020043c>] paging+0x84/0xc8
Thanks and Regards,
Bibin
[-- Attachment #1.2: Type: text/html, Size: 7992 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Problem bringing up Xen 4.4 on omap5432
2014-05-14 2:49 Problem bringing up Xen 4.4 on omap5432 bibin c
@ 2014-05-14 13:54 ` Julien Grall
2014-05-19 10:41 ` bibin c
1 sibling, 0 replies; 3+ messages in thread
From: Julien Grall @ 2014-05-14 13:54 UTC (permalink / raw)
To: bibin c, xen-devel; +Cc: Chen Baozi
(Adding Chen Baozi)
Hello,
On 05/14/2014 03:49 AM, bibin c wrote:
> Hello,
>
> I have been trying to bring up xen 4.4 with Linux DOM0 on omap5432, but
> have been facing
> issue with the same.
>
> I have followed the instructions as mentioned in xen wiki:
> http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/OMAP5432_uEVM
This wiki page is using Xen unstable, I'm not sure what is the status of
Xen 4.4 on the OMAP. Chen may have more input on it.
> Linux kernel 3.12 was used with dtb patched as per the wiki.
>
> With debug enabled, i could see that DOM0 boot fails with Data abort
> (Unexpected trap),
The fail comes from Xen during DOM0 creation not DOM0 itself.
> (XEN) Xen call trace:
> (XEN) [<0024cb04>] gic_route_irq_to_guest+0x144/0x16c (PC)
> (XEN) [<0024bb14>] gic_cpu_mask+0x88/0xc0 (LR)
> (XEN) [<0024a8ec>] handle_node+0x8d4/0xe70
> (XEN) [<0024b384>] construct_dom0+0x4fc/0x9a8
> (XEN) [<00278380>] start_xen+0xba0/0xde4
> (XEN) [<0020043c>] paging+0x84/0xc8
Can you give a try on Xen unstable to see if you have the same issue?
Regards,
--
Julien Grall
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Problem bringing up Xen 4.4 on omap5432
2014-05-14 2:49 Problem bringing up Xen 4.4 on omap5432 bibin c
2014-05-14 13:54 ` Julien Grall
@ 2014-05-19 10:41 ` bibin c
1 sibling, 0 replies; 3+ messages in thread
From: bibin c @ 2014-05-19 10:41 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 7059 bytes --]
Hello Julien,
Thanks for your reply.
As you mentioned, i went ahead and took the unstable version of xen (4.5),
and the linux kernel version of 3.15-r5.
With the configuration changes mentioned in xen wiki, when i tried to boot,
i still faced the issue.
By debugging using xen_raw_printk(), i could see that boot was getting
stuck in init_hw_breakpoint() in kernel/events/core.c:perf_event_init().
By disabling the configuration CONFIG_PERF_EVENTS, which in turn disables
HAVE_HW_BREAKPOINT, i was able
to get dom0 up on omap5432.
Best Regards,
Bibin
On Wed, May 14, 2014 at 8:19 AM, bibin c <bibinc17@gmail.com> wrote:
> Hello,
>
> I have been trying to bring up xen 4.4 with Linux DOM0 on omap5432, but
> have been facing
> issue with the same.
>
> I have followed the instructions as mentioned in xen wiki:
>
> http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/OMAP5432_uEVM
>
> Linux kernel 3.12 was used with dtb patched as per the wiki.
>
> With debug enabled, i could see that DOM0 boot fails with Data abort
> (Unexpected trap),
>
> What could be going wrong, mentioned below is the UART log:
>
>
> ---------------------------------------------------------------------------------------------------------------------
> ## Booting kernel from Legacy Image at 90000000 ...
> Image Name:
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 688912 Bytes = 672.8 KiB
> Load Address: 80200000
> Entry Point: 80200000
> Verifying Checksum ... OK
> ## Flattened Device Tree blob at 825f0000
> Booting using the fdt blob at 0x825f0000
> Loading Kernel Image ... OK
> OK
> reserving fdt memory region: addr=825f0000 size=5000
> Loading Device Tree to feef7000, end feefefff ... OK
>
> Starting kernel ...
>
> - UART enabled -
> - CPU 00000000 booting -
> - Xen starting in Hyp mode -
> - Zero BSS -
> - Setting up control registers -
> - Turning on paging -
> - Ready -
> Checking for initrd in /chosen
> RAM: 0000000080000000 - 00000000feffffff
>
> MODULE[1]: 00000000feef7000 - 00000000feeff000
> MODULE[2]: 00000000a0000000 - 00000000a0a00000
> RESVD[0]: 00000000825f0000 - 00000000825f5000
>
> Command line: sync_console console=dtuart dtuart=serial2 debug
> Placing Xen at 0x00000000fec00000-0x00000000fee00000
> Xen heap: 00000000ee000000-00000000fe000000 (65536 pages)
> Dom heap: 454656 pages
> Looking for UART console serial2
> Xen 4.4.0
> (XEN) Xen version 4.4.0 (ubuntu@) (arm-linux-gnueabihf-gcc (crosstool-NG
> linaro-1.13.1-4.8-2014.04 - Linaro GCC 4.8-2014.04) 4.8.3 20140401 (pr4
> (XEN) Latest ChangeSet:
> (XEN) Console output is synchronous.
> (XEN) Processor: 412fc0f2: "ARM Limited", variant: 0x2, part 0xc0f, rev 0x2
> (XEN) 32-bit Execution:
> (XEN) Processor Features: 00001131:00011011
> (XEN) Instruction Sets: AArch32 Thumb Thumb-2 ThumbEE Jazelle
> (XEN) Extensions: GenericTimer Security
> (XEN) Debug Features: 02010555
> (XEN) Auxiliary Features: 00000000
> (XEN) Memory Model Features: 10201105 20000000 01240000 02102211
> (XEN) ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
> (XEN) Platform: TI OMAP5
> (XEN) Set AuxCoreBoot1 to 00000000fec0004c (0020004c)
> (XEN) Set AuxCoreBoot0 to 0x20
> (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27
> (XEN) Using generic timer at 6144 KHz
> (XEN) GIC initialization:
> (XEN) gic_dist_addr=0000000048211000
> (XEN) gic_cpu_addr=0000000048212000
> (XEN) gic_hyp_addr=0000000048214000
> (XEN) gic_vcpu_addr=0000000048216000
> (XEN) gic_maintenance_irq=25
> (XEN) GIC: 192 lines, 2 cpus, secure (IID 0000043b).
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Allocated console ring of 16 KiB.
> (XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
> (XEN) Bringing up CPU1
> - CPU 00000001 booting -
> - Xen starting in Hyp mode -
> - Setting up control registers -
> - Turning on paging -
> - Ready -
> (XEN) CPU 1 booted.
> (XEN) Brought up 2 CPUs
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Populate P2M 0xa8000000->0xb0000000 (1:1 mapping for dom0)
> (XEN) Loading kernel from boot module 2
> (XEN) CPU0: Unexpected Trap: Data Abort
> (XEN) ----[ Xen-4.4.0 arm32 debug=n Tainted: C ]----
> (XEN) CPU: 0
> (XEN) PC: 0024cb04 gic_route_irq_to_guest+0x144/0x16c
> (XEN) CPSR: 600000da MODE:Hypervisor
> (XEN) R0: 00000001 R1: 00000029 R2: 00403c08 R3: ffffffff
> (XEN) R4: 002bc580 R5: 00000000 R6: 002a7a20 R7: 002bc594
> (XEN) R8: 40012000 R9: 2000005a R10:00000001 R11:002a7a7c R12:00000001
> (XEN) HYP: SP: 002a799c LR: 0024bb14
> (XEN)
> (XEN) VTCR_EL2: 80002558
> (XEN) VTTBR_EL2: 00010000feef4000
> (XEN)
> (XEN) SCTLR_EL2: 30cd187f
> (XEN) HCR_EL2: 0000000000282835
> (XEN) TTBR0_EL2: 00000000fece7000
> (XEN)
> (XEN) ESR_EL2: 94000021
> (XEN) HPFAR_EL2: 0000000000000000
> (XEN) HDFAR: ffffffff
> (XEN) HIFAR: 00000000
> (XEN)
> (XEN) Xen stack trace from sp=002a799c:
> (XEN) 0024ca98 00000000 002b0054 00000002 002a7ba0 40008698 400086c4
> 40012000
> (XEN) 0024a504 00002000 00000000 002be600 002be614 002bb51c 0024d0b4
> 002badd0
> (XEN) 00000000 40012000 00000000 002602c8 002602d4 00000003 00266d48
> 002a7a20
> (XEN) 0024cb78 00000000 0026a6dc 002badd0 0000000a 00000010 00262e2c
> 002a7a74
> (XEN) 00255950 00000029 00000004 00000001 00267254 400084f0 00000003
> 00000000
> (XEN) 00000009 00000004 080f0000 01000000 0b000000 080f0000 ffffffc3
> 40020000
> (XEN) 00000000 40008698 4fff80b0 002a7ba0 40008000 002602b8 40012000
> 002a7b3c
> (XEN) 0024a8ec 002b1118 00000000 00000000 00000020 00000000 0026b020
> 00000000
> (XEN) 00000000 40012000 00000000 002602c8 002602d4 002601e0 00260198
> 00000004
> (XEN) 00000004 00000030 00000004 00000002 02dc0580 002a7afc 002186cc
> 00000000
> (XEN) 00000004 00000002 0000908f 00004000 4002c000 00001000 40020000
> 002a7b0c
> (XEN) 00219908 00000004 002a7b2c 00000000 00000000 002a7ba0 00000000
> 0000000f
> (XEN) 002a7ba0 00000000 0000000f 000a8000 a8000000 00000000 40012000
> 002a7eb4
> (XEN) 0024b384 00000001 00000000 00000000 00000000 00000000 40037f58
> 00000000
> (XEN) 4003e000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 40020000 00000000 00000000 00000000 00000001 00000000
> a8000000
> (XEN) 00000000 08000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) Xen call trace:
> (XEN) [<0024cb04>] gic_route_irq_to_guest+0x144/0x16c (PC)
> (XEN) [<0024bb14>] gic_cpu_mask+0x88/0xc0 (LR)
> (XEN) [<0024a8ec>] handle_node+0x8d4/0xe70
> (XEN) [<0024b384>] construct_dom0+0x4fc/0x9a8
> (XEN) [<00278380>] start_xen+0xba0/0xde4
> (XEN) [<0020043c>] paging+0x84/0xc8
>
>
> Thanks and Regards,
> Bibin
>
>
[-- Attachment #1.2: Type: text/html, Size: 9185 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-05-19 10:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-05-14 2:49 Problem bringing up Xen 4.4 on omap5432 bibin c
2014-05-14 13:54 ` Julien Grall
2014-05-19 10:41 ` bibin c
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.