Red Hat Bugzilla – Bug 468555
[QLogic 5.3 bug] qla2xxx - restore disable by default of MSI, MSI-X
Last modified: 2009-06-20 03:52:40 EDT
When support for the FCoE adapters was added the default behavior of having MSI and MSIX interrupt handling disabled was removed.
IBM's testing of the MRG product has shown problems under load, which were resolved by disabling MSI and MSI-X. This is described in: BZ 466903 - mailbox timeouts observed on ds4700 luns.
This patch disables these interrupt handling mechanisms by default. MSI and MSI-X can be enabled by the module parameter "ql2xenablemsix=1".
Created attachment 321532 [details]
default disable of MSIX
You can download this test kernel from http://people.redhat.com/dzickus/el5
Thank you, I will download, install, test and update bug with results.
~~~ Attention Partners! ~~~
Please test this URGENT / HIGH priority bug at your earliest convenience to ensure it makes it into the upcoming RHEL 5.3 release. The fix should be present in the Partner Snapshot #2 (kernel*-122), available NOW at ftp://partners.redhat.com. As we are approaching the end of the RHEL 5.3 test cycle, it is critical that you report back testing results as soon as possible.
If you have VERIFIED the fix, please add PartnerVerified to the Bugzilla Keywords field to indicate this. If you find that this issue has not been properly fixed, set the bug status to ASSIGNED with a comment describing the issues you encountered.
All NEW issues encountered (not part of this bug fix) should have a new bug created with the proper keywords and flags set to trigger a review for their inclusion in the upcoming RHEL 5.3 or other future release. Post a link in this bugzilla pointing to the new issue to ensure it is not overlooked.
For any additional questions, speak with your Partner Manager.
Patch verified in 2.6.18-123.el5
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.