xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Gihun Jung <gihun.jung@gmail.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Can not boot Dom0 when using Anthony's new XenARM source for Arndale.
Date: Tue, 26 Mar 2013 19:35:22 +0000	[thread overview]
Message-ID: <5151F87A.1020404@citrix.com> (raw)
In-Reply-To: <CALnjYg71h+cuEWOm+D18zywprwOxHv8NDnuNrtGOJ49=JC70OQ@mail.gmail.com>

On 03/25/2013 10:35 AM, Gihun Jung wrote:

> Hi Xen Developers,

Hello,

 
> I had tested new XenARM for Arndale board that is updated in Anthony's
> tree from 2 days ago.
> 
> I expected that will be working. But, I can not boot Dom0 Kernel.
> I used kernel and XenARM both are from Xen
> Wiki(http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale).
> 
> It (seems) stopped after "(XEN) Freed 212kB init memory" message. When
> I changed serial input to Xen ('ctrl-a' 3 times) and dump state, it
> show we are in Undefined processor mode or sometimes in Abort mode.
> 
> Does anyone else have the same problem? or Am I doing something wrong?

I have updated the wiki page and the linux git.
Could you retry with the new instructions? If you still have this issue,
could you send serial output?

Thanks,

Julien

  reply	other threads:[~2013-03-26 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 10:35 Can not boot Dom0 when using Anthony's new XenARM source for Arndale Gihun Jung
2013-03-26 19:35 ` Julien Grall [this message]
2013-03-27  3:03   ` Chen Baozi
2013-03-27 12:21     ` Julien Grall
2013-03-27  8:15   ` Gihun Jung
2013-03-27 11:53     ` Julien Grall
  -- strict thread matches above, loose matches on Subject: below --
2013-03-25 10:43 Gihun Jung

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=5151F87A.1020404@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=gihun.jung@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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).