> okay, I verified that with 2.6.36 this node gets IB link and IPoIB is > working fine, so it must be something in or related to the for-next > branch, I assume around the IBoE patches that touch mlx4 which make > this failure to happen. With 2.6.36 I also see the "awk: > /etc/ofed/setup-mlx4.awk:6: (FILENAME=/etc/ofed/mlx4.conf FNR=21) > fatal: cannot open file `/sbin/setup-mlx4' for reading (No such file > or directory)" warning when loading mlx4_ib, but it doesn't > disruptive in the sense that the node works fine, IB wise.
I suspect I broke either the UD header packing or the build_mlx_header function when I "cleaned up" the patches. I see the same problem, I'll take a look today. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
