Bug 480204

rlary: did you manually remove QLogic from the Partner field above? Let me know, this is a new field we will start using but could be a bug if you didn't touch the field... thanks!

(In reply to comment #1)
> rlary: did you manually remove QLogic from the Partner field above? Let me
> know, this is a new field we will start using but could be a bug if you didn't
> touch the field... thanks!

No I did not manually remove QLogic from the Partner field.  Sorry for delayed response, travelling.

Updating PM score.

Created attachment 338961 [details]
updates 1 for 5.4

Fixes in patch attached above...

 - Ensure fcport obtained from rport->dd_data is not NULL
 - Check QLID signature in FDT.
 - Correct discrepancies during OVERRUN handling on FWI2-capable cards
 - Correct synchronization of software/firmware fcport states.
 - Add supported speed attribute to true.
 - Fix vport abort on main ISP aborts.
 - Use an rport's scsi_target_id member consistently throughout driver.
 - Alert all vports of an aynch event.
 - Correct ISP abort semantics for HBA param  & VPD update.
 - Added 8100 fw, eventaully it will be removed.
 - Correct Kernel Panic with Qlogic 2472 Card.
 - Properly acknowledge IDC notification messages.
 - Fixed IDC handling
 - Added CT Passthru support for 2G HBAs
 - Mask region code
 - Do not retry stop_firmware if the first attemtp timeouts
 - Removed unwanted warning messages

in kernel-2.6.18-144.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.

Verified driver version 8.03.00.04.05.04-k
Testing underway on IBM Power PC QLogic FCoE adapter.

~~ Attention Partners RHEL 5.4 Partner Alpha Released! ~~

RHEL 5.4 Partner Alpha has been released on partners.redhat.com. There should
be a fix present that addresses this particular request. Please test and report back your results here, at your earliest convenience. Our Public Beta release is just around the corner!

If you encounter any issues, please set the bug back to the ASSIGNED state and
describe the issues you encountered. If you have verified the request functions as expected, please set your Partner ID in the Partner field above to indicate successful test results. Do not flip the bug status to VERIFIED. Further questions can be directed to your Red Hat Partner Manager. Thanks!

~~ Attention - RHEL 5.4 Beta Released! ~~

RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!

If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.

Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.

Questions can be posted to this bug or your customer or partner representative.

~~ Attention Partners - RHEL 5.4 Snapshot 1 Released! ~~

RHEL 5.4 Snapshot 1 has been released on partners.redhat.com. If you have already reported your test results, you can safely ignore this request. Otherwise, please notice that there should be a fix available now that addresses this particular request. Please test and report back your results here, at your earliest convenience. The RHEL 5.4 exception freeze is quickly approaching.

If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.

Do not flip the bug status to VERIFIED. Instead, please set your Partner ID in the Verified field above if you have successfully verified the resolution of this issue. 

Further questions can be directed to your Red Hat Partner Manager or other appropriate customer representative.

Verified that the patch to this bug is included in kernel-2.6.18-160.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.

http://rhn.redhat.com/errata/RHSA-2009-1243.html