From: Julien Grall <julien.grall@citrix.com>
To: Sengul Thomas <thomas.sengul@gmail.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
"xen-arm@lists.xen.org" <xen-arm@lists.xen.org>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: Testing xen-arm on Arndale
Date: Tue, 26 Mar 2013 19:29:11 +0000 [thread overview]
Message-ID: <5151F707.8080704@citrix.com> (raw)
In-Reply-To: <5151C711.5090604@citrix.com>
On 03/26/2013 04:04 PM, Anthony PERARD wrote:
> CC'ing xen-devel, where the ARMv7+ port of Xen is happening.
>
> On 25/03/13 09:46, Sengul Thomas wrote:
>> Hello Anthony,
>> I'm hoping your are the right person to ask about xen-arm on Arndale.
>>
>> I've tried the following wiki to run xen-arm on Arndale and it crashes while booting dom0.
>> http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale
>>
>> Here goes some part of log (attached the full log):
>>
>> (XEN) Guest data abort: Translation fault at level 2
>> (XEN) gva=23c1901c
>> (XEN) gpa=0000000023c1901c
>> (XEN) size=2 sign=0 write=1 reg=0
>> (XEN) eat=0 cm=0 s1ptw=0 dfsc=6
>> (XEN) dom0 IPA 0x0000000023c1901c
>> (XEN) P2M @ 02ffbfc0 mfn:0xbfdfe
>> (XEN) 1ST[0x0] = 0x00000000bfdfd6ff
>> (XEN) 2ND[0x11e] = 0x0000000000000000
>> (XEN) ----[ Xen-4.3-unstable arm32 debug=y Tainted: C ]----
>> (XEN) CPU: 0
>> (XEN) PC: 4000893c
>>
>> Looks like dom0 tried to access at 23c1901c and page fault happens.
>> I've got no idea how to figure out what is going on.
>> Could you tell me any helpful tips to move on further?
It's seems the kernel is unable to start when the zImage is loaded at
0x40007000. If you change this address, both in U-Boot and the DTS, by
0x60000000 the kernel is able to start.
I updated wiki page with the new instructions and the new device tree.
Cheers,
Julien
next prev parent reply other threads:[~2013-03-26 19:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJWjLtp3yQhL1x9L=Lb6zq19Qc0dJwfjarwgd1NxFYNxXfER=g@mail.gmail.com>
2013-03-26 16:04 ` Testing xen-arm on Arndale Anthony PERARD
2013-03-26 19:29 ` Julien Grall [this message]
2013-03-27 0:40 ` Sengul Thomas
2013-03-27 10:48 ` [XenARM] " Stefano Stabellini
2013-03-27 8:23 ` Sengul Thomas
2013-03-27 11:42 ` Sengul Thomas
2013-03-27 11:57 ` Stefano Stabellini
2013-03-28 10:25 ` Sengul Thomas
2013-03-28 12:09 ` Stefano Stabellini
2013-03-29 6:57 ` Sengul Thomas
2013-03-29 12:42 ` Julien Grall
2013-03-29 12:50 ` Stefano Stabellini
2013-03-30 3:40 ` Sengul Thomas
2013-04-01 14:15 ` Julien Grall
2013-04-03 9:28 ` See-Hwan Yoo
2013-04-03 10:52 ` Stefano Stabellini
2013-04-03 11:57 ` See-Hwan Yoo
2013-04-03 13:22 ` Julien Grall
2013-04-04 2:06 ` See-Hwan Yoo
2013-04-04 13:38 ` Julien Grall
2013-04-05 1:26 ` See-Hwan Yoo
2013-04-05 11:34 ` Stefano Stabellini
2013-04-05 13:34 ` Julien Grall
2013-04-03 13:37 ` Stefano Stabellini
2013-04-10 11:44 ` Ian Campbell
2013-07-16 6:33 ` [XenARM] " Giridhar Maruthy
[not found] ` <CAHuqX+GCwz8RhC3AxKKWzF5PKf4MWWqboHnHiqde7GfzpZ+T6w@mail.gmail.com>
2013-07-17 9:39 ` Julien Grall
2013-07-17 12:53 ` Giridhar Maruthy
2013-07-17 16:38 ` Julien Grall
2013-07-18 9:58 ` Giridhar Maruthy
2013-07-18 13:43 ` Giridhar Maruthy
2013-07-18 13:54 ` Julien Grall
2013-07-18 14:22 ` Giridhar Maruthy
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=5151F707.8080704@citrix.com \
--to=julien.grall@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=thomas.sengul@gmail.com \
--cc=xen-arm@lists.xen.org \
--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).