Am Donnerstag, den 03.08.2017, 11:52 -0600 schrieb Jason Gunthorpe: > On Thu, Aug 03, 2017 at 02:00:59PM +0200, Benjamin Drung wrote: > > > Yes. That was the issue. I am using an initrd (from initramfs- > > tools). > > The mlx4_core module was included in the initrd, but mlx4_ib was > > missing. I tweaked initramfs-tools to include mlx4_ib and then it > > was > > autoloaded. Thanks. > > Do you know how to fix this generally for Debian? Is it possible? Analysis for Debian jessie/stretch: $ sudo update-initramfs -uv [...] Copying module directory kernel/drivers/net (excluding appletalk arcnet bonding can dummy.ko hamradio hippi ifb.ko irda macvlan.ko macvtap.ko pcmcia sb1000.ko team tokenring tun.ko usb veth.ko wan wimax wireless xen-netback.ko) [...] Adding module /lib/modules/$version/kernel/drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.ko Adding module /lib/modules/$version/kernel/drivers/net/ethernet/mellanox/mlx4/mlx4_core.ko update-initramfs calls auto_add_modules() in /usr/share/initramfs-tools/hook-functions which includes 'net' as default. The 'net' option calls "copy_modules_dir kernel/drivers/net [...]" which copies the mlx5_core.ko and mlx4_core.ko modules. but the mlx4_ib.ko module is in the infiniband directory: $ find kernel/drivers/infiniband ! -type d kernel/drivers/infiniband/hw/mlx5/mlx5_ib.ko kernel/drivers/infiniband/hw/mthca/ib_mthca.ko kernel/drivers/infiniband/hw/mlx4/mlx4_ib.ko kernel/drivers/infiniband/core/ib_sa.ko kernel/drivers/infiniband/core/ib_umad.ko kernel/drivers/infiniband/core/ib_netlink.ko kernel/drivers/infiniband/core/ib_core.ko kernel/drivers/infiniband/core/rdma_cm.ko kernel/drivers/infiniband/core/ib_ucm.ko kernel/drivers/infiniband/core/ib_addr.ko kernel/drivers/infiniband/core/rdma_ucm.ko kernel/drivers/infiniband/core/ib_cm.ko kernel/drivers/infiniband/core/ib_uverbs.ko kernel/drivers/infiniband/core/iw_cm.ko kernel/drivers/infiniband/core/ib_mad.ko kernel/drivers/infiniband/ulp/ipoib/ib_ipoib.ko kernel/drivers/infiniband/ulp/srp/ib_srp.ko By default, nothing from the infiniband directory is included. The question is: What is the right thing to do? Should everything from kernel/drivers/infiniband/hw be included in the initrd by default? > > Remaining problem: The IPoIB InfiniBand partition does not come up > > correctly: > > AFAIK, M-DOWN means 'master-down', it means that the interface 'ib1' > is down. 'ip link set up dev ib1' > > Something wrong with ordering of the legacy network setup script? Thanks. The master-down is correct, since we just use only the InifiniBand partition and not the master device. Even the old configuration had M-DOWN. My ping tests were incorrect. I compared the IP configuration with the previous configuration and it was identical. Then I discovered that the ping target was not reachable even with the old configuration. I took a different host that was pingable with the old config and this one was pingable with rdma-core too. So rdma-core works as designed. -- 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
