From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: Dom0 kernel for Xen4.6 on R-Car H2 (LAGER) Date: Mon, 19 Oct 2015 13:44:16 +0100 Message-ID: <5624E5A0.4030906@citrix.com> References: <5a0aab3289b446c1877348268f2afc39@DEBEMAIL001.kostal.int> <1444919269.1607.95.camel@citrix.com> <0234f7a69dc647fa80b6d16a8f5a7fc8@DEBEMAIL001.kostal.int> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0234f7a69dc647fa80b6d16a8f5a7fc8@DEBEMAIL001.kostal.int> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Ferger, Max" , Ian Campbell , "xen-devel@lists.xen.org" Cc: Oleksandr Tyshchenko , Iurii Konovalenko List-Id: xen-devel@lists.xenproject.org Hello Max, On 19/10/15 13:09, Ferger, Max wrote: > - UART enabled - > - CPU 00000000 booting - > - Xen starting in Hyp mode - > - Zero BSS - > - Setting up control registers - > - Turning on paging - > - Ready - > (XEN) Checking for initrd in /chosen > (XEN) RAM: 0000000040000000 - 000000007fffffff > (XEN) RAM: 0000000140000000 - 00000001ffffffff > (XEN) > (XEN) MODULE[0]: 00000000407f2000 - 00000000407fd000 Device Tree > (XEN) MODULE[1]: 0000000072000000 - 00000000722fd158 Kernel > (XEN) MODULE[2]: 0000000074000000 - 0000000074002559 XSM > (XEN) RESVD[0]: 0000000070f00000 - 0000000070f0b000 > (XEN) RESVD[1]: 000000007ff9a000 - 000000007ff9a120 > (XEN) RESVD[2]: 00000000407f2000 - 00000000407fd000 > (XEN) > (XEN) Command line: console=dtuart dtuart=/soc/serial@e6c50000 dom0_mem=1G > (XEN) Placing Xen at 0x000000007fc00000-0x000000007fe00000 > (XEN) Update BOOTMOD_XEN from 0000000090000000-000000009011b701 => 000000007fc00000-000000007fd1b701 > (XEN) Xen heap: 00000001f8000000-0000000200000000 (32768 pages) > (XEN) Dom heap: 1015808 pages > (XEN) Domain heap initialised > (XEN) Platform: Renesas R-Car Gen2 > (XEN) Looking for dtuart at "/soc/serial@e6c50000", options "" > (XEN) Unable to find device "/soc/serial@e6c50000" You provided the wrong path to the UART. Xen will use earlyprintk rather than the console. If you use the upstream DT (arch/arm/boot/dts/r8a7790-lager.dts), it contains a property stdout-path in the chosen node. As Xen is able to understand it, you can drop "dtuart=/soc/...." and only keep console=dtuart on the command line. [...] > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Loading kernel from boot module @ 0000000072000000 > (XEN) Allocating 1:1 mappings totalling 1024MB for dom0: > (XEN) BANK[0] 0x00000048000000-0x00000070000000 (640MB) > (XEN) BANK[1] 0x000001d8000000-0x000001f0000000 (384MB) > (XEN) Grant table range: 0x0000007fc00000-0x0000007fc72000 > (XEN) DT: no ranges; cannot enumerate > (XEN) Device tree generation failed (-22). Can you turn on DEBUG_DT in xen/arch/arm/domain_build.c (see patch [1]) and paste the log here? Also, can you send the device tree you are using? Regards, [1] diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c index 0c3441a..bdb8b1f 100644 --- a/xen/arch/arm/domain_build.c +++ b/xen/arch/arm/domain_build.c @@ -40,7 +40,7 @@ static void __init parse_dom0_mem(const char *s) } custom_param("dom0_mem", parse_dom0_mem); -//#define DEBUG_DT +#define DEBUG_DT #ifdef DEBUG_DT # define DPRINT(fmt, args...) printk(XENLOG_DEBUG fmt, ##args) -- Julien Grall