[PATCH]: ipoib with mlx4 initialisation ordering

[Jason Bacon]

On 2020-02-24 03:05, Hans Petter Selasky wrote:
> On 2020-02-22 01:48, Andreas Kempe wrote:
>> This issue can be remedied by changing the initialisation of the IPoIB
>> module to happen after the mlx4 driver is initialised. By doing this,
>> all multicast groups will be cleaned up before the ib_multicast client
>> is destroyed.
>
> Hi Andreas,
>
> Are you sure it is not the module exit that should be ordered instead?
>
>  module_exit(ipoib_cleanup_module);
>
> Because from the description this issue happen on shutdown and not load.
>
> I'm currently trying to reproduce the issue.
>
> Dropping freebsd-net @
>
> --HPS
> _______________________________________________
> freebsd-infiniband at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-infiniband
> To unsubscribe, send any mail to 
> "freebsd-infiniband-unsubscribe at freebsd.org"
Side-note: I was seeing the same symptom occasionally on our CentOS 
clusters for years.  I frequently had to go to the data center and check 
on hung systems after routine updates, which would often be stuck at 
"Unloading IB modules".  I wonder if it was a similar issue.

-- 
Earth is a beta site.