On Tue, Oct 26, 2021 at 9:27 AM Edward Pickup <[email protected]> wrote:
> Hi Bruce, > Sorry for the formatting issues, email client config issues > > > > *From:* Bruce Ashfield <[email protected]> > *Sent:* 26 October 2021 14:22 > *To:* Edward Pickup <[email protected]> > *Cc:* [email protected]; Bertrand Marquis < > [email protected]>; [email protected]; nd <[email protected]> > *Subject:* Re: [meta-virtualization] Error building Xen device tree for > qemuarm64 > > > > > > > > On Tue, Oct 26, 2021 at 8:58 AM Edward Pickup <[email protected]> > wrote: > > Hi all, > > I have encountered an error while building the arm64 version of the xen > 4.16 recipe in meta-virtualisation, using the master version of poky and > meta-virtuaisation. > I was wondering if anyone was familiar with the issue or knew how to fix > it. The error is as follows: > > ERROR: xen-image-minimal-1.0-r0 do_write_xen_qemuboot_dtb: > ExecutionError('/home/edwpic01/work/master-update-xen/build/metavirt-host-arm64-4.16-release.prj/tmp/work/qemuarm64-poky-linux/xen-image-minimal/1.0-r0/temp/run.do_write_xen_qemuboot_dtb.3679135', > 2, None, None) > ERROR: Logfile of failure stored in: > /home/edwpic01/work/master-update-xen/build/metavirt-host-arm64-4.16-release.prj/tmp/work/qemuarm64-poky-linux/xen-image-minimal/1.0-r0/temp/log.do_write_xen_qemuboot_dtb.3679135 > . > > I believe the relevant part of the log is as follows: > > | [NOTE]: '3' lopper operation files will be processed > | [INFO]: dtb output format detected, writing > /home/edwpic01/work/master-update-xen/build/metavirt-host-arm64-4.16-release.prj/tmp/work/qemuarm64-poky-linux/xen-image-minimal/1.0-r0/deploy-xen-image-minimal-image-complete/xen-image-minimal-qemuarm64-20211026121502.qemuboot.dtb > | [INFO]: writing output dtb: > /home/edwpic01/work/master-update-xen/build/metavirt-host-arm64-4.16-release.prj/tmp/work/qemuarm64-poky-linux/xen-image-minimal/1.0-r0/deploy-xen-image-minimal-image-complete/xen-image-minimal-qemuarm64-20211026121502.qemuboot.dtb > | > /home/edwpic01/work/master-update-xen/build/metavirt-host-arm64-4.16-release.prj/tmp/work/qemuarm64-poky-linux/xen-image-minimal/1.0-r0/xen-image-minimal-1.0/output.dts: > ERROR (explicit_phandles): /apb-pclk:phandle: bad length (1) phandle > property > | > /home/edwpic01/work/master-update-xen/build/metavirt-host-arm64-4.16-release.prj/tmp/work/qemuarm64-poky-linux/xen-image-minimal/1.0-r0/xen-image-minimal-1.0/output.dts: > ERROR (explicit_phandles): /intc@8000000:phandle: bad length (1) phandle > property > | > /home/edwpic01/work/master-update-xen/build/metavirt-host-arm64-4.16-release.prj/tmp/work/qemuarm64-poky-linux/xen-image-minimal/1.0-r0/xen-image-minimal-1.0/output.dts: > ERROR (explicit_phandles): /pl061@9030000:phandle: bad length (1) phandle > property > | ERROR: Input tree has errors, aborting (use -f to force output) > | WARNING: exit code 2 from a shell command. > > The above error was the result from building on x86_64-linux, target > system was aarch64-poky-linux, running on a qemuarch64 machine, itself > running on x86_64 linux. > As mentioned this was done on the master version of meta-virtualisation. > The bitbake command to generate this was bitbake xen-image-mininal. > The error is also present when building the xen 4.14 and xen 4.15 arm64 > versions, and is not present on the arm32 or x86 builds for xen. > If anyone knows the cause of the error, the information would be > appreciated. > > > > There's something wrong with the input DTS to Lopper .. luckily, I > maintain Lopper, so if there's an actual bug in the processing of the input > DTS .. I can fix that. > > > > I can fire up a build and see if it happens here. > > > > So this is just qemuarm64, with xen + virtualization in the distro > features ? Any other layers ? Anything else ? > > > > Bruce > > Yes, this is just as you say, no other layers or anything else. Thank you > for the speedy reply! > There's a really bad interaction between libfdt and python 3.10. I've traced the error down to libfdt not being able to read anything from the dtbs and hence the chained errors. I'm building some older branches to confirm behaviours .. it will take me a few days to sort through this, but I don't want to mask the issue, as I need to understand exactly what is going on here. Bruce > > > Edward > > > > > Cheers! > > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > > > > > > -- > > - Thou shalt not follow the NULL pointer, for chaos and madness await thee > at its end > - "Use the force Harry" - Gandalf, Star Trek II > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6860): https://lists.yoctoproject.org/g/meta-virtualization/message/6860 Mute This Topic: https://lists.yoctoproject.org/mt/86601809/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
