DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sotiris Salloumis <sotiris.salloumis@ericsson.com>
To: Gilad Berman <giladb@mellanox.com>,
	Olga Shern <olgas@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Mellanox dpdk  issues
Date: Mon, 23 Nov 2015 22:30:15 +0000	[thread overview]
Message-ID: <92E2D0EFD47ECE498537B698D4EF0B120F941DAF@ESESSMB101.ericsson.se> (raw)
In-Reply-To: <AM2PR05MB0675F2FE3D09655CBE36DD75A0070@AM2PR05MB0675.eurprd05.prod.outlook.com>

Hi all, 

For future reference problem root casue was missing package for the kernel version I was using.  

After doing 

zypper install kernel-default-devel-3.12.28-4.6.x86_64

Compilation worked fine.

Thanks Mellanox team for the support.

Regards
Sotiris

-----Original Message-----
From: Gilad Berman [mailto:giladb@mellanox.com] 
Sent: Monday, November 23, 2015 11:38 AM
To: Olga Shern; Sotiris Salloumis; dev@dpdk.org
Subject: RE: Mellanox dpdk issues

Sotiris, 

I've compiled MLNX_DPDK-2.1_1.1 on SLES12  3.12.28-4-default with OFED 3.1-1.0.3 with no issues. Also, no modifications were required - simply follow the quick start guide here - http://www.mellanox.com/page/products_dyn?product_family=209&mtag=pmd_for_dpdk

If you are still having issues please mail me directly and we'll sort it out.

Thx.

Gilad Berman | Staff System Engineer | Business Development | Mellanox Technologies Ltd. 
Work: +972 52 2554262| 6 Ha'Barzel St. Tel Aviv 6971010, Israel


-----Original Message-----
From: Olga Shern 
Sent: Sunday, November 22, 2015 3:45 PM
To: Gilad Berman <giladb@mellanox.com>; Sotiris Salloumis <sotiris.salloumis@ericsson.com>; dev@dpdk.org
Subject: RE: Mellanox dpdk issues

Hi Sotiris, 

You can disable compilation of igb_uio, this module is not needed for Mellanox PMD.

Let me know if you have any question 

Best Regards,
Olga
 



-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Gilad Berman
Sent: Sunday, November 22, 2015 1:30 PM
To: Sotiris Salloumis <sotiris.salloumis@ericsson.com>; dev@dpdk.org
Subject: Re: [dpdk-dev] Mellanox dpdk issues

Let us check and get back to you. 


Gilad Berman | Staff System Engineer | Business Development | Mellanox Technologies Ltd. 
Work: +972 52 2554262| 6 Ha'Barzel St. Tel Aviv 6971010, Israel


-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sotiris Salloumis
Sent: Friday, November 20, 2015 7:35 PM
To: dev@dpdk.org
Subject: [dpdk-dev] Mellanox dpdk issues

Hi all,

I'm trying to build DPDK for Mellanox ( using MLNX_DPDK-2.1_1.1 ) but I get the following error following the guidelines i.e. make install T=x86_64-native-linuxapp-gcc

== Build lib/librte_eal/linuxapp/igb_uio
make[8]: *** /lib/modules/3.12.28-4-default/build: No such file or directory.  Stop.
/root/Downloads/MLNX_DPDK-2.1_1.1/mk/rte.module.mk:79: recipe for target 'igb_uio.ko' failed
make[7]: *** [igb_uio.ko] Error 2
/root/Downloads/MLNX_DPDK-2.1_1.1/mk/rte.subdir.mk:61: recipe for target 'igb_uio' failed
make[6]: *** [igb_uio] Error 2
/root/Downloads/MLNX_DPDK-2.1_1.1/mk/rte.subdir.mk:61: recipe for target 'linuxapp' failed
make[5]: *** [linuxapp] Error 2
/root/Downloads/MLNX_DPDK-2.1_1.1/mk/rte.subdir.mk:61: recipe for target 'librte_eal' failed
make[4]: *** [librte_eal] Error 2
/root/Downloads/MLNX_DPDK-2.1_1.1/mk/rte.sdkbuild.mk:93: recipe for target 'lib' failed
make[3]: *** [lib] Error 2
/root/Downloads/MLNX_DPDK-2.1_1.1/mk/rte.sdkroot.mk:124: recipe for target 'all' failed
make[2]: *** [all] Error 2
/root/Downloads/MLNX_DPDK-2.1_1.1/mk/rte.sdkinstall.mk:58: recipe for target 'x86_64-native-linuxapp-gcc_install' failed
make[1]: *** [x86_64-native-linuxapp-gcc_install] Error 2
/root/Downloads/MLNX_DPDK-2.1_1.1/mk/rte.sdkroot.mk:102: recipe for target 'install' failed
make: *** [install] Error 2

The environment is SLES12


-          Linux linux-okj7 3.12.28-4-default #1 SMP Thu Sep 25 17:02:34 UTC 2014 (9879bd4) x86_64 x86_64 x86_64 GNU/Linux

-          3.12.28-4-default

>From Mellanox point of view the only difference I see is related with firmware version

---- Performing Adapter Device Self Test ---- Number of CAs Detected ................. 1 PCI Device Check ....................... PASS Kernel Arch ............................ x86_64 Host Driver Version .................... MLNX_OFED_LINUX-3.1-1.0.3 (OFED-3.1-1.0.3): 3.12.28-4-default Host Driver RPM Check .................. PASS Firmware on CA #0 NIC .................. v2.35.5130 Firmware Check on CA #0 (NIC) .......... PASS
    NOTE: The found fw version is higher than the fw included in this package (v2.35.5100) Host Driver Initialization ............. PASS Number of CA Ports Active .............. 2 Port State of Port #1 on CA #0 (NIC)..... UP 1X QDR (Ethernet) Port State of Port #2 on CA #0 (NIC)..... UP 1X QDR (Ethernet) Error Counter Check on CA #0 (NIC)...... NA (Eth ports) Kernel Syslog Check .................... PASS Node GUID on CA #0 (NIC) ............... a0:1d:48:03:00:b5:a6:17
------------------ DONE ---------------------

Any hints?

Thanks
Sotiris

      reply	other threads:[~2015-11-23 22:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 17:34 Sotiris Salloumis
2015-11-22 11:30 ` Gilad Berman
2015-11-22 13:45   ` Olga Shern
2015-11-23 10:38     ` Gilad Berman
2015-11-23 22:30       ` Sotiris Salloumis [this message]

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=92E2D0EFD47ECE498537B698D4EF0B120F941DAF@ESESSMB101.ericsson.se \
    --to=sotiris.salloumis@ericsson.com \
    --cc=dev@dpdk.org \
    --cc=giladb@mellanox.com \
    --cc=olgas@mellanox.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).