Bug 468873 - [QLogic 5.3 bug] qla2xxx - fails to report Option Rom version information
Summary: [QLogic 5.3 bug] qla2xxx - fails to report Option Rom version information
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Marcus Barrow
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks: 415811
TreeView+ depends on / blocked
 
Reported: 2008-10-28 15:08 UTC by Marcus Barrow
Modified: 2009-06-20 07:54 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-20 19:59:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
fix class attribute table (2.64 KB, patch)
2008-10-30 04:11 UTC, Marcus Barrow
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2009:0225 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 5.3 kernel security and bug fix update 2009-01-20 16:06:24 UTC

Description Marcus Barrow 2008-10-28 15:08:09 UTC
EMC reports that the QLE2462 and other HBA's are failing to report version information from the Option Rom to the management utilities. This information includes BIOS, EFI, FCODE and firmware versions.

Being able to identify these versions at runtime is important for providing support.

Comment 2 Marcus Barrow 2008-10-30 03:46:28 UTC
After trying to back port upstream patches to provide this support I was able to determine that the code to support providing this information was already present. The bug was that in the RHEL driver there are different class attribute tables for the newer HBA's that support NPIV and also for the NPIV ports themselves. Since their is only a single table upstream, the upstream patches have not been updating all the tables.

I have looked thru the code and updated all the tables to be consistent and correct. This required adding 5 lines to the new tables. I can now see this information being offered in SYSFS as intended.

In addition I have updated the version number and appended the "-k" flag to indicate inbox driver for the management applications.

Comment 3 Marcus Barrow 2008-10-30 04:11:12 UTC
Created attachment 321897 [details]
fix class attribute table

Comment 5 Don Zickus 2008-11-04 16:51:41 UTC
in kernel-2.6.18-122.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5

Comment 7 Chris Ward 2008-11-14 14:05:55 UTC
~~~ 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.

Comment 8 Marcus Barrow 2008-11-18 04:24:16 UTC
Patch verified in 2.6.18-123.el5.

Comment 10 errata-xmlrpc 2009-01-20 19:59:51 UTC
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


Note You need to log in before you can comment on or make changes to this bug.