From: Stefano Stabellini <sstabellini@kernel.org>
To: Roman Shaposhnik <roman@zededa.com>
Cc: xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>,
Stefano Stabellini <stefano.stabellini@xilinx.com>
Subject: Re: [Xen-devel] REGRESSION: Xen 4.13 RC5 fails to bootstrap Dom0 on ARM
Date: Mon, 16 Dec 2019 14:43:48 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.1912161443370.13474@sstabellini-ThinkPad-T480s> (raw)
In-Reply-To: <CAMmSBy8Zh00tebTvz=__GDv478++b-2t4248YnkH0W9DVgqKbw@mail.gmail.com>
Thanks for the report, I'll give it a look!
On Mon, 16 Dec 2019, Roman Shaposhnik wrote:
> Hi!
>
> it appears that something has broken in 4.13 RC5 so that
> I'm now getting the following on ARM (full logs are attached).
>
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Failed to allocate requested dom0 memory. 672MB unallocated
> (XEN) ****************************************
>
> My GRUB boot sequence hasn't changed:
>
> xen_hypervisor /boot/xen.efi console=dtuart dom0_mem=1024M,max:1024M
> dom0_max_vcpus=1 dom0_vcpus_pin
> xen_module /boot/kernel console=hvc0 root=(hd1,gpt1)/rootfs.img text
> devicetree (hd1,gpt4)/eve.dtb
> xen_module (hd1,gpt1)/initrd.img
>
> In fact, if I use Xen 4.12 instead of 4.13 -- everything seems to work
> as it used to.
>
> Thanks,
> Roman.
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-16 22:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 20:12 [Xen-devel] REGRESSION: Xen 4.13 RC5 fails to bootstrap Dom0 on ARM Roman Shaposhnik
2019-12-16 22:43 ` Stefano Stabellini [this message]
2019-12-17 2:55 ` Stefano Stabellini
2019-12-17 4:39 ` Roman Shaposhnik
2019-12-17 11:30 ` Julien Grall
2019-12-17 18:30 ` Stefano Stabellini
2019-12-17 18:33 ` Roman Shaposhnik
2019-12-17 19:25 ` Stefano Stabellini
2019-12-18 0:04 ` Roman Shaposhnik
2019-12-18 1:51 ` Stefano Stabellini
2019-12-18 2:56 ` Roman Shaposhnik
2019-12-18 7:36 ` Roman Shaposhnik
2019-12-18 11:50 ` Julien Grall
2019-12-18 17:03 ` Roman Shaposhnik
2019-12-18 22:17 ` Julien Grall
2019-12-19 0:28 ` Roman Shaposhnik
2019-12-19 7:58 ` Julien Grall
2019-12-20 0:01 ` Stefano Stabellini
2019-12-20 8:21 ` Julien Grall
2019-12-21 1:37 ` Roman Shaposhnik
2019-12-29 18:01 ` Julien Grall
2019-12-31 5:14 ` Roman Shaposhnik
2019-12-31 22:48 ` Roman Shaposhnik
2020-01-01 13:26 ` Julien Grall
2020-01-06 18:13 ` Stefano Stabellini
2019-12-18 13:02 ` Julien Grall
2019-12-18 12:56 ` Julien Grall
2019-12-18 17:09 ` Roman Shaposhnik
2019-12-18 22:40 ` Julien Grall
2019-12-17 18:31 ` Roman Shaposhnik
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=alpine.DEB.2.21.1912161443370.13474@sstabellini-ThinkPad-T480s \
--to=sstabellini@kernel.org \
--cc=roman@zededa.com \
--cc=stefano.stabellini@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.