Created attachment 322912 [details] patch for Emulex lpfc 8.2.0.33.3p - applies on top of 8.2.0.33.2p There's a bug in 8.2.0.33.2p (in kernel 2.6.18-122.el5) involving Fibre Channel discovery. Symptoms: lpfc HBAs fail to discover all the targets after a switch reboot when connected to a QLogic switch. The fix is two lines (actually a single line moved by a few lines), plus the version change. Following are the events that cause this issue. - After a switch reboot HBA receives a link up event - Driver starts discovery by querying the name server and sending PLOGI to the targets. - The PLOGI for one target fails with LS_RJT - The driver started a delay timer to retry the PLOGI after one second. The NLP_NPR_2B_DISC flag of this target is set and target is in NPR state now. - Before delay timer expires, the HBA received an RSCN for the target and lpfc_device_recov_npr_node state machine function is called. This function resets the NLP_NPR_2B_DISC flag and calls lpfc_cancel_retry_delay_tmo function. The counters for keeping track of the number of targets in discovery is updated in lpfc_cancel_retry_delay_tmo function based on NLP_NPR_2B_DISC flag. These counters are not updated because NLP_NPR_2B_DISC flag is cleared before calling lpfc_cancel_retry_delay_tmo function. This leaves the HBA in FC_NDISC_ACTIVE state and results in the driver not responding to any RSCN events. Fix: Moved the clearing of NLP_NPR_2B_DISC flag after the lpfc_cancel_retry_delay_tmo function call in lpfc_device_recov_npr_node function.
in kernel-2.6.18-126.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
~~~ Attention Partners ~~~ The *last* RHEL 5.3 Snapshot 6 is now available at partners.redhat.com. A fix for this bug should be present. Please test and update this bug with test results as soon as possible. If the fix present in Snap6 meets all the expected requirements for this bug, please add the keyword PartnerVerified. If any new bugs are discovered, please CLONE this bug and describe the issues encountered there.
2.6.18-126.el5 has 8.2.0.33.3p and looks good.
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-0225.html