Fwd: Mellanox ethernet card failed when probing

[Jean-Michel Hautbois <jhautbois@gmail.com>]

2012/2/3 Rick Jones <rick.jones2@hp.com>
>
> On 02/03/2012 07:13 AM, Jean-Michel Hautbois wrote:
>>
>> Hi all,
>>
>> I am using a HP server with Mellanox ethernet cards in it.
>> I have compiled the latest linux 3.2 version, and I am encountering
>> the following error :
>>
>> [ 1094.644193] mlx4_core: Mellanox ConnectX core driver v1.1 (Dec, 2011)
>> [ 1094.644196] mlx4_core: Initializing 0000:06:00.0
>> [ 1097.183671] mlx4_core 0000:06:00.0: irq 84 for MSI/MSI-X
>> [ 1097.183681] mlx4_core 0000:06:00.0: irq 85 for MSI/MSI-X
>> [ 1097.183690] mlx4_core 0000:06:00.0: irq 86 for MSI/MSI-X
>> [ 1097.183697] mlx4_core 0000:06:00.0: irq 87 for MSI/MSI-X
>> [ 1097.201267] mlx4_core: Initializing 0000:06:00.1
>> [ 1097.201509] mlx4_core 0000:06:00.1: Multiple PFs not yet supported.
>> Skipping PF.
>> [ 1097.201844] mlx4_core: probe of 0000:06:00.1 failed with error -22
>
> > ...
>
>> I think this is firmware related, but I don't know for sure.
>> I can't find any firmware generated in the /lib/firmware directory...
>
>
> That error message seems to relate to SRIOV support:
>
>                /* We reset the device and enable SRIOV only for physical
>                 * devices.  Try to claim ownership on the device;
>                 * if already taken, skip -- do not allow multiple PFs */
>                err = mlx4_get_ownership(dev);
>                if (err) {
>                        if (err < 0)
>                                goto err_free_dev;
>                        else {
>                                mlx4_warn(dev, "Multiple PFs not yet supported."
>                                          " Skipping PF.\n");
>                                err = -EINVAL;
>                                goto err_free_dev;
>                        }
>                }
>
>
> Isn't SRIOV support a "work in progress" for the Mellanox devices?  The rest of the logging (snipped) seems to suggest that the ".0" PFs did initialize correctly, so are you simply worried about the messages in the log?
>
> rick jones


I am not worried only with this message, but when I am looking at my
devices, even if the mlx4_core module is loaded, I don't have my eth
device.
Initializing is ok, but probe fails, so I can't use the device, this
is what I am worried about :).
I have two types of devices : be2net and mlx4. I want to have bonding
between them, and using an old kernel (debian lenny, 2.6.26), and the
drivers directly recompiled from mellanox website I can get it work.
Using the latest kernel (3.4.0-rc2) and using "modprobe mlx4_en" I get
the same messages related to mlx4_core, but it loads some ethernet
ports.

When booting, it detects the mlx and udev loads mlx4_core, not mlx4_en...
I will try to force it (but I am sure there is a clean way to do that ;-)).

JM