Bug 512266
| Summary: | [Emulex 5.4 bug] Update lpfc driver to 8.2.0.48.2p to fix multiple panics | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Jamie Wellnitz <jamie.wellnitz> | ||||
| Component: | kernel | Assignee: | Rob Evers <revers> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.4 | CC: | andriusb, coughlan, cward, dzickus, jamie.wellnitz, jbao, laurie.barry, mgahagan, revers, vaios.papadimitriou | ||||
| Target Milestone: | rc | Keywords: | OtherQA | ||||
| Target Release: | 5.4 | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-09-02 08:35:01 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 461676 | ||||||
| Attachments: |
|
||||||
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Emulex, Andrius. It's getting very late into the release cycle. Before we accept this new patch, we need explicit confirmation of Emulex's commitment to test. There must also be a clear understanding that if there are problems with this patch, we need to know about them as soon as possible, as kernel code freeze is upon us. Chances are lowered daily with regard to our ability to commit new code into 5.4. Speak with your Partner Manager for more details about the schedule particulars. We also need to understand the full extent of testing planned for the updated kernel build including the requested patch. We need this information to raise our confidence that this patch will introduce no regressions. If these items can be fulfilled, we'll get you a test package very soon to get things moving along. Otherwise, this request will need to be deferred to RHEL 5.5. Thank you for your understanding and expedited response. Query for Emulex - can you please re-assure Red Hat that you will be 100% on the hook for testing this and verifying this? Emulex is committed to verifying every RHEL5.4 snapshot or test kernel you send our way. This patch set should be the last you see from us unless we identify a panic, hang or corruption. On a nightly basis we run the following tests in our Engineering environment: Driver build and load Filesystem dt; 1 per disk; with LIP every 40 sec (with and w/o NPIV) Filesystem dt; 4 per disk; with LIP every 40 sec (with and w/o NPIV) Filesystem dt; 8 per disk; with LIP every 40 sec (with and w/o NPIV) Filesystem dt; 1 per disk; with HBA reset every 40 sec (with and w/o NPIV) Filesystem dt; 4 per disk; with HBA reset every 40 sec (with and w/o NPIV) Filesystem dt; 8 per disk; with HBA reset every 40 sec (with and w/o NPIV) Raw disk dt with HBA reset every 40 sec (with and w/o NPIV) Raw disk dt with LIP every 40 sec (with and w/o NPIV) Raw disk dt to 1 target from multiple HBAs with LIP every 2 min ( with and w/o NPIV) dskio test (with and w/o NPIV) test hbacmd test suite (with and w/o NPIV) hbacmd test suite firmware update (with and w/o NPIV) firmware update Apps install (with and w/o NPIV) aiostress; threads=2 size=1024MB aiostress; threads=3 size=1024MB aiostress; threads=4 size=1024MB aiostress; threads=5 size=1024MB (NPIV) Driver sparse build Create test vport Delete test vport Create and delete vports Vports Expunged via Driver Unload Test Public NPIV Support Scripts sg_util test suite (NPIV) Additionally, starting with RHEL5.4 RC drop, our Qual group will be running a full regression against RHEL5.4 and any issues found will be requested for resolution in the UCNA FCoE DUP or RHEL5.4 errata kernel depending on what turns out to be the easiest process for RH and our OEMs. Laurie Thanks. I'll recommend then that we get this patch included. Thanks for the information and quick response time. in kernel-2.6.18-160.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Please do NOT transition this bugzilla state to VERIFIED until our QE team has sent specific instructions indicating when to do so. However feel free to provide a comment indicating that this fix has been verified. We'll pull this down now and run it through our testing. Thank you Laurie Emulex, any update on testing? Chris, Our testing in the nightly development test bed has been running clean and in scaled up link perturbation testing DVT ran for 17 hours w/o a issue. We are moving onto to test the latest snapshot next. Consider this a pass with Emulex testing on this kernel. Laurie 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. http://rhn.redhat.com/errata/RHSA-2009-1243.html |
Created attachment 354053 [details] Patch to update Emulex lpfc driver to 8.2.0.48.2p (applies on top of 8.2.0.48.1p) * Changed version number to 8.2.0.48.2p * Fixed panic in menlo sysfs handler * Fixed unsolicited CT commands crashing kernel * Fixed persistent port state to use config region 23 (CR 91320) * Fixed panic/hang when using polling mode for FCP commands (CR 91684) * Fix crash when "error" is echoed to board_mode sysfs parameter The "persistent port state" change fixes an issue which can cause the lpfc driver not to bring the link up on some older SLI-3 HBAs, which in turn would prevent the system from booting in a boot-from-SAN configuration.