Product specifications
Table Of Contents
- Table of Contents
- 1 Introduction
- 2 Feature Overview
- 3 Step-by-Step Cluster Setup and MPI Usage Checklists
- 4 InfiniPath Cluster Setup and Administration
- Introduction
- Installed Layout
- Memory Footprint
- BIOS Settings
- InfiniPath and OpenFabrics Driver Overview
- OpenFabrics Drivers and Services Configuration and Startup
- Other Configuration: Changing the MTU Size
- Managing the InfiniPath Driver
- More Information on Configuring and Loading Drivers
- Performance Settings and Management Tips
- Host Environment Setup for MPI
- Checking Cluster and Software Status
- 5 Using QLogic MPI
- Introduction
- Getting Started with MPI
- QLogic MPI Details
- Use Wrapper Scripts for Compiling and Linking
- Configuring MPI Programs for QLogic MPI
- To Use Another Compiler
- Process Allocation
- mpihosts File Details
- Using mpirun
- Console I/O in MPI Programs
- Environment for Node Programs
- Environment Variables
- Running Multiple Versions of InfiniPath or MPI
- Job Blocking in Case of Temporary InfiniBand Link Failures
- Performance Tuning
- MPD
- QLogic MPI and Hybrid MPI/OpenMP Applications
- Debugging MPI Programs
- QLogic MPI Limitations
- 6 Using Other MPIs
- A mpirun Options Summary
- B Benchmark Programs
- C Integration with a Batch Queuing System
- D Troubleshooting
- Using LEDs to Check the State of the Adapter
- BIOS Settings
- Kernel and Initialization Issues
- OpenFabrics and InfiniPath Issues
- Stop OpenSM Before Stopping/Restarting InfiniPath
- Manual Shutdown or Restart May Hang if NFS in Use
- Load and Configure IPoIB Before Loading SDP
- Set $IBPATH for OpenFabrics Scripts
- ifconfig Does Not Display Hardware Address Properly on RHEL4
- SDP Module Not Loading
- ibsrpdm Command Hangs when Two Host Channel Adapters are Installed but Only Unit 1 is Connected to the Switch
- Outdated ipath_ether Configuration Setup Generates Error
- System Administration Troubleshooting
- Performance Issues
- QLogic MPI Troubleshooting
- Mixed Releases of MPI RPMs
- Missing mpirun Executable
- Resolving Hostname with Multi-Homed Head Node
- Cross-Compilation Issues
- Compiler/Linker Mismatch
- Compiler Cannot Find Include, Module, or Library Files
- Problem with Shell Special Characters and Wrapper Scripts
- Run Time Errors with Different MPI Implementations
- Process Limitation with ssh
- Number of Processes Exceeds ulimit for Number of Open Files
- Using MPI.mod Files
- Extending MPI Modules
- Lock Enough Memory on Nodes When Using a Batch Queuing System
- Error Creating Shared Memory Object
- gdb Gets SIG32 Signal Under mpirun -debug with the PSM Receive Progress Thread Enabled
- General Error Messages
- Error Messages Generated by mpirun
- MPI Stats
- E Write Combining
- F Useful Programs and Files
- G Recommended Reading
- Glossary
- Index

D–Troubleshooting
Kernel and Initialization Issues
D-4 IB6054601-00 H
S
If there is no output at all, the driver initialization failed. For more information on
driver problems, see “Driver Load Fails Due to Unsupported Kernel” on page D-3
or “InfiniPath ib_ipath Initialization Failure” on page D-5.
If the output is similar to one of these lines, then interrupts are not being delivered
to the driver.
66: 0 0 PCI-MSI ib_ipath
185: 0 0 IO-APIC-level ib_ipath
The following message appears when driver has initialized successfully, but no
interrupts are seen within 5 seconds.
ib_ipath 0000:82:00.0: No interrupts detected.
A zero count in all CPU columns means that no InfiniPath interrupts have been
delivered to the processor.
The possible causes of this problem are:
Booting the Linux kernel with ACPI disabled on either the boot command
line or in the BIOS configuration
Other infinipath initialization failures
To check if the kernel was booted with the noacpi or pci=noacpi option, use
this command:
$ grep -i acpi /proc/cmdline
If output is displayed, fix the kernel boot command line so that ACPI is enabled.
This command line can be set in various ways, depending on your distribution. If
no output is displayed, check that ACPI is enabled in your BIOS settings.
To track down other initialization failures, see “InfiniPath ib_ipath Initialization
Failure” on page D-5.
The program ipath_checkout can also help flag these kinds of problems. See
“ipath_checkout” on page F-7 for more information.