HP IO Accelerator Driver 3.1.1 Release Notes

Errata 17
$ modprobe iomemory-vsl disable_msi=0
To work around this issue, if you see the error, reboot the system. Also, always load with the same interrupt
type selected. To change between interrupt types, reboot the system first.
RHEL6 udevd warning
When using an IO Accelerator under RHEL6 (or any Linux distribution with udev script version 147 or later),
udevd might emit the following messages:
udevd[154]: worker [19174] unexpectedly returned with status 0x0100
udevd[154]: worker [19174] failed while handling
'/devices/virtual/block/fioa'
These messages are innocuous, and you can ignore them.
RHEL6 gives a warn_slowpath message during device attach
When attaching an IO Accelerator device under RHEL6, you might see log messages similar to the following:
kernel: ------------[ cut here ]------------
kernel: WARNING: at fs/fs-writeback.c:967 __mark_inode_dirty+0x108/0x160()
(Tainted: P ---------------- )
.
.
.
[<ffffffff8106b857>] warn_slowpath_common+0x87/0xc0
[<ffffffff8106b8aa>] warn_slowpath_null+0x1a/0x20
.
.
.
This is due to a bug in the 2.6.32 kernel, and the messages can safely be ignored.
Switching interrupt types with newer kernels might cause errors
With newer Linux kernels, switching interrupt types after initial driver load might cause the kernel to report
doIRQ errors. As a workaround, reboot your system before loading the driver with the new interrupt type
specified.
Stop fio-snmp-agentx when the IO Accelerator driver is unloaded
If the IO Accelerator driver is unloaded and you are running the snmpd and fio-snmp-agentx commands
with the fio-snmp-agentx configured to write to a log file, then stop the fio-snmp-agentx. Otherwise,
the fio-snmp-agentx continually logs error messages to the log file, stating that it is unable to access IO
Accelerator device information. No issues are created with the system other than unnecessary file space
consumption.