Product specifications

D–Troubleshooting
Kernel and Initialization Issues
IB6054601-00 H D-5
A
OpenFabrics Load Errors if ib_ipath Driver Load Fails
When the ib_ipath driver fails to load, the other OpenFabrics drivers/modules
will load and be shown by lsmod, but commands like ibstatus, ibv_devinfo,
and ipath_control -i will fail as follows:
# ibstatus
Fatal error: device ’*’: sys files not found
(/sys/class/infiniband/*/ports)
# ibv_devinfo
libibverbs: Fatal: couldn’t read uverbs ABI version.
No IB devices found
# ipath_control -i
InfiniPath driver not loaded ?
No InfiniPath info available
InfiniPath ib_ipath Initialization Failure
There may be cases where ib_ipath was not properly initialized. Symptoms of
this may show up in error messages from an MPI job or another program. Here is
a sample command and error message:
$ mpirun -np 2 -m ~/tmp/mbu13 osu_latency
<nodename>:ipath_userinit: assign_port command failed: Network is
down
<nodename>:can’t open /dev/ipath, network down
This will be followed by messages of this type after 60 seconds:
MPIRUN<node_where_started>: 1 rank has not yet exited 60 seconds
after rank 0 (node <nodename>) exited without reaching
MPI_Finalize().
MPIRUN<node_where_started>:Waiting at most another 60 seconds for
the remaining ranks to do a clean shutdown before terminating 1
node processes.
If this error appears, check to see if the InfiniPath driver is loaded by typing:
$ lsmod | grep ib_ipath
If no output is displayed, the driver did not load for some reason. In this case, try
the following commands (as root):
# modprobe -v ib_ipath
# lsmod | grep ib_ipath
# dmesg | grep -i ipath | tail -25
The output will indicate whether the driver has loaded. Printing out messages
using dmesg may help to locate any problems with ib_ipath.