[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Problem bringing up Xen 4.4 on omap5432

  • To: xen-devel@xxxxxxxxxxxxx
  • From: bibin c <bibinc17@xxxxxxxxx>
  • Date: Mon, 19 May 2014 16:11:54 +0530
  • Delivery-date: Mon, 19 May 2014 10:42:05 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
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@xxxxxxxxx> 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:

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


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

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

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