[BUG] Xen build for RCAR failing

[BUG] Xen build for RCAR failing

[Manikandan Chockalingam (RBEI/ECF3)]

[-- Attachment #1: Type: text/plain, Size: 4630 bytes --]

Hello Team,

I am trying to build xen hypervisor for RCAR and following the https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X steps.

But am facing the following issues

1.      SRC_URI="http://v3.sk/~lkundrak/dev86/archive/Dev86src-${PV}.tar.gz in recipes-extended/dev86/dev86_0.16.20.bb is not accesible

Modification done: SRC_URI=https://src.fedoraproject.org/lookaside/extras/dev86/Dev86src-0.16.20.tar.gz/567cf460d132f9d8775dd95f9208e49a/Dev86src-${PV}.tar.gz<https://src.fedoraproject.org/lookaside/extras/dev86/Dev86src-0.16.20.tar.gz/567cf460d132f9d8775dd95f9208e49a/Dev86src-$%7bPV%7d.tar.gz>

2.      LIC_FILES_CHKSUM changed in recipes-extended/xen/xen.inc

3.      QA Issue: xen: Files/directories were installed but not shipped in any package:

/usr/bin/vchan-socket-proxy

  /usr/sbin/xenmon

  /usr/sbin/xenhypfs

  /usr/lib/libxenfsimage.so.4.14.0

  /usr/lib/libxenhypfs.so.1

  /usr/lib/libxenfsimage.so

  /usr/lib/libxenhypfs.so.1.0

  /usr/lib/libxenfsimage.so.4.14

  /usr/lib/libxenhypfs.so

  /usr/lib/pkgconfig

  /usr/lib/xen/bin/depriv-fd-checker

  /usr/lib/pkgconfig/xenlight.pc

  /usr/lib/pkgconfig/xenguest.pc

  /usr/lib/pkgconfig/xenhypfs.pc

  /usr/lib/pkgconfig/xlutil.pc

  /usr/lib/pkgconfig/xentoolcore.pc

  /usr/lib/pkgconfig/xentoollog.pc

  /usr/lib/pkgconfig/xenstore.pc

  /usr/lib/pkgconfig/xencall.pc

  /usr/lib/pkgconfig/xencontrol.pc

  /usr/lib/pkgconfig/xendevicemodel.pc

  /usr/lib/pkgconfig/xenstat.pc

  /usr/lib/pkgconfig/xengnttab.pc

  /usr/lib/pkgconfig/xenevtchn.pc

  /usr/lib/pkgconfig/xenvchan.pc

  /usr/lib/pkgconfig/xenforeignmemory.pc

  /usr/lib/xenfsimage/fat/fsimage.so

  /usr/lib/xenfsimage/iso9660/fsimage.so

  /usr/lib/xenfsimage/reiserfs/fsimage.so

  /usr/lib/xenfsimage/ufs/fsimage.so

  /usr/lib/xenfsimage/ext2fs-lib/fsimage.so

  /usr/lib/xenfsimage/zfs/fsimage.so

Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.

xen: 32 installed and not shipped files. [installed-vs-shipped]

ERROR: xen-unstable+gitAUTOINC+be63d9d47f-r0 do_package: Fatal QA errors found, failing task.

ERROR: xen-unstable+gitAUTOINC+be63d9d47f-r0 do_package: Function failed: do_package

ERROR: Logfile of failure stored in: /home/manikandan/yocto_2.19/build/build/tmp/work/aarch64-poky-linux/xen/unstable+gitAUTOINC+be63d9d47f-r0/temp/log.do_package.17889

ERROR: Task 13 (/home/manikandan/yocto_2.19/build/meta-virtualization/recipes-extended/xen/xen_git.bb, do_package) failed with exit code '1'

Can you please let me know is there any update needs to be done in the build steps mentioned in the link? If not, can you please let me know how I can overcome this issues and build a hypervisor image for RCAR?

Thanks in Advance. My build configuration  is as follows.

Build Configuration:
BB_VERSION        = "1.30.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "aarch64-poky-linux"
MACHINE           = "salvator-x"
DISTRO            = "poky"
DISTRO_VERSION    = "2.1.2"
TUNE_FEATURES     = "aarch64 cortexa57-cortexa53"
TARGET_FPU        = ""
SOC_FAMILY        = "rcar-gen3:r8a7795"
meta
meta-poky
meta-yocto-bsp    = "tmp:cca8dd15c8096626052f6d8d25ff1e9a606104a3"
meta-rcar-gen3    = "tmp:95cb48ba09bc7e55fd549817e3e26723409e68d5"
meta-linaro-toolchain
meta-optee        = "tmp:2f51d38048599d9878f149d6d15539fb97603f8f"
meta-oe           = "tmp:55c8a76da5dc099a7bc3838495c672140cedb78e"
meta-virtualization = "morty:6249631f59ad6ee3dc93762de49fc4b443d99abc"
meta-selinux      = "jethro:4c75d9cbcf1d75043c7c5ab315aa383d9b227510"
meta-networking
meta-python       = "tmp:55c8a76da5dc099a7bc3838495c672140cedb78e"
meta-rcar-gen3-xen = "master:60699c631d541aeeaebaeec9a087efed9385ee42"


Mit freundlichen Grüßen / Best regards

Chockalingam Manikandan

ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | Manikandan.Chockalingam@in.bosch.com<mailto:Manikandan.Chockalingam@in.bosch.com>

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner,
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller
​

[-- Attachment #2: Type: text/html, Size: 19858 bytes --]

Re: [BUG] Xen build for RCAR failing

[Oleksandr Andrushchenko]

On 7/7/20 10:58 AM, Manikandan Chockalingam (RBEI/ECF3) wrote:
>
> Hello Team,
>
> I am trying to build xen hypervisor for RCAR and following the https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X steps.
>
> But am facing the following issues
>
> 1.SRC_URI="http://v3.sk/~lkundrak/dev86/archive/Dev86src-${PV}.tar.gz in recipes-extended/dev86/dev86_0.16.20.bb is not accesible
>
> *Modification done:*SRC_URI=https://src.fedoraproject.org/lookaside/extras/dev86/Dev86src-0.16.20.tar.gz/567cf460d132f9d8775dd95f9208e49a/Dev86src-${PV}.tar.gz <https://src.fedoraproject.org/lookaside/extras/dev86/Dev86src-0.16.20.tar.gz/567cf460d132f9d8775dd95f9208e49a/Dev86src-$%7bPV%7d.tar.gz>
>
You can try what we use [1]. And the issue you are facing is rather Yocto related, not R-Car specific, IMO

[1] https://github.com/xen-troops/meta-xt-prod-devel/blob/master/recipes-domd/domd-image-weston/files/meta-xt-prod-extra/recipes-extended/dev86/dev86_%25.bbappend

Re: [BUG] Xen build for RCAR failing

[Bertrand Marquis]

> On 7 Jul 2020, at 08:58, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Team,
>  
> I am trying to build xen hypervisor for RCAR and following the https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X steps.
>  
> But am facing the following issues
> 1.      SRC_URI="http://v3.sk/~lkundrak/dev86/archive/Dev86src-${PV}.tar.gz in recipes-extended/dev86/dev86_0.16.20.bb is not accesible
> Modification done: SRC_URI=https://src.fedoraproject.org/lookaside/extras/dev86/Dev86src-0.16.20.tar.gz/567cf460d132f9d8775dd95f9208e49a/Dev86src-${PV}.tar.gz
> 2.      LIC_FILES_CHKSUM changed in recipes-extended/xen/xen.inc
> 3.      QA Issue: xen: Files/directories were installed but not shipped in any package:
> /usr/bin/vchan-socket-proxy
>   /usr/sbin/xenmon
>   /usr/sbin/xenhypfs
>   /usr/lib/libxenfsimage.so.4.14.0
>   /usr/lib/libxenhypfs.so.1
>   /usr/lib/libxenfsimage.so
>   /usr/lib/libxenhypfs.so.1.0
>   /usr/lib/libxenfsimage.so.4.14
>   /usr/lib/libxenhypfs.so
>   /usr/lib/pkgconfig
>   /usr/lib/xen/bin/depriv-fd-checker
>   /usr/lib/pkgconfig/xenlight.pc
>   /usr/lib/pkgconfig/xenguest.pc
>   /usr/lib/pkgconfig/xenhypfs.pc
>   /usr/lib/pkgconfig/xlutil.pc
>   /usr/lib/pkgconfig/xentoolcore.pc
>   /usr/lib/pkgconfig/xentoollog.pc
>   /usr/lib/pkgconfig/xenstore.pc
>   /usr/lib/pkgconfig/xencall.pc
>   /usr/lib/pkgconfig/xencontrol.pc
>   /usr/lib/pkgconfig/xendevicemodel.pc
>   /usr/lib/pkgconfig/xenstat.pc
>   /usr/lib/pkgconfig/xengnttab.pc
>   /usr/lib/pkgconfig/xenevtchn.pc
>   /usr/lib/pkgconfig/xenvchan.pc
>   /usr/lib/pkgconfig/xenforeignmemory.pc
>   /usr/lib/xenfsimage/fat/fsimage.so
>   /usr/lib/xenfsimage/iso9660/fsimage.so
>   /usr/lib/xenfsimage/reiserfs/fsimage.so
>   /usr/lib/xenfsimage/ufs/fsimage.so
>   /usr/lib/xenfsimage/ext2fs-lib/fsimage.so
>   /usr/lib/xenfsimage/zfs/fsimage.so
> Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
> xen: 32 installed and not shipped files. [installed-vs-shipped]
> ERROR: xen-unstable+gitAUTOINC+be63d9d47f-r0 do_package: Fatal QA errors found, failing task.
> ERROR: xen-unstable+gitAUTOINC+be63d9d47f-r0 do_package: Function failed: do_package
> ERROR: Logfile of failure stored in: /home/manikandan/yocto_2.19/build/build/tmp/work/aarch64-poky-linux/xen/unstable+gitAUTOINC+be63d9d47f-r0/temp/log.do_package.17889
> ERROR: Task 13 (/home/manikandan/yocto_2.19/build/meta-virtualization/recipes-extended/xen/xen_git.bb, do_package) failed with exit code '1'

The configuration from the page is using a rather old release of Yocto.
I would suggest to switch to dunfell which will use xen 4.12.

Current master status of Yocto is not building at the moment.
Christopher Clark has done some work on it here [1] in meta-virtualization but this is not merged yet.

If you are trying to build Xen master by modifying a recipe you will have issues as some things have been added like hypfs which are creating the issues you see when Yocto is checking that everything was installed.

Bertrand

[1] https://lists.yoctoproject.org/g/meta-virtualization/message/5495

RE: [BUG] Xen build for RCAR failing

[Manikandan Chockalingam (RBEI/ECF3)]

Hello Oleksandr Andrushchenko,

Thanks for your quick response. I am using the yocto version[yocto_2.19] mentioned in the link. Still I face the issue.

Mit freundlichen Grüßen / Best regards

 Chockalingam Manikandan

ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | Manikandan.Chockalingam@in.bosch.com

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner, 
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller

-----Original Message-----
From: Oleksandr Andrushchenko <Oleksandr_Andrushchenko@epam.com> 
Sent: Tuesday, July 7, 2020 1:42 PM
To: Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com>; xen-devel@lists.xen.org
Subject: Re: [BUG] Xen build for RCAR failing


On 7/7/20 10:58 AM, Manikandan Chockalingam (RBEI/ECF3) wrote:
>
> Hello Team,
>
> I am trying to build xen hypervisor for RCAR and following the https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X steps.
>
> But am facing the following issues
>
> 1.SRC_URI="http://v3.sk/~lkundrak/dev86/archive/Dev86src-${PV}.tar.gz in recipes-extended/dev86/dev86_0.16.20.bb is not accesible
>
> *Modification done:*SRC_URI=https://src.fedoraproject.org/lookaside/extras/dev86/Dev86src-0.16.20.tar.gz/567cf460d132f9d8775dd95f9208e49a/Dev86src-${PV}.tar.gz <https://src.fedoraproject.org/lookaside/extras/dev86/Dev86src-0.16.20.tar.gz/567cf460d132f9d8775dd95f9208e49a/Dev86src-$%7bPV%7d.tar.gz>
>
You can try what we use [1]. And the issue you are facing is rather Yocto related, not R-Car specific, IMO

[1] https://github.com/xen-troops/meta-xt-prod-devel/blob/master/recipes-domd/domd-image-weston/files/meta-xt-prod-extra/recipes-extended/dev86/dev86_%25.bbappend

RE: [BUG] Xen build for RCAR failing

[Manikandan Chockalingam (RBEI/ECF3)]

Hello Bertrand,

Thanks for your quick response. I tired switching to dunfell branch and build gives parse error as below.

bitbake core-image-weston
ERROR: ParseError in /home/manikandan/yocto_2.19/build/meta-virtualization/classes/: not a BitBake file

Is there any additional changes required here?

Mit freundlichen Grüßen / Best regards

 Chockalingam Manikandan

ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | Manikandan.Chockalingam@in.bosch.com

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner, 
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller


-----Original Message-----
From: Bertrand Marquis <Bertrand.Marquis@arm.com> 
Sent: Tuesday, July 7, 2020 2:27 PM
To: Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com>
Cc: xen-devel@lists.xen.org; nd <nd@arm.com>
Subject: Re: [BUG] Xen build for RCAR failing



> On 7 Jul 2020, at 08:58, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Team,
>  
> I am trying to build xen hypervisor for RCAR and following the https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X steps.
>  
> But am facing the following issues
> 1.      SRC_URI="http://v3.sk/~lkundrak/dev86/archive/Dev86src-${PV}.tar.gz in recipes-extended/dev86/dev86_0.16.20.bb is not accesible
> Modification done: SRC_URI=https://src.fedoraproject.org/lookaside/extras/dev86/Dev86src-0.16.20.tar.gz/567cf460d132f9d8775dd95f9208e49a/Dev86src-${PV}.tar.gz
> 2.      LIC_FILES_CHKSUM changed in recipes-extended/xen/xen.inc
> 3.      QA Issue: xen: Files/directories were installed but not shipped in any package:
> /usr/bin/vchan-socket-proxy
>   /usr/sbin/xenmon
>   /usr/sbin/xenhypfs
>   /usr/lib/libxenfsimage.so.4.14.0
>   /usr/lib/libxenhypfs.so.1
>   /usr/lib/libxenfsimage.so
>   /usr/lib/libxenhypfs.so.1.0
>   /usr/lib/libxenfsimage.so.4.14
>   /usr/lib/libxenhypfs.so
>   /usr/lib/pkgconfig
>   /usr/lib/xen/bin/depriv-fd-checker
>   /usr/lib/pkgconfig/xenlight.pc
>   /usr/lib/pkgconfig/xenguest.pc
>   /usr/lib/pkgconfig/xenhypfs.pc
>   /usr/lib/pkgconfig/xlutil.pc
>   /usr/lib/pkgconfig/xentoolcore.pc
>   /usr/lib/pkgconfig/xentoollog.pc
>   /usr/lib/pkgconfig/xenstore.pc
>   /usr/lib/pkgconfig/xencall.pc
>   /usr/lib/pkgconfig/xencontrol.pc
>   /usr/lib/pkgconfig/xendevicemodel.pc
>   /usr/lib/pkgconfig/xenstat.pc
>   /usr/lib/pkgconfig/xengnttab.pc
>   /usr/lib/pkgconfig/xenevtchn.pc
>   /usr/lib/pkgconfig/xenvchan.pc
>   /usr/lib/pkgconfig/xenforeignmemory.pc
>   /usr/lib/xenfsimage/fat/fsimage.so
>   /usr/lib/xenfsimage/iso9660/fsimage.so
>   /usr/lib/xenfsimage/reiserfs/fsimage.so
>   /usr/lib/xenfsimage/ufs/fsimage.so
>   /usr/lib/xenfsimage/ext2fs-lib/fsimage.so
>   /usr/lib/xenfsimage/zfs/fsimage.so
> Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
> xen: 32 installed and not shipped files. [installed-vs-shipped]
> ERROR: xen-unstable+gitAUTOINC+be63d9d47f-r0 do_package: Fatal QA errors found, failing task.
> ERROR: xen-unstable+gitAUTOINC+be63d9d47f-r0 do_package: Function failed: do_package
> ERROR: Logfile of failure stored in: /home/manikandan/yocto_2.19/build/build/tmp/work/aarch64-poky-linux/xen/unstable+gitAUTOINC+be63d9d47f-r0/temp/log.do_package.17889
> ERROR: Task 13 (/home/manikandan/yocto_2.19/build/meta-virtualization/recipes-extended/xen/xen_git.bb, do_package) failed with exit code '1'

The configuration from the page is using a rather old release of Yocto.
I would suggest to switch to dunfell which will use xen 4.12.

Current master status of Yocto is not building at the moment.
Christopher Clark has done some work on it here [1] in meta-virtualization but this is not merged yet.

If you are trying to build Xen master by modifying a recipe you will have issues as some things have been added like hypfs which are creating the issues you see when Yocto is checking that everything was installed.

Bertrand

[1] https://lists.yoctoproject.org/g/meta-virtualization/message/5495

Re: [BUG] Xen build for RCAR failing

[Bertrand Marquis]

Hi,

> On 7 Jul 2020, at 10:28, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Bertrand,
> 
> Thanks for your quick response. I tired switching to dunfell branch and build gives parse error as below.
> 
> bitbake core-image-weston
> ERROR: ParseError in /home/manikandan/yocto_2.19/build/meta-virtualization/classes/: not a BitBake file
> 
> Is there any additional changes required here?

I do not have this on my side when building using dunfell.
You might need to restart from a fresh build and checkout (you need dunfell branch on all layers).

Bertrand

RE: [BUG] Xen build for RCAR failing

[Manikandan Chockalingam (RBEI/ECF3)]

Hello Bertrand,

Thank you. I will try a fresh build with dunfell branch. All layers in the sense [poky, meta-openembedded, meta-linaro, meta-rensas, meta-virtualisation, meta-selinux, xen-troops] right?

Also, Can I use the same proprietary drivers which I used for yocto2.19[R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170427.zip] for this branch?

Mit freundlichen Grüßen / Best regards

 Chockalingam Manikandan

ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | Manikandan.Chockalingam@in.bosch.com

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner, 
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller


-----Original Message-----
From: Bertrand Marquis <Bertrand.Marquis@arm.com> 
Sent: Tuesday, July 7, 2020 3:03 PM
To: Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com>
Cc: xen-devel@lists.xen.org; nd <nd@arm.com>
Subject: Re: [BUG] Xen build for RCAR failing

Hi,

> On 7 Jul 2020, at 10:28, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Bertrand,
> 
> Thanks for your quick response. I tired switching to dunfell branch and build gives parse error as below.
> 
> bitbake core-image-weston
> ERROR: ParseError in /home/manikandan/yocto_2.19/build/meta-virtualization/classes/: not a BitBake file
> 
> Is there any additional changes required here?

I do not have this on my side when building using dunfell.
You might need to restart from a fresh build and checkout (you need dunfell branch on all layers).

Bertrand

Re: [BUG] Xen build for RCAR failing

[Bertrand Marquis]

> On 7 Jul 2020, at 11:18, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Bertrand,
> 
> Thank you. I will try a fresh build with dunfell branch. All layers in the sense [poky, meta-openembedded, meta-linaro, meta-rensas, meta-virtualisation, meta-selinux, xen-troops] right?

right

> 
> Also, Can I use the same proprietary drivers which I used for yocto2.19[R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170427.zip] for this branch?

I have no idea what is in that but i would guess it will probably not work that easily.
You might need to get in contact with Renesas to get more up-to-date instructions on how to build that.

Bertrand

RE: [BUG] Xen build for RCAR failing

[Manikandan Chockalingam (RBEI/ECF3)]

Hello Bertrand,

I couldn't find dunfell branch in the following repos
1. meta-selinux
2. xen-troops
3. meta-renesas [I took dunfell-dev]

Mit freundlichen Grüßen / Best regards

 Chockalingam Manikandan

ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | Manikandan.Chockalingam@in.bosch.com

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner, 
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller

-----Original Message-----
From: Bertrand Marquis <Bertrand.Marquis@arm.com> 
Sent: Tuesday, July 7, 2020 5:18 PM
To: Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com>
Cc: xen-devel@lists.xen.org; nd <nd@arm.com>
Subject: Re: [BUG] Xen build for RCAR failing



> On 7 Jul 2020, at 11:18, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Bertrand,
> 
> Thank you. I will try a fresh build with dunfell branch. All layers in the sense [poky, meta-openembedded, meta-linaro, meta-rensas, meta-virtualisation, meta-selinux, xen-troops] right?

right

> 
> Also, Can I use the same proprietary drivers which I used for yocto2.19[R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170427.zip] for this branch?

I have no idea what is in that but i would guess it will probably not work that easily.
You might need to get in contact with Renesas to get more up-to-date instructions on how to build that.

Bertrand

Re: [BUG] Xen build for RCAR failing

[Bertrand Marquis]

> On 10 Jul 2020, at 05:26, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Bertrand,
> 
> I couldn't find dunfell branch in the following repos
> 1. meta-selinux
> 2. xen-troops
> 3. meta-renesas [I took dunfell-dev]

Those are not layers i am using.
Not having a dunfell branch could mean that master of those layers is compatible with Dunfell or that those layers are not maintained.

I would advise you to try to contact the maintainers of those layers.

Regards
Bertrand

RE: [BUG] Xen build for RCAR failing

[Manikandan Chockalingam (RBEI/ECF3)]

[-- Attachment #1: Type: text/plain, Size: 4167 bytes --]

Hello Bertrand,

I succeeded in building the core minimal image with dunfell and its compatible branches [except xen-troops (modified some files to complete the build)].

But I face the following error while booting.

(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Timer: Unable to retrieve IRQ 0 from the device tree
(XEN) ****************************************

My Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "aarch64-poky-linux"
MACHINE              = "salvator-x"
DISTRO               = "poky"
DISTRO_VERSION       = "3.1.1"
TUNE_FEATURES        = "aarch64 cortexa57-cortexa53"
TARGET_FPU           = ""
SOC_FAMILY           = "rcar-gen3:r8a7795"
meta                 
meta-poky            
meta-yocto-bsp       = "tmp:39d7cf1abb2c88baaedb3a627eba8827747b2eb9"
meta-rcar-gen3       = "dunfell-dev:2b3b0447fbc6c360a43a13525ae63a253fe3e5b7"
meta-oe              
meta-python          
meta-filesystems     
meta-networking      = "tmp:cc6fc6b1641ab23089c1e3bba11e0c6394f0867c"
meta-selinux         = "dunfell:7af62c91d7d00a260cf28e7908955539304d100d"
meta-virtualization  = "dunfell:ffd787fb850e5a1657a01febc8402c74832147a1"
meta-rcar-gen3-xen   = "master:60699c631d541aeeaebaeec9a087efed9385ee42"

May I know the reason for this error? Am I missing something here? Attaching complete logs for reference.

Mit freundlichen Grüßen / Best regards

 Chockalingam Manikandan

ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | Manikandan.Chockalingam@in.bosch.com

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner, 
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller

-----Original Message-----
From: Manikandan Chockalingam (RBEI/ECF3) 
Sent: Friday, July 10, 2020 9:56 AM
To: 'Bertrand Marquis' <Bertrand.Marquis@arm.com>
Cc: xen-devel@lists.xen.org; nd <nd@arm.com>
Subject: RE: [BUG] Xen build for RCAR failing

Hello Bertrand,

I couldn't find dunfell branch in the following repos 1. meta-selinux 2. xen-troops 3. meta-renesas [I took dunfell-dev]

Mit freundlichen Grüßen / Best regards

 Chockalingam Manikandan

ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | Manikandan.Chockalingam@in.bosch.com

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000; Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner, Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung, Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller

-----Original Message-----
From: Bertrand Marquis <Bertrand.Marquis@arm.com>
Sent: Tuesday, July 7, 2020 5:18 PM
To: Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com>
Cc: xen-devel@lists.xen.org; nd <nd@arm.com>
Subject: Re: [BUG] Xen build for RCAR failing



> On 7 Jul 2020, at 11:18, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Bertrand,
> 
> Thank you. I will try a fresh build with dunfell branch. All layers in the sense [poky, meta-openembedded, meta-linaro, meta-rensas, meta-virtualisation, meta-selinux, xen-troops] right?

right

> 
> Also, Can I use the same proprietary drivers which I used for yocto2.19[R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170427.zip] for this branch?

I have no idea what is in that but i would guess it will probably not work that easily.
You might need to get in contact with Renesas to get more up-to-date instructions on how to build that.

Bertrand


[-- Attachment #2: built-u-boot-xen-bootup-error.txt --]
[-- Type: text/plain, Size: 6480 bytes --]

[    0.000149] NOTICE:  BL2: R-Car H3 Initial Program Loader(CA57)
[    0.004585] NOTICE:  BL2: Initial Program Loader(Rev.2.0.6)
[    0.010119] NOTICE:  BL2: PRR is R-Car H3 Ver.2.0
[    0.014787] NOTICE:  BL2: Board is Salvator-X Rev.1.0
[    0.019814] NOTICE:  BL2: Boot device is HyperFlash(160MHz)
[    0.025325] NOTICE:  BL2: LCM state is CM
[    0.029368] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x53
[    0.035384] NOTICE:  BL2: DDR3200(rev.0.40)
[    0.050722] NOTICE:  BL2: [COLD_BOOT]
[    0.059497] NOTICE:  BL2: DRAM Split is 4ch
[    0.062192] NOTICE:  BL2: QoS is default setting(rev.0.21)
[    0.067635] NOTICE:  BL2: DRAM refresh interval 1.95 usec
[    0.072992] NOTICE:  BL2: Periodic Write DQ Training
[    0.078023] NOTICE:  BL2: v1.5(release):af9f429
[    0.082410] NOTICE:  BL2: Built : 07:07:22, Jul 14 2020
[    0.087597] NOTICE:  BL2: Normal boot
[    0.091238] NOTICE:  BL2: dst=0xe6325100 src=0x8180000 len=512(0x200)
[    0.097623] NOTICE:  BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
[    0.104233] NOTICE:  BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
[    0.111217] NOTICE:  BL2: dst=0x44100000 src=0x8200000 len=1048576(0x100000)
[    0.122179] NOTICE:  BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)
[    0.132033] NOTICE:  BL2: Booting BL31

U-Boot 2018.09 (Jul 12 2020 - 19:09:13 +0000)

CPU: Renesas Electronics R8A7795 rev 2.0
Model: Renesas Salvator-X board based on r8a7795 ES2.0+
DRAM:  3.9 GiB
Bank #0: 0x048000000 - 0x07fffffff, 896 MiB
Bank #1: 0x500000000 - 0x53fffffff, 1 GiB
Bank #2: 0x600000000 - 0x63fffffff, 1 GiB
Bank #3: 0x700000000 - 0x73fffffff, 1 GiB

MMC:   sd@ee100000: 0, sd@ee140000: 1, sd@ee160000: 2
Loading Environment from MMC... OK
In:    serial@e6e88000
Out:   serial@e6e88000
Err:   serial@e6e88000
Net:   
Error: ethernet@e6800000 address not set.
eth-1: ethernet@e6800000
Hit any key to stop autoboot:  0 
=> setenv ethaddr de:ad:be:ef:01:02
=> setenv ipaddr 192.168.2.51
=> setenv serverip 192.168.2.11
=> tftp 0x4A000000 r8a7795-salvator-x-xen.dtb
ethernet@e6800000 Waiting for PHY auto negotiation to complete..... done
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'r8a7795-salvator-x-xen.dtb'.
Load address: 0x4a000000
Loading: *
ARP Retry count exceeded; starting again
=> tftp 0x4A000000 r8a7795-salvator-x-xen.dtb
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'r8a7795-salvator-x-xen.dtb'.
Load address: 0x4a000000
Loading: ######
         2.2 MiB/s
done
Bytes transferred = 80783 (13b8f hex)
=> tftp 0x48200000 Image
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'Image'.
Load address: 0x48200000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ############
         2.3 MiB/s
done
Bytes transferred = 21156352 (142d200 hex)
=> tftp 0x48000000 xen
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'xen'.
Load address: 0x48000000
Loading: ###########################################################
         2.1 MiB/s
done
Bytes transferred = 853328 (d0550 hex)
=> booti 0x48000000 - 0x4A000000
## Flattened Device Tree blob at 4a000000
   Booting using the fdt blob at 0x4a000000
   Using Device Tree in place at 000000004a000000, end 000000004a016b8e

Starting kernel ...

 Xen 4.12.4-pre
(XEN) Xen version 4.12.4-pre (manikandan@) (aarch64-linux-gnu-gcc (Sourcery CodeBench 2018.05-7) 7.3.1 20180612) d0
(XEN) Latest ChangeSet: Tue Jul 7 15:13:40 2020 +0200 git:19e0bbb
(XEN) Processor: 411fd073: "ARM Limited", variant: 0x1, part 0xd07, rev 0x3
(XEN) 64-bit Execution:
(XEN)   Processor Features: 0000000000002222 0000000000000000
(XEN)     Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN)     Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 0000000010305106 0000000000000000
(XEN)   Auxiliary Features: 0000000000000000 0000000000000000
(XEN)   Memory Model Features: 0000000000001124 0000000000000000
(XEN)   ISA Features:  0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00000131:00011011
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 03010066
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 40000000 01260000 02102211
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Timer: Unable to retrieve IRQ 0 from the device tree
(XEN) ****************************************
(XEN) 
(XEN) Reboot in five seconds...

Re: [BUG] Xen build for RCAR failing

[Oleksandr Tyshchenko]

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

Hello

[Sorry for the possible format issues]

On Tue, Jul 14, 2020 at 4:44 PM Manikandan Chockalingam (RBEI/ECF3) <
Manikandan.Chockalingam@in.bosch.com> wrote:

> Hello Bertrand,
>
> I succeeded in building the core minimal image with dunfell and its
> compatible branches [except xen-troops (modified some files to complete the
> build)].
>
> But I face the following error while booting.
>
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Timer: Unable to retrieve IRQ 0 from the device tree
> (XEN) ****************************************
>


The reason for that problem *might* be in the arch timer node in your
device tree which contains "interrupts-extended" property instead of just
"interrupts". As far as I remember Xen v4.12 doesn't have required support
to handle "interrupts-extended".
It went in a bit later [1]. If this is the real reason, I think you should
either switch to the new Xen version or modify your arch timer node in a
way to use the "interrupts" property [2]. I would suggest using the new Xen
version if possible (at least v4.13).

[1]
https://lists.xenproject.org/archives/html/xen-devel/2019-05/msg01775.html
[2]
https://github.com/otyshchenko1/linux/commit/c25044845f2c3678f5df789881e7a125556af6fc

-- 
Regards,

Oleksandr Tyshchenko

[-- Attachment #2: Type: text/html, Size: 2403 bytes --]

RE: [BUG] Xen build for RCAR failing

[Manikandan Chockalingam (RBEI/ECF3)]

[-- Attachment #1.1: Type: text/plain, Size: 3583 bytes --]

Hello Oleksandr Tyshchenko,
Thanks for your quick response. With Xen stable 4.13 branch, the mentioned issue is solved.

Is there any document which I could refer to bring up Xen[DOM0] and have an hands on ? because am currently seeing no output after this

(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 324kB init memory.
(XEN) *** Serial input to Xen (type 'CTRL-a' three times to switch input)

Attaching the complete logs for reference.

Mit freundlichen Grüßen / Best regards

Chockalingam Manikandan

ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | Manikandan.Chockalingam@in.bosch.com<mailto:Manikandan.Chockalingam@in.bosch.com>

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner,
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller
​
From: Oleksandr Tyshchenko <olekstysh@gmail.com>
Sent: Wednesday, July 15, 2020 1:00 AM
To: Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com>
Cc: Bertrand Marquis <Bertrand.Marquis@arm.com>; nd <nd@arm.com>; xen-devel@lists.xen.org
Subject: Re: [BUG] Xen build for RCAR failing

Hello

[Sorry for the possible format issues]

On Tue, Jul 14, 2020 at 4:44 PM Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com<mailto:Manikandan.Chockalingam@in.bosch.com>> wrote:
Hello Bertrand,

I succeeded in building the core minimal image with dunfell and its compatible branches [except xen-troops (modified some files to complete the build)].

But I face the following error while booting.

(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Timer: Unable to retrieve IRQ 0 from the device tree
(XEN) ****************************************


The reason for that problem *might* be in the arch timer node in your device tree which contains "interrupts-extended" property instead of just "interrupts". As far as I remember Xen v4.12 doesn't have required support to handle "interrupts-extended".
It went in a bit later [1]. If this is the real reason, I think you should either switch to the new Xen version or modify your arch timer node in a way to use the "interrupts" property [2]. I would suggest using the new Xen version if possible (at least v4.13).

[1] https://lists.xenproject.org/archives/html/xen-devel/2019-05/msg01775.html<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.xenproject.org%2Farchives%2Fhtml%2Fxen-devel%2F2019-05%2Fmsg01775.html&data=02%7C01%7CManikandan.Chockalingam%40in.bosch.com%7Cf43735b682524701f9e008d8282c6400%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637303518829046287&sdata=8ZritGkF%2Bv29cQsagR2KJaW2NUTVBk0no7Rt7Ez37ek%3D&reserved=0>
[2] https://github.com/otyshchenko1/linux/commit/c25044845f2c3678f5df789881e7a125556af6fc<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fotyshchenko1%2Flinux%2Fcommit%2Fc25044845f2c3678f5df789881e7a125556af6fc&data=02%7C01%7CManikandan.Chockalingam%40in.bosch.com%7Cf43735b682524701f9e008d8282c6400%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637303518829046287&sdata=rLjx9VzjBfldUjg%2Fv6wTD8Z89TzSfN71RFpdxCO%2F%2F0A%3D&reserved=0>

--
Regards,

Oleksandr Tyshchenko

[-- Attachment #1.2: Type: text/html, Size: 9330 bytes --]

[-- Attachment #2: built-u-boot-xen-bootup-error_4.13.txt --]
[-- Type: text/plain, Size: 6604 bytes --]

Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'r8a7795-salvator-x-xen.dtb'.
Load address: 0x4a000000
Loading: ######
         1.8 MiB/s
done
Bytes transferred = 80783 (13b8f hex)
=> tftp 0x48200000 Image
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'Image'.
Load address: 0x48200000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ############
         2.2 MiB/s
done
Bytes transferred = 21156352 (142d200 hex)
=> tftp 0x48000000 xen
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'xen'.
Load address: 0x48000000
Loading: ###############################################################
         1 MiB/s
done
Bytes transferred = 918864 (e0550 hex)
=> booti 0x48000000 - 0x4A000000
## Flattened Device Tree blob at 4a000000
   Booting using the fdt blob at 0x4a000000
   Using Device Tree in place at 000000004a000000, end 000000004a016b8e

Starting kernel ...

 Xen 4.13.2-pre
(XEN) Xen version 4.13.2-pre (manikandan@) (aarch64-linux-gnu-gcc (Sourcery CodeBench 2018.05-7) 7.3.1 20180612) d0
(XEN) Latest ChangeSet: Tue Jul 7 15:05:36 2020 +0200 git:378321b
(XEN) Processor: 411fd073: "ARM Limited", variant: 0x1, part 0xd07, rev 0x3
(XEN) 64-bit Execution:
(XEN)   Processor Features: 0000000000002222 0000000000000000
(XEN)     Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN)     Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 0000000010305106 0000000000000000
(XEN)   Auxiliary Features: 0000000000000000 0000000000000000
(XEN)   Memory Model Features: 0000000000001124 0000000000000000
(XEN)   ISA Features:  0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00000131:00011011
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 03010066
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 40000000 01260000 02102211
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 8333 KHz
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=00000000f1010000
(XEN)         gic_cpu_addr=00000000f1020000
(XEN)         gic_hyp_addr=00000000f1040000
(XEN)         gic_vcpu_addr=00000000f1060000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: Adjusting CPU interface base to 0xf102f000
(XEN) GICv2: 512 lines, 8 cpus, secure (IID 0200043b).
(XEN) XSM Framework v1.0.0 initialized
(XEN) Initialising XSM SILO mode
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) Allocated console ring of 16 KiB.
(XEN) Bringing up CPU1
(XEN) Bringing up CPU2
(XEN) Bringing up CPU3
(XEN) Bringing up CPU4
(XEN) CPU4 MIDR (0x410fd034) does not match boot CPU MIDR (0x411fd073),
(XEN) disable cpu (see big.LITTLE.txt under docs/).
(XEN) CPU4 never came online
(XEN) Failed to bring up CPU 4 (error -5)
(XEN) Bringing up CPU5
(XEN) CPU5 MIDR (0x410fd034) does not match boot CPU MIDR (0x411fd073),
(XEN) disable cpu (see big.LITTLE.txt under docs/).
(XEN) CPU5 never came online
(XEN) Failed to bring up CPU 5 (error -5)
(XEN) Bringing up CPU6
(XEN) CPU6 MIDR (0x410fd034) does not match boot CPU MIDR (0x411fd073),
(XEN) disable cpu (see big.LITTLE.txt under docs/).
(XEN) CPU6 never came online
(XEN) Failed to bring up CPU 6 (error -5)
(XEN) Bringing up CPU7
(XEN) CPU7 MIDR (0x410fd034) does not match boot CPU MIDR (0x411fd073),
(XEN) disable cpu (see big.LITTLE.txt under docs/).
(XEN) CPU7 never came online
(XEN) Failed to bring up CPU 7 (error -5)
(XEN) Brought up 4 CPUs
(XEN) I/O virtualisation disabled
(XEN) P2M: 44-bit IPA with 44-bit PA and 8-bit VMID
(XEN) P2M: 4 levels with order-0 root, VTCR 0x80043594
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading d0 kernel from boot module @ 0000000048200000
(XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
(XEN) BANK[0] 0x00000600000000-0x00000640000000 (1024MB)
(XEN) Grant table range: 0x00000048000000-0x00000048040000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading zImage from 0000000048200000 to 0000000600080000-0000000600f80000
(XEN) Loading d0 DTB to 0x0000000608000000-0x0000000608012d37
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Scrubbing Free RAM in background
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 324kB init memory.
(XEN) *** Serial input to Xen (type 'CTRL-a' three times to switch input)
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) *** Serial input to Xen (type 'CTRL-a' three times to switch input)

Re: [BUG] Xen build for RCAR failing

[Bertrand Marquis]

Hi Manikandan,

> On 15 Jul 2020, at 08:47, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Oleksandr Tyshchenko,
> Thanks for your quick response. With Xen stable 4.13 branch, the mentioned issue is solved.
>  
> Is there any document which I could refer to bring up Xen[DOM0] and have an hands on ? because am currently seeing no output after this
>  
> (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
> (XEN) Freed 324kB init memory.
> (XEN) *** Serial input to Xen (type 'CTRL-a' three times to switch input)
>  
> Attaching the complete logs for reference.

Your DOM0 is probably trying to use the wrong console.
You should add “console=hvc0” to your Dom0 linux command line (and remove any other console= argument)

Regards
Bertrand

>  
> Mit freundlichen Grüßen / Best regards
> 
> Chockalingam Manikandan 
> 
> ES-CM Core fn,ADIT (RBEI/ECF3)
> Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
> Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | Manikandan.Chockalingam@in.bosch.com
> 
> Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
> Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner, 
> Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
> Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller 
> ​
> From: Oleksandr Tyshchenko <olekstysh@gmail.com> 
> Sent: Wednesday, July 15, 2020 1:00 AM
> To: Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com>
> Cc: Bertrand Marquis <Bertrand.Marquis@arm.com>; nd <nd@arm.com>; xen-devel@lists.xen.org
> Subject: Re: [BUG] Xen build for RCAR failing
>  
> Hello
>  
> [Sorry for the possible format issues]
>  
> On Tue, Jul 14, 2020 at 4:44 PM Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> Hello Bertrand,
> 
> I succeeded in building the core minimal image with dunfell and its compatible branches [except xen-troops (modified some files to complete the build)].
> 
> But I face the following error while booting.
> 
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Timer: Unable to retrieve IRQ 0 from the device tree
> (XEN) ****************************************
>  
>  
> The reason for that problem *might* be in the arch timer node in your device tree which contains "interrupts-extended" property instead of just "interrupts". As far as I remember Xen v4.12 doesn't have required support to handle "interrupts-extended".
> It went in a bit later [1]. If this is the real reason, I think you should either switch to the new Xen version or modify your arch timer node in a way to use the "interrupts" property [2]. I would suggest using the new Xen version if possible (at least v4.13).
>  
> [1] https://lists.xenproject.org/archives/html/xen-devel/2019-05/msg01775.html
> [2] https://github.com/otyshchenko1/linux/commit/c25044845f2c3678f5df789881e7a125556af6fc
>  
> -- 
> Regards,
>  
> Oleksandr Tyshchenko
> <built-u-boot-xen-bootup-error_4.13.txt>

Re: [BUG] Xen build for RCAR failing

[Oleksandr Tyshchenko]

[-- Attachment #1: Type: text/plain, Size: 865 bytes --]

Hello all

[Sorry for the possible format issues]


> > Is there any document which I could refer to bring up Xen[DOM0] and have
> an hands on ? because am currently seeing no output after this
>

The actual document I am aware of [1]. *Although this is not exactly how to
bring up Xen Dom0*, this is about how to bring up the whole Xen based
system (based on v4.13 release) with thin generic ARMv8 Dom0 without H/W,
DomD with H/W (based on Renesas BSP v3.21.0) and DomU with set of PV
drivers, so contains a lot of probably an extra/unneeded information for
you, but you could refer to meta-xt-prod-devel/meta-xt-images Yocto layers
anyway in order to find information regarding various Xen bits
(including default chosen node for Host device tree).

[1]
https://github.com/xen-troops/meta-xt-prod-devel/blob/master/INSTALL.txt

-- 
Regards,

Oleksandr Tyshchenko

[-- Attachment #2: Type: text/html, Size: 1664 bytes --]

RE: [BUG] Xen build for RCAR failing

[Manikandan Chockalingam (RBEI/ECF3)]

[-- Attachment #1: Type: text/plain, Size: 6453 bytes --]

Hello Bertrand,

I tried to build Xen on RCAR with the following build configuration.

Build Configuration:
BB_VERSION        = "1.30.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "aarch64-poky-linux"
MACHINE           = "salvator-x"
DISTRO            = "poky"
DISTRO_VERSION    = "2.1.2"
TUNE_FEATURES     = "aarch64 cortexa57-cortexa53"
TARGET_FPU        = ""
SOC_FAMILY        = "rcar-gen3:r8a7795"
meta              
meta-poky         
meta-yocto-bsp    = "tmp:cca8dd15c8096626052f6d8d25ff1e9a606104a3"
meta-rcar-gen3    = "tmp:95cb48ba09bc7e55fd549817e3e26723409e68d5"
meta-linaro-toolchain 
meta-optee        = "tmp:2f51d38048599d9878f149d6d15539fb97603f8f"
meta-oe           = "tmp:55c8a76da5dc099a7bc3838495c672140cedb78e"
meta-virtualization = "morty:f3643212c2a87a29e2c8066a1a544612d1598de8"
meta-selinux      = "jethro:4c75d9cbcf1d75043c7c5ab315aa383d9b227510"
meta-networking   
meta-python       = "tmp:55c8a76da5dc099a7bc3838495c672140cedb78e"
meta-rcar-gen3-xen = "master:affeba788534a04dd30a21dbbb81a573bd033dfa"

Also enabled the early printk in xen 4.7 and I could able to boot Xen and Dom0.

But I couldn’t enter into the command prompt of Dom0. Attaching the complete log for your reference.

I could execute the special keys(0,q,e,R) in xen console. But even after enabling hvc0 in Dom0 commandline, am not seeing any logs after a point and I couldn’t do any operation on Dom0.

Am I missing something here. Thanks in advance.

Mit freundlichen Grüßen / Best regards

 Chockalingam Manikandan

ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | Manikandan.Chockalingam@in.bosch.com

Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner, 
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller

-----Original Message-----
From: Bertrand Marquis <Bertrand.Marquis@arm.com> 
Sent: Wednesday, July 15, 2020 1:14 PM
To: Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com>
Cc: Oleksandr Tyshchenko <olekstysh@gmail.com>; nd <nd@arm.com>; xen-devel@lists.xen.org
Subject: Re: [BUG] Xen build for RCAR failing

Hi Manikandan,

> On 15 Jul 2020, at 08:47, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Oleksandr Tyshchenko,
> Thanks for your quick response. With Xen stable 4.13 branch, the mentioned issue is solved.
>  
> Is there any document which I could refer to bring up Xen[DOM0] and 
> have an hands on ? because am currently seeing no output after this
>  
> (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch 
> input)
> (XEN) Freed 324kB init memory.
> (XEN) *** Serial input to Xen (type 'CTRL-a' three times to switch 
> input)
>  
> Attaching the complete logs for reference.

Your DOM0 is probably trying to use the wrong console.
You should add “console=hvc0” to your Dom0 linux command line (and remove any other console= argument)

Regards
Bertrand

>  
> Mit freundlichen Grüßen / Best regards
> 
> Chockalingam Manikandan
> 
> ES-CM Core fn,ADIT (RBEI/ECF3)
> Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY | 
> http://www.bosch.com/ Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 | 
> Manikandan.Chockalingam@in.bosch.com
> 
> Registered Office: Stuttgart, Registration Court: Amtsgericht 
> Stuttgart, HRB 14000; Chairman of the Supervisory Board: Franz 
> Fehrenbach; Managing Directors: Dr. Volkmar Denner, Prof. Dr. Stefan 
> Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan 
> Hartung, Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, 
> Uwe Raschke, Peter Tyroller ​
> From: Oleksandr Tyshchenko <olekstysh@gmail.com>
> Sent: Wednesday, July 15, 2020 1:00 AM
> To: Manikandan Chockalingam (RBEI/ECF3) 
> <Manikandan.Chockalingam@in.bosch.com>
> Cc: Bertrand Marquis <Bertrand.Marquis@arm.com>; nd <nd@arm.com>; 
> xen-devel@lists.xen.org
> Subject: Re: [BUG] Xen build for RCAR failing
>  
> Hello
>  
> [Sorry for the possible format issues]
>  
> On Tue, Jul 14, 2020 at 4:44 PM Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> Hello Bertrand,
> 
> I succeeded in building the core minimal image with dunfell and its compatible branches [except xen-troops (modified some files to complete the build)].
> 
> But I face the following error while booting.
> 
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Timer: Unable to retrieve IRQ 0 from the device tree
> (XEN) ****************************************
>  
>  
> The reason for that problem *might* be in the arch timer node in your device tree which contains "interrupts-extended" property instead of just "interrupts". As far as I remember Xen v4.12 doesn't have required support to handle "interrupts-extended".
> It went in a bit later [1]. If this is the real reason, I think you should either switch to the new Xen version or modify your arch timer node in a way to use the "interrupts" property [2]. I would suggest using the new Xen version if possible (at least v4.13).
>  
> [1] 
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist
> s.xenproject.org%2Farchives%2Fhtml%2Fxen-devel%2F2019-05%2Fmsg01775.ht
> ml&amp;data=02%7C01%7CManikandan.Chockalingam%40in.bosch.com%7C0ba1432
> c984b48dafbef08d82892eb44%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7
> C637303959344391585&amp;sdata=eGr0jg8ZE6fEZV4M4v57n2sv76d2M9F9k%2F%2Be
> uJBXMwc%3D&amp;reserved=0 [2] 
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> ub.com%2Fotyshchenko1%2Flinux%2Fcommit%2Fc25044845f2c3678f5df789881e7a
> 125556af6fc&amp;data=02%7C01%7CManikandan.Chockalingam%40in.bosch.com%
> 7C0ba1432c984b48dafbef08d82892eb44%7C0ae51e1907c84e4bbb6d648ee58410f4%
> 7C0%7C0%7C637303959344391585&amp;sdata=9kD7NODEpcd%2BtuoVdcAMgPD%2Bnoy
> gp9NC5fRBsgnTmU8%3D&amp;reserved=0
>  
> --
> Regards,
>  
> Oleksandr Tyshchenko
> <built-u-boot-xen-bootup-error_4.13.txt>


[-- Attachment #2: xen_with_jethro_morty_xen_spl_keys_log.txt --]
[-- Type: text/plain, Size: 49785 bytes --]

[    0.000149] NOTICE:  BL2: R-Car H3 Initial Program Loader(CA57)
[    0.004585] NOTICE:  BL2: Initial Program Loader(Rev.2.0.6)
[    0.010119] NOTICE:  BL2: PRR is R-Car H3 Ver.2.0
[    0.014787] NOTICE:  BL2: Board is Salvator-X Rev.1.0
[    0.019814] NOTICE:  BL2: Boot device is HyperFlash(160MHz)
[    0.025325] NOTICE:  BL2: LCM state is CM
[    0.029368] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x53
[    0.035384] NOTICE:  BL2: DDR3200(rev.0.40)
[    0.050718] NOTICE:  BL2: [COLD_BOOT]
[    0.059487] NOTICE:  BL2: DRAM Split is 4ch
[    0.062182] NOTICE:  BL2: QoS is default setting(rev.0.21)
[    0.067626] NOTICE:  BL2: DRAM refresh interval 1.95 usec
[    0.072982] NOTICE:  BL2: Periodic Write DQ Training
[    0.078013] NOTICE:  BL2: v1.5(release):af9f429
[    0.082400] NOTICE:  BL2: Built : 07:07:22, Jul 14 2020
[    0.087587] NOTICE:  BL2: Normal boot
[    0.091228] NOTICE:  BL2: dst=0xe6325100 src=0x8180000 len=512(0x200)
[    0.097614] NOTICE:  BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
[    0.104223] NOTICE:  BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
[    0.111207] NOTICE:  BL2: dst=0x44100000 src=0x8200000 len=1048576(0x100000)
[    0.122169] NOTICE:  BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)
[    0.132024] NOTICE:  BL2: Booting BL31


U-Boot 2018.09 (Jul 12 2020 - 19:09:13 +0000)

CPU: Renesas Electronics R8A7795 rev 2.0
Model: Renesas Salvator-X board based on r8a7795 ES2.0+
DRAM:  3.9 GiB
Bank #0: 0x048000000 - 0x07fffffff, 896 MiB
Bank #1: 0x500000000 - 0x53fffffff, 1 GiB
Bank #2: 0x600000000 - 0x63fffffff, 1 GiB
Bank #3: 0x700000000 - 0x73fffffff, 1 GiB

MMC:   sd@ee100000: 0, sd@ee140000: 1, sd@ee160000: 2
Loading Environment from MMC... OK
In:    serial@e6e88000
Out:   serial@e6e88000
Err:   serial@e6e88000
Net:   eth0: ethernet@e6800000
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device

=> setenv serverip 192.168.2.11
=> setenv ipaddr 192.168.2.51
=> tftp 0x48000000 Image-r8a7795-salvator-x-xen.dtb
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'Image-r8a7795-salvator-x-xen.dtb'.
Load address: 0x48000000
Loading: #####
         1.9 MiB/s
done
Bytes transferred = 67228 (1069c hex)
=> tftp 0x48080000 xen.uImage
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'xen.uImage'.
Load address: 0x48080000
Loading: ########################################################
         2.3 MiB/s
done
Bytes transferred = 820832 (c8660 hex)
=> tftp 0x7a000000 Image
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'Image'.
Load address: 0x7a000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ####################################
         2.2 MiB/s
done
Bytes transferred = 15782400 (f0d200 hex)
=> bootm 0x48080000 - 0x48000000
## Booting kernel from Legacy Image at 48080000 ...
   Image Name:   XEN
   Image Type:   AArch64 Linux Kernel Image (uncompressed)
   Data Size:    820768 Bytes = 801.5 KiB
   Load Address: 78080000
   Entry Point:  78080000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 48000000
   Booting using the fdt blob at 0x48000000
   Loading Kernel Image ... OK
   Using Device Tree in place at 0000000048000000, end 000000004801369b

Starting kernel ...

- UART enabled -
- CPU 00000000 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000048000000 - 000000007fffffff
(XEN) RAM: 0000000500000000 - 000000053fffffff
(XEN) RAM: 0000000600000000 - 000000063fffffff
(XEN) RAM: 0000000700000000 - 000000073fffffff
(XEN) 
(XEN) MODULE[0]: 0000000048000000 - 0000000048011000 Device Tree  
(XEN) MODULE[1]: 000000007a000000 - 000000007c000000 Kernel       
(XEN)  RESVD[0]: 0000000048000000 - 0000000048011000
(XEN) 
(XEN) Command line: dom0_mem=752M console=dtuart dtuart=serial0 dom0_max_vcpus=4
(XEN) Placing Xen at 0x000000007fe00000-0x0000000080000000
(XEN) Update BOOTMOD_XEN from 0000000078080000-0000000078190d81 => 000000007fe00000-000000007ff10d81
(XEN) PFN compression on bits 19...19
(XEN) Domain heap initialised
(XEN) Platform: Generic System
(XEN) Looking for dtuart at "serial0", options ""
 Xen 4.7.0
(XEN) Xen version 4.7.0 (manikandan@) (aarch64-linux-gnu-gcc (Sourcery CodeBench 2018.05-7) 7.3.1 20180612) debug=0
(XEN) Latest ChangeSet: Thu Jul 23 15:36:18 2020 +0530 git:138cede-dirty
(XEN) Processor: 411fd073: "ARM Limited", variant: 0x1, part 0xd07, rev 0x3
(XEN) 64-bit Execution:
(XEN)   Processor Features: 0000000000002222 0000000000000000
(XEN)     Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN)     Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 0000000010305106 0000000000000000
(XEN)   Auxiliary Features: 0000000000000000 0000000000000000
(XEN)   Memory Model Features: 0000000000001124 0000000000000000
(XEN)   ISA Features:  0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00000131:00011011
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 03010066
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 40000000 01260000 02102211
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using PSCI-1.1 for SMP bringup
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 8333 KHz
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=00000000f1010000
(XEN)         gic_cpu_addr=00000000f1020000
(XEN)         gic_hyp_addr=00000000f1040000
(XEN)         gic_vcpu_addr=00000000f1060000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: Adjusting CPU interface base to 0xf102f000
(XEN) GICv2: 512 lines, 8 cpus, secure (IID 0200043b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 64 KiB.
(XEN) Bringing up CPU1
- CPU 00000001 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 1 booted.
(XEN) Bringing up CPU2
- CPU 00000002 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 2 booted.
(XEN) Bringing up CPU3
- CPU 00000003 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 3 booted.
(XEN) Bringing up CPU4
- CPU 00000100 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 4 booted.
(XEN) Bringing up CPU5
- CPU 00000101 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 5 booted.
(XEN) Bringing up CPU6
- CPU 00000102 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 6 booted.
(XEN) Bringing up CPU7
- CPU 00000103 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 7 booted.
(XEN) Brought up 8 CPUs
(XEN) P2M: 40-bit IPA with 40-bit PA
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 000000007a000000
(XEN) Allocating 1:1 mappings totalling 752MB for dom0:
(XEN) BANK[0] 0x00000700000000-0x00000720000000 (512MB)
(XEN) BANK[1] 0x00000722000000-0x00000730000000 (224MB)
(XEN) BANK[2] 0x0000073e000000-0x0000073f000000 (16MB)
(XEN) Grant table range: 0x0000007fe00000-0x0000007fe63000
(XEN) Loading zImage from 000000007a000000 to 0000000700080000-0000000700fdc000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading dom0 DTB to 0x0000000708000000-0x000000070800fd15
(XEN) Scrubbing Free RAM on 1 nodes using 8 CPUs
(XEN) ....done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 288kB init memory.
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER4
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER8
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER12
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER16
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER20
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER24
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER28
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER32
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER36
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER40
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER44
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER48
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER52
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER56
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER60
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER0
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.0-yocto-standard (manikandan@manikandan-VirtualBox) (gcc version 5.2.1 20151005 (0
[    0.000000] Boot CPU: AArch64 Processor [411fd073]
[    0.000000] debug: ignoring loglevel setting.
[    0.000000] Xen 4.7 support found
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Reserved 128 MiB at 0x0000000728000000
[    0.000000] On node 0 totalpages: 192512
[    0.000000]   DMA zone: 3008 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 192512 pages, LIFO batch:31
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv0.2 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] percpu: Embedded 21 pages/cpu @ffff80003ef44000 s48152 r8192 d29672 u86016
[    0.000000] pcpu-alloc: s48152 r8192 d29672 u86016 alloc=21*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Detected PIPT I-cache on CPU0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 189504
[    0.000000] Kernel command line: console=hvc0 root=/dev/nfs nfsroot=192.168.2.11:/export/target/rcar3/yocto ip=M
[    0.000000] log_buf_len individual max cpu contribution: 4096 bytes
[    0.000000] log_buf_len total cpu_extra contributions: 12288 bytes
[    0.000000] log_buf_len min size: 16384 bytes
[    0.000000] log_buf_len: 32768 bytes
[    0.000000] early log buf free: 14704(89%)
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[    0.000000] Memory: 604456K/770048K available (9212K kernel code, 884K rwdata, 4228K rodata, 1024K init, 289K b)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     modules : 0xffff000000000000 - 0xffff000008000000   (   128 MB)
[    0.000000]     vmalloc : 0xffff000008000000 - 0xffff7dffbfff0000   (129022 GB)
[    0.000000]       .text : 0xffff000008080000 - 0xffff000008980000   (  9216 KB)
[    0.000000]     .rodata : 0xffff000008980000 - 0xffff000008db0000   (  4288 KB)
[    0.000000]       .init : 0xffff000008db0000 - 0xffff000008eb0000   (  1024 KB)
[    0.000000]       .data : 0xffff000008eb0000 - 0xffff000008f8d200   (   885 KB)
[    0.000000]        .bss : 0xffff000008f8d200 - 0xffff000008fd59bc   (   290 KB)
[    0.000000]     fixed   : 0xffff7dfffe7fd000 - 0xffff7dfffec00000   (  4108 KB)
[    0.000000]     PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000   (    16 MB)
[    0.000000]     vmemmap : 0xffff7e0000000000 - 0xffff800000000000   (  2048 GB maximum)
[    0.000000]               0xffff7e0000000000 - 0xffff7e0000fc0000   (    15 MB actual)
[    0.000000]     memory  : 0xffff800000000000 - 0xffff80003f000000   (  1008 MB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 64.
[    0.000000]  RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[    0.000000] NR_IRQS:64 nr_irqs:64 0
[    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 8.33MHz (virt).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1ec02923e, max_idle_ns: 4407952s
[    0.000003] sched_clock: 56 bits at 8MHz, resolution 120ns, wraps every 2199023255496ns
[    0.000387] Console: colour dummy device 80x25
[    0.346199] console [hvc0] enabled
[    0.349664] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.66 BogoMIPS (lpj=3333)
[    0.359934] pid_max: default: 32768 minimum: 301
[    0.364643] Security Framework initialized
[    0.368778] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[    0.375492] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[    0.383263] ASID allocator initialised with 65536 entries
[    0.389042] xen:grant_table: Grant tables using version 1 layout
[    0.394968] Grant table initialized
[    0.398502] xen:events: Using FIFO-based ABI
[    0.402842] Xen: initializing cpu0
[    0.436227] EFI services will not be available.
(XEN) d0v1: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d0v2: vGICD: unhandled word write 0xffffffff to ICACTIVER0
(XEN) d0v3: vGICD: unhandled word write 0xffffffff to ICACTIVER0
[    0.480864] Detected PIPT I-cache on CPU1
[    0.486483] Xen: initializing cpu1
[    0.486498] CPU1: Booted secondary processor [411fd073]
[    0.516969] Detected PIPT I-cache on CPU2
[    0.522563] Xen: initializing cpu2
[    0.522577] CPU2: Booted secondary processor [411fd073]
[    0.553077] Detected PIPT I-cache on CPU3
[    0.558671] Xen: initializing cpu3
[    0.558685] CPU3: Booted secondary processor [411fd073]
[    0.558738] Brought up 4 CPUs
[    0.600027] SMP: Total of 4 processors activated.
[    0.604784] CPU features: detected feature: 32-bit EL0 Support
[    0.610759] CPU: All CPU(s) started at EL1
[    0.615372] devtmpfs: initialized
[    0.625400] DMI not present or invalid.
[    0.629316] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.640526] pinctrl core: initialized pinctrl subsystem
[    0.646019] Detected Renesas R-Car Gen3 r8a7795 ES2.0
[    0.651921] NET: Registered protocol family 16
[    0.657922] vdso: 2 pages (1 code @ ffff000008987000, 1 data @ ffff000008eb4000)
[    0.665230] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.672722] DMA: preallocated 256 KiB pool for atomic allocations
[    0.678761] xen:swiotlb_xen: Warning: only able to allocate 4 MB for software IO TLB
[    0.687300] software IO TLB [mem 0x726c00000-0x727000000] (4MB) mapped at [ffff800026c00000-ffff800026ffffff]
[    0.697305] Serial: AMBA PL011 UART driver
[    0.704971] r8a7795_pinmux_init: R-Car H3 >= ES2.0
[    0.709886] sh-pfc e6060000.pfc: r8a77951_pfc support registered
[    0.756435] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.763915] ACPI: Interpreter disabled.
[    0.769363] rcar-cpufreq: use avs value: 0
[    0.773801] xen:balloon: Initialising balloon driver
[    0.778745] xen_balloon: Initialising balloon driver
[    0.784815] vgaarb: loaded
[    0.787599] SCSI subsystem initialized
[    0.791420] libata version 3.00 loaded.
[    0.795390] usbcore: registered new interface driver usbfs
[    0.800819] usbcore: registered new interface driver hub
[    0.806192] usbcore: registered new device driver usb
[    0.811707] media: Linux media interface: v0.10
[    0.816167] Linux video capture interface: v2.00
[    0.820861] pps_core: LinuxPPS API ver. 1 registered
[    0.825818] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.834996] PTP clock support registered
[    0.839051] dmi: Firmware registration failed.
[    0.843617] Advanced Linux Sound Architecture Driver Initialized.
[    0.850362] i2c-sh_mobile e60b0000.i2c: I2C adapter 7, bus speed 400000 Hz
[    0.857603] clocksource: Switched to clocksource arch_sys_counter
[    0.863707] VFS: Disk quotas dquot_6.6.0
[    0.867612] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.874641] pnp: PnP ACPI: disabled
[    0.882743] OF: /soc/thermal-zones/sensor-thermal3/cooling-maps/map0: could not find phandle
[    0.891085] missing cooling_device property
[    0.895306] failed to build thermal zone sensor-thermal3: -22
[    0.901165] NET: Registered protocol family 2
[    0.905802] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.912785] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[    0.919397] TCP: Hash tables configured (established 8192 bind 8192)
[    0.925761] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.931692] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.938160] NET: Registered protocol family 1
[    0.942751] RPC: Registered named UNIX socket transport module.
[    0.948576] RPC: Registered udp transport module.
[    0.953322] RPC: Registered tcp transport module.
[    0.958073] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.964558] PCI: CLS 0 bytes, default 128
[    0.969087] hw perfevents: enabled with armv8_cortex_a57 PMU driver, 1 counters available
[    0.977255] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 1 counters available
[    0.985645] kvm [1]: HYP mode not available
[    0.991397] futex hash table entries: 1024 (order: 5, 131072 bytes)
[    0.997646] audit: initializing netlink subsys (disabled)
[    1.003041] audit: type=2000 audit(0.755:1): initialized
[    1.008781] workingset: timestamp_bits=46 max_order=18 bucket_order=0
[    1.020511] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.026782] NFS: Registering the id_resolver key type
[    1.031755] Key type id_resolver registered
[    1.035985] Key type id_legacy registered
[    1.040039] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.046900] 9p: Installing v9fs 9p2000 file system support
[    1.054265] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    1.061561] io scheduler noop registered
[    1.065616] io scheduler cfq registered (default)
[    1.072763] libphy: mdio_driver_register: phy-bcm-ns2-pci
[    1.079857] gpio_rcar e6050000.gpio: driving 16 GPIOs
[    1.085455] gpio_rcar e6051000.gpio: driving 28 GPIOs
[    1.090835] gpio_rcar e6052000.gpio: driving 15 GPIOs
[    1.096239] gpio_rcar e6053000.gpio: driving 16 GPIOs
[    1.101665] gpio_rcar e6054000.gpio: driving 18 GPIOs
[    1.107182] gpio_rcar e6055000.gpio: driving 26 GPIOs
[    1.112767] gpio_rcar e6055400.gpio: driving 32 GPIOs
[    1.117986] gpio_rcar e6055800.gpio: driving 4 GPIOs
[    1.124174] OF: PCI: host bridge /soc/pcie@fe000000 ranges:
[    1.129671] OF: PCI:    IO 0xfe100000..0xfe1fffff -> 0x00000000
[    1.135617] OF: PCI:   MEM 0xfe200000..0xfe3fffff -> 0xfe200000
[    1.141580] OF: PCI:   MEM 0x30000000..0x37ffffff -> 0x30000000
[    1.147536] OF: PCI:   MEM 0x38000000..0x3fffffff -> 0x38000000
[    1.203603] rcar-pcie fe000000.pcie: PCIe link down
[    1.208451] OF: PCI: host bridge /soc/pcie@ee800000 ranges:
[    1.214010] OF: PCI:    IO 0xee900000..0xee9fffff -> 0x00000000
[    1.219965] OF: PCI:   MEM 0xeea00000..0xeebfffff -> 0xeea00000
[    1.225927] OF: PCI:   MEM 0xc0000000..0xc7ffffff -> 0xc0000000
[    1.231885] OF: PCI:   MEM 0xc8000000..0xcfffffff -> 0xc8000000
[    1.287915] rcar-pcie ee800000.pcie: PCIe link down
[    1.309538] xen:xen_evtchn: Event-channel device installed
[    1.316205] bd9571mwv 7-0030: bd9571mwv probed
[    1.323949] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.331648] SuperH (H)SCI(F) driver initialized
[    1.336506] e6e68000.serial: ttySC1 at MMIO 0xe6e68000 (irq = 138, base_baud = 0) is a scif
[    1.345302] msm_serial: driver initialized
[    1.349640] [drm] Initialized
[    1.353137] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.359649] [drm] No driver support for vblank timestamp query.
[    1.366757] Unable to detect cache hierarchy from DT for CPU 0
[    1.375742] loop: module loaded
[    1.379630] hisi_sas: driver version v1.6
[    1.385395] scsi host0: sata_rcar
[    1.388828] ata1: SATA max UDMA/133 irq 162
[    1.394715] libphy: Fixed MDIO Bus: probed
[    1.399196] tun: Universal TUN/TAP device driver, 1.6
[    1.404159] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    1.411543] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.417285] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.423301] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[    1.430248] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.435907] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    1.443722] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.449729] sky2: driver version 1.30
[    1.481913] libphy: ravb_mii: probed
[    1.486160] ravb e6800000.ethernet eth0: Base address at 0xe6800000, de:ad:be:ef:01:01, IRQ 135.
[    1.495234] xen_netfront: Initialising Xen virtual ethernet driver
[    1.501535] VFIO - User Level meta-driver version: 0.3
[    1.507874] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.514316] ehci-pci: EHCI PCI platform driver
[    1.518832] ehci-platform: EHCI generic platform driver
[    1.524207] ehci-platform ee080100.usb: Error: DMA mask configuration failed
[    1.531192] ehci-platform: probe of ee080100.usb failed with error -5
[    1.537687] ehci-platform ee0a0100.usb: Error: DMA mask configuration failed
[    1.544733] ehci-platform: probe of ee0a0100.usb failed with error -5
[    1.551221] ehci-platform ee0c0100.usb: Error: DMA mask configuration failed
[    1.558295] ehci-platform: probe of ee0c0100.usb failed with error -5
[    1.564819] ehci-exynos: EHCI EXYNOS driver
[    1.569105] ehci-msm: Qualcomm On-Chip EHCI Host Controller
[    1.574701] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.580845] ohci-pci: OHCI PCI platform driver
[    1.585353] ohci-platform: OHCI generic platform driver
[    1.590696] ohci-platform: probe of ee080000.usb failed with error -5
[    1.597105] ohci-platform: probe of ee0a0000.usb failed with error -5
[    1.603583] ohci-platform: probe of ee0c0000.usb failed with error -5
[    1.610083] ohci-exynos: OHCI EXYNOS driver
[    1.614599] xhci-hcd ee000000.usb: xHCI Host Controller
[    1.619739] xhci-hcd ee000000.usb: new USB bus registered, assigned bus number 1
[    1.627198] xhci-hcd ee000000.usb: Direct firmware load for r8a779x_usb3_v3.dlmem failed with error -2
[    1.636501] xhci-hcd ee000000.usb: can't setup: -2
[    1.641336] xhci-hcd ee000000.usb: USB bus 1 deregistered
[    1.646799] xhci-hcd: probe of ee000000.usb failed with error -2
[    1.653090] usbcore: registered new interface driver usb-storage
[    1.660152] renesas_usbhs e6590000.usb: no transceiver found
[    1.665820] renesas_usbhs e6590000.usb: gadget probed
[    1.670923] renesas_usbhs e6590000.usb: probed
[    1.675632] mousedev: PS/2 mouse device common for all mice
[    1.682017] i2c /dev entries driver
[    1.692111] cs2000-cp 2-004f: revision - C1
[    1.696236] i2c-rcar e6510000.i2c: probed
[    1.701004] 5p49x 4-006a: Rev.0xff, probed
[    1.705034] i2c-rcar e66d8000.i2c: probed
[    1.709469] adv7482 4-0034: chip found @ 0x68 (e66d8000.i2c)
[    1.730072] adv7482 4-0034: adv7482 revision is 2143
[    1.738342] random: fast init done
[    1.802169] adv7482 4-0034: adv7482 txa power down
[    1.809616] ata1: link resume succeeded after 1 retries
[    1.846169] adv7482 4-0034: adv7482 txb power down
[    1.851055] adv7482 4-0034: adv7482 enable csi1 and csi4
[    1.857803] adv7482 4-0070: chip found @ 0xe0 (e66d8000.i2c)
[    1.878067] adv7482 4-0070: adv7482 revision is 2143
[    1.921102] ata1: SATA link down (SStatus 0 SControl 300)
[    1.946167] adv7482 4-0070: adv7482 txa power down
[    1.990167] adv7482 4-0070: adv7482 txb power down
[    1.995049] adv7482 4-0070: adv7482 enable csi1 and csi4
[    2.014344] rcar-vin e6ef0000.video: Device registered as video0
[    2.020614] rcar-vin e6ef1000.video: Device registered as video1
[    2.026837] rcar-vin e6ef2000.video: Device registered as video2
[    2.033074] rcar-vin e6ef3000.video: Device registered as video3
[    2.039305] rcar-vin e6ef4000.video: Device registered as video4
[    2.045579] rcar-vin e6ef5000.video: Device registered as video5
[    2.051853] rcar-vin e6ef6000.video: Device registered as video6
[    2.058141] rcar-vin e6ef7000.video: Device registered as video7
[    2.064508] rcar-csi2 fea80000.csi2: 1 lanes found. virtual channel number 1 use
[    2.072311] rcar-csi2 feaa0000.csi2: 4 lanes found. virtual channel number 1 use
[    2.081951] rcar_gen3_thermal e6198000.thermal: Thermal sensor probed
[    2.089614] rcar_gen3_thermal e61a0000.thermal: Thermal sensor probed
[    2.096148] rcar_gen3_thermal e61a8000.thermal: Can't register thermal zone
[    2.104167] cpu cpu0: failed to get clock: -2
[    2.108454] cpufreq-dt: probe of cpufreq-dt failed with error -2
[    2.114801] sdhci: Secure Digital Host Controller Interface driver
[    2.120886] sdhci: Copyright(c) Pierre Ossman
[    2.125852] sh_mobile_sdhi ee100000.sd: Got CD GPIO
[    2.130648] sh_mobile_sdhi ee100000.sd: Got WP GPIO
[    2.261705] sh_mobile_sdhi ee140000.sd: mmc0 base at 0xee140000 max clock rate 200 MHz
[    2.269892] sh_mobile_sdhi ee160000.sd: Got CD GPIO
[    2.274739] sh_mobile_sdhi ee160000.sd: Got WP GPIO
[    2.279827] Synopsys Designware Multimedia Card Interface Driver
[    2.288458] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.294722] ledtrig-cpu: registered to indicate activity on CPUs
[    2.302530] usbcore: registered new interface driver usbhid
[    2.308010] usbhid: USB HID core driver
[    2.321447] rcar_sound ec500000.sound: probed
[    2.326043] NET: Registered protocol family 17
[    2.330458] 9pnet: Installing 9P2000 support
[    2.334769] Key type dns_resolver registered
[    2.339524] registered taskstats version 1
[    2.347693] thermal emergency: shutdown cpu none
[    2.352258] thermal emergency: set temperature to 110 celsius
[    2.358324] renesas_irqc e61c0000.interrupt-controller: driving 6 irqs
[    2.365836] phy_rcar_gen3_usb2 ee080200.usb-phy: Unbalanced pm_runtime_enable!
[    2.373944] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.380461] [drm] No driver support for vblank timestamp query.
[    2.421760] mmc0: new MMC card at address 0001
[    2.426495] mmcblk0: mmc0:0001 BGSD3R 0 B 
[    2.487173] platform fead0000.hdmi0: Detected HDMI controller 0x20:0x1a:0xa0:0xc1
[    2.494885] platform fead0000.hdmi0: registered DesignWare HDMI I2C bus driver
[    2.502142] platform feae0000.hdmi1: Detected HDMI controller 0x20:0x1a:0xa0:0xc1
[    2.509792] platform feae0000.hdmi1: registered DesignWare HDMI I2C bus driver
(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0)
(XEN) '0' pressed -> dumping Dom0's registers
(XEN) *** Dumping Dom0 vcpu#0 state: ***
(XEN) ----[ Xen-4.7.0  arm64  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) PC:     ffff000008097ef8
(XEN) LR:     ffff00000808510c
(XEN) SP_EL0: ffff000008eb0000
(XEN) SP_EL1: ffff000008eb3f10
(XEN) CPSR:   600001c5 MODE:64-bit EL1h (Guest Kernel, handler)
(XEN)      X0: 0000000000000000  X1: 0000000000000000  X2: 0000000000000001
(XEN)      X3: 0000000000000001  X4: 00000000000001c0  X5: 0100000000000000
(XEN)      X6: 000f78b9bade2c38  X7: ffff80003ef4e9b8  X8: ffff000008ec08d0
(XEN)      X9: ffff000008eb0000 X10: 0000000000000870 X11: 00000000000081ab
(XEN)     X12: 0000000000000001 X13: 000000000000004c X14: 0000000000000033
(XEN)     X15: 0000000000000019 X16: 0000000000000001 X17: 0000000000000007
(XEN)     X18: 000000000000000e X19: ffff000008eb72e8 X20: ffff000008eb7258
(XEN)     X21: 0000000000000001 X22: 0000000000000000 X23: 0000000000000000
(XEN)     X24: ffff000008eb0000 X25: ffff000008e7a8b0 X26: ffff000008ed38ab
(XEN)     X27: ffff000008eb7000 X28: ffff000008eb7000  FP: ffff000008eb3f10
(XEN) 
(XEN)    ELR_EL1: ffff000008085110
(XEN)    ESR_EL1: 96000004
(XEN)    FAR_EL1: 0000000000000028
(XEN) 
(XEN)  SCTLR_EL1: 34d5d91d
(XEN)    TCR_EL1: 34b5103510
(XEN)  TTBR0_EL1: 0000000700f91000
(XEN)  TTBR1_EL1: 0000000700fd9000
(XEN) 
(XEN)   VTCR_EL2: 80023558
(XEN)  VTTBR_EL2: 000100073ff2c000
(XEN) 
(XEN)  SCTLR_EL2: 30cd183d
(XEN)    HCR_EL2: 000000008038663f
(XEN)  TTBR0_EL2: 000000007ff04000
(XEN) 
(XEN)    ESR_EL2: 07e00000
(XEN)  HPFAR_EL2: 0000000000f10100
(XEN)    FAR_EL2: ffff000008000f00
(XEN) 
(XEN) Guest stack trace from sp=ffff000008eb3f10:
(XEN)    ffff000008eb3f20 ffff0000080f71d0 ffff000008eb3f80 ffff00000896b020
(XEN)    0000000000000002 ffff000008f92000 ffff000008f92000 ffff000008eb7000
(XEN)    ffff80003efff700 ffff000008e01408 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000700db0018 ffff000008eb3fa0 ffff000008db0b40
(XEN)    ffff000008f92000 ffff000008db0b2c ffff000008eb3ff0 ffff000008db01d8
(XEN)    0000000000000000 0000000000000000 0000000708000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 ffff000008e01408
(XEN)    0000000000000000 000000070097625c
(XEN) *** Dumping Dom0 vcpu#1 state: ***
(XEN) ----[ Xen-4.7.0  arm64  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) PC:     ffff000008097ef8
(XEN) LR:     ffff00000808510c
(XEN) SP_EL0: ffff8000278f8000
(XEN) SP_EL1: ffff8000278fbf60
(XEN) CPSR:   600000c5 MODE:64-bit EL1h (Guest Kernel, handler)
(XEN)      X0: 0000000000000000  X1: 0000000000000000  X2: 0000000000000001
(XEN)      X3: 0000000000000001  X4: 00000000000000c0  X5: 0100000000000000
(XEN)      X6: 0012181bb2dd5dab  X7: ffff80003ef639b8  X8: ffff8000278ea1d0
(XEN)      X9: ffff8000278f8000 X10: 0000000000000870 X11: 0000000000007afb
(XEN)     X12: 0000000000000001 X13: 000000000000004c X14: 0000000000000033
(XEN)     X15: 0000000000000019 X16: 0000000000000001 X17: 0000000000000007
(XEN)     X18: 000000000000000e X19: ffff000008eb72e8 X20: ffff000008eb7258
(XEN)     X21: 0000000000000002 X22: 0000000000000000 X23: 0000000000000000
(XEN)     X24: ffff8000278f8000 X25: ffff000008e7a8b0 X26: ffff000008ed38ab
(XEN)     X27: ffff000008eb7000 X28: ffff000008eb7000  FP: ffff8000278fbf60
(XEN) 
(XEN)    ELR_EL1: ffff000008085110
(XEN)    ESR_EL1: 00000000
(XEN)    FAR_EL1: 0000000000000000
(XEN) 
(XEN)  SCTLR_EL1: 34d5d91d
(XEN)    TCR_EL1: 34b5103510
(XEN)  TTBR0_EL1: 0000000700f91000
(XEN)  TTBR1_EL1: 0000000700fd9000
(XEN) 
(XEN)   VTCR_EL2: 80023558
(XEN)  VTTBR_EL2: 000100073ff2c000
(XEN) 
(XEN)  SCTLR_EL2: 30cd183d
(XEN)    HCR_EL2: 000000008038663f
(XEN)  TTBR0_EL2: 000000007ff04000
(XEN) 
(XEN)    ESR_EL2: 07e00000
(XEN)  HPFAR_EL2: 0000000000f10100
(XEN)    FAR_EL2: ffff000008000f00
(XEN) 
(XEN) Guest stack trace from sp=ffff8000278fbf60:
(XEN)    ffff8000278fbf70 ffff0000080f71d0 ffff8000278fbfd0 ffff00000808e100
(XEN)    0000000000000001 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 00000007009761a4
(XEN)    0000000000000000 0000000000000000 ffffffffffffffff ffffffffffffffff
(XEN) *** Dumping Dom0 vcpu#2 state: ***
(XEN) ----[ Xen-4.7.0  arm64  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) PC:     ffff000008097ef8
(XEN) LR:     ffff00000808510c
(XEN) SP_EL0: ffff8000278fc000
(XEN) SP_EL1: ffff8000278fff60
(XEN) CPSR:   600000c5 MODE:64-bit EL1h (Guest Kernel, handler)
(XEN)      X0: 0000000000000000  X1: 0000000000000000  X2: 0000000000000001
(XEN)      X3: 0000000000000001  X4: 00000000000000c0  X5: 0100000000000000
(XEN)      X6: 002fa86c12d44547  X7: 0000001101db8d0e  X8: ffff8000278eae50
(XEN)      X9: ffff8000278fc000 X10: 0000000000000870 X11: 0000000000001392
(XEN)     X12: 0000000000000001 X13: ffff800026bdd800 X14: ffffffffffffffff
(XEN)     X15: 0000000000000019 X16: 0000000000000001 X17: 0000000000000007
(XEN)     X18: 000000000000000e X19: ffff000008eb72e8 X20: ffff000008eb7258
(XEN)     X21: 0000000000000004 X22: 0000000000000000 X23: 0000000000000000
(XEN)     X24: ffff8000278fc000 X25: ffff000008e7a8b0 X26: ffff000008ed38ab
(XEN)     X27: ffff000008eb7000 X28: ffff000008eb7000  FP: ffff8000278fff60
(XEN) 
(XEN)    ELR_EL1: ffff000008085110
(XEN)    ESR_EL1: 96000004
(XEN)    FAR_EL1: 0000000000000000
(XEN) 
(XEN)  SCTLR_EL1: 34d5d91d
(XEN)    TCR_EL1: 34b5103510
(XEN)  TTBR0_EL1: 0000000700f91000
(XEN)  TTBR1_EL1: 0000000700fd9000
(XEN) 
(XEN)   VTCR_EL2: 80023558
(XEN)  VTTBR_EL2: 000100073ff2c000
(XEN) 
(XEN)  SCTLR_EL2: 30cd183d
(XEN)    HCR_EL2: 000000008038663f
(XEN)  TTBR0_EL2: 000000007ff04000
(XEN) 
(XEN)    ESR_EL2: 07e00000
(XEN)  HPFAR_EL2: 0000000000f10100
(XEN)    FAR_EL2: ffff000008000f00
(XEN) 
(XEN) Guest stack trace from sp=ffff8000278fff60:
(XEN)    ffff8000278fff70 ffff0000080f71d0 ffff8000278fffd0 ffff00000808e100
(XEN)    0000000000000002 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 00000007009761a4
(XEN)    0000000000000000 0000000000000000 dfffffffffffffff ffffffffffffffff
(XEN) *** Dumping Dom0 vcpu#3 state: ***
(XEN) ----[ Xen-4.7.0  arm64  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) PC:     ffff000008970424
(XEN) LR:     ffff0000080e33e0
(XEN) SP_EL0: ffff800026b04000
(XEN) SP_EL1: ffff80003ef86e30
(XEN) CPSR:   000001c5 MODE:64-bit EL1h (Guest Kernel, handler)
(XEN)      X0: ffff80003ef8d900  X1: 0000000018bb18ba  X2: 0000000000000001
(XEN)      X3: 00000000000018ba  X4: ffff000008ecf708  X5: ffff000008eccfd8
(XEN)      X6: ffff000008eb6000  X7: ffff000008eceb80  X8: ffff000008e7c700
(XEN)      X9: 0000000000000000 X10: 0000000000000040 X11: ffff000008ecde00
(XEN)     X12: ffff000008ecde00 X13: ffff000008f9bfd2 X14: ffffffffffffff54
(XEN)     X15: 0000000000000008 X16: 0000000000000001 X17: 0000000000000007
(XEN)     X18: ffff8000a6b06e9b X19: ffff80003ef8d900 X20: ffff000008e7b000
(XEN)     X21: ffff000008eb7000 X22: 0000000000000003 X23: ffff800026890c80
(XEN)     X24: ffff80003ef8a1d0 X25: ffff000008ed38db X26: 0000000087ac63a0
(XEN)     X27: ffff000008124990 X28: ffff80003ef8a1c0  FP: ffff80003ef86e30
(XEN) 
(XEN)    ELR_EL1: ffff000008970788
(XEN)    ESR_EL1: 96000004
(XEN)    FAR_EL1: 0000000000000028
(XEN) 
(XEN)  SCTLR_EL1: 34d5d91d
(XEN)    TCR_EL1: 34b5103510
(XEN)  TTBR0_EL1: 0000000700f91000
(XEN)  TTBR1_EL1: 0000000700fd9000
(XEN) 
(XEN)   VTCR_EL2: 80023558
(XEN)  VTTBR_EL2: 000100073ff2c000
(XEN) 
(XEN)  SCTLR_EL2: 30cd183d
(XEN)    HCR_EL2: 000000008038663f
(XEN)  TTBR0_EL2: 000000007ff04000
(XEN) 
(XEN)    ESR_EL2: 07e00000
(XEN)  HPFAR_EL2: 0000000000f10100
(XEN)    FAR_EL2: ffff000008000f00
(XEN) 
(XEN) Guest stack trace from sp=ffff80003ef86e30:
(XEN)    ffff80003ef86e70 ffff0000081154a0 ffff800026890c80 ffff800026b04000
(XEN)    0000000000000000 0000000000000001 0000000000000001 ffff000008c530c8
(XEN)    ffff80003ef86ea0 ffff000008124950 ffff800026b06ea8 ffff800026b06da0
(XEN)    0000000087ac6580 ffff0000081249b8 ffff80003ef86ec0 ffff0000081249d4
(XEN)    ffff80003ef8a5d8 ffff800026b06da0 ffff80003ef86ef0 ffff000008115fa4
(XEN)    ffff80003ef8a180 ffff80003ef8a5d8 0000000087ac63a0 0000000000000001
(XEN)    ffff80003ef86f50 ffff000008116330 ffff80003ef8a180 0000000000000003
(XEN)    0000000087ac63a0 7fffffffffffffff ffff80003ef8a198 ffff80003ef8a228
(XEN)    ffff80003ef8a268 ffff80003ef8a2a8 0000000087ac63a0 ffff800026b04000
(XEN)    ffff80003ef86fb0 ffff000008818638 ffff800027804800 ffff000008eb9b70
(XEN)    ffff800027810c00 0000000000000003 ffff800027808000 ffff800026890c80
(XEN)    ffff80003ef830a0 ffff80003ef87090 ffff000008ec3000 ffff800026b04000
(XEN)    ffff80003ef86fc0 ffff000008106b98 ffff80003ef86ff0 ffff00000810197c
(XEN)    ffff000008e79000 0000000000000000 0000000000000000 0000000000000001
(XEN)    ffff80003ef87000 ffff000008101fec
(XEN) 'q' pressed -> dumping domain info (now=0x17:AE3C8449)
(XEN) General information for domain 0:
(XEN)     refcnt=3 dying=0 pause_count=0
(XEN)     nr_pages=192512 xenheap_pages=5 shared_pages=0 paged_pages=0 dirty_cpus={} max_pages=4294967295
(XEN)     handle=00000000-0000-0000-0000-000000000000 vm_assist=00000000
(XEN) p2m mappings for domain 0 (vmid 1):
(XEN)   1G mappings: 0 (shattered 0)
(XEN)   2M mappings: 633 (shattered 1)
(XEN)   4K mappings: 1887
(XEN) Rangesets belonging to domain 0:
(XEN)     Interrupts { 32-43, 48-53, 55, 61-62, 66-69, 71-95, 99-101, 104-107, 116-119, 134, 137, 139-142, 144-145}
(XEN)     I/O Memory { 30000-40000, c0000-d0000, e6020-e6021, e6050-e6056, e6060-e6061, e60a0-e60a1, e60b0-e60b1, }
(XEN) NODE affinity for domain 0: [0]
(XEN) VCPU information and callbacks for domain 0:
(XEN)     VCPU0: CPU0 [has=F] poll=0 upcall_pend=00 upcall_mask=01 dirty_cpus={}
(XEN)     cpu_hard_affinity={0-127} cpu_soft_affinity={0-127}
(XEN)     pause_count=0 pause_flags=0
(XEN) GICH_LRs (vcpu 0) mask=0
(XEN)    VCPU_LR[0]=0
(XEN)    VCPU_LR[1]=0
(XEN)    VCPU_LR[2]=0
(XEN)    VCPU_LR[3]=0
(XEN) Inflight irq=27 lr=255
(XEN) Pending irq=27
(XEN)     No periodic timer
(XEN)     VCPU1: CPU1 [has=F] poll=0 upcall_pend=00 upcall_mask=01 dirty_cpus={}
(XEN)     cpu_hard_affinity={0-127} cpu_soft_affinity={0-127}
(XEN)     pause_count=0 pause_flags=1
(XEN) GICH_LRs (vcpu 1) mask=0
(XEN)    VCPU_LR[0]=0
(XEN)    VCPU_LR[1]=0
(XEN)    VCPU_LR[2]=0
(XEN)    VCPU_LR[3]=0
(XEN)     No periodic timer
(XEN)     VCPU2: CPU2 [has=F] poll=0 upcall_pend=00 upcall_mask=01 dirty_cpus={}
(XEN)     cpu_hard_affinity={0-127} cpu_soft_affinity={0-127}
(XEN)     pause_count=0 pause_flags=1
(XEN) GICH_LRs (vcpu 2) mask=0
(XEN)    VCPU_LR[0]=0
(XEN)    VCPU_LR[1]=0
(XEN)    VCPU_LR[2]=0
(XEN)    VCPU_LR[3]=0
(XEN)     No periodic timer
(XEN)     VCPU3: CPU3 [has=T] poll=0 upcall_pend=00 upcall_mask=01 dirty_cpus={}
(XEN)     cpu_hard_affinity={0-127} cpu_soft_affinity={0-127}
(XEN)     pause_count=0 pause_flags=0
(XEN) GICH_LRs (vcpu 3) mask=1
(XEN)    VCPU_LR[0]=2a00001b
(XEN)    VCPU_LR[1]=0
(XEN)    VCPU_LR[2]=0
(XEN)    VCPU_LR[3]=0
(XEN) Inflight irq=27 lr=0
(XEN)     No periodic timer
(XEN) Notifying guest 0:0 (virq 1, port 0)
(XEN) Notifying guest 0:1 (virq 1, port 0)
(XEN) Notifying guest 0:2 (virq 1, port 0)
(XEN) Notifying guest 0:3 (virq 1, port 0)
(XEN) 'e' pressed -> dumping event-channel info
(XEN) Event channel information for domain 0:
(XEN) Polling vCPUs: {}
(XEN)     port [p/m/s]
(XEN)        1 [0/0/  -   ]: s=2 n=0 x=0 d=0
(XEN)        2 [1/1/  -   ]: s=5 n=0 x=0 v=2
(XEN) Dumping timer queues:
(XEN) CPU00:
(XEN)   ex=        3080us timer=000080037ff29e60 cb=vtimer.c#virt_timer_expired(000080037ff29e50)
(XEN)   ex=        8220us timer=000080037ffa9880 cb=sched_credit.c#csched_acct(000080037ffa9860)
(XEN)   ex=        5938us timer=000080037ffa9a68 cb=sched_credit.c#csched_tick(0000000000000000)
(XEN) CPU01:
(XEN)   ex=       31081us timer=000080037fef1e60 cb=vtimer.c#virt_timer_expired(000080037fef1e50)
(XEN)   ex=       36331us timer=000080037ffa9e28 cb=sched_credit.c#csched_tick(0000000000000001)
(XEN) CPU02:
(XEN)   ex=       51081us timer=000080037fef0e60 cb=vtimer.c#virt_timer_expired(000080037fef0e50)
(XEN)   ex=       56338us timer=000080037ffd4088 cb=sched_credit.c#csched_tick(0000000000000002)
(XEN) CPU03:
(XEN)   ex=       66771us timer=000080037ffd42d8 cb=sched_credit.c#csched_tick(0000000000000003)
(XEN)   ex=       96717us timer=000080037ffd20e0 cb=schedule.c#s_timer_fn(0000000000000000)
(XEN) CPU04:
(XEN)   ex=       92386us timer=000080037ffd4528 cb=sched_credit.c#csched_tick(0000000000000004)
(XEN) CPU05:
(XEN)   ex=      101762us timer=000080037ffd4778 cb=sched_credit.c#csched_tick(0000000000000005)
(XEN) CPU06:
(XEN)   ex=      109017us timer=000080037ffd49c8 cb=sched_credit.c#csched_tick(0000000000000006)
(XEN) CPU07:
(XEN)   ex=      115337us timer=000080037ffd4c18 cb=sched_credit.c#csched_tick(0000000000000007)
(XEN) Dumping timer queues:
(XEN) CPU00:
(XEN)   ex=         476us timer=000080037ffa9a68 cb=sched_credit.c#csched_tick(0000000000000000)
(XEN)   ex=       20053us timer=000080037ffa9880 cb=sched_credit.c#csched_acct(000080037ffa9860)
(XEN)   ex=        1074us timer=000080037ff29e60 cb=vtimer.c#virt_timer_expired(000080037ff29e50)
(XEN) CPU01:
(XEN)   ex=       33075us timer=000080037fef1e60 cb=vtimer.c#virt_timer_expired(000080037fef1e50)
(XEN)   ex=       35812us timer=000080037ffa9e28 cb=sched_credit.c#csched_tick(0000000000000001)
(XEN) CPU02:
(XEN)   ex=       49075us timer=000080037fef0e60 cb=vtimer.c#virt_timer_expired(000080037fef0e50)
(XEN)   ex=       54043us timer=000080037ffd4088 cb=sched_credit.c#csched_tick(0000000000000002)
(XEN) CPU03:
(XEN)   ex=       72418us timer=000080037ffd42d8 cb=sched_credit.c#csched_tick(0000000000000003)
(XEN)   ex=       96718us timer=000080037ffd20e0 cb=schedule.c#s_timer_fn(0000000000000000)
(XEN) CPU04:
(XEN)   ex=       91416us timer=000080037ffd4528 cb=sched_credit.c#csched_tick(0000000000000004)
(XEN) CPU05:
(XEN)   ex=      100953us timer=000080037ffd4778 cb=sched_credit.c#csched_tick(0000000000000005)
(XEN) CPU06:
(XEN)   ex=      110654us timer=000080037ffd49c8 cb=sched_credit.c#csched_tick(0000000000000006)
(XEN) CPU07:
(XEN)   ex=      120332us timer=000080037ffd4c18 cb=sched_credit.c#csched_tick(0000000000000007)
(XEN) Synced stime skew: max=120ns avg=120ns samples=1 current=120ns
(XEN) Synced cycles skew: max=0 avg=0 samples=1 current=0
(XEN) sched_smt_power_savings: disabled
(XEN) NOW=187135494059
(XEN) Online Cpus: 0-7
(XEN) Cpupool 0:
(XEN) Cpus: 0-7
(XEN) Scheduler: SMP Credit Scheduler (credit)
(XEN) info:
(XEN)   ncpus              = 8
(XEN)   master             = 0
(XEN)   credit             = 2400
(XEN)   credit balance     = 0
(XEN)   weight             = 256
(XEN)   runq_sort          = 6164
(XEN)   default-weight     = 256
(XEN)   tslice             = 30ms
(XEN)   ratelimit          = 1000us
(XEN)   credits per msec   = 10
(XEN)   ticks per tslice   = 3
(XEN)   migration delay    = 0us
(XEN) idlers: 00000000,00000000,00000000,000000f6
(XEN) active vcpus:
(XEN)     1: [0.3] pri=-1 flags=0 cpu=3 credit=-856 [w=256,cap=0]
(XEN) CPU[00]  sort=6164, sibling=00000000,00000000,00000000,00000001, core=00000000,00000000,00000000,00000001
(XEN)   run: [32767.0] pri=0 flags=0 cpu=0
(XEN) CPU[01]  sort=6164, sibling=00000000,00000000,00000000,00000002, core=00000000,00000000,00000000,00000002
(XEN)   run: [32767.1] pri=-64 flags=0 cpu=1
(XEN) CPU[02]  sort=6164, sibling=00000000,00000000,00000000,00000004, core=00000000,00000000,00000000,00000004
(XEN)   run: [32767.2] pri=-64 flags=0 cpu=2
(XEN) CPU[03]  sort=6164, sibling=00000000,00000000,00000000,00000008, core=00000000,00000000,00000000,00000008
(XEN)   run: [0.3] pri=-1 flags=0 cpu=3 credit=-1333 [w=256,cap=0]
(XEN)     1: [32767.3] pri=-64 flags=0 cpu=3
(XEN) CPU[04]  sort=6164, sibling=00000000,00000000,00000000,00000010, core=00000000,00000000,00000000,00000010
(XEN)   run: [32767.4] pri=-64 flags=0 cpu=4
(XEN) CPU[05]  sort=6164, sibling=00000000,00000000,00000000,00000020, core=00000000,00000000,00000000,00000020
(XEN)   run: [32767.5] pri=-64 flags=0 cpu=5
(XEN) CPU[06]  sort=6164, sibling=00000000,00000000,00000000,00000040, core=00000000,00000000,00000000,00000040
(XEN)   run: [32767.6] pri=-64 flags=0 cpu=6
(XEN) CPU[07]  sort=6164, sibling=00000000,00000000,00000000,00000080, core=00000000,00000000,00000000,00000080
(XEN)   run: [32767.7] pri=-64 flags=0 cpu=7
(XEN) sched_smt_power_savings: disabled
(XEN) NOW=198914291251
(XEN) Online Cpus: 0-7
(XEN) Cpupool 0:
(XEN) Cpus: 0-7
(XEN) Scheduler: SMP Credit Scheduler (credit)
(XEN) info:
(XEN)   ncpus              = 8
(XEN)   master             = 0
(XEN)   credit             = 2400
(XEN)   credit balance     = 0
(XEN)   weight             = 256
(XEN)   runq_sort          = 6551
(XEN)   default-weight     = 256
(XEN)   tslice             = 30ms
(XEN)   ratelimit          = 1000us
(XEN)   credits per msec   = 10
(XEN)   ticks per tslice   = 3
(XEN)   migration delay    = 0us
(XEN) idlers: 00000000,00000000,00000000,000000f6
(XEN) active vcpus:
(XEN)     1: [0.3] pri=-1 flags=0 cpu=3 credit=-775 [w=256,cap=0]
(XEN) CPU[00]  sort=6551, sibling=00000000,00000000,00000000,00000001, core=00000000,00000000,00000000,00000001
(XEN)   run: [32767.0] pri=0 flags=0 cpu=0
(XEN) CPU[01]  sort=6551, sibling=00000000,00000000,00000000,00000002, core=00000000,00000000,00000000,00000002
(XEN)   run: [32767.1] pri=-64 flags=0 cpu=1
(XEN) CPU[02]  sort=6551, sibling=00000000,00000000,00000000,00000004, core=00000000,00000000,00000000,00000004
(XEN)   run: [32767.2] pri=-64 flags=0 cpu=2
(XEN) CPU[03]  sort=6551, sibling=00000000,00000000,00000000,00000008, core=00000000,00000000,00000000,00000008
(XEN)   run: [0.3] pri=-1 flags=0 cpu=3 credit=-1252 [w=256,cap=0]
(XEN)     1: [32767.3] pri=-64 flags=0 cpu=3
(XEN) CPU[04]  sort=6551, sibling=00000000,00000000,00000000,00000010, core=00000000,00000000,00000000,00000010
(XEN)   run: [32767.4] pri=-64 flags=0 cpu=4
(XEN) CPU[05]  sort=6551, sibling=00000000,00000000,00000000,00000020, core=00000000,00000000,00000000,00000020
(XEN)   run: [32767.5] pri=-64 flags=0 cpu=5
(XEN) CPU[06]  sort=6551, sibling=00000000,00000000,00000000,00000040, core=00000000,00000000,00000000,00000040
(XEN)   run: [32767.6] pri=-64 flags=0 cpu=6
(XEN) CPU[07]  sort=6551, sibling=00000000,00000000,00000000,00000080, core=00000000,00000000,00000000,00000080
(XEN)   run: [32767.7] pri=-64 flags=0 cpu=7
(XEN) 'R' pressed -> rebooting machine
[    0.000149] NOTICE:  BL2: R-Car H3 Initial Program Loader(CA57)
[    0.004585] NOTICE:  BL2: Initial Program Loader(Rev.2.0.6)
[    0.010119] NOTICE:  BL2: PRR is R-Car H3 Ver.2.0
[    0.014787] NOTICE:  BL2: Board is Salvator-X Rev.1.0
[    0.019814] NOTICE:  BL2: Boot device is HyperFlash(160MHz)
[    0.025325] NOTICE:  BL2: LCM state is CM
[    0.029368] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x53
[    0.035384] NOTICE:  BL2: DDR3200(rev.0.40)
[    0.050718] NOTICE:  BL2: [COLD_BOOT]
[    0.059488] NOTICE:  BL2: DRAM Split is 4ch
[    0.062182] NOTICE:  BL2: QoS is default setting(rev.0.21)
[    0.067625] NOTICE:  BL2: DRAM refresh interval 1.95 usec
[    0.072982] NOTICE:  BL2: Periodic Write DQ Training
[    0.078013] NOTICE:  BL2: v1.5(release):af9f429
[    0.082400] NOTICE:  BL2: Built : 07:07:22, Jul 14 2020
[    0.087587] NOTICE:  BL2: Normal boot
[    0.091228] NOTICE:  BL2: dst=0xe6325100 src=0x8180000 len=512(0x200)
[    0.097614] NOTICE:  BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
[    0.104223] NOTICE:  BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
[    0.111207] NOTICE:  BL2: dst=0x44100000 src=0x8200000 len=1048576(0x100000)
[    0.122169] NOTICE:  BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)
[    0.132023] NOTICE:  BL2: Booting BL31

Re: [BUG] Xen build for RCAR failing

[Bertrand Marquis]

Hi Manikandan,

> On 19 Aug 2020, at 15:00, Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@in.bosch.com> wrote:
> 
> Hello Bertrand,
> 
> I tried to build Xen on RCAR with the following build configuration.
> 
> Build Configuration:
> BB_VERSION        = "1.30.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "universal"
> TARGET_SYS        = "aarch64-poky-linux"
> MACHINE           = "salvator-x"
> DISTRO            = "poky"
> DISTRO_VERSION    = "2.1.2"
> TUNE_FEATURES     = "aarch64 cortexa57-cortexa53"
> TARGET_FPU        = ""
> SOC_FAMILY        = "rcar-gen3:r8a7795"
> meta              
> meta-poky         
> meta-yocto-bsp    = "tmp:cca8dd15c8096626052f6d8d25ff1e9a606104a3"
> meta-rcar-gen3    = "tmp:95cb48ba09bc7e55fd549817e3e26723409e68d5"
> meta-linaro-toolchain 
> meta-optee        = "tmp:2f51d38048599d9878f149d6d15539fb97603f8f"
> meta-oe           = "tmp:55c8a76da5dc099a7bc3838495c672140cedb78e"
> meta-virtualization = "morty:f3643212c2a87a29e2c8066a1a544612d1598de8"
> meta-selinux      = "jethro:4c75d9cbcf1d75043c7c5ab315aa383d9b227510"
> meta-networking   
> meta-python       = "tmp:55c8a76da5dc099a7bc3838495c672140cedb78e"
> meta-rcar-gen3-xen = "master:affeba788534a04dd30a21dbbb81a573bd033dfa"
> 
> Also enabled the early printk in xen 4.7 and I could able to boot Xen and Dom0.
> 
> But I couldn’t enter into the command prompt of Dom0. Attaching the complete log for your reference.
> 
> I could execute the special keys(0,q,e,R) in xen console. But even after enabling hvc0 in Dom0 commandline, am not seeing any logs after a point and I couldn’t do any operation on Dom0.
> 
> Am I missing something here. Thanks in advance.

Xen is booting properly here and the kernel hvc0 console is also working ([    0.346199] console [hvc0] enabled)

It seems that all your cores are ending up in idle in Linux (all ELR are at the same address).

So you probably have a problem mounting a root filesystem or you network is not coming up.
An other solution would be that you linux is missing the hvc0 console entry in inittab.

I would suggest to try the following:
- pass console=ttySC1 which is probably the second serial line of your board and connect to it to see if linux goes further
- use an sdcard based or usb based root filesystem instead of NFS
- add rootwait option

But all in all Xen works well and you now have a linux boot issue probably not related to xen.

Regards
Bertrand

PS: You might want to switch to xen-user mailing list instead of xen-devel :-)