From: Julien Grall <julien.grall@arm.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
baozich@gmail.com, WeiLiu <wei.liu2@citrix.com>
Subject: Re: Frequent reports about Xen unstable hanging on ARM boots
Date: Tue, 15 Mar 2016 18:37:43 +0000 [thread overview]
Message-ID: <56E85677.2050604@arm.com> (raw)
In-Reply-To: <5BFA3B79-F43D-4E3D-97A7-D7A8427544C7@gmail.com>
(CC Chen for the omap port)
Hi Lars,
On 15/03/16 10:56, Lars Kurth wrote:
> Folks,
>
> I just noticed a cluster of issues related to Xen unstable hanging on various ARM boards. See
> * http://xenproject.org/help/questions-and-answers/dra7-j6-evm-xen-booting-issue.html
Xen seems to be stuck just after bringing up the secondary CPU. This
would require further debug to find where Xen is stuck.
I don't have the board but I'm happy to give advice on which part to focus.
> * http://xenproject.org/help/questions-and-answers/problem-with-dom0.html
> * http://xenproject.org/help/questions-and-answers/running-xen-on-omap5.html
"(XEN) Freed 280kB init memory" is the last message printed by Xen
before DOM0 is booting.
At this stage, the problem is usually specific to the board. I've looked
at the wiki page, it is recommended to use upstream but doesn't provide
a version which is known to work. Chen, do you remember which version of
Linux is supposed to work on this board?
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-15 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 10:56 Frequent reports about Xen unstable hanging on ARM boots Lars Kurth
2016-03-15 18:37 ` Julien Grall [this message]
2016-03-16 9:05 ` Chen Baozi
2016-03-16 21:18 ` Lars Kurth
2016-03-16 21:57 ` Paul Sujkov
2016-03-18 17:20 ` Paul Sujkov
2016-03-18 17:36 ` Юрій Коноваленко
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=56E85677.2050604@arm.com \
--to=julien.grall@arm.com \
--cc=baozich@gmail.com \
--cc=lars.kurth.xen@gmail.com \
--cc=stefano.stabellini@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).