QLogic OFED+ Host Software User Guide, Rev. B
QLogic OFED+ Host Software User Guide, Rev. B
QLogic OFED+ Host Software User Guide, Rev. B
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
F–Troubleshooting<br />
<strong>QLogic</strong> MPI Troubleshooting<br />
The following message indicates a mismatch between the <strong>QLogic</strong> interconnect<br />
hardware in use and the version where the software was compiled:<br />
Number of buffer avail registers is wrong; have n, expected m<br />
build mismatch, tidmap has n bits, ts_map m<br />
These messages indicate a mismatch between the InfiniPath software and<br />
hardware versions. Consult Technical Support after verifying that current drivers<br />
and libraries are installed.<br />
The following examples are all informative messages about driver initialization<br />
problems. They are not necessarily fatal themselves, but may indicate problems<br />
that interfere with the application. In the actual printed output, all of the messages<br />
are prefixed with the name of the function that produced them.<br />
assign_port command failed: str<br />
Failed to get LID for unit u: str<br />
Failed to get number of units: str<br />
GETPORT ioctl failed: str<br />
can't allocate memory for ipath_ctrl: str<br />
can't stat infinipath device to determine type: str<br />
file descriptor is not for a real device, failing<br />
get info ioctl failed: str<br />
ipath_get_num_units called before init<br />
ipath_get_unit_lid called before init<br />
mmap of egr bufs from h failed: str<br />
mmap of pio buffers at %llx failed: str<br />
mmap of pioavail registers (%llx) failed: str<br />
mmap of rcvhdr q failed: str<br />
mmap of user registers at %llx failed: str<br />
userinit command failed: str<br />
Failed to set close on exec for device: str<br />
NOTE:<br />
These messages should never occur. If they do, notify Technical Support.<br />
The following message indicates that a node program may not be processing<br />
incoming packets, perhaps due to a very high system load:<br />
eager array full after overflow, flushing (head h, tail t)<br />
The following error messages should rarely occur; they indicate internal software<br />
problems:<br />
ExpSend opcode h tid=j, rhf_error k: str<br />
Asked to set timeout w/delay l, gives time in past (t2 < t1)<br />
Error in sending packet: str<br />
In this case, str can give additional information about why the failure occurred.<br />
F-26 D000046-005 B
Change language