Allied Telesis NETEXTREME II AT-2973SX - Manual (Page 75)

AT-2973SX, AT-2973T, and AT-2973T/4 NetExtreme II Family Adapters Installation and User’s Guide
75
Setting Optional Properties for the bnx2 Driver
The disable_msi optional property can be supplied as a command line
argument to the insmod or modprobe command. The property can also be
set in the modprobe.conf command. See the man page for more
information.
All other driver settings can be queried and changed using the ethtool
utility. See the ethtool man page for more information. The ethtool
settings do not persist across a reboot or module reload. In addition, you
can put the ethtool commands in a startup script, such as
/etc/rc.local, to preserve the settings across a reboot.
Note
Some combinations of property values may conflict and result in
failures. The driver cannot detect all conflicting combinations.
This property is used to disable Message Signal Interrupts (MSI). The
property is valid only on 2.6 kernels that support MSI. This property cannot
be used on 2.4 kernels. By default, the driver enables MSI if it is supported
by the kernel. It runs an interrupt test during initialization to determine if
MSI is working. If the test passes, the driver enables MSI. Otherwise, it
uses legacy INTx mode. To set the bnx2 driver, enter one of the following:
insmod bnx2.ko disable_msi=1
or
modprobe bnx2 disable_msi=1
Setting Optional Properties for the bnx2i Driver
You can supply the optional parameters en_tcp_dack, error_mask1 and
error_mask2 as command line arguments to the insmod or modprobe
command for the bnx2i driver.
error_mask1 and error_mask2
Use “Config FW iSCSI Error Mask #" to configure certain iSCSI protocol
violations to be treated either as a warning or a fatal error. All fatal iSCSI
protocol violations result in session recovery (ERL 0). These are bit
masks. By default, all violations are treated as errors.
Caution
Do not use the error_mask parameter if you are not sure about the
consequences. Discuss these values with the Broadcom
development team on a case-by-case basis. This is a mechanism to
work around iSCSI implementation issues on the target side and