Date: Sun, 9 Jun 2013 11:46:04 -0700 From: Garrett Cooper <yaneurabeya@gmail.com> To: Alex Liptsin <alexl@mellanox.com> Cc: "freebsd-infiniband@freebsd.org" <freebsd-infiniband@freebsd.org>, Regev Lev <regevl@mellanox.com>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Mellanox NIC names changed, each kldunload/kldload mlx4ib module Message-ID: <03D4440E-2D1D-497C-B084-CAB47DE5F880@gmail.com> In-Reply-To: <64DAB3164E410447932305F50F896D8D6AF6D2E6@MTLDAG01.mtl.com> References: <64DAB3164E410447932305F50F896D8D6AF6D2E6@MTLDAG01.mtl.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 9, 2013, at 5:35 AM, Alex Liptsin wrote: > Hi. > > I work with FreeBSD9.1 and Mellanox devices. > Every time I unload / load mlx4ib module, NIC names of mellanox devices (ibX) are renamed. > Can I prevent it? > > [root@h-qa-032 mlx4]# ifconfig > ib8: flags=8002<BROADCAST,MULTICAST> metric 0 mtu 65520 > options=80018<VLAN_MTU,VLAN_HWTAGGING,LINKSTATE> > lladdr 80.28.0.48.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.31 > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > ib9: flags=8002<BROADCAST,MULTICAST> metric 0 mtu 65520 > options=80018<VLAN_MTU,VLAN_HWTAGGING,LINKSTATE> > lladdr 80.28.0.49.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.32 > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > > [root@h-qa-032 mlx4]# kldunload mlx4ib > > [root@h-qa-032 mlx4]# kldload -v mlx4ib > Loaded mlx4ib, id=9 > > [root@h-qa-032 mlx4]# ifconfig > ib10: flags=8002<BROADCAST,MULTICAST> metric 0 mtu 65520 > options=80018<VLAN_MTU,VLAN_HWTAGGING,LINKSTATE> > lladdr 80.30.0.48.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.31 > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > ib11: flags=8002<BROADCAST,MULTICAST> metric 0 mtu 65520 > options=80018<VLAN_MTU,VLAN_HWTAGGING,LINKSTATE> > lladdr 80.30.0.49.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.32 > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> You're probably running into a driver bug because OFED/ipoib was never meant to be unloaded (assuming you're using my sources). Check the detach/destroy routines to make sure that it's properly detaching everything and updating indexes in the network stack before it unloads the driver. Cheers, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?03D4440E-2D1D-497C-B084-CAB47DE5F880>