Product specifications

Table Of Contents
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.