From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>, xen-devel@lists.xen.org
Cc: kevin.tian@intel.com, jun.nakajima@intel.com, jbeulich@suse.com
Subject: Re: Xen on Intel Atom E3815: crash, no output
Date: Tue, 1 Aug 2017 10:38:21 +0100 [thread overview]
Message-ID: <66c1a4df-d534-97e3-febb-e67a2aa0986a@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1707311627410.22381@sstabellini-ThinkPad-X260>
On 01/08/17 00:39, Stefano Stabellini wrote:
> Hi all,
>
> I noticed that Xen does not boot on Intel Atom E3815. The system is a
> Dell Edge Gateway 3003:
>
> http://i.dell.com/sites/doccontent/shared-content/data-sheets/en/Documents/Dell_Edge_Gateway_3000_Series_spec_sheet.pdf?newtab=true
>
> Grub2 loads Xen and Dom0, but no output comes out of Xen. After the
> "Loading" messages from Grub2, Xen doesn't manage to print even a single
> character and the system obviously crashes, but I don't know why because
> there is no output. Before you ask, no I don't have a serial on the
> system.
>
> I tried to pass console=vga vga=text-80x25 and console=vga vga=ask, but
> I still got nothing.
>
> Do you have any ideas how to get some output on the screen? Do you know
> how to get Xen to boot successfully?
Sorry, but you are going to have to do some debugging. If you can't get
serial, then you need to start with this:
mov $'A, 0xb8000
scattered around head.S
Do you know whether you are booting MB1, MB2 or MB2+EFI? Swapping that
around at the grub level might be the first step.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-08-01 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 23:39 Xen on Intel Atom E3815: crash, no output Stefano Stabellini
2017-08-01 3:10 ` Tian, Kevin
2017-08-01 6:52 ` Alexey G
2017-08-01 9:38 ` Andrew Cooper [this message]
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=66c1a4df-d534-97e3-febb-e67a2aa0986a@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=sstabellini@kernel.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).