From: J Dhanasekar <jdhanasekar@velankanigroup.com>
To: "Venkatesh, Supreeth" <Supreeth.Venkatesh@amd.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Ramakrishnan Kumaraswamy <ramakrishnan@bydesignindia.net>
Subject: Re: build error in AMD Ethanolx
Date: Tue, 3 Nov 2020 21:02:07 +0530 [thread overview]
Message-ID: <CAOW9pY1nyeawBBDYkPTt572pJ4KqiuCijbc4xz9N6dVgMhePvw@mail.gmail.com> (raw)
In-Reply-To: <CAOW9pY1WMKjq4V55szP8A56MMZY2QotswnuEibK3sVt8SdjvCw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 7533 bytes --]
Hi Supreeth,
Is LDT for Daytona CRB ready ?.
Please provide me, if it is available.
Thanks,
Dhanasekar
On Fri, Oct 9, 2020 at 6:59 PM J Dhanasekar <jdhanasekar@velankanigroup.com>
wrote:
> Hi Supreeth,
>
> Nice to hear from you.
> Thanks for the info.
>
> -Dhanasekar
>
> On Fri, Oct 9, 2020 at 6:20 PM Venkatesh, Supreeth <
> Supreeth.Venkatesh@amd.com> wrote:
>
>> [AMD Public Use]
>>
>>
>>
>> Hi Dhanasekar,
>>
>>
>>
>> Thanks for helping out.
>>
>> We will make DT for Daytona CRB available latest by early next month or
>> end of this month.
>>
>>
>>
>> Thanks,
>>
>> *Supreeth Venkatesh*
>>
>> System Manageability Architect |* AMD*
>> Server Software
>>
>>
>>
>> *From:* J Dhanasekar <jdhanasekar@velankanigroup.com>
>> *Sent:* Friday, October 9, 2020 12:14 AM
>> *To:* Venkatesh, Supreeth <Supreeth.Venkatesh@amd.com>
>> *Cc:* OpenBMC Maillist <openbmc@lists.ozlabs.org>; Ramakrishnan
>> Kumaraswamy <ramakrishnan@bydesignindia.net>
>> *Subject:* Re: build error in AMD Ethanolx
>>
>>
>>
>> [CAUTION: External Email]
>>
>> Hi Supreeth,
>>
>>
>>
>> If the DTSs file for Daytona CRB is available, I will work parallel to
>> enable openBMC for Daytona CRB.
>>
>>
>>
>>
>>
>> Thanks,
>>
>> Dhanasekar
>>
>>
>>
>> On Thu, Oct 8, 2020 at 7:51 PM J Dhanasekar <
>> jdhanasekar@velankanigroup.com> wrote:
>>
>> Supreeth,
>>
>>
>>
>> Thanks for the info.
>>
>> Will OpenBMC on Daytona available end of this year?.
>>
>>
>>
>> Thanks,
>>
>> Dhanasekar
>>
>>
>>
>> On Thu, Oct 8, 2020 at 7:31 PM Supreeth Venkatesh <
>> supreeth.venkatesh@amd.com> wrote:
>>
>> On 10/8/20 1:02 AM, J Dhanasekar wrote:
>> > [CAUTION: External Email]
>> > Hi Supreeth,
>> >
>> > I was able to build the AMD Ethanolx source successfully. I have
>> executed your mentioned commands only,
>> >
>> > *. setup ethanolx
>> > bitbake obmc-phosphor-image *
>> >
>> > I built the code in normal user privilege, not root user.
>> > Thanks for your support.
>> Thanks for letting me know.
>> >
>> > Do you have a linux DTS for BMC of DaytonaCRB ?.
>> Unfortunately, we are not supporting Daytona CRB yet, but we are working
>> towards enabling OpenBMC on Daytona soon. Stay tuned.
>>
>> >
>> > -Dhanasekar
>> >
>> > On Thu, Oct 8, 2020 at 12:21 AM Anton Kachalov <rnouse@google.com
>> <mailto:rnouse@google.com>> wrote:
>> >
>> > Hey,
>> >
>> > would you mind to find the *log.do_rootfs* file for
>> obmc-phosphor-initramfs under build/tmp/work. This task has failed.
>> >
>> > For instance, on qemuarm target the path looks like this (for
>> obmc-phosphor-*image* instead of obmc-phosphor-*initramfs*):
>> >
>> >
>> build/tmp/work/qemuarm-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/temp/log.do_rootfs
>> >
>> > On Wed, 7 Oct 2020 at 20:35, Supreeth Venkatesh <
>> supreeth.venkatesh@amd.com <mailto:supreeth.venkatesh@amd.com>> wrote:
>> >
>> > On 10/7/20 10:11 AM, J Dhanasekar wrote:
>> > > [CAUTION: External Email]
>> > > Hi Supreeth,
>> > >
>> > > Thanks for the reply,
>> > >
>> > > I have attached the complete error log. Please view it.
>> > >
>> > > I have removed the build folder and created a new one twice.
>> Still I am seeing the same error.
>> > This may be environment issue in your setup.
>> > I am not seeing this error in my environment with the latest
>> master.
>> >
>> > . setup ethanolx
>> > bitbake bitbake obmc-phosphor-image
>> >
>> >
>> > "WARNING: Host distribution "ubuntu-18.04" has not been
>> validated with this version of the build system; you may possibly
>> experience unexpected failures. It is recommended that you use a tested
>> distribution.
>> > NOTE: Resolving any missing task queue dependencies
>> >
>> > Build Configuration:
>> > BB_VERSION = "1.47.0"
>> > BUILD_SYS = "x86_64-linux"
>> > NATIVELSBSTRING = "ubuntu-18.04"
>> > TARGET_SYS = "arm-openbmc-linux-gnueabi"
>> > MACHINE = "ethanolx"
>> > DISTRO = "openbmc-phosphor"
>> > DISTRO_VERSION = "0.1.0"
>> > TUNE_FEATURES = "arm thumb arm1176jzs"
>> > TARGET_FPU = "soft"
>> > meta
>> > meta-oe
>> > meta-networking
>> > meta-perl
>> > meta-python
>> > meta-phosphor
>> > meta-aspeed
>> > meta-amd
>> > meta-ethanolx =
>> "master:c3d88e4d9fcc08e1aae7cc9d0337c0261e996c64""
>> >
>> > ....
>> > ....
>> > ....
>> >
>> > NOTE: Running task 4241 of 4243
>> (/home/supvenka/work/openbmc_upstream/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:
>> do_image_complete)
>> > NOTE: recipe obmc-phosphor-image-1.0-r0: task
>> do_image_complete: Started
>> > NOTE: recipe obmc-phosphor-image-1.0-r0: task
>> do_image_complete: Succeeded
>> > NOTE: Running task 4242 of 4243
>> (/home/supvenka/work/openbmc_upstream/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:
>> do_populate_lic_deploy)
>> > NOTE: recipe obmc-phosphor-image-1.0-r0: task
>> do_populate_lic_deploy: Started
>> > NOTE: recipe obmc-phosphor-image-1.0-r0: task
>> do_populate_lic_deploy: Succeeded
>> > NOTE: Running noexec task 4243 of 4243
>> (/home/supvenka/work/openbmc_upstream/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:
>> do_build)
>> > NOTE: Tasks Summary: Attempted 4243 tasks of which 2 didn't
>> need to be rerun and all succeeded."
>> > >
>> > > Thanks,
>> > > Dhanasekar
>> > >
>> > > On Wed, Oct 7, 2020 at 8:08 PM Supreeth Venkatesh <
>> supreeth.venkatesh@amd.com <mailto:supreeth.venkatesh@amd.com> <mailto:
>> supreeth.venkatesh@amd.com <mailto:supreeth.venkatesh@amd.com>>> wrote:
>> > >
>> > > On 10/7/20 5:44 AM, J Dhanasekar wrote:
>> > > > [CAUTION: External Email]
>> > > > Hi openBMC,
>> > > Hi Dhanasekar
>> > >
>> > > >
>> > > > I am working to build BMC for AMD Ethanolx platform,
>> > > Nice to hear.
>> > > >
>> > > > After running *bitbake u-boot-aspeed* and *bitbake
>> obmc-phosphor-image*,
>> > > > I am getting below error,
>> > > >
>> > > > ERROR: obmc-phosphor-initramfs-1.0-r0 do_rootfs: The
>> postinstall intercept hook 'update_gio_module_cache' failed, details in
>> /home/user/dhanasekar/BMC/AMD/openbmc/build/tmp/work/ethanolx-openbmc-linux-gnueabi/obmc-phosphor-initramfs/1.0-r0/temp/log.do_rootfs
>> > > > ERROR: Logfile of failure stored in:
>> /home/user/dhanasekar/BMC/AMD/openbmc/build/tmp/work/ethanolx-openbmc-linux-gnueabi/obmc-phosphor-initramfs/1.0-r0/temp/log.do_rootfs.14182
>> > > > ERROR: Task
>> (/home/user/dhanasekar/BMC/AMD/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-initramfs.bb:do_rootfs)
>> failed with exit code '1'
>> > > >
>> > > Can you send me the complete build logs?
>> > >
>> > > > Please help me to fix the error,
>> > > rm the build folder and retry once.
>> > > I will build it once today as well and confirm. It may
>> not been tested with latest upstream changes.
>> > >
>> > > >
>> > > > Thanks,
>> > > > Dhanasekar,
>> > >
>> >
>>
>>
[-- Attachment #1.2: Type: text/html, Size: 13477 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 3608 bytes --]
next prev parent reply other threads:[~2020-11-03 15:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 10:44 build error in AMD Ethanolx J Dhanasekar
2020-10-07 14:38 ` Supreeth Venkatesh
2020-10-07 15:11 ` J Dhanasekar
2020-10-07 18:34 ` Supreeth Venkatesh
2020-10-07 18:51 ` Anton Kachalov
2020-10-08 6:02 ` J Dhanasekar
2020-10-08 14:01 ` Supreeth Venkatesh
2020-10-08 14:21 ` J Dhanasekar
2020-10-09 5:13 ` J Dhanasekar
2020-10-09 12:50 ` Venkatesh, Supreeth
2020-10-09 13:29 ` J Dhanasekar
2020-11-03 15:32 ` J Dhanasekar [this message]
2020-11-05 23:46 ` Venkatesh, Supreeth
2020-11-06 13:44 ` J Dhanasekar
2020-12-09 4:30 ` J Dhanasekar
2020-12-15 14:57 ` J Dhanasekar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOW9pY1nyeawBBDYkPTt572pJ4KqiuCijbc4xz9N6dVgMhePvw@mail.gmail.com \
--to=jdhanasekar@velankanigroup.com \
--cc=Supreeth.Venkatesh@amd.com \
--cc=openbmc@lists.ozlabs.org \
--cc=ramakrishnan@bydesignindia.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).