DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
	Ruoshan Shi <ruoshan.shi@nxp.com>
Cc: "X.f. Ren" <xiaofeng.ren@nxp.com>, ci@dpdk.org
Subject: Re: [dpdk-ci] Upgraded DTS Version for NXP
Date: Thu, 3 Dec 2020 11:53:25 -0500	[thread overview]
Message-ID: <57460d91-a51f-f69a-eee5-9b84e36f67b9@iol.unh.edu> (raw)
In-Reply-To: <CAOeXdvYOOcD=OPfkSF+Z45D6fmkRu5YJxXKQut8VMmSE1F987g@mail.gmail.com>

Hi everyone,


Has anybody got a chance to look at this issue?

I'm not sure if the NXP system specifically needs the DTS version from 
your local BitBucket repository. It seems that there are some obstacles 
that the original DTS repository is not able to deal with. Could 
somebody point me in the right direction to get this set up?


Thanks,

Brandon

On 10/22/2020 1:26 PM, Brandon Lo wrote:
> Hi everyone,
>
> It seems that the DTS instance on the community lab's NXP system uses
> a DTS that is internal to your bitbucket which makes it unable to be
> pulled for the new changes.
> I have gotten past the point of compiling DPDK manually, but DTS is
> still the outdated version that relies on make.
>
> I have attempted to use a new, clean version of DTS pulled directly
> from the repo, but I am having a bit of trouble with setting it up.
> Which interfaces are used for testing between the DUT and the tester?
> The ports I have found within the conf/ports.cfg file do not seem to
> match up.
> It also seems that mydut.py and project_mydut.py change the behavior
> of DTS itself.
>
> Could someone help look into this issue?
>
> Thanks,
> Brandon
>
> On Tue, Sep 22, 2020 at 10:06 AM Brandon Lo <blo@iol.unh.edu> wrote:
>> Hi Juraj,
>>
>> Running a `file` command shows me that the fixdep is ARM aarch64.
>> fixdep: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV),
>> dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for
>> GNU/Linux 3.7.0,
>> BuildID[sha1]=2024bac4b13890933f59d28a2aa1a82eef2e02f2, not stripped
>>
>> It seems right to me(?) since `uname -m` prints aarch64.
>> I will continue investigating this and see if I can get any further.
>>
>> Thanks,
>> Brandon
>>
>> On Tue, Sep 22, 2020 at 1:56 AM Juraj Linkeš <juraj.linkes@pantheon.tech> wrote:
>>> Hi Brandon,
>>>
>>> The Exec format error looks like an error which happens when you try to run an arm binary on an x86 machine (or in general the binary format doesn't match the host architecture). What does "file scripts/basic/fixdep" say and what's the host architecture?
>>>
>>> Juraj
>>>
>>>> -----Original Message-----
>>>> From: ci <ci-bounces@dpdk.org> On Behalf Of Brandon Lo
>>>> Sent: Friday, September 18, 2020 6:56 PM
>>>> To: Hemant Agrawal <hemant.agrawal@nxp.com>
>>>> Cc: Ruoshan Shi <ruoshan.shi@nxp.com>; X.f. Ren <xiaofeng.ren@nxp.com>;
>>>> ci@dpdk.org; Lincoln Lavoie <lylavoie@iol.unh.edu>
>>>> Subject: Re: [dpdk-ci] Upgraded DTS Version for NXP
>>>>
>>>> Hi Hemant,
>>>>
>>>> I have gotten more progress into building; now I am running into a different
>>>> issue.
>>>> There is currently an issue building a kernel module: "FAILED:
>>>> kernel/linux/igb_uio/igb_uio.ko"
>>>>
>>>> I believe this issue is related to the following message: "/bin/sh: 1:
>>>> scripts/basic/fixdep: Exec format error"
>>>> Any ideas of where this error comes from?
>>>>
>>>> Thanks,
>>>> Brandon
>>>>
>>>> On Fri, Sep 18, 2020 at 7:52 AM Hemant Agrawal <hemant.agrawal@nxp.com>
>>>> wrote:
>>>>> HI,
>>>>>          What is the issue are you observing ?
>>>>>
>>>>> 1. install ARM cross tool chain
>>>>>
>>>>> sudo apt-get install gcc-aarch64-linux-gnu g++-aarch64-linux-gnu sudo
>>>>> apt-get install build-essential autoconf libtool cmake pkg-config git
>>>>> python-dev swig3.0 libpcre3-dev nodejs-dev
>>>>>
>>>>> 2. If you want to build kernel mods
>>>>> Specify the kernel_dir
>>>>> meson arm64-build --cross-file config/arm/arm64_dpaa_linux_gcc
>>>>> -Dexamples=all --werror -Denable_kmods=True -Dlibdir=lib
>>>>> --default-library=static ninja -C arm64-build
>>>>>
>>>>> 3. or build with kmods
>>>>> meson arm64-build --cross-file config/arm/arm64_dpaa_linux_gcc
>>>>> -Dexamples=all --werror -Dlibdir=lib --default-library=static ninja -C
>>>>> arm64-build
>>>>>
>>>>>
>>>>> Regards,
>>>>> Hemant
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: ci <ci-bounces@dpdk.org> On Behalf Of Brandon Lo
>>>>>> Sent: Friday, September 18, 2020 2:30 AM
>>>>>> To: Ruoshan Shi <ruoshan.shi@nxp.com>
>>>>>> Cc: X.f. Ren <xiaofeng.ren@nxp.com>; ci@dpdk.org; Lincoln Lavoie
>>>>>> <lylavoie@iol.unh.edu>
>>>>>> Subject: [dpdk-ci] Upgraded DTS Version for NXP
>>>>>>
>>>>>> Hi Ruoshan,
>>>>>>
>>>>>> Since DPDK has discontinued make support for compiling, a DTS
>>>>>> upgrade is needed for performance testing to continue on all systems.
>>>>>>
>>>>>> I am attempting to upgrade DTS on the NXP machine, but it seems that
>>>>>> it is a fork of DTS that is from NXP's bitbucket server.
>>>>>> Is it possible to pull from the upstream DPDK DTS repository and use
>>>>>> that instead?
>>>>>>
>>>>>> I also installed meson and ninja on the machine which is needed for
>>>>>> the new version, but I am having trouble building.
>>>>>> It uses these commands to build (172.18.0.202 in /root/dpdk):
>>>>>> 1. CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib --default-
>>>>>> library=static arm64-dpaa-linuxapp-gcc 2. ninja -C
>>>>>> arm64-dpaa-linuxapp-gcc -j
>>>>>> 8
>>>>>>
>>>>>> Could you help me look into this?
>>>>>>
>>>>>> Thanks,
>>>>>> Brandon
>>>>>>
>>>>>> --
>>>>>> Brandon Lo
>>>>>>
>>>>>> UNH InterOperability Laboratory
>>>>>>
>>>>>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>>>>>
>>>>>> blo@iol.unh.edu
>>>>>>
>>>>>> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww
>>>>>> .i
>>>>>>
>>>> ol.unh.edu%2F&amp;data=02%7C01%7Chemant.agrawal%40nxp.com%7Ce3
>>>> d40a1a7c8246676acf08d85b4cbe49%7C686ea1d3bc2b4c6fa92cd99c5c301635
>>>> %
>>>> 7C0%7C0%7C637359732457337624&amp;sdata=IrFBG%2BvSBQi8uodqX%2FX
>>>>>> QmIPnB7CVg6EbDK%2Fq3bOtdbQ%3D&amp;reserved=0
>>>>
>>>>
>>>> --
>>>>
>>>> Brandon Lo
>>>>
>>>> UNH InterOperability Laboratory
>>>>
>>>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>>>
>>>> blo@iol.unh.edu
>>>>
>>>> www.iol.unh.edu
>>
>> --
>>
>> Brandon Lo
>>
>> UNH InterOperability Laboratory
>>
>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>
>> blo@iol.unh.edu
>>
>> www.iol.unh.edu
>
>

  reply	other threads:[~2020-12-03 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 21:00 Brandon Lo
2020-09-18 11:52 ` Hemant Agrawal
2020-09-18 16:55   ` Brandon Lo
2020-09-22  5:56     ` Juraj Linkeš
2020-09-22 14:06       ` Brandon Lo
2020-10-22 17:26         ` Brandon Lo
2020-12-03 16:53           ` Brandon Lo [this message]
2021-01-19 21:02             ` Brandon Lo

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=57460d91-a51f-f69a-eee5-9b84e36f67b9@iol.unh.edu \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=ruoshan.shi@nxp.com \
    --cc=xiaofeng.ren@nxp.com \
    /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).