On Tue, Jul 25, 2017 at 11:27:50AM -0500, Steve Wise wrote: > > I do not have nearly enough hardware to exhaustively test this, I have checked > > that the basic elements are working, but there is lots of room for little > > errors, particularly in module names and udev matching. It would be great of > > someone could try this on iwarp hardware and confirm all the autoloading works > > as expected. > > Hey Jason, > > Thanks for doing all this! I'm testing with cxgb4 today. > > I get these errors building the rpms using the spec file in your tree: I think you are using ./rdma-core.spec? I forgot about that one and didn't make it work, I will fix it. You probably want to use redhat/rdma-core.spec anyhow? When testing, you want to start with a system that doesn't load any modules, then install the new rpms and see what happens. (rdma-core, iwpmd) For iwarp I expect that systemd will auto start these units: rdma-load-modules@iwpmd.service loaded active exited Load RDMA modules from /etc/rdma/modules/iwpmd.conf rdma-load-modules@rdma.service loaded active exited Load RDMA modules from /etc/rdma/modules/rdma.conf rdma-load-modules@iwarp.service loaded active exited Load RDMA modules from /etc/rdma/modules/iwarp.conf iwpmd.service loaded active running iWarp Port Mapper And you should have a reasonable set of modules loaded. Check the journal for interesting errors also.. For cxgb4 these are the two critical udev lines: ENV{ID_NET_DRIVER}=="cxgb4", RUN{builtin}+="kmod load iw_cxgb4" DRIVERS=="cxgb4", ENV{ID_RDMA_IWARP}="1" The first should load iw_cxgb4 if an ethernet device with the cxgb4 driver is found (the driver name being matched is as reported by ethtool -i) Both need to trigger for things to work properly, you can check with: $ udevadm info /sys/class/net/ethX $ udevadm info /sys/class/infiniband/cxgb4_0 # ?? Thanks, Jason -- 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