Am Freitag, den 28.07.2017, 09:47 -0600 schrieb Jason Gunthorpe:
> On Fri, Jul 28, 2017 at 05:42:05PM +0200, Benjamin Drung wrote:
>
> > $ journalctl | grep mlx
> > mlx4_core: Mellanox ConnectX core driver v3.3-1.0.4 (03 Jul 2016)
> > mlx4_core: Initializing 0000:02:00.0
> > mlx4_core: device is working in RoCE mode: Roce V1
>
> So you are running purely in roce mode?
I want to use mlx4_ib and IPoIB. The output is the same for a properly
working system, but these system will load mlx4_ib and then more logs
will appear.
> What does this say:
>
> $ udevadm info /sys/class/net/XXX
>
> Where 'XXX' is the ethernet device for the mlx4?
The net device is missing. When I load mlx4_ib manually, they will
appear and show:
$ sudo udevadm info /sys/class/net/ib0
P: /devices/pci0000:00/0000:00:02.0/0000:02:00.0/net/ib0
E: DEVPATH=/devices/pci0000:00/0000:00:02.0/0000:02:00.0/net/ib0
E: ID_BUS=pci
E: ID_MODEL_FROM_DATABASE=MT27500 Family [ConnectX-3]
E: ID_MODEL_ID=0x1003
E: ID_NET_DRIVER=ib_ipoib
E: ID_PATH=pci-0000:02:00.0
E: ID_PATH_TAG=pci-0000_02_00_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Network controller
E: ID_VENDOR_FROM_DATABASE=Mellanox Technologies
E: ID_VENDOR_ID=0x15b3
E: IFINDEX=6
E: INTERFACE=ib0
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/ib0
E: TAGS=:systemd:
E: USEC_INITIALIZED=65619465
> > No clue how to further debug it.
>
> This is the line that is expected to load mlx4_ib:
>
> ENV{ID_NET_DRIVER}=="mlx4_en", RUN{builtin}+="kmod load mlx4_ib"
>
> So we should see ID_NET_DRIVER=mlx4_en in the above udevadm print.
Strange. It is ib_ipoib instead of mlx4_en.
--
Benjamin Drung
System Developer
Debian & Ubuntu Developer
ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin
Email: benjamin.drung@xxxxxxxxxxxxxxxx
Web: https://www.profitbricks.com
Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Achim Weiss.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
