Quantcast
Channel: Mellanox Interconnect Community: Message List
Viewing all articles
Browse latest Browse all 6226

ConnectX-2: mlx4_en: Port: 1, invalid mac burned: 0x0, quiting

$
0
0

Hello, I'm trying to use the mlx4_en driver instead of mlx4_ib to hopefully increase bandwidth in a filtering device that uses ConnectX-2 MT26428 adapters).

 

I did a fresh install of CentOS-6.2 since the infiniband adapters are running firmware 2.8 and the mlnx drivers that support this version have been tested with RHEL-6.2 according to the release notes. Kernel used is 2.6.32-358.2.1.el6.x86_64.

 

With the standard centos drivers (mlx4_core 1.1), I saw this in dmesg:

 

command 0xc failed: fw status = 0x40

 

And 'modprobe mlx4_en' didn't create any ethernet devices. Modprobing mlx4_ib ib_sa ib_cm ib_umad ib_addr ib_uverbs ib_ipoib ib_ipath resulted in ib0 and ib1 showing up.

 

I downloaded mlnx_en-1.5.8.3.tgz (mlx4_1.5.7.2) from the download archives and mlx4_en still doesn't create an ethernet device, but the error in dmesg is:

 

mlx4_core: Mellanox ConnectX core driver v1.0-mlnx_ofed1.5.3 (November 3, 2011)

...

mlx4_en: Mellanox ConnectX HCA Ethernet driver v1.5.7.2 (Dec 2011)

...

mlx4_en: Port: 1, invalid mac burned: 0x0, quiting

 

I've compiled and installed all versions of the drivers by

- extracting the tgz from mellanox

- rpm2cpio SRPMS/mellanox-mlnx-en-x.y.z.tgz

- extract, run scripts/mlnx_en_patch.sh; 2 errors:

  - kernel_patches/backport/2.6.32-EL6.2/dma_mapping*.patch does not exist

  - kernel_patches/backport/2.6.32-EL6.2/memtrack*.patch does not exist

- make -> no errors, .ko files resulted

 

I've also tried mlnx_en drivers 1.5.9 and 1.5.10 from an ubuntu-server 12.04 (kernel 3.2) with the same results. Using the mlx4_ib driver, I could do netperf tests across two servers and the devices were functional.

 

Is there any other setup step required for using the mlx4_en driver ?


Viewing all articles
Browse latest Browse all 6226

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>