The problem was finally identified as being incompatibility issues between 
ofed drivers and inbox kernel drivers. Solution was to remove all ofed 
drivers and enable kernel modules only. All is good. Thank you for your 
support all.

Moussa

On Thursday, October 16, 2014 4:11:55 PM UTC-7, Or Gerlitz wrote:
>
>  
> On 10/17/2014 02:05 AM, Moussa Ba wrote:
>  
>
>
> On Thursday, October 16, 2014 4:01:49 PM UTC-7, Or Gerlitz wrote: 
>>
>>
>> On 10/16/2014 09:14 PM, Moussa Ba wrote: 
>> > FYI the system is a supermicro based system with integrated ConnextX3 
>> > card running 2.30....firmware info is below (obtained when installing 
>> > mlnx-en-2.3.1.0.0 from Mellanox website). 
>>
>> oops, you can't mix two driver (mlx4_core and mlx4_en) from an overlay 
>> install of mlnx-en install with the rest of the rdma stack originated 
>> from the inbox kernel. This will not work, AFAIK. Please remove that 
>> package or @ least the rpm which installs these two kernel drivers (if 
>> you need to locate it do rpm -qf on the module files and them rpm -e) 
>>
>
>  The network interface only showed up after installing mlnx-en-2.3.1.0.0. 
>  
>
> so that's a pre-condition/issue we need to solve
>
> remove the mlx4_core and mlx4_en from ofed, reload the inbox mlx4_core 
> with debug_level=1 and see if there are errors, you need to get into a 
> situation where the inbox EN driver is up and running
>
>  What is the proper way of enabling iser/ROCE with the inbox kernel?
>
>   
>  
>
> it should just work once the EN (mlx4_en) driver is OK and you load the IB 
> driver (mlx4_ib)
>
>  
>> > 
>> > 
>> > Device #1: 
>> > ---------- 
>> > 
>> >   Device Type:      ConnectX3 
>> >   Part Number:      AOC-CIBF-M1 
>> >   Description:      ConnectX-3 single-port QSFP; FDR IB (56Gb/s) and 
>> > 40GigE; PCIe3.0 x8 8GT/s; RoHS R6 
>> >   PSID:             SM_1101000001000 
>> >   PCI Device Name:  0000:01:00.0 
>> >   Port1 GUID:       002590ffff07f15d 
>> >   Port2 MAC:        00259007f15e 
>> >   Versions:         Current        Available 
>> >      FW             2.30.3000      N/A 
>> > 
>> > 
>> > 
>> > #ibv_devinfo -v 
>> > No IB devices found 
>> > 
>> no IB device --> no RDMA 
>>
>
>  Well as you can see the device does show up under lspci. Am i missing a 
> module? 
>  
> oh I wanted to say no kernel software IB device --> no RDMA services
>
>  
>  Moussa 
>  
>
>  

-- 
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to