From: Julien Grall <julien.grall@linaro.org>
To: Chen Baozi <baozich@gmail.com>
Cc: Xen Developer List <xen-devel@lists.xen.org>
Subject: Re: Problems when creating domU on OMAP5
Date: Tue, 17 Sep 2013 12:54:37 +0100 [thread overview]
Message-ID: <523842FD.4090206@linaro.org> (raw)
In-Reply-To: <20130916134222.GA28300@cbz-workstation>
On 09/16/2013 02:42 PM, Chen Baozi wrote:
> On Mon, Sep 16, 2013 at 09:18:28PM +0800, Chen Baozi wrote:
>> Hi all,
>>
>> I tried to create a domU on OMAP5 today. But it seems there are still some
>> problems to solve before I can successfully creat it.
>>
>> I first cloned Julien's arndale-domU-3.9 branch which mentioned in wiki.
>> Then I modified gic addresses xenvm-4.2.dts to meet OMAP5432 requirement:
>>
>> --- a/arch/arm/boot/dts/xenvm-4.2.dts
>> +++ b/arch/arm/boot/dts/xenvm-4.2.dts
>> @@ -49,13 +49,13 @@
>> reg = <0 0x80000000 0 0x08000000>;
>> };
>>
>> - gic: interrupt-controller@2c001000 {
>> + gic: interrupt-controller@48211000 {
>> compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic";
>> #interrupt-cells = <3>;
>> #address-cells = <0>;
>> interrupt-controller;
>> - reg = <0 0x10481000 0 0x1000>,
>> - <0 0x10482000 0 0x100>;
>> + reg = <0 0x48211000 0 0x1000>,
>> + <0 0x48212000 0 0x1000>;
>> };
>>
>> timer {
>>
>> And make the kernel image as wiki said:
>>
>> $ cat arch/arm/boot/zImage arch/arm/boot/xenvm-4.2.dtb > image
>>
>> Write a config file used by xl like:
>>
>> kernel = "/root/domU/image"
>> memory = "128"
>> name = "domU"
>> vcpus = 1
>> disk = [ 'phy:/dev/loop0,xvda,w' ]
>>
>> Setup loop device:
>>
>> $ losetup /dev/loop0 /root/domU/xen-arm.img
>>
>> which xen-arm.img is the a bootable rootfs.
>>
>> Finally I execute xl to create the domU:
>>
>> $ sudo xl create -f config -d
>> Parsing config from config
>> unable to format domain config as JSON (YAJL:1)
>> [ 80.685264] Failed to unmap pfn:9bce5 rc:-2
>> [ 80.691741] Failed to unmap pfn:9e7da rc:-2
>> [ 80.696310] Failed to unmap pfn:9bce5 rc:-2
>> [ 80.702494] Failed to unmap pfn:9ba57 rc:-2
>> [ 80.706932] Failed to unmap pfn:9bce3 rc:-2
>> [ 80.718394] Failed to unmap pfn:9bce2 rc:-2
>> libxl: error: libxl_device.c:894:device_backend_callback: unable to add device with path /local/domain/0/backend/vbd/1/51712
>> libxl: error: libxl_create.c:932:domcreate_launch_dm: unable to add disk devices
>> libxl: error: libxl_device.c:894:device_backend_callback: unable to remove device with path /local/domain/0/backend/vbd/1/51712
>> libxl: error: libxl.c:1451:devices_destroy_cb: libxl__devices_destroy failed for 1
>> (XEN) mm.c:1092:d0 gnttab_mark_dirty not implemented yet
>>
>
> Besides, after few minutes of executing "xl create" command, there are
> continuous kernel oops message such as:
I suspect an interrupt problem. I have a patch series that should fix
the different issues with the interrupts, but I didn't take time to
rewrite properly :(.
Can you give a try to the following branch (and your patches) on the omap5?
git clone -b interrupts-v1
git://xenbits.xen.org/people/julieng/xen-unstable.git
Thanks,
>
> [ 1009.236697] INFO: rcu_sched self-detected stall on CPU { 0} (t=65130
> jiffies g=582 c=)
> [ 1009.245404] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.11.0-rc3+ #4
> [ 1009.251843] [<c001b5ec>] (unwind_backtrace+0x0/0xf8) from [<c0017b90>] (show_stack+0x1)
> [ 1009.260426] [<c0017b90>] (show_stack+0x10/0x14) from [<c056dcac>] (dump_stack+0x70/0x8)
> [ 1009.268600] [<c056dcac>] (dump_stack+0x70/0x8c) from [<c00b776c>] (rcu_check_callbacks)
> [ 1009.277701] [<c00b776c>] (rcu_check_callbacks+0x340/0x7a8) from [<c005039c>] (update_p)
> [ 1009.287680] [<c005039c>] (update_process_times+0x38/0x64) from [<c008e9a0>] (tick_sche)
> [ 1009.297313] [<c008e9a0>] (tick_sched_handle+0x48/0x54) from [<c008ebe4>] (tick_sched_t)
> [ 1009.306599] [<c008ebe4>] (tick_sched_timer+0x44/0x74) from [<c00658c0>] (__run_hrtimer)
> [ 1009.315624] [<c00658c0>] (__run_hrtimer+0x7c/0x1dc) from [<c0066450>] (hrtimer_interru)
> [ 1009.324917] [<c0066450>] (hrtimer_interrupt+0x104/0x2a0) from [<c0446e48>] (arch_timer)
> [ 1009.334983] [<c0446e48>] (arch_timer_handler_virt+0x28/0x30) from [<c00b1e40>] (handle)
> [ 1009.345485] [<c00b1e40>] (handle_percpu_devid_irq+0x78/0x114) from [<c00ae7b0>] (gener)
> [ 1009.355551] [<c00ae7b0>] (generic_handle_irq+0x20/0x30) from [<c0014db4>] (handle_IRQ+)
> [ 1009.364402] [<c0014db4>] (handle_IRQ+0x38/0x94) from [<c0008670>] (gic_handle_irq+0x28)
> [ 1009.372909] [<c0008670>] (gic_handle_irq+0x28/0x5c) from [<c0573bc4>] (__irq_svc+0x44/)
> [ 1009.381321] Exception stack(0xc0805dd0 to 0xc0805e18)
> [ 1009.386445] 5dc0: 00000001 00000000 00000000 c08108
> [ 1009.394690] 5de0: c0802900 c0802900 c101e900 cbcbfc00 60000113 ce67f600 c101e9b4 c0805c
> [ 1009.402935] 5e00: 60000193 c0805e18 c0095e90 c0470d1c 60000113 ffffffff
> [ 1009.409626] [<c0573bc4>] (__irq_svc+0x44/0x58) from [<c0470d1c>] (enqueue_to_backlog+0)
> [ 1009.418563] [<c0470d1c>] (enqueue_to_backlog+0x148/0x290) from [<c04711d4>] (netif_rx+)
> [ 1009.427503] [<c04711d4>] (netif_rx+0x54/0x154) from [<c03cf738>] (smsc95xx_rx_fixup+0x)
> [ 1009.436272] [<c03cf738>] (smsc95xx_rx_fixup+0xcc/0x22c) from [<c03d2e64>] (usbnet_bh+0)
> [ 1009.445123] [<c03d2e64>] (usbnet_bh+0xbc/0x260) from [<c0049108>] (tasklet_action+0x64)
> [ 1009.453628] [<c0049108>] (tasklet_action+0x64/0xf8) from [<c0048450>] (__do_softirq+0x)
> [ 1009.462481] [<c0048450>] (__do_softirq+0x114/0x290) from [<c0048970>] (irq_exit+0xa0/0)
> [ 1009.470822] [<c0048970>] (irq_exit+0xa0/0xd8) from [<c0014db8>] (handle_IRQ+0x3c/0x94)
> [ 1009.478796] [<c0014db8>] (handle_IRQ+0x3c/0x94) from [<c0008670>] (gic_handle_irq+0x28)
> [ 1009.487304] [<c0008670>] (gic_handle_irq+0x28/0x5c) from [<c0573bc4>] (__irq_svc+0x44/)
> [ 1009.495717] Exception stack(0xc0805f60 to 0xc0805fa8)
> [ 1009.500841] 5f60: 00000001 00000001 00000000 c0810648 c0804000 c088b340 c0804000 c088a4
> [ 1009.509087] 5f80: c088b340 c057d320 c080c554 c0804000 60000093 c0805fa8 c0095ed4 c00150
> [ 1009.517330] 5fa0: 20000013 ffffffff
> [ 1009.520895] [<c0573bc4>] (__irq_svc+0x44/0x58) from [<c0015100>] (arch_cpu_idle+0x20/0)
> [ 1009.529228] [<c0015100>] (arch_cpu_idle+0x20/0x30) from [<c0084d10>] (cpu_startup_entr)
> [ 1009.538356] [<c0084d10>] (cpu_startup_entry+0x78/0x220) from [<c07a37f4>] (start_kerne)
>
> Baozi
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
--
Julien Grall
next prev parent reply other threads:[~2013-09-17 11:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 13:18 Problems when creating domU on OMAP5 Chen Baozi
2013-09-16 13:42 ` Chen Baozi
2013-09-17 11:54 ` Julien Grall [this message]
2013-09-18 2:08 ` Chen Baozi
2013-09-30 8:30 ` Chen Baozi
2013-10-07 12:36 ` Julien Grall
2013-11-07 6:14 ` Chen Baozi
2013-11-07 8:23 ` Ian Campbell
2013-09-17 11:47 ` Julien Grall
2013-09-18 2:06 ` Chen Baozi
2013-09-18 14:48 ` Julien Grall
2013-09-18 16:12 ` Andrii Anisov
2013-09-19 13:39 ` Chen Baozi
2013-09-24 0:39 ` Vaibhav Bedia
2013-09-25 9:12 ` Chen Baozi
2013-09-25 13:39 ` Vaibhav Bedia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=523842FD.4090206@linaro.org \
--to=julien.grall@linaro.org \
--cc=baozich@gmail.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).