[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: XEN/ARM Cortex-A72: Unable to copy the kernel in the hwdom memory


  • To: "xen-users@xxxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxxx>
  • From: Anda-alexandra Dorneanu <anda-alexandra.dorneanu@xxxxxxx>
  • Date: Wed, 18 Nov 2020 14:56:35 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nxp.com; dmarc=pass action=none header.from=nxp.com; dkim=pass header.d=nxp.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=JqAlpbC1JVCHllav2HKwWTZUHtlz9wenuAWMhZLycU0=; b=W5a5D+ZR1PcduZOMRJ6fiT4mn2d0z5IztQnGjaUP6uwKN+Cptdh3OlT7ypWnJHaVBuBQ/ZfCOEYcCMK26WCwLuUF5m7Qht0/qRXIrOs64itbXxOooMo36hl0oNXRorWemxcZQ0JYaCVsub2NaL28JzpLAfpVJrW4+LeVdNJOj6Gjv6cSFOaLGkoNWb0dfFPU62HvxcQiMYCtBvzbWiWyP+P8liC5gP6ofWfcX2+1AQRbLkvFu0mD79XZw2l3V+GQnJ80q/oh06n9E3WcURlYZIO/i9udecRmB19gGSqUus6AFPwXtpiQf8auvXwv4veGxeXBirl6KmwG3cFXqudAsA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TG0egHChXJCg1GDhgDKF+CU2otzv8kIaFZyXRHxvaf2ulrJiRP/m+OOuVrrhKItwMiUgJOSVj4Rynv0TB5ngiWqTdXnigD5NiiMyQJT+etzRGs1Z1tJoQoD73tinyQfzSaf8mSzznuiIDNNQALXI5tlTdkKI9bGKHlcOrju/EDglLOXDYrs/beyOyV5Vo7tHQPalXFFE67PFCjYxcox6DisbjQ8/bGSeTv0S9+Xl3xNuoeRSU5RPg7TUxMdI94qD5U0oru/N9GzMKlOsa/e7ITRCPsT+/PzBBh3kGshv3caO56DaO1v5Q6PdJBezMalLcJtxTrGeWJzqAygKTXP6yw==
  • Authentication-results: lists.xenproject.org; dkim=none (message not signed) header.d=none;lists.xenproject.org; dmarc=none action=none header.from=nxp.com;
  • Delivery-date: Wed, 18 Nov 2020 14:57:23 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>
  • Thread-index: Ada9uex5MLsM6quPTWK5p+K3MF6HiQ==
  • Thread-topic: XEN/ARM Cortex-A72: Unable to copy the kernel in the hwdom memory

Hi Leo,

> Hi,
>
> I am trying to set up XEN on a ARM Cortex-A72 (NXP LS1028A) and running into 
> some problems here.
> While some of them I could solve on my own, the following error is hard for 
> me to understand and solve.
> I would be grateful for some hints e.g. about some specific nodes in the 
> device tree that I might need to take care of.
>
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Loading Domd0 kernel from boot module @ 0000000081200000
> (XEN) Allocating 1:1 mappings totalling 512MB for dom0:
> (XEN) BANK[0] 0x000000c0000000-0x000000e0000000 (512MB)
> (XEN) Grant table range: 0x00000081000000-0x00000081040000
> (XEN) Allocating PPI 16 for event channel interrupt
> (XEN) Loading zImage from 0000000081200000 to 
> 00000000c0080000-00000000c1597008
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Unable to copy the kernel in the hwdom memory
> (XEN) ****************************************
>
> For me, the memory ranges given look good. Or is there something here I 
> overlooked?
>
> My XEN boot arguments: "console=dtuart dtuart=serial0 dom0_mem=512M 
> dom0_max_vcpus=1 bootscrub=0 vwfi=native sched=null"
> Full boot log is attached (does this work here?).
> If anything else is needed to at least make a best guess what the problem is, 
> let me know.
>
> I would really appreciate the help!
> Thanks & best regards,
> Leo

I encountered the same issue. A possible workaround is to remove the gpu node 
from the dts. 
The issue occurs due to the entire low memory bank being reserved for this 
device.

Hope it helps.

Best regards,
Anda Dorneanu



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.