ServeRAID M1000 Series SAS/SATA Controller Firmware Update
Adapters Supported: ServeRAID M1115 SAS/SATA Controller for IBM System X (81Y4448) ServeRAID M1015 SAS/SATA Controller (46M0831)
Version 20.10.1-0107 - Suggested ------------------- Fixes: - Fixed grammatical errors in WebBIOS. - Fixed an issue in WebBIOS Drive Group Definition screen where enclosures should not be selectable in the Drives column. - Fixed an issue in uEFI-WebBIOS where the white bars do not match up under VD properties page. - Fixed an HII browser issue where a drive performing a copyback displayed the state as "Replacing" but other utilities showed the state as copyback. - Fixed an HII browser display issue where SATA drives showed "0" for the value of RPM under drive properties. - Fixed a display issue where the HDD port number showed incorrectly in an HII browser. - Fixed an HII browser issues where creating a global hotspare gave the user an error message. - Fixed an HII browser issue when security is changed with local key management the changing security report current mode is disabled as external keu management. - Fixed an HII browser issue where the user got the following error message, "The request command has invalid arguments," when changing the security key report. - Fixed an HII browser issue where the user was unable to save the configuration after adding an extra span during array creation. - Fixed an HII browser issue where the return value was not correct when the browser called extract config with a result of null.
Version 20.10.1-0101 - Suggested ------------------- Fixes: - Fixed an issue where a system uefi error will occur when the bootTargetId is set to 0. - Fixed a problem where the firmware will allocate the sata bbl entry for the drive when moved from unsupported to supported. - Fixed a firmware issue where the TargetId for the recon LD should be set to its original LD. - Fixed a HII error message "Question Value mismatch with Option value!" after selecting factory defaults in HII. - Fixed an issue where the firmware fails to create the configuration and utilities fail to report the VD size after the reconstruction.
Version 20.10.1-0091-01 - Non-Critical ------------------- Fix - Fixed issue where update may fail to find all supported controllers in SLES 11 SP 2. Note not change in the firmware; it is the same as package 20.10.1-0091.
Version 20.10.1-0091 - Suggested ------------------- Enhancement: - Add support for ServeRAID M1115
Fixes: - Fixed issue where after starting a reconstruction on a RAID 0 the progress %, does not increase. - Fixed an issue where a new drive, inserted after a drive failure, goes to JBOD and not auto rebuild. - Fixed physical drive count issue that stated more than (16) devices already exists
Version 20.10.1-0069- Suggested ------------------- Enhancement: - ServeRAID M1015 Dimmer Switches are disabled by default.
Fixes: - Fixed issue where enabling security causes the configuration to be missing, and a configured FDE array to be seen as foreign on reboot. - Fixed issue where WebBIOS gives garbled message when enabing FDE on an existing Disk Group - Fixed issue where the logical Unit ID (VPD page 0x83) changed after foreign import. - Fixed issue where the LDBBM entries are incorrect after foreign import. - Fixed a problem where firmware was taking to long to complete the PCI config read. Causing the system to generate an NMI. - Fixed issue where the controller does not work with pci set to nomsi in kdump kernel. - Fixed issue where the LED behavior is incorrect, wrong drive will blink activity. - Fixed issue where the configuration becomes foreign after the firmware fails multiple attempts to access raid key during boot. - Fixed firmware issue where a replacement drive is not seen if the replacement is added during power cycle. - Fixed an intermittent RAID key failure during power-on.
Version 20.10.1-0052- Critical ------------------- Enhancement: - Add support to pass SMART errors for JBOD drives to MSM
Fixes: - Added check to return SCSI sense Check condition if PMI is set and LBA is non zero for SCSI Read Cap 16. - Fixed issue where a bluescreen occurs handling RAID 1 with HSP and medium errors. The bluescreen occurs becausethe driver timesout while fw is retrying sense 0x02. Firmware causes Fatal Error when HSP drive responded with Sense 0x02 for Write/Verify or TUR - Fixed hang condition or condition where the uEFI driver does not load due to the uEFI Driver issuing a command in poll mode to firmware to early
Version 20.10.1-0045 - Critical ------------------- Fix: - Fixed issue where firmware has incomplete writes during power fail and recovery
Version 20.10.1-0036 - Critical ------------------- Fixes: - Fixed issue where uEFI WebBIOS version may not display the product name of the second controller - Fixed issue to prevent users to downlevel firmware to older versions - Fixed an issue where firmware reports "Unexpected sense, Invalid field in CDB" for LOG SENSE command sent to Seagate drives - Fixed issue where SMART failures can take longer then 5 minutes to report or in some cases fail to report - Fixed issue where it appears to the user the harddrive cache policy is changed when requested but the change did not occur
Version 20.10.1-0022 - Critical ------------------- - Fixed issue where Windows 2008 R2 WS08 cannot be installed properly on ServeRAID M1015 SATA JBOD with a uEFI boot. - Added warning message when user tried to change more then 16 drives to JBOD. - Addressed a problem where direct attached drives are given incorrect slot numbers - Added fixes from LSI channel products. - Fixed issue where a single JBOD drive will not boot after a Windows 2008 R2 installation.
Version 20.5.1-0014 - Critical ------------------- - Addressed data issue with database applications that use overlapping read write operating. - Addressed data issue which may occur during a reconstruction on some RAID levels that have an associated CacheCade virtual drive enabled. - Fixed problem where the controller may halt if a drive has medium errors that are being used in a check consistency, patrol read, or have delayed writes.
Version 20.1.1-0059 - Critical ------------------- Fixes: - Fixed an issue where a physical drive that is changed to JBOD from powersave will become unconfigured good again - Addresses an issue where data becomes inaccessible when a drive is secured after data has been written
Version 20.1.1-0049 - Suggested ------------------- Enhancement - Support M1000 key for RAID 5 and SED support
Fixes: - Fixed an issue in M3950M3 where webbios would hang - Fixed an issue where the controller properties in WebBIOS such as Rebuild, CC and BGI are not changing when we use up and down arrow keys. - Fixed an issue where Enclosure ID's are not being shown in MSM
Version 20.1.1-0046 - Suggested ------------------- - Enabled support for the ServeRAID M1000 Series Advanced Feature Key.
Note: All Logical Drives must previously have the encryption enabled before data is written on to the SED drives. Please read Retain TIP H123152 for more details.
Version 20.1.1-0042 ------------------- - Initial release ibm_fw_sraidmr_m1000-20_10_1-0107_linux_32-64_chg
Integrated Management Module (IMM) Firmware Update Change History
IMPORTANT: Prerequisite for updating to IMM firmware version 1.30 (yuooc7e) ========== Updating to IMM firmware version 1.30 (yuooc7e) requires the current IMM firmware version to be 1.10 (yuoo57h), or later. If this prerequisite is not met before updating to version 1.30 (yuooc7e) the system will not power on correctly. If the system is not running a minimum of IMM version 1.10 (yuoo57h), update the IMM before attempting to update to 1.30 (yuooc7e). This prerequisite was a limitation of IMM version 1.30, and it has been fixed in IMM version 1.31(yuooc7f). This prerequisite does not apply to IMM version 1.31 or later.
IMPORTANT: Please DO NOT apply the firmware update (yuoo91e, v1.24) ========= if you are using AEM functions in x3620M3 or x3630M3. The v1.24 firmware will disable the power capping functionality in those two systems. Please remain on the current IMM version or update the firmware to v1.25 or newer. Users not using AEM functions can still update to v1.24.
IMPORTANT: Read before using the MAX5 ========== This Technical Update supplements the documentation that comes with the IBM MAX5 for System x. Keep this document with your other MAX5 documentation. Before you attach the MAX5 to the server and try to use it, you must update the server firmware with the latest level of firmware or code. If you attach and try to use the MAX5 without updating the server firmware, you might get unexpected system behavior or the server might not power on. For special instructions to follow before you attach the MAX5 to the server, go to http://www.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5085756.
IBM maintains pages on the World Wide Web where you can get the latest technical information and download device drivers and updates. To access these pages, go to http://www.ibm.com/systems/support/ and follow the instructions.
IMPORTANT: If you are at IMM firmware versions prior to 1.12 (yuoo67c) and ========== updating IMM firmware in Microsoft Windows, when you update IMM to versions between 1.14 (YUOO73M) and 1.30 (YUOOC7E), it will take up to 10 minutes additional wait time; when you update IMM to version 1.30 (YUOOC7E) or later, it will take up to 20 minutes additional wait time. This is due to the iflash tool checking the IMM before flashing. During this time the flashing process may appear hung or unresponsive. The flashing will then complete and there is no functional impact.
IMPORTANT: Make sure the current IMM firmware level is 1.14 or later ========== before you update the uEFI, FPGA, or DSA Preboot firmware. The recommended firmware update sequence is IMM followed by UEFI followed by FPGA followed by DSA Preboot.
IMPORTANT: A firmware change was made in YUOO57H (v1.10) that enforces the ========= requirement for login accounts on the IMM to have passwords that contain both alpha and numeric characters. If you are updating the IMM firmware from YUOO56K (v1.09) or earlier, to YUOO57H (v1.10) or newer, prior to updating the firmware, please ensure that the IMM user account passwords contain both alpha and numeric characters. If the firmware is updated and the passwords do not contain both alpha and numeric characters, you may need to reset the IMM to its default settings using the menus in the UEFI F1 set up display.
IMPORTANT: When updating the IMM firmware from a version earlier than ========= version 1.05 (build YUOO32F) to version 1.05 or newer, the Remote Alert Recipient Email Addresses and the Daylight Saving Time setting will revert to the default setting. Users that utilize these settings will need to set them again after the update.
IMPORTANT: When updating IMM, uEFI, pDSA, FPGA via any method, ========== please follow firmware update best practice document (http://www-947.ibm.com/support/entry/portal/docdisplay?brand= 5000020&lndocid=MIGR-5082923) for suggested update sequence and prerequisite.
IMPORTANT: Due to an Intel errata, if your server is running a 32-bit Linux ========== Operating System, C-states may need to be disabled while updating uEFI, IMM, or DSA Preboot through the Linux command line interface. See RETAIN TIP H195678 for more information. Updates performed through the AMM, Bootable Media Creator, or the IMM web or CLI interfaces do not have this requirement.
IMPORTANT: Updated firmware version numbers might not be visible in SMBIOS ========== tables until after the server is rebooted.
IMPORTANT: After downgrading IMM firmware from version 1.22 ========== to an earlier version, the user needs to reset the IMM to factory default before normal operation.
Version 1.41, YUOOF7C Problem Fixed: - Fixed the problem on blades where sometimes no throttle event was reported by AMM when CPU temperature is higher than Tcontrol. Enhancements: - Enhanced logging for throttle and Power Management.
Version 1.40, YUOOF7A Problems Fixed: - Fixed the problem on x3690X5 that host OS will be shut down due to wrong overtemp event. - Fixed the problem that "unsupported software version" could be showed in event logs after updating IMM version 1.30 or newer on x3850/x3950 X5, x3690X5 and HX5 - Fixed the problem that SMTP user name field on IMM web page only allows 16 chars. - Fixed the problem on HS22 where IMM reports 0 watt power during initialization
Enhancements: - Enabled IMM to fail over to backup automatically when there is a IMM firmware corruption - Enhanced IMM web GUI response. - Added notification when a corrupted GUID Partition Table (GPT) is encountered by UEFI during POST. Please refer to RETAIN Tip H207759 for details. - Enhanced logging for Power Controls management.
Version 1.39, YUOOF2C Problems Fixed: - Fixed the problem on IBM System x3850X5 where SAP HANA configurations can reset in rare cases. More details in RETAIN Tip H207295.
Version 1.38, YUOOF2B Problems Fixed: - Fixed the problem on x3850 X5/x3950 X5 where the System Fault LED will be lit when only one PSU is installed.
Version 1.37, YUOOE9C Problems Fixed: - Corrected the voltage sensor threshold for HS22 and HS22V system.
Version 1.36, YUOOF2A Enhancements: - Improved IMM web page Accessibility
Version 1.35, YUOOE9B Problems Fixed: - Fixed the thermal issue for Broadcom quad port ethernet (IBM PN 49Y7948., FRU 49Y7949). - Fixed the problem that user authentication for LDAP with SSL will fail when Configured Credentials is enabled. - Updated the thermal profile for NVIDIA M2090 GPU card support in dx360 M3. - Fixed the problem on HS22 systems where pressing the KVM button too soon (right after Power LED starts blinking slowly) would make the KVM owner unable to be changed. - Fixed the problem on blade servers where IMM may report the "Unsupported blade/blower combination" error for 130W Westmere CPUs. - Fixed the problem on x3200 M3 where when power policy is set as "restore" or "always on" in uEFI, enforcing system shutdown during POST will cause automatic system boot-up. - Fixed the problem about SNMP drops intermittently and SNMP data cannot be accessed in a period of time - Fixed the problem on x3850 X5/x3950 X5 Multi-Node systems where "redundancy lost" event is not logged in the Primary Node when one of the power supplies in the Secondary Node is lost. - Optimized CPU power consumption calculation method for x3690 X5. - Fixed the problem on blade servers where IMM does not automatically recover NCSI. - Fixed the problem on blade servers that IMM constantly has "Init Failures" and fails to start up. - Fixed the Readme file problem that some IP addresses of LAN-over-USB instructions are inconsistent. - Fixed the CMOS Voltage Over Threshold problem on HS22V systems. - Fixed the problem that SSH login failed when the setting is configured as "Local first then Ldap" or ldap settings are not valid. - Fixed the problem that the IMM web interface responds too slowly or even fails to respond.
Enhancements: - Enhanced the entropy (randomness) when generating SSL keys. - Added secure SMTP authentication support. - Added I/O board VPD information in IMM web interface - Added the function of letting Location LED remain on after system power-off. - Enhanced event Severity reporting of the QPI Link LED on x3850 X5/x3950 X5 so that IBM Director can interpret it correctly. - Improved IMM version reporting for IBM Director. - Added a function to keep 110V Power Supply Redundancy by throttling the system for x3850 X5/x3950 X5. - Usability enhancement: all events will be checked by default on the alert setting web page. - Enabled ASU to control each sub-category for email alert recipient setting and SNMP alerts setting. - Added new BCH Midplane (that supports 8Gbit Fibre Channel) support. - Added the function to capture all IMM logs with one button click. - Enhanced the DataPower appliance blade support.
Version 1.34, YUOOE3E Enhancement: - Add support of the following fusion-io adapters : 1.2TB High IOPS MLC Adapter for IBM System x 2.4TB High IOPS MLC Adapter for IBM System x 365GB High IOPS MLC PCIe Adapter for IBM System x 785GB High IOPS MLC PCIe Adapter for IBM System x
Version 1.33, YUOOE3C Problems Fixed: - Fixed the problem that a blade's Fault LED is showed as "on" on AMM GUI while there is no active critical event and the LED on the physical blade is off. - Fixed the problem that the "Date" header is missing from the IMM SMTP trap. - Fixed the problem that the "Look Below" LED (CR48) on x3690 X5 Memory Expansion Board may turn on incorrectly when there are no errors detected. - Fixed the problem on x3850 X5/x3950 X5 where the system information in the IMM configuration file may be truncated and the incomplete system information will cause the HTTP server in IMM run into an unstable state. - Fixed the problem that the Scalability LED turns off after the IMM on either node of a 2-Node x3850 X5/x3950 X5 is reset. - Fixed the problem that IMM on x3850 X5/x3950 X5 might fail to start after the IMM firmware is successfully upgraded. - Fixed the problem where "Comm Errors" may occur when the IMM firmware on HX5 is upgraded. - Fixed the problem that dx360 M3 may have PCI errors when a NVIDIA M2090 GPU card is installed. - Fixed the problem that opening the ActiveX remote console closes all open tabs in the same Internet Explorer window. - Fixed the problem that x3550 M3 may occur ServerRAID BBU over temperature and ServerRAID M5016 over heat issues.
Enhancements: - Added Internet Explorer 9 support. - Changed the maximum User's Distinguished Name(DN) for LDAP from 128 bytes to 256 bytes. - Removed the limitation of 255 memberOf groups for an LDAP user in IMM. - Enhanced IMM Web session management. - Added an IMM command line (CLI) command for one time PXE boot option setting. - Added a new unique error code in AMM and changed the text in AMM and IMM for CMOS battery errors. - Updated Russia time zone definition to no more daylight saving time.
Version 1.32, YUOOD4G Problems Fixed: - Fixed a problem where IMM web interface does not lock out a user if the same user exhausts login retries and gets locked out through the SSH interface - Fixed a problem that caused the IMM to report false critical DIMM temperature events - Fixed an intermittent problem where sometimes the Power Supply DC status LED is not illuminated on the x3550 M2/M3, x3650 M2/M3, x3620 M3 and x3630 M3 - Fixed a problem that sometimes causes the IMM web interface to shut down after multiple invalid login attempts Enhancements: - Added Service Advisor support on x3850/x3950 X5 and x3690 X5 - Changed the IMM firmware to allow every service port to be Enabled or Disabled - Changed the IMM firmware to not disable the network interface when there is a conflict IP address on the network - Changed the IMM firmware to permit SSL client certificates to be managed while the SSL client is enabled
Version 1.31, YUOOC7F Problems Fixed: - Fixed the problem that after updating IMM firmware from versions prior to v1.10(YUOO57H) to v1.30(YUOOC7E) the system won't power on correctly
Version 1.30, YUOOC7E Problems Fixed: - Fixed the intermittent Power Supply error on x3550M2/M3 and x3650M2/M3 - Fixed the false alarm message for ArBel Power Supply on x3550M2/M3 and x3650M2/M3 - Fixed the issue that a blade intermittently does not respond to the system management bus on HX5 and HS22/S22V - Fixed the duplicate PECI messages issue on x3850/x3950 X5, x3690X5 and HX5 - Fixed the intermittent problem that a user can not login to IMM web after inventory from IBM Director - Fixed the problem that SMTP test alert doesn't work - Fixed the problem that SNMP remote alert doesn't work - Fixed the intermittent IMM reset problem - Fixed the SSL vulnerability issue Enhancements: - Added 64-bit ActiveX Remote Presence Client support - Added BGE overweight detection on HS22 - Added support of differentiating memory failures happening during UEFI POST and during run-time - Added support of reporting AC restore status on x3850/x3950 X5 - Added the change to include DIMM slot number info in the memory error event message
Version 1.29, YUOOB7F Problem(s) Fixed: - Fixed a problem where false memory configuration error messages are sometimes reported on the x3850/x3950 X5
Version 1.28, YUOOB7C Problem(s) Fixed: - Fixed a problem where the IMM sometimes records duplicate event log entries - Fixed a problem that caused the DIMM Bank number to not be correctly reported - Fixed a problem that prevented the system from powering on when there is a firmware mismatch - Fixed a problem that didn't allow a password to be saved if it contains a & or < character - Fixed a problem where the IMM VPD sometimes is not available on the web page - Fixed a problem where one port on the QLogic 8GB HBA card sometimes is not recognized - Fixed a problem that sometimes caused the DVD drive to disappear in RHEL5 after the IMM is reset - Fixed a false Power Supply failure message - Removed the error message pop up when changing the IMM password to default - Fixed the problem that BBU gets over temp during discharging on x3550 M3 - Corrected a problem where the BOFM address became permanent after BOFM is disabled on the AMM - Corrected a system hang when a Multi-Bit memory error occurs with a mixture of 2GB & 4GB DIMMs installed - Fixed the problem where the reported DC Power consumed on the dx360 M3 is higher than actual AC input power - Fixed the MIB mismatch issue - Fixed the incorrect OID in MIB Enhancements: - Added support for 32-bit ActiveX Remote Presence Clients - Added the ability to change the SMTP port number - Changed the firmware to completely shut down the telnet sevice when the telnet max user count is set to 0 - Added support for LDAP Active Directory Application Mode - Added support for LDAP Authentication Only Mode - Changed the firmware to report a configuration error if the CPU installed on the EXA system is not a Westmere CPU - Changed the firmware to allow the x3690X5 to be powered on sooner - Changed the firmware to decrease the amount of time that it takes for the IMM to become ready after it is reset
Version 1.27, YU00A7C Enhancements: - Added support for the IBM BladeCenter HX5(MT: 1910,7873)
Version 1.26, YU00A6A Enhancements: - Added support for the System x3850/x3950 X5(MT: 7143,7191) and System x3690 X5(MT: 7147,7192)
Version 1.25, YU0091K Problem(s) Fixed: - Fixed a problem that hangs the server when F2 is pressed during POST to start Diagnostics - Fixed a problem in the HS22/HS22v that causes the IMM to report an unexpected throttle condition after the AMM is reset - Fixed a problem that causes the IMM lose its DHCP assigned IP address - Improved the monitoring of hard drive status when the server is powered up - Fixed a problem when using a Japanese keyboard with the remote presence function - Fixed a gradual fan speed reduction due to pressure sensor fluctuation on System x3690 X5, System x3550 M2/3, System x3650 M2/3 - Improved the response to an IO Hub over temperature condition on System x3690 X5, System x3650 M2/M3, and System x3550 M2/M3 - Fixed a problem that IBM Systems Director needs to re-discover IMM in order to receive events from IMM after IMM upgrade Enhancements: - Added support for a 460W power supply in the System x3620 M3 - Added support for a 675W high efficiency power supply in the System x3620 M3 and System x3630 M3
Version 1.24, YU0091E Problem(s) Fixed: - Fixed a problem where the IMM sometimes incorrectly reports a Pwr Rail fault or Pwr 240A_A/Pwr 240A_B fault - Fixed an issue where blade would hang on boot with ABR firmware corruption message - Fixed a problem when downgrading IMM firmware from version 1.22 to earlier levels. The IMM network fails - Fixed a problem that caused the firmware update using IMM Command Line Interface to fail on an IPv6 network - Fixed a problem that caused the IPv6 Link-local address not to be displayed after resetting the IMM to its defaults - Fixed a problem where the IMM fails to set SNMP configuration using ASU - Fixed a problem where IMM cannot set the value 10 for the OSWatchdog value using ASU - Fixed a problem where IMM Remote Media would not re-initialize after network error - Fixed problem if KCS error bit status may not be clear which may cause KCS communication stop - Fixed a problem that IMM web interface hang with Remote Control session opened - Fixed a problem that blade unexpected powered on after power off command Enhancements: - Added IPv6 configuration support via IMM SNMP interface - Added support for BladeCenter PCIe Expansion 4 on BladeCenter HX5 - Added support for BladeCenter GPU Expansion on BladeCenter HS22 - Added support for LDAP sub-tree searching with Novell eDirectory 8.7 - Added support for SNMP trap definitions - Updated fan response and logic for Fusion IO PCIe adapter - Updated ambient temperature sensor calculation
Version 1.22, YUOO84C Problem(s) Fixed: - Fixed a problem where the IMM sometimes incorrectly reports a Processor 2 (CPU 2) internal error - Fixed a problem where after powering down an HS22, the HS22 powered on without user request - Fixed a problem while Log in to IMM might fail if the Host name contains a dash - Fixed a problem where the IMM makes some certificate management settings protected that should not be protected - Fixed a problem where users can't get the full details of an expansion card using the IPMI FRU command - Fixed a problem where IMM would hang after an LDAP login using some German or French characters - Fixed a problem with the IMM SMTP client not conforming to RFC821 - Fixed a problem where the email alert setting won't accept a hyphen - Fixed a problem with the Windows key in the IMM Remote Control feature - Fixed a problem where IMM login via LDAP authentication fails to acquire Supervisor authority via Group membership with an OpenLDAP server. - Fixed a problem where a user with Remote Server Power/Restart Access authority can't change the power off delay - Fixed a problem that prevented a Processor Throttled event from being logged for the x3200 M3 and x3250 M3 models - Fixed a problem that where a user's permission is always set from the LDAP account not the local account profile - Fixed a problem where the CPU2 VCore/CPU2 VDIMM sensors become unreadable after updating the IMM in the x3500 M3 model - Fixed problem for DHCP may get time out if using "Shared NIC" mode but without any LAN cable to be plugged into "Sys Mgmt" port Enhancement: - Added IPv6 support - Added Dynamic DNS support (IPv4 only) - Added support for BladeCenter PCIe Expansion 4 on BladeCenter HS22 - Added BCH-R3 support
Version 1.21, YUOO75V Enhancement: - Added support for BladeCenter Max 5 Memory Expansion Unit (MEU) - Added feature to report SMI Lane failure for BladeCenter HX5
Version 1.20, YUOO75T Enhancement: - Added support for Max 5 Memory Expansion Unit (MEU)for SystemX 3690 X5 - Added support for Max 5 Memory Expansion Unit (MEU)for BladeCenter HX5 - Added feature to show pending firmware level during firmware update process - Added feature to block power on when multi-node complex has firmware mismatch Problem(s) Fixed: - Fixed DASD LED behavior for drives 8-32 - Fixed fan over cooling on SystemX 3690 X5 - Fixed Flash failure due to packet loss - Fixed Power Cycle events not appearing in SystemX 3690 SEL - Fixed DIMM throttle behavior in acoustic mode for BladeCenter HX5 - Fixed CPU type checking
Version 1.19, YUOO75X Enhancement: - Added support for Max 5 Memory Expansion Unit (MEU)for SystemX 3850/3950 X5 - Added support for 130W CPUs in High Performance Blades - Added virtual NIC VPD support - Changed the default value of SerialExitCLIKeySequence to ^[( - Added TPM Physical Presence Sensor support - Added AC metering and capping to System x3850/3950 X5 Problem(s) Fixed: - Fixed server time out authority in web interface - Fixed non-recoverable events that appeared as warning events in web event log - Fixed Server State "unknown" status in web interface - Prevented multiple log entries from being created for the same event - Fixed IPMI multi-session handling when sessions fail - Fixed IMM flash failed at 0 percent update progress error - Fixed Internal Error 255 during FPGA update - Fixed CPU Overtemp messages on FPGA update. - Removed unnecessary events for Power Unit sensors - Fixed failure to log VRD error on voltage fault - Fixed Power Redundancy Sensor handling for 220V configurations - Fixed CPU configuration check for System x3850/3950 X5 - Fixed IMM Network ARP - Fixed flash error "Image transfer timed out - error 15" - Corrected a problem that caused the system to not automatically power on after performing an Automatic BIOS Recovery (ABR)
Version 1.18, YUOO75J Enhancement: - Added support for the System x3630 M3
Version 1.17, YUOO75H Enhancement: - Added support for the System x3690 X5
Version 1.16, YUOO73O Enhancement: - Added support for the BladeCenter System HX5
Version 1.14, YUOO73M Problem(s) Fixed: - Corrected the MIB file to address a compiling problem - Fixed a problem when a second CPU might not been recognized by the IMM, when cycling power on the System x3550 - Fixed a problem where web session may hang after staying on the System Status web page for a while - Disabled the interface to the shared network port when the dedicated systems management network interface is selected. - Fixed a web page pop-up error message that may occur after upgrading the IMM from 48d and 57f - Fixed power/thermal calibration error in the x3620 M3 - Fixed a problem where the IMM may log a CPU Automatically Throttled event or a Redundancy Lost for a cooling zone event in the log after cycling power - Fixed a problem where the IMM doesn't send an ambient temperature alert or IO Hub temperature alert in the x3400 M3 and x3500 M3 - Corrected a remote presence problem that occurs while mounting an ISO image if the remote client does not have any removable devices. Enhancement: - Added a fan control enhancement for performance mode - Added support for additional types of power supplies - Improved the accuracy of power readings on 3550 M3, 3650 M3, and 3620 M3
Version 1.14, YUOO73K (released for multinode System x3850 X5 and x3950 X5 only) Problem(s) Fixed: - Fixed a problem that caused the IMM not to respond to some IPMI commands - Corrected a problem with LDAP authentication when role-based security is enabled - Corrected a problem which could cause a false CPU error to occur - Prevented false automatic boot failure recovery events from being reported Enhancements: - Added multinode support for System x3850 X5 and System x3950 X5 - Added support to activate FPGA updates with a warm boot - Added support for AC power metering and AC power capping on single node System x3850 X5 and System x3950 X5 - Added support to improve permit early power on support - Add support to report the version information for updates that have been flashed but not yet activated - Added support to report an FPGA firmware mismatch
Version 1.12, YUOO67C Problems(s) Fixed: - Adjust the Planar VBAT voltage threshold in HS22 Enhancement: - Added support for the System x3620 M3 - Added support for DC power supplies in the System x3550 M3 and System x3650 M3
Version 1.11, YUOO56O Enhancements: - Improved ABR handling to prevent invalid ABR behavior
Version 1.10, YUOO57J (released for HS22 only) Problem(s) Fixes: - Fixed a problem where the IMM sometimes incorrectly reports a Processor 1 (CPU 1) internal error
Version 1.10, YUOO57H Problem(s) Fixed: - Made changes to improve the robustness of firmware update operations. - Corrected an LDAP authentication problem. - Corrected a problem where SNMP settings could be lost after updating the firmware. - Enable ssh by default. - Permit the Adavnced Setting Utility to enable or disable ssh. - Added support for logging a message when the blade CPU is not compatible with the chassis' blower capacity - Permit the realtime power management controller firmware to be flashed to an earlier level. - Corrected a problem that prevented the remote presence function from working with network address translation - Fixed an issue where blades would throttle/hang when chassis power supply is removed Enhancement: - Added support for the System x3550 M3, System x3650 M3, System x3500 M3, System x3400 M3, System x iDataPlex dx360 M3, and the HS22V blade - Enhanced power measurement and capping capabilities in support of xSmartEnergy control - Increased support for the number of DIMMs from 12 to 18
Version 1.09, YUOO56K Enhancement: - Added support for the System x3850 X5 and the System x3950 X5
Version 1.08, YUOO48F Problem(s) Fixed: - Made changes to improve the robustness of firmware update operations. Limitations: Limitations for versions 1.07 and 1.08: If you are down-leveling the IMM firmware to a version older than 1.07 and the IMM firmware is currently at version 1.07 or 1.08, you must remove AC power from the server before performing a server reboot.
Version 1.07, YUOO48E Prerequisites: IMPORTANT: This firmware update contains changes to permit servers ========== to be powered on sooner after plugging them into AC power. Before installing UEFI with firmware that supports the early power on changes, be sure to update the IMM with this firmware version. UEFI Firmware with early power on support: BladeCenter HS22 UEFI Build P9E131A or newer System x3550 M2 UEFI Build D6E131C or newer System x3650 M2 UEFI Build D6E131C or newer System x3200 M3 UEFI Build GYE129A or newer System x3250 M3 UEFI Build GYE129A or newer System x3400 M2 UEFI Build Y4E131B or newer System x3500 M2 UEFI Build Y4E131B or newer System x iDataplex dx360 M2 UEFI Build TME132A or newer Problem(s) Fixed: - Corrected an Ethernet bug that caused network packets to be dropped - Changed the firmware to improve server performance when the Ethernet over USB interface is enabled - Corrected an intermittent problem where some of the IMM interfaces would not function after flashing the IMM with new firmware - Corrected a problem where LDAP users in nested groups are not permitted access to the IMM - Corrected a problem where the fault LED is not lit on the HS22 server when a hard drive is removed - Fixed a problem where the IMM sometimes incorrectly reports faults when the server is power cycled (for example, a loss of redundancy or a critical fan fault, or a processor is operating in a Degraded State, etc...) - Corrected a problem where the server would sometimes hang at checkpoint 'E8' - Changed the firmware to light the Information LED if the primary UEFI bank becomes corrupted - Corrected a problem that prevented the Remote Disk on Card feature from properly working - Corrected a problem that prevented an HS22 server with a full configuration from powering on - Changed the firmware to send processor information to the Advanced Management Module for display - Corrected a problem where faults for fan numbers 2 and 4 for the System X3200 M3 were swapped - Corrected a problem where the IMM firmware could corrupt itself over time Enhancements: - Changed the firmware to permit servers to be powered on sooner after plugging them into AC power - Improved the performance when displaying pages on the web interface - Added support to permit management traffic over the daughter cards in the HS22 server
Version 1.06, YUOO39B Enhancement: - Added support for Machine Types 4251, 4252, 4261, 7327, 7328
Version 1.05, YUOO32F Limitations: Problem(s) Fixed: - This update package contains updated Management Information Base files for use when managing the server through the IMM's SNMP interface - Fixed a problem where user accounts and settings could become lost - Improved performance when changing settings through the web interface - Corrected a problem where some configuration settings were lost after flashing the IMM with new firmware - Improved the wording of messages in the Chassis Event Log - Restored the ability to the IMM SNMP interface to add or remove user accounts and to set the account security level - Corrected a problem that prevented some configuration settings from being set through the Advanced Setting Utility (ASU) - Fixed a problem that prevented a user from specifying an email alert recipient with a hyphen in the name - Fixed an IMM flash update problem where the IMM erroneously reports a CPU Configuration error and/or illuminates the fault LED on the HS22 Blade Server with no corresponding entry in the Advanced Management Module log - Fixed an IMM flash update issue which can result in blades never completing the Discovery state Enhancement: - Added support for the BladeCenter PCIe Expansion module 3 - Added support for servers running real-time Linux - Enhanced the automatic recovery of communication errors in BladeCenter - Added the ability to configure a hostname for SNMPV3 traps, rather than just an IP address
Version 1.04, YUOO24I Problem(s) Fixed: - This is a critical update for x3550 M2 and x3650 M2. It corrects a possible problem that can occur when adding options such as memory, hard drives, and Central Processing Units (CPUs), and makes the system may become unresponsive. In some cases the server cannot power on again, or network connectivity to the Integrated Management Module is not possible. The problem may also occur when rebooting the IMM while the system is powered on with certain hardware configurations. - Replaced the ibm_rndis_server_os.inf and device.cat in the IMM firmware update package for Windows. The new files are used to workaround a potential performance issue when the IMM's Ethernet over USB is enabled. Enhancement: - Added support for different hard drives - Added support that enables the Advanced Management Module to display CPU information for the HS22 blade.
Version 1.03, YUOO23C Problem(s) Fixed: - Removed the empty virtual drives that were presented to the server by default. Virtual drives are now not presented to the server unless media is present and mounted from the Remote Control client. Enhancement: - Added support for Machine Types 7836, 7837, and 7839
Version 1.02, YUOO19G Problem(s) Fixed: - Corrected a problem where a critical fan fault was erroneously logged when powering off the server
Version 1.01, YUOO19E Enhancement: - Added support for Machine Types 7946, 4198, 7947, 4199, 7321, 6380, 7323
Version 1.00, YUOO18D - Original Release - Supports Machine Types 7870, 1936
(C) Copyright International Business Machines Corporation 2008 - 2013. All rights reserved.
Firmware Version 2.01a3 (w/ 5.12a5 Universal Boot Code)
New Features
* Enhanced timeout notifications for processing abort failures.
Problems Fixed:
1. All multi-abort I/Os are returned on the same ring from which the ABORT_MXRI command was received.
2. Changed the TRCV response in the abort state to CMD RJT to enable the TRSP to be processed.
3. Corrected an issue with blocked TSEND operations.
4. Corrected a buffer leak issue with RRQ exchanges.
5. Corrected an issue where the TRCV IOCB was de-queued improperly causing a XFR_RDY flood.
6. Corrected an issue where the OXID field was not loaded in the XRI_ABORTED IOCB.
7. Corrected an issue in recognizing whether an EEPROM is present.
Dependencies: - The corresponding FC Storport device driver and OneCommand Manager Core-kit (management) will need to be installed for this package to function properly.
1. 118933 Fixed an issues booting when more than 8 ports are present in the system and fixed an adapter display issue when more than 8 ports are present in the systems 2. 118933 Fixed issues installing and booting O/Ss on ports greater than 8. 3. 121923 Fixed issues installing and booting O/Ss on ports greater than 8. 4. 122286 Fixed some boot time screen display issues.
(2) OpenBoot version 3.10a3
This version of OpenBoot supports FC-AL, Private loop, Public loop, and Fabric Point to Point. Also, it supports multi-initiators and multi-LUNs (0 through 4055)
Problems fixed, features added or other updates:
1. Unrelated to IBM
(3) EFIBoot version 4.12a12
The current EFI (Extensible Firmware Interface) Boot provides 64-bit System boot capability through the use of the EFI Shell. This EFIBoot supports EFI Specification 1.10 and EFI Source Code version 1.10.14.61.
Problems fixed, features added or other updates:
1. Only certain OEM HBAs will locate PlatformToDriverConfigurationProtocolGuid. Others just skip and continue processing 2. UEFI2.3 Hii Configuration Utility changes 3. HII Browser Save option does not work
1. CR105423 - On a port connected to a 3PAR "MBOD" cage, the test runs IO to the disk drives and issues a "controlport offline" command to offline the port while IO is running.
2. CR111194 - While doing target side cable pull testing with Block Guard (T10) Enabled we observed that adapter is not sending RSCN to AIX.
3. CR111625 - *IBM defect 775960 - HBQ ring index pointers?
5. CR111928 - 3PAR - LR with port and subsequent FLOGI failing.
Dependencies: - The corresponding FC Storport device driver and OneCommand Manager Core-kit (management) will need to be installed for this package to function properly. elx_fw_fc_ibm1206-2_01a9_linux_32-64_chg
ServeRAID M5000 Series SAS/SATA Controller Firmware Update
Version 12.12.0-0133 - Suggested ------------------- Enhancement: - Implemented limited band charging for iBBU08. Fixes: - Addressed an issue where battery over temperature messages could occur during charging. - Fixed issue in the HII broswer where the drive performing copyback will be stated as replacing and not copyback. - Fixed issue in the HII browser where the RPM for SATA drives show "0" - Fixed issue in HII browers where port 4 is shown on both ports 0 and 1 - Fixed HII browser issue where the user will get an error message when a global hot spare is created. - Fix HII browser issue where a RAID volume with greater then 3 spans will fail to create.
Version 12.12.0-0126 - Suggested ------------------- Fixes: - Fixed a issue where the RAID configuration can be lost when updating from firmware package 12.0.1-0097 or below. - Fixed an issue with 4-kilobyte (KB) sector disk support compatibility in NTFS by disabling 512E drive support mode.
Version 12.12.0-0111 - Suggested ------------------- Enhancement: - Implemented limited band charging for iBBU 07.
Fixes: - Set the compatibility bit to 1 so that patrol reads can be executed on SSD's - Fixed an issue where EEPROM init failures are not handled properly causing the user to see the following message on POST "The native configuration is no longer supported by the current controller and firmware." - Fixed an issue where the controller fails to read the header info from CFI Flash ROM. - Resolved issue switching to WT mode for recently failed batteries.
Version 12.12.0-0098 - Suggested ------------------- Fixes: - Fixed issue where the battery gauge is not accurate for aged batteries due to the discharge profiles of aged batteries not matching that of the new batteries. - Fixed a issue where a reboot would cause a hot spare to revert to 'Unconfigured Good' state when Performance Accelerator Key is attached. (RETAIN Tip H204925)
Version 12.12.0-0085 - Suggested ------------------- Enhancements: - Prevent non IBM firmware from being flashed on IBM ServeRAID branded controllers. - Enabled iBBU08 battery modes. - ibbu battery will no longer be marked as bad when very high capacity is detected. - Dimmer Switch function has been disabled by default.
Fixes: - Fixed a issue where firmware was taking to long to complete the PCI config read, causing the system to generate an NMI. - Fixed issue where enabling security causes the configuration to be missing, and a configured FDE array to be seen as foreign on reboot. - Removed BBU mode select from Web BIOS for all controllers. - Fixed issue where pulling VD 0 from a R60 and rebooting would cause two foreign configurations. - Fixed issue where WebBIOS gives unclear message when enabling FDE on an existing Disk Group. - Fixed issue where iBBU07 batteries display 65K capacity and are marked SOH bad. - Fixed issue where iBBU Absolute Charge is displayed differently - Fixed issue where the logical Unit ID (VPD page 0x83) changed after foreign import. - Fixed issue where the LDBBM entries are incorrect after foreign import. - Fixed issue where the controller does not work with pci set to nomsi in kdump kernel. - Fixed issue where the LED behavior is incorrect, wrong drive will blink activity. - Fixed issue where the controller cannot sustain at least 950 MBps performance with Cache Flush setting one sec. - Fixed issue where the set properties command fails - Fixed issue where the iBBU07 battery reported remaining capacity is much too high (64751 mAh) after a learn cycle. - Fixed issue where extended retries of write verify commands cause a driver timeout. - Fixed issue where the configuration becomes foreign after the firmware fails multiple attempts to access raid key during boot. - Fixed firmware issue where a replacement drive is not seen if the replacement is added during power cycle. - Fixed a issue where an alert should be sent when one phy connector between the SAS controller and SAS expander is degraded. - Enabled puncturing for SATA drives. - Enabled copy back on SMART. - Fixed an intermittent RAID key failure during power-on. - Fixed firmware issue where firmware would cause the controller to (sles11sp1/rhel6) reset when ‘lspci –vvx’ command is executed. - Change for iBBU-08 to support firmware Mode5 WB capacity from 960mAh to 674mAh for low power DDR-2 - Fixed a issue where the iBBU battery will not charge while the server continually resets causing the iBBU battery to over-charge.
Version 12.12.0-0065 - Critical ------------------- Fixes: - Fixed issue where the firmware takes too long to complete a PCI Config Read cycle causing SLES11 to kernel panic. - Fixed issue where MegaCLI may not be able to change drive or controller cache setting resulting in a return code of 0x03. - Added check to return SCSI sense Check condition if PMI is set and LBA is non Zero for SCSI Read Cap 16 - Fixed issue where a blue screen occurs handling RAID 1 with HSP and medium errors. The blue screen occurs because the driver times out while the firmware is retrying sense 0x02. Firmware causes Fatal Error when HSP drive responded with Sense 0x02 for Write/Verify or TUR - Change the boot with pinned cache RAID level support which was only allowed for raid level 0. The check is removed and is allowed for any raid level. - Fixed hang condition or condition where the uEFI driver does not load due to the uEFI Driver issuing a command in poll mode to firmware to early - Remove the following message "Battery cannot initiate transparent learn cycles" when the iBBU08 is under mode 4 or 5 - Fixed issue where BGI will not disable when a user issues megacli -LDBI -Dsbl -L0 -a0
Version 12.12.0-0056 - Critical ------------------- Fixes - Fixed issue where multi-bit ECC's are not reported during POST - Lowered the capacity level at which event notifications are generated for early warning and end of life alerts for iBBU to equal 48 hours
Version 12.12.0-0047 - Critical ------------------- Fixes: - Fixed issue where uEFI WebBIOS version may not display the product name of the second controller - Fixed issue to prevent users from downleveling firmware to older versions - Fixed an issue where firmware reports "Unexpected sense, Invalid field in CDB" for LOG SENSE command sent to Seagate drives - Fixed issue where SMART failures can take longer then 5 minutes to report or in some cases fail to report - Fixed issue where it appears to the user the harddrive cache policy is changed when requested but the change did not occur - Fixed issue where a remote iBBU08 will not be seen by the controller - Fixed data issue When IO is in progress to a RAID 1 array that contains media errors and is under a rebuild - Fixed issue where a drive is not marked as foreign during a drive move between servers causing the import of the configuration to fail - Fixed issue where the uEFI WebBIOS does not accept the + symbol in the key code or pass phrase - Fixed issue for iBBU08
Enhancement: - Enhancement to Reserve/release call for VCS Symantec configurations - Enhancements to iBBU event notifications, including the addition of early warning message. - Raised the capacity level at which event notifications are generated for early warning and end of life alerts for iBBUs
Version 12.12.0-0039 - Critical ------------------- Fixes: - Fixed intermittent initialization failure during POST with the ServeRAID M5025, M5015, and M5014 where the RAID BIOS could fail to load or the user will see one of the following error messages on POST:
RAID Adapter Unrecoverable Error!!! Please check the SDRAM connection.
or
Multi-bit ECC errors were detected on the RAID controller
Version 12.12.0-0037 - Critical ------------------- Enhancement: - Add support for iBBU08 (Battery Backup)
Fixes: - Addressed data issue while reconstructing from RAID1 to RAID0. - Addressed data issue after power lose to ServeRAID controllers. - Addressed data issue in some database applications. - Added fixes from LSI channel products.
Version 12.7.0-0020 - Critical ------------------- Enhancement: - Initial release for ServeRAID M5025 SAS/SATA Controller (46M0830)
Fixes: - Addressed data issue with database applications that use overlapping read write operating. - Addressed data issue which may occur during a reconstruction on some RAID levels that have an associated CacheCade virtual drive enabled. - Fixed issue where the controller may halt if a drive has medium errors that are being used in a check consistency, patrol read, or have delayed writes.
Version 12.0.1-0097 - Critical ------------------- Fixes: - Addresses an issue where data becomes inaccessible when drive is secured after data has been written . Version 12.0.1-0096 - Critical ------------------- Fixes: - Fixed an issue where the BBU may not be seen on POST. - Fixed an issue where the firmware doesn't follow the spinupdelay and maxtargetspinup values set in NVDATA causing spin up of all the drives a at the same time. - Fixed a very intermittent issue where the RAID key (M5000) authentication may not occur on boot leaving users without key options. - Addressed a very rare issue with the expander devices where the firmware megamon could occur if the sgpio configuration cable has errors.
Version 12.0.1-0090 - critical ------------------- Fixes: - Fixed issue where controller properties such as Rebuild, CC, and BGI are not changing when up and down arrow keys are used. - Fixed issue on x3950 M3 servers that can cause a system hang at reboot
Version 12.0.1-0084 - Non-critical ------------------- Enhancement: - Support added for the ServeRAID M5000 Series Advanced Feature Key.
Version 12.0.1-0064 ------------------- - Initial release ibm_fw_sraidmr_m5000-12_12_0-0133_linux_32-64_chg
IBM ServeRAID MR10i and MR10is SAS Controller Firmware Update
Adapters Supported: IBM ServeRAID MR10i SAS Controller (43W4296) IBM ServeRAID MR10is SAS Controller (44E8695)
NOTE TO SERVICE - Reference RETAIN #NA
Version 11.0.1-0042 - Critical ------------------- Enhancements: Adjust various battery parameters and alerts to improve product - Reword the battery ‘Prefail‚ and ‘Fail‚ Alerts and all places it is documented - Add visibility of ‘battery nearing end of usable life‚ condition to CLI and MSM - Adjust parameters used to calculate battery capacity amount for Early Warning and EOL alerts
Fixes - Fixed issue where While correcting massive UNC sectors, I/O will be interrupted causing OS becomes unusable - Fixed issue where SPD Data can get Corrupted on Boot causing the following message on boot the message displayed is "Check SDRAM Connection". - Fixed issue where firmware has Incompleted Writes During Power Fail and Recovery causing the following message on boot "Controller cache discarded due to memory/battery problems
Version 11.0.1-0040 - Critical ------------------- Fixes: - Fixed an issue that was contributing to early fallout with battery packs. - Fixed an issue that was causing a loss of battery capacity. - Fixed an issue where the gas gauge was reporting capacity of 65000+mAh and then marking battery as SOH bad. - Fixed issue where multiple reboots were required after a new battery was inserted in a controller. - Fixed issue where T95: VT#00560-T95386=Battery cannot support data retention for more than 59 hours. Please replace the battery. When battery logic generates the event MR_EVT_BBU_REPLACEMENT_NEEDED_SOH_NOT_OPTIMAL, the FW prints the error, T95: EVT#00538-T95: 386=Unknown ARG type=24, code=182.
- Changed post message from
RAID ADAPTER Memory Error !!! Please check the SDRAM connection. If problems persist contact Tech Support. Press Any Key to Continue…
to
Check the SDRAM connection, if applicable, or replace the controller."
Version 11.0.1-0036 - Critical ------------------- Enhancements - BBU AEN enhancements
Fixes: - Fixed issue where firwmare fault could occur when a hot spare drive responds with Sense 0x02 for Write/Verify. - Fixed issue where a firwmare fault could occur when consecutive Medium Errors are found in Degraded SATA RAID5, 6 state
Version 11.0.1-0033 - Critical ------------------- Fixes: - Fixed issue where SATA hard drive write cache could be enabled on a drive insert or system reboot.
Version 11.0.1-0032 - Critical ------------------- Fixes: - Modified memory settings for the ServeRAID MR10k that where not optimal for the controller causing memory failues.
Version 11.0.1-0031 - Critical ------------------- Fixes: - Addressed an issue where a physical drive with an excessive amount of medium errors will cause the array to fail
Version 11.0.1-0030 - Critical ------------------- Fixes: - Leaving array size field blank during array creation to resolve issue where raid level would change but array size did not change with the level. Retain tip H196863. - Fixed issue where the Cursor movement is not proper while entering Security Key/PassPhrase in EFI WebBIOS environment - Fixed issue where the Visibility of webbios version doing controller selection is not there - Address compatabilty issue with uEFI WebBIOS in the x3850 x5 and HS22 x5 - Fixed issue where a fatal FW Error happens during Consistency Check operation while a patrol read is in progress.
Version 11.0.1-0024 - Critical ------------------- NOTE TO SERVICE - H196421, H196426, H196374 Fixes: - Fixed issue with Firmware Hang (Fatal Error) when drive responds with Sense 0x02 for Test Unit Ready Command. - Fixed an issue where the ServeRAID-MR10ie (CIOv) battery fault indicator never clears - Added limit to quantity of consecutive relearn cycles to cache battery unit - Fixed issue where the Pass phrase can not be entered on the ServeRAID MR10is controller - Fixed issue where the user cannot enter the uEFI WebBIOS or system will hang on boot
Version 11.0.1-0022 - Critical ------------------- NOTE TO SERVICE - No current tips Fixes: - Fixed an issue where systems that use DL_DOWN instead of (or in addition to) PCI reset exhibit 1800 PCI ERROR. - Fixed an issue where a non-responsive disk caused fatal firmware error - Fixed an issue with write journaling - Fixed an issue with READ XOR logic in RAID1 special operations
Functionality: - Added support for dynamically toggling readjustment of PCIe maximum read request size
Version 11.0.1-0019 - Critical ------------------- NOTE TO SERVICE - No current tips Fixes: - Addressed an issue in x3550 M2 and x3650 M2 where the slot numbers could change on a cold reboot.
Version 11.0.1-0017 - Suggested ------------------- NOTE TO SERVICE - No current tips Fixes: - Fixed an issue where, on shudown, firmware was not sending a command for the drive to flush its internal cache. - Removed I/O delay during device firmware update for non-disk devices. - Added check for additional error data from mode sense command.
Functionality: - Added pass through command support for applications.
Version 11.0.1-0014 - Critical ------------------- NOTE TO SERVICE - Reference RETAIN #H194939 Fixes: - Addressed an issue where, during I/O and manual copyback on a degraded RAID 6 virtual drive with medium errors, incorrect data could be created on the drive. - Fixed an issue where, on the ServeRAID 10ie (CIOv), a new or changed battery installation was not detected on the iBBU. - Fixed an issue where SATA drives may not be detected at POST when attached to an expander. (Retain tip H194939) - Addressed an issue where the controller may hang if a medium error occurs during a rebuild. - Fixed an issue where cache data could be lost during a reset after the express link is dropped. - Addressed an issue where a consistency check doesn't regenerate parity after hitting a double media error. - Fixed an issue where the uEFI WebBIOS can hang if the user presses the right mouse button when user input is not required. - Addressed an issue where an invalid memory or battery error is reported on boot, but does not reappear on a subsequent boot.
Version 11.0.1-0012 - Suggested ------------------- NOTE TO SERVICE - No current tips Fixes: - Fixed an issue where, rarely, cached data may be lost on system shutdown or reboot.
Version 11.0.1-0008 - Critical ------------------- NOTE TO SERVICE - Reference RETAIN #H194224, H194505, H194171 Fixes: - Fixed an issue which could result in incorrect data on the drives after heavy I/O. (Retain tip H194224) - Fixed an issue where, if medium errors are experienced while a background operation is running, incorrect data could be written to the drives. (Retain tip H194505) - Changed the warning message that appears when the card goes in to temporary write through mode. (Retain tip H194171) - Fixed an error where erroneous Bad Battery messages were displayed even after a Learn Cycle was performed. - Fixed an issue that resulted in SERRs on a ServeRAID-MR10M controller. - Improved the handling of bad cable scenarios which could cause system hangs.
Functionality: - Added support for UEFI based systems. - Added support for Solid State Drives (SSDs). - Added tape support for the ServeRAID 10ie (CIOv) controller. - Added the ability to handle SGPIO and SES signalling on a per-port basis to handle configurations with both direct attached and expander attached drives on a single controller. - Added a field to show hard drive model names in WebBIOS.
Version 9.0.1-0030 - Critical ------------------ Fixes: - Fixed an issue where, if a battery was fully discharged and was reported as 'missing', a reboot was be required before the battery would be detected as 'charging'. - Fixed an issue where a hotspare was reported as unconfirmed good after replacement. - Fixed an issue where an invalid alert 2121 was logged when a virtual drive was created. - Display and log a warning message when a consistency check is started on an uninitialized logical drive. - Fixed an issue where the message "SES enclosure 1 Recovered after fault" would be logged, after which the discovery process would take a very long time. - Fixed an issue where the multipath enclosure IDs were not updated correctly when an ESM or a drive was pulled and reinserted. - Fixed an issue where, if a unconfigured drive was pulled and reinserted, the size of the drive would be reported incorrectly. - Fixed an issue where a dedicated hotspare would become a global hotspare. This could happen after a migration or, in some circumstances, after a system reboot. - Fixed an issue where the firmware could hang when trying to view hotspare information under CTRL-R. - Fixed an issue where a rebuild would not start when a new drive was inserted. - Fixed an issue where a logical drive is still shown as optimal after a drive was pulled. - Fixed a critical firmware error that occurred when a physical drive was pulled from a RAID10 or RAID1E during heavy I/O. - Fixed an issue where a hang could occur when an ESM was removed. - Fixed an issue where, if multiple physical drives are pulled from an enclosure, additional drives might be lost. This could lead to incorrect data on the disks. - Fixed an issue where reconfiguring a virtual disk by adding a drive, or similar activity, will cause a dedicated hotspare to become unassociated. - Fixed an issue where a success code was incorrectly returned when data was sent to a failed drive. This could cause a loss of data. - Fixed an issue where, if additional drives failed in a virtual disk while a rebuild was happening, the system could hang. - Fixed an issue where daisy-chained enclosures would all be reported with the same position number. Also fixed a related issue where 'locate' did not function properly for daisy-chained enclosures. - Fixed an issue where the controller could hang if diagnostics were run while a rebuild was happening. - Fixed an issue where hotspares were lost during configuration import. - Fixed an issue where, if two enclosures were configured and the cable was pulled from each, then reattached in a swapped configuration, the system would hang on boot. - Fixed an issue where successive power cycles in a multi-enclosure configuration could result in offline drives or a system hang. - Fixed an issue where, with the controller mux set to 'Auto', configuration would be lost during reboot. - Fixed an issue where rebuilds might fail to resume after enclosure power is restored. - Corrected several issue where the consistency check was not properly handling double medium errors. - Ensured that BGI (Background Initialization) setting was retained during foreign configuration import. - Fixed an issue which caused MSM to not allow creation of additional virtual disks once 16 virtual disks existed. - Fixed an issue that caused a hang if a rebuild was in progress when a configuration was migrated from an IR to an MR controller. - Fixed an issue where load balancing would not resume properly after a cable pull. - Fixed an issue where, during a target or chip reset, the Disk Write Cache setting on a SATA drive would be reset to default, which is generally 'enabled'. - Fixed an issue where, when BGI is aborted, the status for the CC (consistency check), rather than the status for the BGI, is reported. - Fixed an issue where, if a physical disk fails, causing a logical drive to become degraded, trying to clear or change the configuration would result in a hang until the failed drive was physically removed. - Fixed a hang that was seen when a cable was pulled just before system shutdown. - Ensured that a hotspare would revert back to hotspare state after a rebuild to that hotspare failed. - Fixed several issue that could cause "Illegal Request Sense Data" messages. - Fixed an issue where a rebuild would hang if one of the logical drives on the array was deleted during the rebuild. - Fixed an issue which could result in incorrect data in a scenario where RAID 50 arrays are running in a degraded state for an extended period of time. - Fixed several issues where medium errors could result in offline drives, incorrect data on drives, failed rebuilds, or system hangs. - Fixed an issue where, when a redundant path in a multipath system fails, some drives are marked offline. - Fixed an issue which could cause hangs when replacing a controller with an existing configuration. - Fixed several grammatical and formatting issues. - Fixed an issue where importing foreign configuration under CTRL-R could cause the firmware to crash. - Fixed an issue where an unresponsive SEP could result in a "greater than 122 devices detected" message. - Fixed an issue where the, after a RAID 6 is reconstructed as a RAID 5, the configuration is reported incorrectly upon reboot. - Fixed an issue which could result in incorrect data on the drives when I/O is run while a capacity expansion is in progress. - Fixed an issue that could cause a hang when an enclosure is power cycled while I/O is running. - Fixed an issue where, if a physical drive became invalid during a rebuild to that drive, the rebuild would pause, rather than fail. - Fixed an issue where Battery Warning messages would appear, even when disabled. - Fixed an issue which resulted in "Unexpected sense" messages in the log with SATA drives. - Fixed an issue where Cache Data could be lost during a power failure. - Fixed an issue where not all SATA drives were found during discovery. - Fixed an issue which may result in a firmware hang during a reconstruction operation. - Fixed an issue where the firmware would continue to try to communicate with a bad drive. The symptom of this issue is a drive where the status light is blinking amber and the activity light is solid green. - Fixed an issue where an enclosure reboot could, very rarely, cause a condition where the driver sends a Kill Adapter signal. - Fixed an issue where, if a medium error is encountered on a source drive during a rebuild, the bad block may not get marked as bad. - Fixed an issue where running in degraded mode with medium errors could cause the firmware to hang. - Fixed an issue where running heavy I/O on daisy-chained enclosures for an extended period of time could cause a hang. - Fixed an issue where, with some hardware, the configuration is not found within the timeout time on a cold reboot. This leads to a prompt to import configuration, after which, the configuration is seen correctly. - Fixed an issue with I2C LED support. - Fixed an issue where the write cache policy would unexpectedly change from write back to write through, then would change back after about a minute. - Fixed an issue where, if a cable is pulled in a multipath environment, the alternate path is sometimes not followed. - Fixed an error in the ECC error logging which can cause a memory leakage. - Fixed an issue where the firmware will hang if discovery does not complete in two minutes. - Fixed an issue where full initialization of a large number of SATA drives would cause timeouts. - Fixed several LED issues with I2C backplanes. - Fixed an issue sensing dual I2C backplanes in a multipath environment.
Functionality: - Added support for 64 virtual disks per array. - Added support for expanded RAID 1, a form of RAID 1E which supports even numbers of drives. - Added the ability to hot-swap a battery. - Added the ability to manually initiate the battery learn cycle. - Added multipathing support for SATA drives. - Added the ability to enable or disable NCQ from the CLI or WebBIOS. - Added the copyback feature, which is used when a drive goes defunct and the array rebuilds to a hotspare. Copyback allows the hotspare to rebuild to a new drive that is inserted to replace the defunct drive. - Clarified several log event messages. - Implemented load balancing when multipath SAS is used. - Added logging for some events that were not previously logged. - Increased the PHY count from 512 to 640 to support 21 enclosures.
Version 8.0.1-0036 - Non-critical ------------------ Fixes: - Address issue where SATA drives attached to an expander will not respond in a specific time period causing the drives to be seen as foreign. - Add support for the IBM ServeRAID 10il SAS/SATA adapter.
Version 8.0.1-0033 - Suggested ------------------ Fixes: - Fixed issue where current write policy is not changed to write back even if iBBU completes the charging in 1078 HWR. - Fixed an issue where the firmware reports "MonTask: line 3566 in file ../../raid/1078dma.c" while running reconstruction on a degraded logical drive and injecting media errors. - Fixed an issue where a controller would hang during a reboot. - Fix is done to invalidate the parity cache for the punctured block before releasing the cache line - Fix for WebBIOS hangs with greater then 5 MegaRAID adapters installed.
Version 8.0.1-0029 - Critical ------------------ Fixes: - Fixed an issue where, while performing I/O during a RAID level migration or an array capacity expansion, incorrect data may be passed during a data transfer.
Version 8.0.1-0027 - Critical ------------------ Fixes: - Implemented changes to ensure the firmware does not violate the DDR2 spec during the initialization sequence in a 1078 ROMB environment. - Fixed an issue where the controller enters MegaMon when a rebuilding span is removed. - Fixed an issue where the operating system may crash after an S3 resume followed by a manual restart. - Fixed an issue where a bad SAS cable, connected between two enclosures, could cause the firmware on the associated controller to crash. - Fixed a chip reset that could happen during boot sequence of RHEL 5 64-bit. - Fixed an issue where WebBIOS does not initially see external devices, and, if RAID is configured, the “missing config” prompt is shown in the BIOS. This was caused by the firmware not waiting for the second discovery attempt that is necessary to find external devices. - Fixed an issue where, on a 1078 chip, firmware was not properly marking a drive dead. Consequently, a write to that drive would appear to complete successfully, but would actually fail, therefore the data could be incorrect. - Fixed an issue where, under heavy load, with write back enabled, the following error was seen: "ERROR: Stale read check failure. Page image returned does not match previous write. Check hardware and caches. Read size was 16384" - Fixed an issue where import of foreign drive configuration would fail. - Fixed an issue where firmware could crash when a large number of hard drives is connected to a ServeRAID MR10M. - Fixed an issue where multiple reboots of cascading enclosures could result in incorrect data. - Fixed an issue where the Global Hard Drive Summary LED was not working. - Disallowed the addition of logical drives in an array that is being rebuilt. This fixes an issue where a newly created logical drive on a rebuilding array would be deleted on reboot. - Fixed an issue where the drive sizes were shown incorrectly after drive migration in an array with two or more different sized drives. - Fixed an issue where the source drive in a rebuild would be failed after several ECC errors.
Functionality: - Implemented Slot ID mapping support in a mixed topology. - Implemented a performance enhancement for sequential read workloads. - Reenabled offline hard drive firmware flash. Now hard drive firmware can be flashed in either an online or an offline state. - Implemented a new event so that dirty cache will be discarded on a virtual drive that is missing or offline.
Version 8.0.1-0021 ------------------ - Initial release ibm_fw_sraidmr_10i-10is-11_0_1-0042_linux_32-64_chg
BIOS/FW/UEFI Update for ServeRAID H1110 SAS/SATA Controller for IBM System x
Controller Supported: ServeRAID H1110 SAS/SATA Controller for IBM System x (81Y4492)
Fixes: - Fixed issue where HII do not report Multi-LUN devices from external RAID enclosure. - Do not show external RAID LUNs in HII RAID configuration page. - Report NVDATA version consistently in Hex or Decimal. - Fixed issue where update will not install with the 09.101 megaraid_sas device driver.
Note: HII changes may not affect all controllers. Changes for the controller are based on RAID volume support. - HII fix to return EFI_SUCCESS when RETRIEVE Action is given in HII Callback function. - HII fix for Write cache disabling fails for SATA HDD/SSD connected to the IT controller. - HII fix for saved Controller Events Filename. - Behvioral change for the way a volume is created in HII.
Note: The following fixes only effect blade systems that support Bofm. - Fixed boot issues in Windows 2008 where after installation in uEFI the os will not boot due to the BuildDevicePath not allocating enough memory for the DevicePathreturned to caller. - Fixed issue with Bofm configurations where the BOFM supplied addresses for external/switch attach Phys are being assigned to the internal/direct attach Phys. - Fixed a Bofm issue where the SAS WWIDs not reverting to Man Page 5 Default when a Blade is moved back to non-BOFM slot.
Note: HII changes may not affect all controllers. Changes for the controller are based on RAID volume support.
- HII change to Remove Legacy BIOS Enable/Disable option. - Fixed issue where after creating a volume using SATA SSD the Associated Physical Disks always show up as SATA HDD. - Fixed issue where a hotspare could not be created for any volume in the HII browser. - HII fix for the View Physical Disk Properties form where the Serial number of SATA disks were being displaced with a space. - HII fix for the IR help strings displayed when using an IT controller. - Fixed HII issue where a 'Question value mismatch with Option value' error occurs when saying No for creating RAID10/RAID1E volume. - Fixed HII issue where help is not available when having only RAID0 and RAID1 levels in Create Configuration form. - Fixed a problem where the UEFI driver ATA PassThru Protocol is corrupt while trying to access the Mode field. - HII behavior change for 'Manage Foreign Configurations.' - HII change to provide proper extended RAID Levels in help messages based on supported extended RAID Levels.
IBM ServeRAID MR10M SAS Controller Firmware Update
Adapters Supported: IBM ServeRAID MR10M SAS Controller (43W4339)
NOTE TO SERVICE - Reference RETAIN #NA
Version 11.0.1-0042 - Critical ------------------- Enhancements: Adjust various battery parameters and alerts to improve product - Reword the battery ‘Prefail‚ and ‘Fail‚ Alerts and all places it is documented - Add visibility of ‘battery nearing end of usable life‚ condition to CLI and MSM - Adjust parameters used to calculate battery capacity amount for Early Warning and EOL alerts
Fixes - Fixed issue where While correcting massive UNC sectors, I/O will be interrupted causing OS becomes unusable - Fixed issue where SPD Data can get Corrupted on Boot causing the following message on boot the message displayed is "Check SDRAM Connection". - Fixed issue where firmware has Incompleted Writes During Power Fail and Recovery causing the following message on boot "Controller cache discarded due to memory/battery problems
Version 11.0.1-0040 - Critical ------------------- Fixes: - Fixed an issue that was contributing to early fallout with battery packs. - Fixed an issue that was causing a loss of battery capacity. - Fixed an issue where the gas gauge was reporting capacity of 65000+mAh and then marking battery as SOH bad. - Fixed issue where multiple reboots were required after a new battery was inserted in a controller. - Fixed issue where T95: VT#00560-T95386=Battery cannot support data retention for more than 59 hours. Please replace the battery. When battery logic generates the event MR_EVT_BBU_REPLACEMENT_NEEDED_SOH_NOT_OPTIMAL, the FW prints the error, T95: EVT#00538-T95: 386=Unknown ARG type=24, code=182.
- Changed post message from
RAID ADAPTER Memory Error !!! Please check the SDRAM connection. If problems persist contact Tech Support. Press Any Key to Continue…
to
Check the SDRAM connection, if applicable, or replace the controller."
Version 11.0.1-0036 - Critical ------------------- Enhancements - BBU AEN enhancements
Fixes: - Fixed issue where firwmare fault could occur when a hot spare drive responds with Sense 0x02 for Write/Verify. - Fixed issue where a firwmare fault could occur when consecutive Medium Errors are found in Degraded SATA RAID5, 6 state
Version 11.0.1-0033 - Critical ------------------- Fixes: - Fixed issue where SATA hard drive write cache could be enabled on a drive insert or system reboot.
Version 11.0.1-0032 - Critical ------------------- Fixes: - Modified memory settings for the ServeRAID MR10k that where not optimal for the controller causing memory failues.
Version 11.0.1-0031 - Critical ------------------- Fixes: - Addressed an issue where a physical drive with an excessive amount of medium errors will cause the array to fail
Version 11.0.1-0030 - Critical ------------------- Fixes: - Leaving array size field blank during array creation to resolve issue where raid level would change but array size did not change with the level. Retain tip H196863. - Fixed issue where the Cursor movement is not proper while entering Security Key/PassPhrase in EFI WebBIOS environment - Fixed issue where the Visibility of webbios version doing controller selection is not there - Address compatabilty issue with uEFI WebBIOS in the x3850 x5 and HS22 x5 - Fixed issue where a fatal FW Error happens during Consistency Check operation while a patrol read is in progress.
Version 11.0.1-0024 - Critical ------------------- NOTE TO SERVICE - H196421, H196426, H196374 Fixes: - Fixed issue with Firmware Hang (Fatal Error) when drive responds with Sense 0x02 for Test Unit Ready Command. - Fixed an issue where the ServeRAID-MR10ie (CIOv) battery fault indicator never clears - Added limit to quantity of consecutive relearn cycles to cache battery unit - Fixed issue where the Pass phrase can not be entered on the ServeRAID MR10is controller - Fixed issue where the user cannot enter the uEFI WebBIOS or system will hang on boot
Version 11.0.1-0022 - Critical ------------------- NOTE TO SERVICE - No current tips Fixes: - Fixed an issue where systems that use DL_DOWN instead of (or in addition to) PCI reset exhibit 1800 PCI ERROR. - Fixed an issue where a non-responsive disk caused fatal firmware error - Fixed an issue with write journaling - Fixed an issue with READ XOR logic in RAID1 special operations
Functionality: - Added support for dynamically toggling readjustment of PCIe maximum read request size
Version 11.0.1-0017 - Suggested ------------------- NOTE TO SERVICE - No current tips Fixes: - Fixed an issue where, on shudown, firmware was not sending a command for the drive to flush its internal cache. - Removed I/O delay during device firmware update for non-disk devices. - Added check for additional error data from mode sense command.
Functionality: - Added pass through command support for applications.
Version 11.0.1-0014 - Critical ------------------- NOTE TO SERVICE - Reference RETAIN #H194939 Fixes: - Addressed an issue where, during I/O and manual copyback on a degraded RAID 6 virtual drive with medium errors, incorrect data could be created on the drive. - Fixed an issue where, on the ServeRAID 10ie (CIOv), a new or changed battery installation was not detected on the iBBU. - Fixed an issue where SATA drives may not be detected at POST when attached to an expander. (Retain tip H194939) - Addressed an issue where the controller may hang if a medium error occurs during a rebuild. - Fixed an issue where cache data could be lost during a reset after the express link is dropped. - Addressed an issue where a consistency check doesn't regenerate parity after hitting a double media error. - Fixed an issue where the uEFI WebBIOS can hang if the user presses the right mouse button when user input is not required. - Addressed an issue where an invalid memory or battery error is reported on boot, but does not reappear on a subsequent boot.
Version 11.0.1-0012 - Suggested ------------------- NOTE TO SERVICE - No current tips Fixes: - Fixed an issue where, rarely, cached data may be lost on system shutdown or reboot.
Version 11.0.1-0008 - Critical ------------------- NOTE TO SERVICE - Reference RETAIN #H194224, H194505, H194171 Fixes: - Fixed an issue which could result in incorrect data on the drives after heavy I/O. (Retain tip H194224) - Fixed an issue where, if medium errors are experienced while a background operation is running, incorrect data could be written to the drives. (Retain tip H194505) - Changed the warning message that appears when the card goes in to temporary write through mode. (Retain tip H194171) - Fixed an error where erroneous Bad Battery messages were displayed even after a Learn Cycle was performed. - Fixed an issue that resulted in SERRs on a ServeRAID-MR10M controller. - Improved the handling of bad cable scenarios which could cause system hangs.
Functionality: - Added support for UEFI based systems. - Added support for Solid State Drives (SSDs). - Added tape support for the ServeRAID 10ie (CIOv) controller. - Added the ability to handle SGPIO and SES signalling on a per-port basis to handle configurations with both direct attached and expander attached drives on a single controller. - Added a field to show hard drive model names in WebBIOS.
Version 9.0.1-0030 - Critical ------------------ Fixes: - Fixed an issue where, if a battery was fully discharged and was reported as 'missing', a reboot was be required before the battery would be detected as 'charging'. - Fixed an issue where a hotspare was reported as unconfirmed good after replacement. - Fixed an issue where an invalid alert 2121 was logged when a virtual drive was created. - Display and log a warning message when a consistency check is started on an uninitialized logical drive. - Fixed an issue where the message "SES enclosure 1 Recovered after fault" would be logged, after which the discovery process would take a very long time. - Fixed an issue where the multipath enclosure IDs were not updated correctly when an ESM or a drive was pulled and reinserted. - Fixed an issue where, if a unconfigured drive was pulled and reinserted, the size of the drive would be reported incorrectly. - Fixed an issue where a dedicated hotspare would become a global hotspare. This could happen after a migration or, in some circumstances, after a system reboot. - Fixed an issue where the firmware could hang when trying to view hotspare information under CTRL-R. - Fixed an issue where a rebuild would not start when a new drive was inserted. - Fixed an issue where a logical drive is still shown as optimal after a drive was pulled. - Fixed a critical firmware error that occurred when a physical drive was pulled from a RAID10 or RAID1E during heavy I/O. - Fixed an issue where a hang could occur when an ESM was removed. - Fixed an issue where, if multiple physical drives are pulled from an enclosure, additional drives might be lost. This could lead to incorrect data on the disks. - Fixed an issue where reconfiguring a virtual disk by adding a drive, or similar activity, will cause a dedicated hotspare to become unassociated. - Fixed an issue where a success code was incorrectly returned when data was sent to a failed drive. This could cause a loss of data. - Fixed an issue where, if additional drives failed in a virtual disk while a rebuild was happening, the system could hang. - Fixed an issue where daisy-chained enclosures would all be reported with the same position number. Also fixed a related issue where 'locate' did not function properly for daisy-chained enclosures. - Fixed an issue where the controller could hang if diagnostics were run while a rebuild was happening. - Fixed an issue where hotspares were lost during configuration import. - Fixed an issue where, if two enclosures were configured and the cable was pulled from each, then reattached in a swapped configuration, the system would hang on boot. - Fixed an issue where successive power cycles in a multi-enclosure configuration could result in offline drives or a system hang. - Fixed an issue where, with the controller mux set to 'Auto', configuration would be lost during reboot. - Fixed an issue where rebuilds might fail to resume after enclosure power is restored. - Corrected several issue where the consistency check was not properly handling double medium errors. - Ensured that BGI (Background Initialization) setting was retained during foreign configuration import. - Fixed an issue which caused MSM to not allow creation of additional virtual disks once 16 virtual disks existed. - Fixed an issue that caused a hang if a rebuild was in progress when a configuration was migrated from an IR to an MR controller. - Fixed an issue where load balancing would not resume properly after a cable pull. - Fixed an issue where, during a target or chip reset, the Disk Write Cache setting on a SATA drive would be reset to default, which is generally 'enabled'. - Fixed an issue where, when BGI is aborted, the status for the CC (consistency check), rather than the status for the BGI, is reported. - Fixed an issue where, if a physical disk fails, causing a logical drive to become degraded, trying to clear or change the configuration would result in a hang until the failed drive was physically removed. - Fixed a hang that was seen when a cable was pulled just before system shutdown. - Ensured that a hotspare would revert back to hotspare state after a rebuild to that hotspare failed. - Fixed several issue that could cause "Illegal Request Sense Data" messages. - Fixed an issue where a rebuild would hang if one of the logical drives on the array was deleted during the rebuild. - Fixed an issue which could result in incorrect data in a scenario where RAID 50 arrays are running in a degraded state for an extended period of time. - Fixed several issues where medium errors could result in offline drives, incorrect data on drives, failed rebuilds, or system hangs. - Fixed an issue where, when a redundant path in a multipath system fails, some drives are marked offline. - Fixed an issue which could cause hangs when replacing a controller with an existing configuration. - Fixed several grammatical and formatting issues. - Fixed an issue where importing foreign configuration under CTRL-R could cause the firmware to crash. - Fixed an issue where an unresponsive SEP could result in a "greater than 122 devices detected" message. - Fixed an issue where the, after a RAID 6 is reconstructed as a RAID 5, the configuration is reported incorrectly upon reboot. - Fixed an issue which could result in incorrect data on the drives when I/O is run while a capacity expansion is in progress. - Fixed an issue that could cause a hang when an enclosure is power cycled while I/O is running. - Fixed an issue where, if a physical drive became invalid during a rebuild to that drive, the rebuild would pause, rather than fail. - Fixed an issue where Battery Warning messages would appear, even when disabled. - Fixed an issue which resulted in "Unexpected sense" messages in the log with SATA drives. - Fixed an issue where Cache Data could be lost during a power failure. - Fixed an issue where not all SATA drives were found during discovery. - Fixed an issue which may result in a firmware hang during a reconstruction operation. - Fixed an issue where the firmware would continue to try to communicate with a bad drive. The symptom of this issue is a drive where the status light is blinking amber and the activity light is solid green. - Fixed an issue where an enclosure reboot could, very rarely, cause a condition where the driver sends a Kill Adapter signal. - Fixed an issue where, if a medium error is encountered on a source drive during a rebuild, the bad block may not get marked as bad. - Fixed an issue where running in degraded mode with medium errors could cause the firmware to hang. - Fixed an issue where running heavy I/O on daisy-chained enclosures for an extended period of time could cause a hang. - Fixed an issue where, with some hardware, the configuration is not found within the timeout time on a cold reboot. This leads to a prompt to import configuration, after which, the configuration is seen correctly. - Fixed an issue with I2C LED support. - Fixed an issue where the write cache policy would unexpectedly change from write back to write through, then would change back after about a minute. - Fixed an issue where, if a cable is pulled in a multipath environment, the alternate path is sometimes not followed. - Fixed an error in the ECC error logging which can cause a memory leakage. - Fixed an issue where the firmware will hang if discovery does not complete in two minutes. - Fixed an issue where full initialization of a large number of SATA drives would cause timeouts. - Fixed several LED issues with I2C backplanes. - Fixed an issue sensing dual I2C backplanes in a multipath environment.
Functionality: - Added support for 64 virtual disks per array. - Added support for expanded RAID 1, a form of RAID 1E which supports even numbers of drives. - Added the ability to hot-swap a battery. - Added the ability to manually initiate the battery learn cycle. - Added multipathing support for SATA drives. - Added the ability to enable or disable NCQ from the CLI or WebBIOS. - Added the copyback feature, which is used when a drive goes defunct and the array rebuilds to a hotspare. Copyback allows the hotspare to rebuild to a new drive that is inserted to replace the defunct drive. - Clarified several log event messages. - Implemented load balancing when multipath SAS is used. - Added logging for some events that were not previously logged. - Increased the PHY count from 512 to 640 to support 21 enclosures.
Version 8.0.1-0036 - Non-critical ------------------ Fixes: - Address issue where SATA drives attached to an expander will not respond in a specific time period causing the drives to be seen as foreign. - Add support for the IBM ServeRAID 10il SAS/SATA adapter.
Version 8.0.1-0033 - Suggested ------------------ Fixes: - Fixed issue where current write policy is not changed to write back even if iBBU completes the charging in 1078 HWR. - Fixed an issue where the firmware reports "MonTask: line 3566 in file ../../raid/1078dma.c" while running reconstruction on a degraded logical drive and injecting media errors. - Fixed an issue where a controller would hang during a reboot. - Fix is done to invalidate the parity cache for the punctured block before releasing the cache line - Fix for WebBIOS hangs with greater then 5 MegaRAID adapters installed.
Version 8.0.1-0029 - Critical ------------------ Fixes: - Fixed an issue where, while performing I/O during a RAID level migration or an array capacity expansion, incorrect data may be passed during a data transfer.
Version 8.0.1-0027 - Critical ------------------ Fixes: - Implemented changes to ensure the firmware does not violate the DDR2 spec during the initialization sequence in a 1078 ROMB environment. - Fixed an issue where the controller enters MegaMon when a rebuilding span is removed. - Fixed an issue where the operating system may crash after an S3 resume followed by a manual restart. - Fixed an issue where a bad SAS cable, connected between two enclosures, could cause the firmware on the associated controller to crash. - Fixed a chip reset that could happen during boot sequence of RHEL 5 64-bit. - Fixed an issue where WebBIOS does not initially see external devices, and, if RAID is configured, the “missing config” prompt is shown in the BIOS. This was caused by the firmware not waiting for the second discovery attempt that is necessary to find external devices. - Fixed an issue where, on a 1078 chip, firmware was not properly marking a drive dead. Consequently, a write to that drive would appear to complete successfully, but would actually fail, therefore the data could be incorrect. - Fixed an issue where, under heavy load, with write back enabled, the following error was seen: "ERROR: Stale read check failure. Page image returned does not match previous write. Check hardware and caches. Read size was 16384" - Fixed an issue where import of foreign drive configuration would fail. - Fixed an issue where firmware could crash when a large number of hard drives is connected to a ServeRAID MR10M. - Fixed an issue where multiple reboots of cascading enclosures could result in incorrect data. - Fixed an issue where the Global Hard Drive Summary LED was not working. - Disallowed the addition of logical drives in an array that is being rebuilt. This fixes an issue where a newly created logical drive on a rebuilding array would be deleted on reboot. - Fixed an issue where the drive sizes were shown incorrectly after drive migration in an array with two or more different sized drives. - Fixed an issue where the source drive in a rebuild would be failed after several ECC errors.
Functionality: - Implemented Slot ID mapping support in a mixed topology. - Implemented a performance enhancement for sequential read workloads. - Reenabled offline hard drive firmware flash. Now hard drive firmware can be flashed in either an online or an offline state. - Implemented a new event so that dirty cache will be discarded on a virtual drive that is missing or offline.
Version 8.0.1-0021 ------------------ - Initial release ibm_fw_sraidmr_10m-11_0_1-0042_linux_32-64_chg
Dynamic System Analysis (DSA) Preboot Change History
Version 9.32, Build ID DSYTA9C o New System Support: o New Operating System support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: Refer to readme o Functional change: o Dependencies: o Special usage: - IMMv1 & IMMv2 system 2013 R1 LFC
Version 9.27, Build ID DSYTA7 o New System Support: o New Operating System support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: Refer to readme o Functional change: o Dependencies: o Special usage: - IMMv1 system 2012 4Q-LFC
Version 9.26, Build ID DSYTA6G o New System Support: o New Operating System support: o New server options support: o Problem(s) Fixed: o Enhancement: DSA Performance Optimization o Limitations: Refer to readme o Functional change: o Dependencies: o Special usage: - 2012 ToolsCenter 12C
Version 9.21, Build ID DSYTA1U o New System Support: o New Operating System support: o New server options support: o Problem(s) Fixed: 1.Recovered LSI Rawdata: "MegaCli -FwTermLog -Dsply -aALL" o Enhancement: o Limitations: Refer to readme o Functional change: o Dependencies: o Special usage: - 2012 ToolsCenter 12B Plus
Version 9.20, Build ID DSYTA0R o New System Support: x3530 M4 (7160) x3630 M4 (7158) x3750 M4 (8722, 8733) HS23E (8038, 8039) Flex System x220 Compute Node (7906, 2585) o New Operating System support: vSphere Hypervisor 5.0u1 with IBM customization o New server options support: o Problem(s) Fixed: 1. PMR 05819,YL2,760 An error occured during the execution of DSA on Windows, DSA exits with an error at the eventlog plugin.
o Enhancement: o Limitations: Refer to readme o Functional change: 1. Add HW remote presence key collection for High volume systems. o Dependencies: o Special usage: - 2012 ToolsCenter 12B
Version 9.07, Build ID DSYT9CA o New System Support: x3750 M4 (8722, 8733) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 9.06, Build ID DSYT9BC o New System Support: Flex System x220 Compute Node (7906) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 9.05, Build ID DSYT9AA o New System Support: x3630 M4 (7158) x3530 M4 (7160) x3100 M4 Refresh1 (2582) x3250 M4 Refresh1 (2583) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 9.04, Build ID DSYT99E o New System Support: Flex System x240 Compute Node (8737, 8738, 7863) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies:
Version 9.03, Build ID DSYT98I o New System Support: HS23E (8038, 8039) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies:
Version 9.02, Build ID DSYT97C o New System Support: iDataPlex dx360 M4 server/2U chassis (7912/7913) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Functional change:
Version 9.01, Build ID DSYT96D o New System Support: x3500 M4 (7383) x3550 M4 (7914) x3650 M4 (7915) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage: o Special usage:
Version 9.00, Build ID DSYT95W o New System Support: BladeCenter HS23 (7875) BladeCenter HX5 (7873, 1910) Flex System x240 Compute Node (8737, 8738, 7863) Flex System Manager Node (8735) x3500 M4 (7383) x3550 M4 (7914) x3630 M4 (7158) x3650 M4 (7915) x3690 X5 (7192, 7147) x3850 X5 / x3950 X5 (7143, 7191) o New server options support: o Problem(s) Fixed: 1. PMR 24817,8QG,000, PMR 30680,499,000 After kicking off DSA on one of the management nodes (x3650 M2) of SONAS 1.2(RHEL5 based), the node became unresponsive and dropped out of the cluster.
2. PMR 53575,000,834, PMR 05961,YL4,760 After running DSA, when using linux dump command on a DDS5 usb internal tape drive attached in x3650M2 backup speed becomes very slowly or failed.
3. PMR 26905,095,866 Running DSA 4.0 as well as DSA 3.4 on x3850 X5 the server is freezing, users have to reboot the server.
4. DSA 4.00 and previous version segmentation fault issue
6. PMR 15086,OTH,760 DSA 9.00 with --no-imm-lan option does not work correctly on RHEL5.3. The USB port state is changed during the execution of DSA.
o Enhancement: o Limitations: o Dependencies: o Functional change: 1. Add GUI and CLI menu for Features on Demand (FoD) Activation Key Management o Special usage:
Version 4.02, Build ID DSYT92I o New System Support: iDataPlex Direct Water Cooled dx360 M4 server o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 4.01, Build ID DSYT92H o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage: - 2011 4Q lifecycle
Version 4.00, Build ID DSYT91S o New System Support: o New server options support: o Problem(s) Fixed: 1. PMR 15065,OTR,760 On Unisys ES7000 or x3850 X5, the Memory Card number with failed DIMM can not be reported in IPMI Eventlog if the Memory Card is bigger than 4.
o Enhancement: o Limitations: o Dependencies: o Functional change: 1. Added > 1TB memory test support o Special usage: - 2011 ToolsCenter 11D
Version 3.48, Build ID DSYT89PUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage: - 2011 3Q lifecycle
Version 3.47, Build ID DSYT89LUS o New System Support: x3100 M4 (2582) x3250 M4 (2583) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 3.46, Build ID DSYT89GUS o New System Support: System x iDataPlex dx360 M3 (6391) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 3.45, Build ID DSYT89EUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage: - x3850 X5 / x3950 X5 (7143, 7191) EXA scaling
Version 3.43, Build ID DSYT87HUS o New System Support: BladeCenter HX5 (7873,1910) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 3.43, Build ID DSYT87FUS o New System Support: x3850 X5 / x3950 X5 (7143, 7191) x3690 X5 (7192, 7147) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 3.40, Build ID DSYT85T o New System Support: BladeCenter HS22 (1911) x3650 M3 (5454) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 3.30, Build ID DSYT80S o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: 1. Correct a problem with LSI MegaRAID reporting for IBM Service o Special usage:
Version 3.20, Build ID DSYT75X o New System Support: x3630 M3 (7377) x3690 X5 (7148, 7149) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: - If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831 installed, you will need one of the following: - uEFI GYE133A or greater for x3200 M3 and x3250 M3 - uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3 - uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3 o Functional change: 1. Add LSI Hard Disk Drive (HDD) diagnostic back for both the onboard SAS chip and ServeRAID o Special usage:
Verion 3.20, Build ID DSYT75U o New System Support: x3755 M3 (7164) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Verion 3.10, Build ID DSYT70X o New System Support: x3400 M3(7378, 7379) x3500 M3(7380) x3550 M3 (7944, 4254) x3620 M3 (7376) x3650 M3 (7945, 4255) x3690 X5 (7148, 7149) x3850 X5 Standard Single-node and Multi-node models(7145, 7146) x3950 X5 Specially configured Database Engine models (7145, 7146) iDataplex dx360 M3 (6391) HS22V (7871,1949) HX5 (7872, 1909) o New server options support: Emulex 10Gb/s Fibre Channel over Ethernet Dual Channel Converged Network Adapter(LP21002) Emulex PCI-e Gen2.0 Dual Port 10Gb NIC (49Y4250) 6Gb SSD HBA (46M0912) 6Gb SAS HBA (46M0907) Intel QuadPort Ethernet Server Adapter CFFh Intel Ethernet Daughter Card FCoE SRIOV Key (Ethernet) iSCSI Key (Ethernet) Secure Encryption HBA for 8Gb FC eHBA Emulex Brocade 4Gb FC HBA(59Y1992, 59Y1998) Emulex 2-Port 10Gb Multi-function IO Adapter (CFFh) (49Y4235) Brocade 10Gb Dual-port CNA (42C1820) Broadcom NetXtreme II 1000 Express Quad port Ethernet Adapter (49Y4220) Broadcom NetXtreme II 1000 Express Dual Port Ethernet Adapter (42C1780) MAX5 Memory Expansion Unit o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: 1. Add a new option --disable-imm-lan to take down IMM USB Over Lan interface when DSA complete. 2. Added ServeRAID data collection o Limitations: - The following function has been temporarily removed from DSA Preboot for both the onboard SAS chip and ServeRAID: - LSI Hard Disk Drive (HDD) diagnostic o Dependencies: - If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831 installed, you will need one of the following: - uEFI GYE133A or greater for x3200 M3 and x3250 M3 - uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3 - uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3 o Special usage:
Version 3.02.56, Build ID DSYT56e o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - The following systems are supported when BoMC downloads the corresponding system enablement pack: HS22V (7871,1949) x3550 M3 (7944,4254) x3650 M3 (7945,4255) x3400 M3 (7378,7379) x3500 M3 (7839) dx360 M3 (6391) o Limitations: - No HDD diagnostics available - To ensure quality and stability of the DSA code, we have reverted some display functionality of RAID information to what was shown in previous versions of DSA. This affects RAID display on the following adapters: Megaraid 8480 Serveraid MR10i Serveraid MR10is Serveraid MR10m Serveraid MR10k Serveraid M1015 Serveraid M5014 Serveraid M5015 On these adapters, the RAID information is generated from the output of separate command line tools and the format may not match other output in DSA. Dependencies: o Dependencies: o Functional change: o Special usage:
Version 3.00, Build ID: DSYT55a o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - Added support for Machine Types 7327, 7328, 4251, 4252, 4261 o Limitations: - No HDD diagnostics available o Dependencies: o Functional change: o Special usage:
Version 1.16, Y4YT19AUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - Added support for Machine Types 7839, 7836, 7837 o Limitations: o Dependencies: o Functional change: o Special usage:
Version 1.15, TMYT20AUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - Added support for Machine Types 7321, 6380, 7323 o Limitations: o Dependencies: o Functional change: o Special usage:
Version 1.14, D6YT37AUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - Added support for Machine Types 7946, 4198, 7947, 4199 o Limitations: o Dependencies: o Functional change: o Special usage:
Version 1.13, P9YT48AUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - Added support for Machine Types 7870, 1936, 7809 o Limitations: o Dependencies: o Functional change: o Special usage:
Version 1.00 - Initial release
(C) Copyright International Business Machines Corporation 2008 - 2012. All rights reserved. ibm_fw_dsa_dsyta9c-9_32_anyos_anycpu_chg
=============================================== Change History =============================================== Document Name: Change History Document Status: IBM General Avalibility Document Version: 3.2 Latest Driver Version: 3.2.0.0 Document Updated: 12/18/2012 Product: Brocade FC HBA / FCoE CNA
=================================================
Please visit www.brocade.com/hba for full documentation, additional drivers, and management applications.
Version 3.2.0.0 New Features and Feature Enhancement: - For Brocade 8x5/4x5, I/O interrupt latency values are dynamically updated. Changes are effective for all the ports on the given adapter. - Addressed infrequent PSOD in VMware ESX with iSCSI or VLAN configured traffic in DCB enabled network. - Enhanced BR1860 Tape IO performance. - Improved BR1860 initialization on Xen kernel.
Fixes and Enhancements: - BB Credit Recovery - Forward Error Correction (FEC) - Diagnostic Port (D-Port) - LUN Level IO Latency/Stats - UCM (Unified Configuration Manager) - Windows Network Performance and scalability enhancement
Version 3.1.0.0 Key features and enhancements supported for the software release 3.1.0.0 include the following:
New Features: - D-port support between Brocade 16Gb HBAs and Brocade 16Gb FC switch platforms with FOS v7.0.1 and later releases - FC-AL support for direct attach to storage - Ability to assign minimum bandwidth to each vNIC - Queue Depth adjustment - FC QoS set by percentage - Performance enhancements in Ethernet drivers - Technology Preview support of 1860 HBA on Power PC architecture
Fixes or Enhancements: - Resolved an issue where HCM Agent may not start if BR1860 adapter is configured in NIC mode. - Improved stability with Hyper-V and Teaming configurations. - Resolved I/O errors when running traffic with Brocade HBAs(models 415, 425, 815, 825, and 804), if the server’s PCI max read request size is configured to be 2K or greater with PCI Gen2x8.
Version 3.0.0.0 Fixes and Enhancements: - Added support for Brocade 1860 AnyIO Fabric Adapter (User configurable port mode - FC or NIC or CNA) - Added Fibre Channel 16G Support - Enabled Fabric Assigned Address in Fibre Channel Fabric - Added PF based Virtualization – vHBA - Enhanced CLI, HCM GUI and CIM support in inbox drivers. - Added PF based Virtualization - vNIC - Added iSCSI over DCB Support - Added Multiple Tx Priority Queues Support - Added SNMP Support
Version 2.3.0.3 Fixes and Enhancements: - Enhanced SNIA API to report port speed of 4 and 8Gbps in SNIA format. - Enhanced XIV array interoperability that addresses a data integrity corner case. - Enhanced the transmit path handling in Linux Network Driver to avoid a corner case that could lead to transmit path stall. - Enhanced the Linux Adapter Software installer script to update the initrd with the correct name even when there are multiple copies of the OEM specific initrd(s).
Version 2.3.0.0 Enhancements: - Enabled HP DL120 server to support Boot over SAN with two Brocade HBAs installed. - Improved network driver CPU and performance optimization. - Enabled automated target and LUN discovery of enterprise HDS storage once LUN masking has occurred. - Improved Tivoli interoperability to meet device display requirements.
Version 2.2.0.1 Added capability to handle ADISC frames. Unhandled ADISC use can cause SAN boot failure when booting from IBM storage array.
Version 2.2.0.0 Adds support for bootcode updates to Bladecenter 10G Converged Network Adapters
Version 2.1.0.0 Adds support for bootcode updates to 10G Converged Network Adapters
Version 2.0.0.0 Initial release for 4/8G FC HBAs brcd_dd_nic_bna-3_2_0_0_sles10_32-64_chg
=============================================================================== Emulex NIC Device Driver for Linux ===============================================================================
Linux NIC Device Driver Version: 4.2.389.0
Problems Fixed: - Unloading the driver hangs the system after running IPv6 traffic - Link status messages cleaned up when in Switch Agnostic mode - Miscellaneous network performance issues to improve throughput - Miscellaneous problems related to SRIOV to improve usability - Ethtool wol command displays wol enabled even when disabled - Ethtool speed reported as 10000Mb/s for disabled devices in Switch Agnostic mode
Incremental Interoperability: - RHEL6.3 GA Kernel - Increase default B/W for SRIOV vf's to 10Gb from 100Mb
Known Issues: - SR-IOV configuration section of the Linux NIC Driver Documentation will be modified as follows to improve clarity (noted by << >>):
11. Use the Virtual Machine Manager GUI to attach the VF (step 7 on page 34) to the guest operating system by using the add physical device option.
<< Note 1: If user wants to re-configure an already configured setup, it can be done by removing the attached VF from the respective guest operating system using the remove option after selecting the VF attached. And then attaching another VF (step 11).
Note 2: Consult the documentation for your host operating system for help using the Virtual Machine Manager to attach and detach virtual interfaces. >>
12. Start the RHEL 6.x guest operating system. Once the guest operating system is booted, use the lspci command to confirm the visibility of the OneConnect NIC function. The output shows a OneConnect NIC function, for example: 03:00.0 Ethernet controller: Emulex Corp. Emulex OneConnect 10Gb NIC (be3)
13. The OneConnect Ethernet driver automatically loads with the inbox driver, and creates the network interfaces. Use the ifconfig command to verify that the interface is created.
14. After configuring the network interfaces with proper IP addresses, you can send and receive network traffic from the VM. << (Consult the documentation for your host and guest operating systems for network configuration help). >>
- WOL changes for Linux NIC driver as mentioned in Bug# 24543 - SR IOV UE when attempt to do multiple (3 times) driver load/unload - Speed is 10000Mb/s for Disabled devices in UMC Mode - Incorrect Duplex value is shown for unconnected port of NC552m in Rhel6.1 32bit - SLES 11 SP2 GMC: Enable support for Lnx NIC Driver - SRIOV: When VGT is configured for a VF, ip link show doesn't display it for the VF configured. - RHEL 5.8 GA: Enable support for Lnx NIC Driver - ip link command with vlan = 4095 has toggling effect - ip link command with vlan =0 should remove guest VGT privilege
- SR-IOV: Can't load be2net driver in a VM after the VM has been rebooted - SR-IOV: Unload PF driver with VF driver loaded causes system instability - SR-IOV: VF MAC always gets Emulex OUI - SR-IOV: Partition the limited per port VLAN entries across VFs and PFs - Non Member VLAN packets not received in interface promiscuous mode in BE3 - Avoid CQ full condition in HW - be2net: use RX_FILTER cmd to program multicast addresses - account for skb allocation failures in ethtool stats - Support 60 second delay to Linux NIC driver to allow FAT dump completion on recovery from EEH - Link status is up [ethtool and OCM] when the bandwidth is assign 0 for UMC configuration - Remove msix module parameter - Use V1 version of COMMON_NTWK_LINK_STATUS_QUERY for Lancer. - Emulex: Ethtool failing to update FW - Emulex: Panic in be2net driver in SLES11-SP2-B7 on adapter - TCP ACKs from different connections are getting received in single queue - Multicast filtering feature not working on PPC - Exit of mcast promiscous mode not working - VLAN promiscous mode cannot be set on Lancer - Can't communicate after changing MAC address via VLAN interface - Improper memory accounting in received packets - WOL changes for Linux NIC driver as mentioned in bug - Transparent VLAN tagging feature not working in SR-IOV elx_dd_nic_ibm1206-4_2_389_0_sles10_32-64_chg
IBM ServeRAID BR10i SAS Controller BIOS and Firmware Update BIOS Version 6.30.02.00, Firmware Version 1.30.10.00 and BSD Version 3.16.00.06
Adapters Supported: IBM ServeRAID BR10i SAS Controller (44E8689)
NOTE TO SERVICE - Reference RETAIN #N/A
NOTE: This change history is common between several of the IBM and LSI Basic or Integrated RAID SAS controllers for non-BOFM enabled, uEFI systems. Not all levels were released for all controllers.
BSD Fixes: - Fixed an issue where the controller was hanging during initialization when an adapter was hung in reset with insufficient information to reset itself. - Fixed an issue where the SAS MPT BIOS CU reports wrong array size.
BSD Fixes - Removed the "SAS/SATA missing" warning message when SAS and SATA arrays are present on the same controller. Firmware Fixes - Addressed issue where 6Gb SATA drives will only negotiate at 1.5Gb/s instead of 3Gb/s. - Fixed issue where SAS/SATA mixing errors will occur when the controller is setup to allow mixing of devices. - Fixed issue with large topology of SATA drives where media errors on a single drive will cause one phy to hang after IOs to other drives start to timeout. - Fixed discovery Error 0x2 in maximum topology with SATA devices, - Addressed issue where Credit would be stuck at zero until controller resets resulting in a phy becoming hung and IO failing. Only occurs with very high IO.
Fixes: - Addressed issue with SATA devices where the drive could go missing for several minutes. - Fixed issue where incorrect release of scatter gather list could cause issues with pending IO to missing devices. - Addressed issue where IOs to a host with a bad drive could fail.
Fixes: - Fixed issue where Target mode responds with incorrect WWID after ports are swapped. - Fixed issue with Incorrect/Unexpected discovery errors on RAID storage enclosures. - Fixed issue where device added events are not sent to the host on RAID storage enclosures. - Fixed issue where it is possible for a Incorrect/Duplicate Device handle to get assigned to a target that is a SSP Initiator. - Fixed problem of the boot order selection not being saved
Fixes: - Changed BIOS text to state an IS Volume creation can be 1 to 10 drives. - Fixed issue with 2TB and above drives where SAS MPT BIOS CU reports wrong array size. - Addressed an issue that will maintain Target IDs for attached devices to an enclosure if the enclosure is removed for a short time.
Fixes: - Fixed an issue where, after running heavy I/O to NCQ enabled SATA drives, the controller may log false data underruns for read or write I/Os. The PHY on which the I/Os were reported as underrun may eventually lock up.
Fixes: - Fixed an issue where Solid State Drives (SSDs) were not seen after a link reset. - Fixed an issue where direct attached SATA drives were not reported missing after they were removed. This could result in degraded or failed volumes being reported as healthy. - Fixed an issue introduced by new functionality in package 2.50. The issue would cause a dual attached device to be hidden from both the direct connection and the expander connection. - Changed the behavior during drive quiescing/un-quiescing to prevent the drive metadata from being unnecessarily updated. - Fixed an issue where drives might go offline during a firmware update, due to I/O timeouts caused by the length of time needed to update the firmware.
Fixes: - Fixed an issue where, on certain drives, it was not possible to create a RAID 0. - Fixed an issue which could cause drive ID0 to go offline. - Fixed an issue with SSD hot spares being reported as Orphaned. - Fixed an issue where hot spares could not be created when the first physical disk of a roaming IME volume is missing. - Fixed a memory leak which could occur in verification of hot spare. - Fixed several issues involving creating a volume or hot spare immediately after deleting a volume or hot spare. - Fixed various issues with hot spare reporting. - Fixed an issue where, in a multi-path environment under heavy I/O, an open timeout can cause Linux file systems to become read-only. - Fixed an issue where drives may go offline during a firmware flash under Windows. - Fixed an issue that caused a 0x7600 fault while running heavy I/O to expander attached disks. - Fixed an issue where, when a driver at a certain volume ID is roamed, the volume ID would change on the next reboot. - Fixed an issue which caused a 0x266D fault on reinsertion of a hotspare. - Fixed an issue where a volume cannot be deleted due to foreign metadata from a new drive. - Fixed an issue where a 0x8055 fault could occur upon insertion of drives with deleted metadata. - Fixed a rare issue where drives could go missing under a heavy load. - Fixed an issue where a 0x800F fault may be seen at startup on large topologies. - Fixed an issue that could cause a 0x0B83 fault when a SATA drive failed to initialize. - Fixed an issue where the LED of a critical drive would revert to the pattern for an optimal drive before the drive was truly optimal again. - Fixed an issue where a resync would resume, rather than restart, when a primary drive was removed and re-inserted. - Fixed an issue that could result in 0x6001 faults while running I/O. - Removed some extraneous error messages, which were triggered by reboots or firmware flashes, from the firmware log. - Fixed an issue which cause a 0x266D fault during volume creation.
Functionality: - Enhanced support for SSDs (Solid State Drives). - Implemented support for single drive RAID 0. - Added a new volume status 'Sync Pending' for a volume that could be resynching, but is waiting for the first volume to complete resync. - Added ability to remove an orphaned hot spare when its associated, missing, volume is deleted. - Implemented some LED blink pattern changes to account for new hardware. - Added the ability to enable/disable data scrubbing on SSDs. - Enabled functionality to update drive firmware on disks in a degraded volume (the update must be done via the IBM Online SAS/SATA HDD Update Program, which must also contain a fix to enable this function).
Fixes: - Fixed an issue which could cause the operating system's file system to become read only in a multi-path environment. - For the 1064 option for System x3200 M2, x3250 M2, or x3350, fixed an issue where the amber LED would not light up on a defunct drive.
Fixes: - Fixed an issue where, with dual solid state disks (SSD) installed, hard drive 0 goes defunct or disappears or a RAID 1 mirror becomes degraded. - Fixed an issue which slightly degraded performance in a Large Drive Count (LDC) configuration. - Fixed an issue where SATA drives may fail when alternate paths are removed and reinserted in a multipath configuration. - Fixed a condition which caused a 0x1904/0x1903 fault when issuing a TARGET RESET to certain SATA drives. - Fixed an issue where a 0x0800 fault occurs when an inactive or non-optimal volume is deleted. - Changed a resource allocation so that topology and other discovery related events aren't affected when other resources are heavily stressed. - Fixed an issue where, if a volume is removed, then reinserted, into a SAS topology, the volume becomes inaccessible. - Fixed an issue where discovery appears to hang due to multiple Expander Removed events sent for a single expander. - Fixed an which causes an OS not to boot if one of the hard disks in the boot volume is removed. An error similar to "Adapter LSI RAID 0/1 SAS 4P (0) was 1: Disk (0) missing after reboot". - Fixed an issue where continuous 'device added' events would be sent during discovery when a controller is attached to a topology with more end devices than are supported. - Fixed an issue that could cause I/O timeouts or 0x0900/0x1600 faults with SATA drives under heavy I/O load during any memory deallocation. - Fixed an issue where multiple WRITE BUFFER commands may cause a 0x4202 fault. - Fixed an issue where a 0x1904/0x1903 fault may be seen when a duplicate I/O results in a double completion. - Prevented task management timeouts which occurred when the SATA engine was involved with multiple error handling. - Fixed an issue that could cause the Initiator Command queue to become corrupt, resulting in a 0x6001 fault. - Fixed an issue where some error information was lost during Record Not Found media errors. - Fixed an issue with the reporting/retrieval of some LDC statistics. - Fixed an issue which may cause firmware initialization failure when many (more than 50) SATA targets are attached. - Fixed an issue which, in rare cases, could cause a 0x266D fault. - Fixed an issue which could cause a 0x1904 fault when issuing task management requests during heavy IO. - Fixed an issue that caused a break of the MPI spec in a scenario where an end device fails SATA initialization or an expander is out of routing table entries. - Fixed an issue where a virtual PHY is counted multiple times, resulting in the same Bus/Target ID being assigned to two different devices. - Fixed a stack overflow issue which could result as a 0x0900 fault or a fault code 11h during system initialization. - Enabled modification of Write Cache settings for RAID 0 volumes. - Fixed an issue which caused an "Insufficient Resources" response for an MPT RAID Passthrough command. - Fixed an issue where SMP requests are sent through the SMP passthrough, a 0x4203 fault occurs. - Fixed an issue where drives with SMART errors are not detected as volume members. - Prevented a false "Device Not Responding" event during discovery under heavy I/O. - Fixed an issue where an Activity LED would erroneously blink when a raw hard drive was added to a previously occupied slot. - Fixed an issue which could result in media errors at 51% rebuild point when a hot spare is present. - Fixed I/O timeouts and/or invalid SAS Expander Page #0 content which could occur if a bad link caused rapid linkup/linkdown states on a drive. - Fixed an issue which could result in a 0xBADn fault (where n is the PHY number) after a HARD RESET primitive is received. - Corrected an issue where the swap out status of a drive is always set to 0, rather than to a meaningful value. - Fixed an issue where, if a card enters fail-safe mode due to unreadable or unreachable settings, a fault 0x0700 was seen and the card would never enter READY state. - Fixed an issue where a hotspare which was created through the BIOS would not be correctly reported until after a reboot. - Corrected an issue where media errors would cause unnecessary device resets. - Fixed an issue where, if a disk is hot swapped with an incompatible disk, the new disk would incorrectly be assigned the volume ID as its target ID. - Prevented multiple paths from being returned unless multipathing is specifically enabled in NVDATA. - Fixed an issue which results in a 0x6014 fault during discovery in complex topologies. - Corrected an issue where pulling a drive in a volume would caused a 0x801F fault. - Fixed an issue where a 0x6002 fault is encountered in LDC topologies. - Ensured the MPI_EVENT_IR2_RC_PD_REMOVED event is properly reported when a foreign disk is removed. - Fixed an issue which could result in a 0x0800 fault under heavy I/O. - Corrected an issue which results in 0x4E01 fault when processing multiple simultaneous NCQ errors. - Fixed an issue where, if four or more drives are configured as any mix of volumes or hot spares, when you delete the volume, the associated hot spare(s) are correctly deleted, but the physical drives don't reappear in BIOS until after a reboot. - Fixed an issue where, if the same LUN is issued two active resets, the second reset could be completed before the first reset. - Fixed an issue which causes SATA initialization failure if a WRITE command is processed concurrently with a RESET command. The volume would then change to a FAILED state. - Ensured that metadata size is automatically detected by the firmware. - Fixed an issue where the BIOS stops responding if a rebuilding hard drive is removed. - Fixed an issue where 0x7600 faults were encountered when running heavy I/O to cascaded x12 expanders. - Fixed an issue where, with a 1078 chip, a 0x266D fault may occur when hot spare is reinserted. - Corrected an issue where SAS or SATA drives may be reported missing after a target reset to an end device. - Fixed an issue where, if the drive at the volume ID slot is roamed, the volume ID might change on the next reboot.
Functionality: - Implemented various changes to the LED blink pattern for SGPIO. - New functionality to ensure that, if a dual-ported device is connected via both direct and expander attached connections, only the direct connection is hidden when the HideNonzeroAttachedPhyIdentifiers bit is set.
Note: - The multi-path read only fix that was added in version 2.45 is not present in 2.50. It is reintroduced in version 2.51.
Fixes: - Fixed an issue where there is a very low probability of experiencing data corruption while under very heavy I/O stress. - Reworked the firmware download function into an asynchronous operation to allow I/O to continue during the process. - Fixed an issue where a direct-attached SEP device will not be assigned an ID or handle which will prevent communication with the device. - Fixed an issue where a direct-attached SEP will be incorrectly assigned TargetID 0.
Fixes: - Fixed an issue where, in a setup with cascaded expanders, a timeout occurred during PortEnable after an adapter initialization. - Increased several preset maximum values to allow all devices to be seen in large topologies. - Fixed an issue where SATA initialization would hang in a multiple initiator environment. - Fixed an issue that could result in a system hang when an active-active MUX that did not support NCQ was detected in the topology. - Fixed several issues which would cause doorbell faults when using SATA drives. Faults include 0x6001, 0x0B85, or 0x6212. - Fixed an issue where "Persistent Table Full" messages were seen even with persistent mapping disabled. - Fixed a SATA initialization error which could occur when I/O was sent to the drive shortly after the DEVICE ADD event. - Fixed a discovery error that was seen when rebooting initiators under heavy I/O in a multi-initiator environment. - Fixed an issue that could cause a 0x7A02 doorbell fault in a 1078-based complex topology environment. - Fixed an issue which caused doorbell fault 0x4203 when an expander is disconnected during discovery. - Fixed a multipathing issue where devices were not seen after a secondary path was removed and readded quickly. - Fixed an issue where, under heavy I/O, the message indicating discovery completion could be lost. - Fixed multiple issues that were specific to multipathing. - Fixed issues where a controller would hang after firmware or BIOS flash. - Fixed an issue that could cause loginfo 0x31123000 during heavy I/O. - Fixed various issues that could cause doorbell faults 0x4104, 0x0B85, 0x266D, 0x2100, 0x4202, or 0x7711. - Fixed an issue where SATA initialization would fail if the drive did not support write caching. - Fixed an issue where, when logs were generated for a passive path, the enclosure handle and slot information for the active path were stored in the logs. - Fixed an issue where all disks become inaccessible if a SATA logical loop is introduced into a topology with SAS drives. - Fixed an issue which caused BIOS timeouts which resulted in the boot device not being found. - Fixed an issue where, during certain MPT BIOS activity, the system BIOS could not read the MPT BIOS, resulting in a "no bootable device" error. - Fixed an issue where, if translated SCSI commands where sent to a SATA drive the I/O would hang. - Fixed an issue where a hard reset sent to one initiator in a multi-initiator environment could cause a cascade of hard resets through the environment. - Fixed an issue where a corrupted sector in a primary volume was not being correctly restored with the correct data from the secondary volume. - Fixed an issue where, if the secondary drive is cold swapped during a volume resync, the resync is not resumed on system start. - Fixed an issue where the driver temperature info is not sent for SCT enabled drives. - Fixed an issue where the second path is not being hidden when a non-volume drive is inserted in a volume ID slot. - Fixed an issue where, during initialization, the SAS BIOS displays 'Adapter Malfunctioning!' Fault 13. - Prevented Device Missing Delay replies when DevMissingTimeout and IoDelayTimeout are disabled. - Fixed and issue where, when inserting a new drive into the topology while I/O is running, I/O to existing drives may experience a delay of ~600msec. - Fixed an issue where the execution of a command in CFGGEN following execution of a command without a ‘noreset’ switch causes controller to hang. - Fixed an issue where firmware update of an online SATA drive would fail. - Fixed several issues where, when detecting whether a device is an HDD or SDD, the device type was detected incorrectly. - Fixed an issue where physical disk firmware download commands were being rejected. - Fixed an IOC hang that could be caused by a SCSI INQUIRY command. - Fixed an issue where, in a multipath environment, a degraded RAID volume with a missing disk is rebooted, it may re-sync to a non-RAID disk. - Fixed a SATA specific issue where a doorbell fault 0x1903 or 0x1904 was seen when hot-plugging an active drive. - Fixed a large topology issue where I/O to the SAS drives times out after a bus reset. - Fixed an issue where, when the last device in a volume is missing, the volume may be calculated as the wrong media type. This will prevent hotplug and failover from working correctly. - Fixed an issue where the volume ID changes after removing the drive at a roamed volume ID. - Fixed an issue where, when a volume's disk is swapped and starts to resync, a controller reset (reboot) may result in either the volume losing a disk that was previously in the volume, and/or the wrong disk reported as the primary. - Fixed an issue where discovery would fail when a 1078 controller is connected to a JBOD with dual-I2C SEP functionality.
Functionality: - Initial release for: IBM BladeCenter LS22 and LS42 onboard LSI 1064e controller - Fixed the ability for the BIOS configuration utility to create hotspares with SSD (Solid State Drive) devices. - Enhanced SATA I/O performance for NCQ drives. - Allowed the host to set the name of a RAID volume. - Added ability to retrieve SATA drive temperature through "Information Exception". - For SGPIO, turned on the fault LED when an IR volume member is detected as missing. - Added ability to specify bus/target ID & slot mapping for direct-attached disks. - Expanded the ability for the backplane to define the sideband interface method (I2C/SGPIO). This was previously enabled for 1078, now it is enabled for 1064 and 1068 as well. - Several changes the blink LED patterns. ibm_fw_sraidbr_10i-2_75_linux_32-64_chg
IBM Online SAS/SATA Hard Disk Drive Update Program
Version 1.12.01 Build ID: SAS_11201
NOTE TO SERVICE - Reference RETAIN #H207740
*******************************************
Version 1.12.01 Critical Release
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA450900EST1, VPCA600900EST1 to A3C4, Corrects firmware bug that may cause data corruption. For further information, please refer to Retain Tip H207740.
- ST3300657SS, ST3450857SS, ST3600057SS to BA5A VPCA300900EST1, VPCA600900EST1 to A3C2 Additions to VPD information used by manufacturing
- ST3750630SS, ST31000640SS to BC1I ST31000424SS, ST32000444SS to BC2C Mode Page change to address performance issues under certain system configurations
- ST33000650SS to BC3D ST1000NM0001, ST2000NM0001 to BC48 Protection Information Fix - see Retain Tip H206140
- HUS723020ALS64, HUS723030ALS64 to J26C Initial Code Release
SAS 2.5"
- ST9300603SS, ST9146803SS to B53E ST9600204SS to B549 Additions to VPD information used by manufacturing
- ST9300605SS, ST9600205SS, ST9900805SS to B55C ST9146853SS, ST9300653SS to B63A ST9500620SS, ST91000640SS to BD2C ST9300505SS to E555 ST9146753SS to E635 Protection Information Fix - see Retain Tip H206140
- ST9600105SS, ST9900705SS to E555 Inital Code Release
- HUC106030CSS60, HUC106060CSS60 to D3A6 Performance improvements, critical fixes for Protection Information (PI) operation - see Retain Tip H206140
- MK1401GRRB, MK3001GRRB to SC27 Additions to VPD information used by manufacturing
- WD9001BKHG-23D, WD6001BKHG-23D, WD3001BKHG-23D to ZA31 Initial Code Release
SATA 3.5"
- WD2502ABYS-23B7A0 to 02.03B08 WD1602ABYS-23B7A0 to 02.03B07 Critical fix to address premature drive failures.
- ST3500514NS, ST31000524NS, ST32000644NS to BB2A ST33000650NS to BB38 ST1000NM0011, ST2000NM0011, ST500NM0011 to BB47 Fixes a potential, but rare data corruption issue which requires a background reallocation that exceeds the error recovery timer.
- HUA723020ALA640 to MK70A900 HUA723030ALA640 to MKA0A900 Initial Code Release
SATA 2.5"
- ST9160511NS, ST9500530NS to BE1A ST9250610NS, ST9500620NS, ST91000640NS to BE25 Fixes a potential, but rare data corruption issue which requires a background reallocation that exceeds the error recovery timer.
SSD
- MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA to MA52 Initial Code Release
- MTFDDAA512MAR-1K1AB, MTFDDAK064MAR-1J1AA, MTFDDAK512MAR-1K1AA, MTFDDAA064MAR-1K1AB, MTFDDAA128MAR-1K1AB, MTFDDAA256MAR-1K1AB to MA52 Fixes SMART attribute 190 (Current Temp) which caused warning messages with some versions of Linux
- STEC MACH8 IOPS to 2804 STEC M8PSB2 T4 to SM06 Additions to VPD information used by manufacturing Fixes potential drive failure if power loss occurs during firmware update.
*******************************************
Version 1.11.01 (Non-Critical) - Fixed issue where hard disk drives may not be detected in configurations with multiple Emulex adapters.
See Verion 1.11 for Hard Disk Drive support, firmware levels, and respective change History.
- ST33000650SS to BC3A ST1000NM0001, ST2000NM0001 to BC44 Additions and corrections to VPD information used by manufacturing
SAS 2.5"
- ST9300605SS, ST9600205SS, ST9900805SS to B559 ST9146853SS, ST9300653SS to B637 ST9500620SS, ST91000640SS to BD29 ST9300505SS to E553 SST9146753SS to E633 HUC106030CSS60, HUC106060CSS60 to D390 Additions and corrections to VPD information used by manufacturing
- MK1401GRRB, MK3001GRRB to SC23 Fixes a pottential data corruption bug if there is an unexpected power loss.
SATA 3.5"
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB15 ST3500514NS, ST31000524NS, ST32000644NS to BB29 ST33000650NS to BB36 ST1000NM0011, ST2000NM0011, ST500NM0011 to BB46
SATA SSD
- SG9XCS1B50GMIBM, SG9XCS1F200GEIBM to SA03SB6C SG9XCS2D200GEIBM to SA03SE6C Fix for potential hang during an unexpected power cycle
MTFDDAK128MAR-1JAAB, MTFDDAK256MAR-1JAAB to MA44 Initial Release
=========================================== Version 1.10 (Critical)
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA600900EST1 to A3C0 Correction to VPD information used by manufacturing
- ST31000424SS, ST32000444SS to BC2B Fixes to improve robustness from certain read errors due to encroachment
- ST33000650SS to BC37 Fixes to improve overall robustness.
- ST1000NM0001, ST2000NM0001 to BC42 Inital Release
SAS 2.5" (SFF)
- ST9300605SS, ST9600205SS, ST9900805SS to B556 - ST9146853SS, ST9300653SS to B635 Fixes to improve overall robustness.
ST9300505SS to E552 ST9146753SS to E632 Initial Release
- ST9500620SS, ST91000640SS to BD26 Improve general robustness and added support for DPICZ
- HUC106030CSS60, HUC106060CSS60 to D340 Improve general robustness
- MBF2300RC, MBF2600RC to SB28 Improves performance in certain benchmarks
SATA 3.5"
- ST33000650NS to BB34 Fixes to improve overall robustness.
- ST1000NM0011, ST2000NM0011, ST500NM0011 to BB45 Initial Release
- ST3500514NS, ST31000524NS, ST32000644NS to BB29 Fixes for intermittent drive hangs
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB15 Added enhancement for improved robustness
SATA 2.5"
- ST9250610NS, ST9500620NS, ST91000640NS to BE24 Initial Release
- ST9160511NS, ST9500530NS to BE19 Fixes for overall robustness.
SATA 2.5" SSD
- STEC MACH8 IOPS to 2765 STEC M8PSB2 T4 to SM05 Fixes potential drive lock up during cold or warm boots Fixes issues with RHEL 6.x installation
- SG9XCS2D200GEIBM to SA03SE6C Fixes default drive VPD information for manufacturing, the default LED behavior on certain systems and fixes issues with client install thru VMWare 5.x
SATA 1.8" SSD
- STEC M8PSB1 to 0409 STEC M8PSB1 T4 to SM16 Fixes potential drive lock up during cold or warm boots Fixes issues with RHEL 6.x installation
- SG9XCS1B50GMIBM to SA03SB6C SASG9XCS1F200GEIBM to SA03SB6C Fixes potential drive lock up during cold or warm boots and the default LED behavior on certain systems and fixes issues with client install thru VMWare 5.x
=========================================== Version 1.09 (Critical)
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- ST31000424SS, ST32000444SS to BC28 Added enhancement for improved RV robustness
- MBE2073RC, MBE2147RC to SC17 - MBA3073RC, MBA3147RC, MBA3300RC to SA0A Added VPD changes for manufacturing
SAS 2.5" (SFF)
- ST9300603SS, ST9146803SS to B53C ST9600204SS to B548 SST973452SS, ST9146852SS to B62C CBRCA146C3ETS0, CBRCA300C3ETS0 to C610 Added fixes for overall drive robustness
- MBD2147RC, MBD2300RC to SB1A Added VPD changes for manufacturing Addresses issues seen with DSA HDD Diagnostic test.
- MBF2300RC, MBF2600RC to SB25 Addresses issues seen with DSA HDD Diagnostic test.
- ST9500620SS, ST91000640SS to BD22 HUC106030CSS60, HUC106060CSS60 to D2F8 Inital Release
SATA 3.5"
- WD2502ABYS-23B7A0 , WD1602ABYS-23B7A0 to 02.03B07 Addresses firmware issues that may cause a drive to be marked defunct prematurely under certain application workloads.
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB14 ST3500514NS, ST31000524NS, ST32000644NS to BB28 Added enhancement for improved robustness
- WD5003ABYX-23 to WC31 Initial Release
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V10 (Critical) Addresses firmware issues that may cause a drive to be marked defunct prematurely under certain application workloads.
- ST9250610NS, ST9500620NS, ST91000640NS to BE21 Initial Release
SATA 2.5" SSD
- STEC MAC8 IOPS to 2732 STEC M8PSB2 T4 to SM04 Addresses an issue installing RHEL 6.0 onto this drive.
SATA 1.8" SSD
- SG9XCS1B50GMIBM, SG9XCS1F200GEIBM to SA03SB63 Addresses rare issue where the drive may not being seen on power up.
- STEC M8PSB1 to 0408 STEC M8PSB1 T4 to SM15 Addresses an issue installing RHEL 6.0 onto this drive.
- ST373455SS, ST3146855SS, ST3300655SS to BA2D - ST373355SS, ST3146755SS, ST3300555SS to BA38 - ST3146356SS, ST3300656SS, ST3450856SS to BA4C - ST3300657SS, ST3450757SS, ST3600057SS to BA58 - ST3750630SS, ST31000640SS to BC1G - ST31000424SS, ST32000444SS to BC26 (All Above Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- MBA3073RC, MBA3147RC, MBA3300RC to SA08 This code corrects a firmware bug that may cause the drive to not come ready on a cold boot.
SAS 2.5" (SFF)
- ST973402SS, ST9146802SS to B52B - ST936751SS, ST973451SS to B617 - ST9600204SS to B546 - ST973452SS, ST9146852SS to B629 - ST9300503SS to E536 - ST9146752SS to E625 - ST9500430SS to BD14 (All Above Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
SATA 3.5"
- ST3500514NS, ST31000524NS, ST32000644NS to BB26
- WD2003FYYS-23W0B0 to WA32 - WDC WD1003FBYX-23Y7B0 to WB31 Initial release
SATA 2.5" SSD
- STEC MACH8 IOPS to 2582 (Critical) Corrects firmware bug that may cause data corruption. For further information, please refer to retain tip H197650.
SATA 1.8" SSD
- STEC M8PSB1 to 0405 (Critical) Corrects firmware bug that may cause data corruption. For further information, please refer to retain tip H197650.
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA450900EST, VPCA600900EST1 to A3B8 Initial Release
- VPBPA300C3EST1 to A529 Initial Release
- ST3300657SS, ST3450757SS, ST3600057SS to BA56 (Critical) Performance improvements under certain workloads. Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST31000424SS, ST32000444SS to BC21 Initial Release
SAS 2.5" (SFF)
- ST9300603SS, ST9146803SS to B53A (Critical) Performance improvements under certain workloads. Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST9600204SS to B544 (Critical) Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST973452SS, ST9146852SS to B626 Performance improvements under certain workloads.
- ST9500430SS to BD13 Performance improvements under certain workloads
- ST9300503SS to E534 and ST9146752SS to E623 Performance improvements under certain workloads.
- MBD2147RC, MBD2300RC to SB19 (Critical) Retain Tip H196899 MBE2073RC, MBE2147RC to SC16 (Critical) Retain Tip H196899 Corrects a firmware bug that erroneously reported medium errors which may cause the drive to report PFA alerts and in some cases be marked offline
SATA 3.5"
- WDC WD2502ABYS-23B7A0, WD2502ABYS-23B7A0, WD802ABYS-23B7A0, WD1602ABYS-23B7A0 to 02.03B05 (Critical) Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST3500514NS, ST31000524NS, ST32000544NS to BB26 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB13 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- HUA722020ALA330 to JKAOA3GA HUA722050CLA330 to JP2OA3GB HUA722010CLA330 to JP4OA3GB Initial Release
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V09 (Critical) This code corrects an additional issue where the drive may be marked defunct.
- ST9160511NS, ST9500530NS to BE18 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382. Also improves performance under certain workloads.
SATA 2.5" SSD
- STEC MACH8 IOPS to 2366 (critical) Corrects firmware bug that may cause degraded performance and in some cases the drive may not come ready after a warm or old boot.
SATA 1.8" SSD
- STEC M8PSB1 to 0404 Turns the default for write cache off
*******************************************
Version 1.06 (Critical)
Added support for the following controllers:
- IBM ServeRAID BR10il SAS controller v2 (49Y4731) - IBM ServeRAID M1015 SAS controller (46M0831) - IBM ServeRAID M5015 SAS controller (46M0829) - IBM ServeRAID M5014 SAS controller (46M0916)
The following is a list of drives and the firmware that they will be checked for and updated to as necessary.
This package includes new updates to drives with product ID strings of:
SAS 3.5" --------------
- ST373455SS, ST3146855SS, ST3300655SS to BA2A ST373355SS, ST3146755SS, ST3300555SS to BA36 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632.
- ST3750630SS, ST31000640SS to BC1E ST3146356SS, ST3300656SS, ST3450856SS to BA4A This code address an issue where the drive may report an erroneous hardware error to the controller.
- MBA3073RC, MBA3147RC, MBA3300RC to SA07 This code improves sequential write performance under certain workloads when write cache is turned on.
- ST3300657SS, ST3450757SS, ST3600057SS to BA52 NOTE: This is the first code release to be included in the hard drive update package.
SAS 2.5" (SFF)
- ST973402SS, ST9146802SS to B52A ST936751SS, ST973451SS to B616 (Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632.
- MBB2073RC, MBB2147RC to SB07 MBD2147RC, MBD2300RC to SB17 MBE2073RC, MBE2147RC to SC14 CBRCA146C3ETS0, CBRCA300C3ETS0 to C370 This code improves sequential write performance under certain workloads when write cache is turned on.
- ST9500430SS to BD11 This is the first code release to be included in the hard drive update package.
SATA 3.5"
- WD2003FYYS-23T8B0 to 01.00D04 This is the first code releases to be included in the hard drive update package.
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V08 (Critical) This code corrects an issue where the drive may generate a false PFA alert. It also corrects an issue where the drive may be marked defunct
- ST9160511NS, ST9500530NS to BE16 This is the first code releases to be included in the hard drive update package.
*******************************************
Version 1.05
The following is a list of drives and the firmware that they will be checked for and updated to as necessary.
This package includes new updates to drives with product ID strings of:
SAS 2.5" (SFF) -------------- ST9xxxx51SS to B616 ST9xxxx02SS to B52A - This code improves the robustness of write cache operations.
ST9xxxx52SS to B624 ST9xxxx03SS to B536 - This code improves the robustness of write cache operations and sequential write performance when write cache is enabled. NOTE: This is the first code for the ST9xxxx52SS and ST9xxxx02SS drives to be included in a hard drive update package. It is an update from the code that is shipped with the drive.
MBD2xxxRC to SB14 - Initial release
SAS 3.5" -------- ST3xxxxx6SS to BA49 ST3750630SS to BC1D - This code improves the robustness of write cache operations.
SATA 2.5" --------- WD3000xxxxx to 04.04V05 - Adjusted PHY setting for better signal quality margin.
SATA 2.5" SSD -------------- STEC MACH8 IOPS to 2269 GBRL0xxxxx to 4.17 GBRLBxxxxx to 4.26 - The new firmware will correct a rare data error condition in the drives where invalid data may be passed to the system without any error condition flagged.
Due to the severity of this potential issue, IBM strongly recommends applying this firmware as soon as possible.
For further information, please refer to retain tip H195663.
NOTE: This is the first code for the GBRLBxxxxx drives to be included in a hard drive update package. It is an update from the code that is shipped with the drive.
*******************************************
Version 1.04
The following is a list of drives and the firmware that they will be checked for and updated as necessary.
This package includes new updates to drives with product ID strings of:
SAS 2.5" (SFF) -------------- CBRBAxxxxxx to C49B - Modified VPD for JSxx Blades
MBBxxxxxx to SB05 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller.
MBC2073RC to SC04 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller.
SAS 3.5" -------- MBAxxxxxx to SA06 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller.
ST3xxxxx6SS to BA48 - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632.
ST3750630SS to BC1A - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632. - Fixes a hang condition during failover operation on a BladeCenter-S chassis with an RSSM controller.
BBAxxxxxx to BH0K - Fixed an issue where a drive may prematurely report a PFA trip.
GNAxxxxxx to BH0J - Fixed an issue where a drive may prematurely report a PFA trip.
SATA 3.5" --------- ST31000340NS, ST370330NS, ST3250310NS, ST3500320NS to BB12 - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632. - This code addresses a rare potential for data loss. After a power cycle, the drive will no longer be available and becomes unresponsive. Data will become inaccessible due to the drive not responding. For further information, please refer to retain tip H194623.
WDC WD2502ABYSxxxxx to 02.03B04 - Fixed incorrect VPD data.
SATA 2.5" --------- WD3000xxxxx to 04.04V04 - Fixed a Critical issue - IBM recommends a backup of the data on the drive before attempting to update the firmware. This is a fix for an issue where data required for spin up of the drive may be overwritten, rendering the drive inoperable on a subsequent warm or cold system reboot. - Fixed a bug with an internal timer that may cause a drive to go offline when used in a non-RAID environment.
SATA 2.5" SSD ------------- STEC MACH8 IOPS to 2103 - Initial Release
*******************************************
Version 1.03
Added the capability to update SAS and SATA drives online under Windows or Linux. This capability is only supported if the drives are attached to one of the following SAS adapters: - IBM ServeRAID MR10k SAS Controller - IBM ServeRAID MR10i SAS Controller - IBM ServeRAID MR10M SAS Controller - IBM ServeRAID MR10il SAS Controller - IBM ServeRAID MR10is SAS Controller - MegaRAID 8480 SAS Controller - IBM ServeRAID BR10i SAS Controller - IBM ServeRAID BR10il SAS/SATA Controller - IBM SAS HBA - IBM SAS Expansion Card (CFFv) for IBM BladeCenter - IBM SAS Connectivity Card (CFFv) for IBM BladeCenter - Onboard LSI 1064 SAS controller (2MB only) - Onboard LSI 1068 SAS controller - Onboard LSI 1078 SAS controller
This package includes new updates to drives with product ID strings of:
SAS 2.5" (SFF) -------------- ST9146802SS, ST973402SS to B529 - Added support for JS2x Blades in a BladeCenter-S chassis. - Picked up the latest network roll of firmware fixes to address some unexpected system hangs.
ST936751SS, ST973451SS to B615 - Added support for JS2x Blades in a BladeCenter-S chassis. - Picked up the latest network roll of firmware fixes to address some unexpected system hangs.
CBRBAxxxxxx to C495 - Initial release
MBBxxxxxx to SB04 - Initial release
MBC2073RC to SC03 - Initial release
SAS 3.5" -------- VPBAxxxxxx to A496 - Added support for JS2x Blades in a BladeCenter-S chassis.
ST3146855SS, ST3300655SS, ST373455SS to BA29 - Added support for JS2x Blades in a BladeCenter-S chassis. - Picked up the latest network roll of firmware fixes to address some unexpected system hangs.
ST3450856SS to BA47 - IBM was notified by our vendor that there is a defect in a level of firmware used in the IBM 450GB 15K SAS 3.5" HS HDD (PN 41Y8454) in option 42D0519, which under certain conditions may lead to data being written or read back incorrectly on the drive. IBM has worked closely with the vendor to identify the problem and developed a firmware fix to resolve the problem. Customers should upgrade to firmware level BA47.
MBAxxxxxx to SA05 - Initial release
ST3750630SS to BC17 - Initial release
SATA 3.5" --------- ST3250620NS, ST3500630NS, ST3750640NS to 3.AEV - Initial release
ST3250621NS, ST3500631NS, ST3750641NS to 4AEV - Initial release
ST31000340NS, ST3750330NS, ST3250310NS, ST3500320NS to BB10 - Initial release
HUA721050KLA330, HUA721075KLA330, HUA721010KLA330, to AB4A - Initial Release
SATA 2.5" SSD ------------- GBRL001xxx, GBRL0031xxx to 4.14 - Corrects intermittent hangs during operations.
Version 4.22.80.08 - Suggested ------------------ Enhancement: - Add support for SLES 10 SP4 kernel.
Version 4.22.80.06 - Suggested ------------------ Fixes: - Fixed an issue where the driver would report the same Hard Disk Drive to OS twice.
Version 4.22.80.05 - Suggested ------------------ Fixes: - Fixed an issue where the driver would report the same Hard Disk Drive to OS twice.
Version 4.22.80.04 - Suggested ------------------ Fixes: - Fixed issue where an internal reset can occur when a device is removed
Version 4.22.80.03 - Suggested ----------------- Fixes: - Changed device missing delay timer from 8 bit to 16 bit structure to prevent the midlayer from timing out commands while the driver is still handling the device removal delay. - Fix issue where the IOdeviceMissingDelay and ReportDeviceMissingDelay where incorrectly converted to big endian as a 16 bit value instead of a 8 bit value
Version 4.22.80.01 - Suggested ----------------- Enhancement: - Add SLES 10 SP3 support in fixid package
Version 4.16.80.01 - Suggested ----------------- - Fixed an issue where targets were not found when the driver is initially loaded. - Fixed an issue where, after removing and reading a volume during heavy I/O, the volume is not detected. - Fixed a timing issue which prevented the detection of hot-inserted devices. - Fixed an issue which could occasionally cause a kernel panic when a cable was pulled. - Resolved a conflict with a function definition in the RHEL 5.2 kernel. - Fixed an issue which caused mkinitrd failures in SLES 10. - Fixed an issue where bad drive information was not cleared on removal, which caused a system reboot when a new good drive was inserted. - Fixed an issue which caused a driver crash during kdump. - Fixed an issue where, after deleting an array, the drivers from that array are no longer be seen by the OS. - Adjusted a timing value to ensure that devices added during error recovery are seen.
Version 4.00.37.07 - Suggested ----------------- - Fixed an issue where the OS becomes unresponsive during startup and shutdown after repeated power cycles.
Version 4.00.37.04 - Suggested ----------------- - Fixed an issue where, due to an incorrect delay timing, LUNs may not return after a 7157 reset. - Fixed an issue where the driver was not adding a device when a new device was detected by the firmware. - Added a new function to handle the removal, addition, or swapping of devices during a reset. - Corrected an issue where, if a system with a multipath environment was shutdown ungracefully, the OS might no longer boot. - Fixed an issue where the BIOS version of the controller was reported in hexadecimal, rather than decimal. - Fixed an issue where, if an external storage enclosure is configured with multiple LUNs, with no LUN 0, none of the LUNs would be detected. - Fixed an issue which caused a kernel panic when a cable was pulled on a device with the device missing delay enabled. - Moved firmware event handling to a separate, single CPU threaded, work queue, and prevented events from being handled during a firmware reset.
Version 4.00.33.00 - Suggested ----------------- - Moved the “ioc not found” debug message MPT_DEBUG_IOCTL debug level. - Fixed issue where hidden RAID components were not being reported to /dev/sg when they were brought online after being taken offline by an application. - Fixed an issue that is seen when an HBA reports that it supports less than the hard coded queue depth value of 128. - Made some adjustments to handle config page request time outs resulting from low resources. - added “id", "channel", and "phys_num” to logging info for IR2 events. - Enabled MSI interrupt routing for all SAS parts. - Added functionality to Power Management to enable/disable resources from power management entry points, and to block IO. - Made improvements to the processing of events in SAS Transport topology reporting. - For kernels newer than 2.6.20, implemented a new method for requesting resources at driver load time which avoids using IORESOURCES_IO unless the part requires firmware download. This solves a possible resource shortage when handling multiple HBAs. - Fixed an oops in mptctl_getiocinfo when traversing the device list while trying to obtain the number of devices. - Fixed a function definition conflict which is seen with the SLES 10 update 2 kernel.
Version 4.00.21.00 - Suggested ----------------- - Broadcast AEN support for multi-initiator devices - Fixed compile errors for kernels above 2.6.20 - Fixed an issue where extra device nodes were mapped to the same device when the HBA had target_mode enabled. - Added dual port support for RAID volumes with two paths to a single device. - Fixed an issue where a driver panic would occur when the mptspi driver was loaded for a controller with IR firmware. - Fixed an issue which caused the driver to hang when loading CSMI agents in RHEL 5. - Fixed an issue where CSMI agents were not returning any data for SMP_PASSTHRU. - Fixed an issue where the controller failed to resume when coming out of hibernation.
Version 4.00.13.10 - Suggested ----------------- - Added RHEL5 support - Fixed issue where GET_LOCATION ioctl in csmitool didn’t work - Fixed issue where a panic was seen when csmitool ioctl GET_PHY_INFO was called in RHEL5 32-bit. - Fixed issue where pulling a drive from a RAID1 volume would result in the volume being remounted as “read-only”.
Version 3.03.17.01-1 - Suggested ----------------- - Fixed issue where GET_RAID_CONFIG in csmitool didn’t show fault tolerant volume with rebuilding status when it’s rebuilding. - Fixed issue where GET_RAID_CONFIG in csmitool didn’t show FAILED logical volumes.
Version 3.03.15-1 - Suggested ----------------- - Fixed issue where ioctl get_raid_config doesn’t display a sass address when drive is pulled. - Fixed issue with the displays of a hotspare in IS volumes.
Version 3.03.13-2 ----------------- - Initial release ibm_dd_mptsas_4_22_80_08_sles10_32-64_chg
**************************************************************** | | | | | IBM Online Tape Drive/Optical Update Program | | Revision: 1.11.00.1075 Build Date: 6.23.11 | | | | (C) Copyright International Business Machines Corporation | | 2000-2011 . All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Note: Before using this information and the product it | | supports, read the general information under "NOTICES AND | | TRADEMARKS" in this document. | | | | Updated: 6/23/2011 | | | ****************************************************************
CONTENTS:
Change History
ver 1.1
Increased the tape tension during drive cleaning from 4g to 7g, which improves the cleaning effectiveness significantly.
ver 1.0
This firmware will change the firmware of your DDS tape drive to the latest available. ibm_fw_tape_dds-1_1_linux_32-64_chg
**************************************************************** | | | Tape LTO firmware update | | | | | | (C) Copyright International Business Machines Corporation | | 2000-2010 . All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Note: Before using this information and the product it | | supports, read the general information under "NOTICES AND | | TRADEMARKS" in this document. | | | | Updated: 9/24/2010 | | | ****************************************************************
Change History
ver 1.4_01
updated firmware for LTO 4 to A23E
ver 1.4_00
updated firmware for LTO 5 to A6S1 updated firmware for LTO 4 to A231
ver 1.3_02
update .txt and .chg files
ver 1.3_01
corrected XML / TML file names for new firmware (A4Q1 -> A5M1)
ver 1.3_00
updated firmware for LTO 5 to A5M1
ver 1.2
updated firmware for LTO 5 to A4Q1
ver 1.1
updated XML / TML to add new systems
ver 1.0
This firmware will change the firmware of your LTO tape drive to the latest available, unless it is already at the latest level.
- IBM HH LTO5 SAS (49Y9898 - 3628L5X - 3628N5X) @ A2C1 - IBM HH LTO1 SCSI (24P2396 - Newton) @ N2CG - IBM HH LTO1 SCSI (24P2396 - Pompy) @ P63I - IBM HH LTO2 SCSI (39M5658) @ 0468 - IBM HH LTO3 SAS (43W8478) @ 93G1 - IBM HH LTO4 SAS (44E8895) @ 93Y1 - IBM FH LTO1 SCSI (00N8016) @ 59C0 - IBM FH LTO2 SCSI (59P6744) @ 8571 - IBM FH LTO3 SCSI (39M5657) @ 87G0 ibm_fw_tape_lto-1_4_linux_32-64_chg
- Intermittent link status with IBM Virtual Fabric Switch when set to IBM Virtual Fabric Mode - The option to enable/disable SRIOV on HS23 LOM Port 0 is missing from OneCommand Manager. This selection is available in UEFI F1 setup. - Under high network stress, NMI errors can be seen with x3690 X5 and x3850 X5 - 10GbE ports running at 1GbE speed 10% below wirespeed at certain block sizes. - Unable to perform PXE boot with LPVID assigned to vNIC interface - 1Gb ports of HS23 do not handle tagging properly if multichannel mode enabled (pnic ok). Note: ESX driver patch also required. - Port flapping link after FW upgrade and "reboot" when connected to 10Gb PTM module (DAC)
Interoperability Since Previous Release:
- Support for Emulex Virtual Fabric Adapter Advanced (BE2) for IBM BladeCenter - Support for Emulex Virtual Fabric Adapter (BE2) for IBM BladeCenter - Support for Emulex Virtual Fabric Adapter (BE2) for IBM System X
Known Issues:
- All 10Gb KX4 ports must be used with 10Gb switches. They will not link at 1Gb. This applies to HS23 LOM and IBM BladeCenter VFA adapters only. - IPv6 IP address not visible via IMM GUI for IBM Option 90Y6456
- All VFS on Port 1 on optional Card unreachable from outside the host (x3750 M4) - 'Logical Admin Link' not enabled after applying BOFM in Switch Agnostic mode - IBM pre-boot Diagnostics NIC physical loopback test fails in Command and GUI mode - Multiple cosmetic issues with iSCSI UEFI BIOS - 10Gb ports do not detect 'Link Down' with some switches - 1Gb ports on HS23 LOM not able link up with IBM ICPM (FRU part 44W4486) in BCS chassis - Performance issues with specific DAC cables and SND top of rack switch
Interoperability Since Previous Release:
- UEFI 2.3.1 Compliance - Increased VF count in SR-IOV (was 16 VFs per port, is now 32 VFs per port) - Support for next generation 10GbaseT PHY - Expose IBM Feature On Demand licensing information in UEFI configuration utility
Known Issues:
- All 10Gb ports must be used with 10Gb switches. They will not link at 1Gb. - IPv6 IP address not visible via IMM GUI for IBM Option 90Y6456 - Intermittent link status with IBM Virtual Fabric Switch when set to IBM Virtual Fabric Mode - The option to enable/disable SRIOV on HS23 LOM Port 0 is missing from OneCommand Manager. This selection is available in UEFI F1 setup.
- Fixed an issue where ASIC randomly hangs losing network connectivity when certain commands are sent from the host. Resulting behavior varies between OS's (Yellow bangs in Windows, PSOD in VMWare) - PHY Loopback fails on 10G ports - UE and hang on LOM or Robalo when powering off Janice in UEFI or PXESelect - Loopback on HS23 now functional in DSAp - DCBX does not converge with firmware on a FCoE fabric - Control C Broken on BE2 - 7 second delay in GET_CARD_ATTRIBUTES command - Emulex VF adapter FCoE link lost on VMware 5.0 - flow control set for 10G Base T phys for autonegotiation - Dynamic link update is not working with NIC UEFI driver - Remove unused definitions in UEFI NIC - Emulex driver expects that the Login Options field be zero - "map r" displays a iSCSI BLK device when no LUNs presented - "X/x Exit without save" does not work as expected - Display proper description as part of EFI Driver Model Related Information - Intermittent "Configuration changed. reset to apply it now?" - Garbled output being displayed at the LUN configuration section. - All Emulex Configuration settings get lost after a reset - Perform additional checks when no Luns are mapped to the target - CHAP name only accepts 6 to 10 characters - Hii ???iSCSI Initiator Configuration??? showing old version screen - iSCSI name is case sensitive - iSCSI HII allows user to select first 8 LUNs as bootable. - iSCSI Boot Enable/Disable option should be port specific - LUN Configuration shows LUN 0, even if no LUNs presented to initiator.
Interoperability Since Previous Release:
- Support for Emulex Virtual Fabric Adapter Advanced (CFFh, 2+2) for IBM BladeCenter
- NCSI transmit workaround for IBM - Issues with data reporting when BOFM enabled - Improved network performance throughput - Issues with IBM Management network performance - Logical link status for IBM mezz card shown as 'N/A' - Serial Over LAN fails when more than one blade installed with a single switch - Removed UEFI menu items for unsupported functions on a port - Issues with diagnositics in virtual NIC/UMC mode - Issues with MAC and PHY loopback on OneConnect devices - Several issues with FCoE on some OEM fabric switches
Interoperability Since Previous Release:
- Support for HS23 Virtual Fabric LAN on Motherboard - Support for VFA III (95Y3762, 95Y3768), 90Y6456 - Support for IBM's Features on Demand (FOD) - Formal support for SR-IOV
- iLab Tucson - lpfc Device Resets and path failures continue after error inject. - Writes do not complete when running LIP test on BE3 port 2 - IPV6 implementations no longer experience an unrecognized routing type error. - VLAN tagging is now disabled on the OneConnect UCNA when multichannel is disabled. - UEFI/BIOS-assigned LPVIDs now function properly on the OneConnect 10102-based UCNA. - OneConnect UCNAs no longer send and receive only double-tagged packets and discard all other packets. - PHY, MAC, and External loopback tests no longer fail on all platforms. - Firmware now returns the proper OneConnect UCNA model number. - IPV6 implementations no longer experience an unrecognized routing type error. - Installing Windows 2008 or Windows 2008 R2 on remote iSCSI disks no longer causes the system to hang. - Issues no longer occur when resetting a server configured for multipathing on VMware ESX systems. - VLAN tagging is now disabled on the OneConnect UCNA when multichannel is disabled. - UEFI/BIOS-assigned LPVIDs now function properly on the OneConnect 10102-based UCNA. - OneConnect UCNAs no longer send and receive only double-tagged packets and discard all other packets. - An adapter hardware error no longer occurs when running I/O with LUNs on x86 platforms. - Changing from Convergence Enhanced Ethernet (CEE) to Chassis Internal Network (CIN) and then rebooting no longer fails to link-flap (CIN Fabric Login (FLOGI) now occurs). - PHY, MAC, and External loopback tests no longer fail on all platforms. - Firmware now returns the proper OneConnect UCNA model number. - DCB settings can now be configured. - (iSCSISelect) When enabling DHCP for an iSCSI initiator, the Emulex iSCSI Network Configuration utility now waits approximately 20 seconds to make a DHCP connection before returning control. - (FCoE BootBIOS) FCF CEE parameters for Boot from SAN configuration are now saved properly.
Interoperability Since Previous Release:
- Added support for switch-independent multichannel mode. - Added support for IBM Virtual Fabric 10Gb RackSwitch firmware 6.8.1.0. - Added support for IBM Virtual Fabric 10G Switch Module firmware 6.8.1.0. - Added support for Fibre Channel over Ethernet (FCoE) on rack systems. - Added support for iSCSI hardware offload on rack systems. - Added support for Cisco Nexus 5000-series switches.
=============================================== Change History =============================================== Document Name: Change History Document Status: IBM General Avalibility Document Version: 3.2 Latest Driver Version: 3.2.0.0 Document Updated: 01/14/2013 Product: Brocade FC/NIC/CNA
=================================================
Please visit www.brocade.com/hba for full documentation, additional drivers, and management applications.
Version 3.2.0.0 Release for FC/NIC/CNA
New Features and Feature Enhancement: - BB Credit Recovery - Forward Error Correction (FEC) - Diagnostic Port (D-Port) - LUN Level IO Latency/Stats - UCM (Unified Configuration Manager) - Windows Network Performance and scalability enhancement
Fixes or enhancements: - For Brocade 8x5/4x5, I/O interrupt latency values are dynamically updated. Changes are effective for all the ports on the given adapter. - Addressed infrequent PSOD in VMware ESX with iSCSI or VLAN configured traffic in DCB enabled network. - Enhanced BR1860 Tape IO performance. - Improved BR1860 initialization on Xen kernel.
Version 3.1.0.1 Release for 16G FC/NIC/CNA
Adapter Features - Updated code for Brocade 1867 IBM 16G Mezzanine Fabric Adapter.
HBA - Fibre Channel 16G Support
Fixes and Enhancements: N/A
Version 3.0.3.1 Initial release for 16G FC/NIC/CNA
Adapter Features - Initial support for Brocade 1867 IBM 16G Mezzanine Fabric Adapter.
HBA - Fibre Channel 16G Support
Fixes and Enhancements: N/A brcd_fw_cna_3_2_0_0_linux_32-64_chg
IBM (x3400 M2/M3 / x3500 M2/M3) uEFI Flash Update Version 1.15(BuildID Y4E160A) - Suggested (Be aware to check the change history for any critical updates) Change History
Version 1.15 - BuildID: Y4E160A - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed: - Incorporated Microcode Update (MCU) M03106A5_00000019 (Nehalem) and M03206C2_0000001A (Westmere) to address Intel Erratum BT248 for System Resets with 32-bit (PAE Enabled) Guest OS and VT FlexPriority enabled. For more information, refer to IBM RETAIN Tip H21370. - Incorporated Microcode Update (MCU) M03206C2_0000001A (Westmere)to address Intel Erratum BD131 Intel Xeon X5675, X5687, X5690 6-core Westmere-EP Processors. For more information, refer to IBM RETAIN Tip H21371.
Enhancements:
Version 1.14 - BuildID: Y4E159A - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed: - Updated README for new year 2013
Enhancements: - Added confirmation message for Reset System option - Intel Memory Reference Code Release 2.50 - Improved handling of memory in high stress application/usage
Version 1.13 - BuildID: Y4E158A - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed: - Fix system can't complete shutdown when a serial modem is attached - Somtimes pDSA image can not boot successfully - Fixed CPU C-state Limit ACPI C2_C3 test fail
Enhancements: - iFlash 1.12.19 update
Version 1.12 - BuildID: Y4E157A - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed: - Limited Admin Access within F1 allows POP setup
Enhancements: - Intel Memory Reference Code Release 2.40 - Added Limit Boot Attempts ported - Added VLAN ID support
Version 1.11 - BuildID: Y4E156A - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed:
Enhancements: - Upgraded SMBIOS type 9 and type 41 to version 2.6. - Added SMBIOS type 11 structure to support slot group/bus/device/function information. - Intel Microcode Update SRV_P_108
Version 1.10 - BuildID: Y4E154A - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed: - Fix Corrupted Iscsi Attempt List issue - Fix iSCSI boot issue - Fix reusing memory after free call issue - Fix CRTM warning message does not appear after flashing uEFI - Address a potential issue relates to direct device assignment in Intel Virtual Technology application
Enhancements: - Update Intel Memory Reference Code Release 2.30 - Update Intel Xeon 56xx Processor Microcode to Revision 00000014 - F1 Network page update - Add CRTM Info at Setup Menu
Version 1.09 - BuildID: Y4E152A - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed: - Westmere:No LEDs or Logs from CPU Type Mismatch - Port Hii fixes from EDKII to Thurley (pre-req for IPv6)
Enhancements: - Initial port of IPv6 for Thurley platfoms
Version 1.08 - BuildID: Y4E150C - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed: - Fixed memory multi-bit error event can't be deasserted after re-enable - Fixed IMM Network Settings have not been saved if reset IMM immediately - Disable propagation of Intel VT-d faults as fatal errors to avoid guest VM to cause the entire system to crash. - Fixed iMM backup flashing behavior is misleading - Fixed hang when updating FLASH from version 1.01 directly to version 1.07
Enhancements:
Version 1.07 - BuildID: Y4E150A - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed: - Update VPD extraction from IMM to strip trailing blanks from buildid
Enhancements: - Add Out-of-band PXE Configuration - Renaming of output files to add version information. - Re-enable disabled DIMM while AC Power Cycle. - Reverse F1 Setup Event Log number order and change the number format.
Version 1.06 - BuildID: Y4E149A - Critical ------------------------------------------------- Problem(s) Fixed: - Fixed Misc errors in boot order management - Fixed prompt uncompleted rectangle after saving IMM Network settings - To correct an Intel(R) Xeon(R) 5600 series processor's internal circuit marginality issue, that could cause false memory errors when the C6-state is enabled
Enhancements: - Update Intel Westmere Memory Reference Code to V2.21 - Update Intel Westmere QPI Reference Code to V1.85 - Add IMM IP6 enablement code to Setup
Version 1.05 - BuildID: Y4E148B - Critical ------------------------------------------------- Problem(s) Fixed: * Fixed Turbo mode cannot work under Performance Mode * Fixed low HDD performance while install HDD at Bay2 or Bay3 * Fixed issue where UEFI SYSTEMS WITH HBAs AND > 2 TB LUN MAY HAVE DATA ERRORS. Please refer to RETAIN tip number: H16222 or MIGR-5084554 for additional details. * Fixed iMM HostName can not change under UEFI setup menu. * Fixed CPU which not support Turbo mode but still show enable/disable in Performance/Acoustic/Power Efficiency mode. * Fixed load default settings in UEFI setup menu may cause some settings hidden until system restart.
Enhancements: * Memory Sparing Mode support (Only for Intel Xeon Processor 5600 series) * 16GB DIMM support
Version 1.04 - BuildID: Y4E145D - Critical ------------------------------------------------- Problem(s) Fixed: * Fixed issue where the system can hang following a UEFI flash, due to a numeric configuration setting getting corrupted when the new UEFI image no longer supports the value.
Enhancements: * Update Intel 56xx Processor Microcode to version 0x0000000C
- Setup * Enable setting of processor 'Data Reuse' option via ASU for high performance computing configurations
Version 1.03 - BuildID: Y4E145B - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed: - General * Fix system has incorrect Pcap_min and Pcap_max values after rebooting. * Fix Win2K8 displayed Diagnostic partition * Fix Memory mirror setting under standalone become not smooth. * Fix system hang reset but No blue screen * Virtual machine failed to install with uefi 41T * Intel Framework Update 8.6.4.1.W1.0 * Fix core select item shows 4,5 when installed 4core CPU * Fix uEFI "Turbo Mode" is sitll working when CPU doesn't support it * Fix missing CPU2 L1 Cache info * Fix incorrect Cache Memory in Inventory * Fix the amount of CPU package 1 cores on Westmere is incorrect * Fix adapter Option ROM menu can not show slot7 or slot8 * Fix Blade/UEFI: DisA SAS uEFI "appears" 2 reboot w/ 2 splsh screens * Fix L3 Cache shows wrong sizes in SMBIOS (Type 7) * Hang during legacy PXE boot when MAC address is disabled in PXE configuration * PXE VLAN settings do not persist across boot cycles * Help text for onboard device settings was not clear * Early video shuts down during POST * SAS topology was ignored when it was available * VPD string content was not consistent across boot system firmware releases * Processor Turbo mode was not being enabled properly leaving it disabled * Correct the Version in SMBIOS type2 and type3. - Setup: * Implement ASU lacks setting to set execute disable bit setting - Memory RAS * Incorrect DIMM is called out for double bit error in mirrored mode * 2DPC 8GB Qualified DIMMs display inconsistently in Setup * SMBIOS Type 17 structure displays 10 memory banks * Improve reporting of memory related CATERRs * Correct a potential memory error problem caused by demand scrubbing collisions
Enhancements: - Add BCM5716 support - Add Westmere 1.5V Memory Strategy PCR support - Create XML entries for Westmere features/options - Update processor core count settings for Westmere processors. - Implement Intel Westmere Reference Code Release p2.50 - Update Intel Memory Reference Code to V2.11 - Update fpm for westmere - Update Intel Framework Code to Release 8.6.4.1.W1.0 - Updrade TianoCore EDK support to version 1.05.05 - Upgrade Broadcom NIC driver support to version T.5.0A.3.1 - Setup * Allow L1 power state to be disabled to improve system performance * Add QuietBoot mode selection
Version 1.02 - BuildID: Y4E131B - Critical ------------------------------------------------- Problem(s) Fixed: - General: * Length reading of PCI info is wrong. * On-board video fails during some legacy mode operations under UEFI - POST: * Hang during early POST (PEI) initialization * Hang during POST when power cycling systems - SMBIOS: * Invalid change in SMBIOS structure data occurs over AC power cycles * SMBIOS blade specific information is missing tables - USB: * May not be able to boot a fixed disk in a USB enclosure * Miscellaneous problems when booting from legacy USB devices - Setup: * Power restore policy is not reset to default setting properly * SEL event log display shows incomplete BMC sensor events * Change Boot Order does not operate correctly * C-states are exposed to OS when package limit is less than C-state * Miscellaneous errors/clarifications in help text * Administrative password dialog accepts 5 letter passwords * Advanced Setup Utility (ASU) is unable to update iSCSI.MacAddress parameter * Advanced Setup Utility (ASU) is unable to autotest. * Remove C0/C1/C7 selections in Advanced Setup Utility (ASU) * Remove Hard Disk 4 in F12 Boot Menu. - pDSA: * Unable to boot when a Sandisk USB key is installed * Memory test only reports the first 256 correctable errors
Enhancements: - Implement feature for Execute Disable bit option Enabled reset requested. - uEFI.SpareErrorThreshold set to protected. - Improve early (PEI) video support for console messages - Enable early power-on support for IMM (requires future IMM update) - Improve DIMM SMBUS recovery mechanism to prevent possible bus hangs and loss of access to DIMM(s) during memory initialization. - Setup: * Allow disablement of legacy USB 2.0 * Add support for controlling UEFI PCI Option ROM execution * Add support for "Embedded Hypervisor" Boot Option.
Version 1.01 - BuildID: Y4E130A - Suggested (Be aware to check the change history for any critical updates) ------------------------------------------------- Problem(s) Fixed: - Fix vGPIO handler memory allocation bug - Correct Blink LED under Broadcom appears to have no function. - Correct Redhat logo missing when boot RHEL5.3 from DVD-ROM. - Correct MR10M on extender PCI-E unable to entry MegaRAID setup utility - Correct the description missing for EIST mode under Operating Modes - Correct value can't be changed while adjust the operating mode - Fix adjust operating mode will make impact on some values - make sure USB info is valid in timer irq - Correct abnormalities in SOL display when running pre-boot Diagnostics - Correct errors in the display of SEL error entries * Incorrect descriptions for IPMI error entries * Display of SEL full message when SEL is not full - Errors when PXE booting with a SAS adapter card installed in the system - Missing help text for Setup IMM configuration - Correct video display problem when installing SLES 11 - Correct a problem setting Setup PackageCState option via ASU - Force reservation of SATA/IDE interrupt even if no hard drive is installed - Add RTOS table to CSM EBDA to support RTOS - Correct improper handling of an interrupt shared with an IDE device interrupt - Correct inability to set 'Physical Presence' for TPM updates - Update the PXE TFTP_GET_FILE_SIZE API interface to return a proper size value instead of a 'load error' response - Correct a problem in which WOL boot options could not be configured - Correct inconsistent text displayed for some SEL messages - Fix an error reporting prioblem in which PCIe errors in some slots were not being reported. - Correct text errors in security information panel displays - Correct simultaneous display of BDS hot keys and password dialog - Correct a problem where boot order information from ASU was not being accepted - Correct a program exception which occurred during boot option configuration - Correct a CSM problem in which the network option ROM is being called with an invalid parameter - Correct a PCI device problem where an unused base address register on a device could cause the resource allocation algorithms to fail resulting in a system hang. - Add a setup option to allow disabling of processor execution.
Enhancements: - Disable on-board VGA when set Active Video to "Add-in Device" and install add-in VGA card. - Add CDROM/DVD Enable/Disable Feature - Add Real-Time OS SMM Support Driver - Add legacy key/mouse support for ehci controllers - Add some legacy variables - Update legacy iscsi rom - Add support for MRC 1.05. - Add CRTM error strings - Add support for forcing planar video option - Add FRU commands to the ipmi library - Implement feature Enable S1 support. - Auto demotion: de-couple C3/C6 based on F1 Setup - Update Intel CPU microcode to release 0011 - Update Intel QPI/Memory Reference Code to release 1.05 - Add setup options to support selection of system power profiles - Add setup option to allow disablement of USB 2.0 support - Add basic video support during PEI boot phase - Update memory error handling support for Pre-boot Diagnostics - Add WHEA error log support - Improve reliability of memory configuration updates
IBM 3Gb SAS HBA v2 BIOS and Firmware Update for Linux BIOS v6.30.02.00, Firmware v1.30.10.00 and uEFI Driver v3.12.00.07
Systems Supported: IBM BladeCenter HS22 (7870)
NOTE TO SERVICE - Reference RETAIN #N/A
NOTE: This change history is common between several of the IBM and LSI Basic or Integrated RAID SAS controllers for BOFM enabled, uEFI systems. Not all levels were released for all controllers.
BIOS Fixes: - Fixed an issue where the controller was hanging during initialization when an adapter was hung in reset with insufficient information to reset itself. - Fixed an issue where the SAS MPT BIOS CU reports wrong array size.
BSD Fixes - Removed the "SAS/SATA missing" warning message when SAS and SATA arrays are present on the same controller. Firmware Fixes - Addressed issue where 6Gb SATA drives will only negotiate at 1.5Gb/s instead of 3Gb/s. - Fixed issue where SAS/SATA mixing errors will occur when the controller is setup to allow mixing of devices. - Fixed issue with large topology of SATA drives where media errors on a single drive will cause one phy to hang after IOs to other drives start to timeout. - Fixed discovery Error 0x2 in maximum topology with SATA devices, - Addressed issue where Credit would be stuck at zero until controller resets resulting in a phy becoming hung and IO failing. Only occurs with very high IO. - Fixed issue where booting to a target LUN greater then 2TB will fail.
Fixes: - Addressed issue with SATA devices where the drive could go missing for several minutes. - Fixed issue where incorrect release of scatter gather list could cause issues with pending IO to missing devices. - Addressed issue where IOs to a host with a bad drive could fail.
Fixes: - Fixed issue where Target mode responds with incorrect WWID after ports are swapped. - Fixed issue with Incorrect/Unexpected discovery errors on RAID storage enclosures. - Fixed issue where device added events are not sent to the host on RAID storage enclosures. - Fixed issue where it is possible for a Incorrect/Duplicate Device handle to get assigned to a target that is a SSP Initiator. - Changed IO Delay missing setting to 144 seconds - Fixed problem of the boot order selection not being saved
Fixes: - Changed BIOS text to state an IS Volume creation can be 1 to 10 drives. - Fixed issue with 2TB and above drives where SAS MPT BIOS CU reports wrong array size. - Adjusted NVSRAM access timing to fix an issue that could prevent controller detection during POST. - Addressed an issue that will maintain Target IDs for attached devices to an enclosure if the enclosure is removed for a short time.
Fixes: - Fixed an issue where, after running heavy I/O to NCQ enabled SATA drives, the controller may log false data underruns for read or write I/Os. The PHY on which the I/Os were reported as underrun may eventually lock up.
Fixes: - Fixed an issue where Solid State Drives (SSDs) were not seen after a link reset. - Fixed an issue where direct attached SATA drives were not reported missing after they were removed. This could result in degraded or failed volumes being reported as healthy. - Fixed an issue introduced by new functionality in package 2.50. The issue would cause a dual attached device to be hidden from both the direct connection and the expander connection. - Changed the behavior during drive quiescing/un-quiescing to prevent the drive metadata from being unnecessarily updated. - Fixed an issue where drives might go offline during a firmware update, due to I/O timeouts caused by the length of time needed to update the firmware.
**************************************************************** | | | Tape / Backup RDX firmware update | | | | | | | | IBM Online Tape Drive Update Program | | Revision: 1.10.01.1073 Build Date: 3.3.10 | | | | (C) Copyright International Business Machines Corporation | | 2000-2010 . All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Note: Before using this information and the product it | | supports, read the general information under "NOTICES AND | | TRADEMARKS" in this document. | | | | Updated: 7/27/2010 | | | ****************************************************************
Change History
ver 1.2_00
Updated XML / TML support (SUSE 11)
ver 1.1_01
Updated XML / TML to reflect the correct firmware files
ver 1.1
Updated drive string to include: Imation RDX-USB (in addition to IBM RDX) Updated 'tapedrv' to version 1.10.01.1073 Updated to include more systems Updated to firmware level 43 (3043; 2043)
ver 1.0
RDX firmware update
2041 / 3041 ibm_fw_tape_rd-1_2_linux_32-64_chg
Broadcom Firmware Update Utility for IBM servers and options using the Broadcom NetXtreme and NetXtreme II ethernet adapter.
Version 2.1.9b, March 27th, 2013
2.1.9b has been created to pick latest Broadcom linux Bmapi to fix 49Y7910 reboot issue. There is no fw code level change between 2.1.9a and 2.1.9b.
This package updates the Broadcom firmware for the following items:
package version 2.1.9b Problems Fixed: - The only change is Broadcom linux bmapi to fix 49Y7910 reboot issues. No code level change between 2.1.9a and 2.1.9b.
package version 2.1.9a Problems Fixed: - Changes were made to the boot code, NSCI, fcode, ISCSI, EFI, PXE code for the 49Y7900, 49Y7902(BCM5718).
package version 2.1.8e Problems Fixed: - Changes were made to the UEFI code to fix 49Y7910(BCM57712) issues.
package version 2.1.8d (See brcm_fw_nic_2.1.8d-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 46M6164, 46M6168, 49Y7910 and 81Y3133. - Changes were mande to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168, 49Y4220, 49Y7910 and 81Y3133. - Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168, 49Y4220, 49Y7910 and 81Y3133. - Changes were made to the iSCSI code for the 42C1780, 42C1781, 49Y4220 and 49Y7910.
package version 2.1.7e (See brcm_fw_nic_2.1.7e-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the UEFI code for the 42C1780, 42C1781, 44W4475 , 44W4479 , 44X1940
and 49Y4220. - Added support for the 49Y7910.
package version 2.1.7d (See brcm_fw_nic_2.1.7d-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4465 , 44W4466 , 44W4475 , 44W4479 , 44X1940 , 46M6164 , 46M6168, 49Y4220 and 81Y3133. - Fixed a problem where the MAC addresses for the HS22/HS22V LOM were incorrectly set to zero.
package version 2.1.7c (See brcm_fw_nic_2.1.7c-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 46M6164 and 46M6168. - Changes were made to the NCSI code for the 46M6164 and 46M6168. - Changes were made to the PXE code for the 42C1790, 42C1791, 46M6164, 46M6168, 44W4465 and 44W4466. - Changes were made to the UEFI code for the 42C1790, 42C1791, 46M6164, 46M6168, 44W4465 and 44W4466. - Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220.
package version 2.1.7b (See brcm_fw_nic_2.1.7b-chg_anyos_anycpu.zip for details.) Problems Fixed: - Fixed problem running the PPC firmware update tool on some PPC systems.
package version 2.1.7a (See brcm_fw_nic_2.1.7a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4195, 4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7148, 7149, 7164, 7233, 7234, 7378, 7379, 7380, 7809, 7836, 7837, 7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781, 42C1790, 42C1791, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220 - Changes were made to the NCSI code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4195, 4198, 4199, 4254, 4255, 7145, 7146, 7148, 7149, 7164, 7378, 7379, 7380, 7809, 7836, 7837, 7839, 7870, 7871, 7872, 7944, 7945, 7946, 7947, 44W4475, 44W4479, 46M6164 and 46M6168. - Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220. - Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220. - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220.
package version 2.1.6b (See brcm_fw_nic_2.1.6b-chg_anyos_anycpu.zip for details.) Problems Fixed: - The update tool was modified to fix a problem updating the firmware when certain option cards are installed in the system.
package version 2.1.6a (See brcm_fw_nic_2.1.6a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4195, 4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7148, 7149, 7164, 7233, 7234, 7378, 7379, 7380, 7809, 7836, 7837, 7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220 - Changes were made to the NCSI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790, and 42C1791. - Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220. - Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220. - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220.
package version 2.1.5b (See brcm_fw_nic_2.1.5b-chg_anyos_anycpu.zip for details.) Problems Fixed: - Added iSCSI config update support for mfg.
package version 2.1.5a (See brcm_fw_nic_2.1.5a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the NCSI code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4195, 4198, 4199, 4254, 4255, 7145, 7146, 7148, 7149, 7164, 7378, 7379, 7380, 7809, 7836, 7837, 7839, 7870, 7871, 7872, 7944, 7945, 7946, 7947, 44W4475, 44W4479, 42C1790 and 42C1791 - Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220. - Changes were made to the IPMI code for the 7141, 7144, 7233, 7234, 7901 and 7902.
package version 2.1.4a (See brcm_fw_nic_2.1.4a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168. - Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168.
package version 2.1.3c (See brcm_fw_nic_2.1.3c-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the iSCSI code for the 42C1780 and 42C1781. - Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168. - Changes were made to the boot code for the 46M6164 and 46M6168.
Enhancements: - Added version check to prevent firmware updates of code that is not newer than already installed code. - Added "-force" command line option to allow forcing the firmware update.
package version 2.1.3b (See brcm_fw_nic_2.1.3b-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7233, 7234, 7378, 7379, 7380, 7836, 7837, 7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781, 44W4475, 44W4479 and 44X1940. - Changes were made to the NCSI code for the 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 4254, 4255, 7145, 7146, 7378, 7379, 7380, 7836, 7837, 7839, 7870, 7871, 7944, 7945, 7946, 7947, 44W4475 and 44W4479. - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 44W4475, 44W4479 and 44X1940. - Changes were made to the UEFI code for the 42C1780, 42C1781, 44W4475, 44W4479 and 44X1940. - Changes were made to the iSCSI code for the 42C1780 and 42C1781.
package version 2.1.3a (See brcm_fw_nic_2.1.3a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the PXE code for the 26K4842, 39R8624, 39Y9306, 39Y9310, 42C1600, 42C1632, 46M6164, 46M6168, 44W4465, 44W4466, 73P9030, 22P7801, 31P6301, 31P6401, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 42C1790, 42C1791, 73P3501, 73P4001, 73P4101 and 73P4201. - Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790, and 42C1791. - Changes were made to the NCSI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790, and 42C1791. - Changes were made to the boot code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790, and 42C1791.
package version 2.1.1c (See brcm_fw_nic_2.1.1c-chg_anyos_anycpu.zip for details.) Problems Fixed: - none.
Enhancements: - Added support for the 1949, 4254, 4255, 7378, 7379, 7380, 7871, 7944 and 7945.
package version 2.1.1b (See brcm_fw_nic_2.1.1b-chg_anyos_anycpu.zip for details.) Problems Fixed: - Fixed problem where the firmware update failed to run correctly on RHEL5u4-XEN.
package version 2.1.1a (See brcm_fw_nic_2.1.1a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1885, 1913, 1914, 1915, 1936, 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 7141, 7144, 7163, 7233, 7234, 7809, 7836, 7837, 7839, 7870, 7901, 7902, 7946, 7947, 7978, 7979, 7995, 7996, 7997, 8853, 8877, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 39Y6066, 42C1780, 42C1781, 42C1790 and 42C1791. - Changes were made to the NCSI code for the 1936, 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 7809, 7836, 7837, 7839, 7870, 7946, 7947, 44W4465, 44W4466, 44W4475, 44W4479, 42C1790 and 42C1791. - Changes were made to the PXE code for the 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 39Y6066, 42C1780, 42C1781, 42C1790 and 42C1791. - Changes were made to the UEFI code for the 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 42C1780, 42C1781, 42C1790 and 42C1791. - Changes were made to the iSCSI code for the 42C1780 and 42C1781.
Enhancements: - Added support for the 46M6164 and 46M6168.
package version 2.1.0a (See brcm_fw_nic_2.1.0a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1936, 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 7141, 7144, 7233, 7234, 7836, 7837, 7839, 7870, 7901, 7902, 7946, 7947, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479 and 44X1940. - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479 and 44X1940. - Changes were made to the ISCSI code for the 42C1780 and 42C1781.
package version 2.0.9h (See brcm_fw_nic_2.0.9h-chg_anyos_anycpu.zip for details.) Problems Fixed: - Removed the minimum boot code level check for the 44W4465 and 44W4466.
Enhancements: - Added support for the 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 7836, 7837, 7839 and 9233.
package version 2.0.9g (See brcm_fw_nic_2.0.9g-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the UEFI code for 42C1780, 42C1781, 42C1790, 42C1791, 44W4465 44W4466, 44W4475, 44W4479 and 44X1940. - Fixed the problem where the PXE code for the 44W4465 and 44W4466 failed to update under 64bit Linux.
Enhancements: - Added support for the 7946 and 7947.
package version 2.0.9f (See brcm_fw_nic_2.0.9f-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7141, 7144, 7233, 7234,
7940, 7941, 7971, 7972, 7978, 7979, 7985, 7995, 7996, 7997, 8853, 8877, 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479. - Changes were made to the NCSI code for the 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479. - Changes were made to the PXE code for 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479.
Enhancements: - Added support for the 1936, 7870 and 44W4475. - Added UEFI code for 42C1790, 42C1791, 44W4465, 44W4466, 44W4479 and 44X1940.
package version 2.0.9e (See brcm_fw_nic_2.0.9e-chg_anyos_anycpu.zip for details.) Problems Fixed: - Added a bnx2 device driver version check for version 1.6.6b or greater.
package version 2.0.9c (See brcm_fw_nic_2.0.9c-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1885, 1915, 7901, 7902, 7971, 7972, 7995, 8853 and 44W4479. - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781 and 44W4479. - Changes were made to the iSCSI code for the 42C1780 and 42C1781 - Changes were made to the NCSI code for the 44W4479.
Enhancements: - Added support for the 44X1940.
package version 2.0.8f (See brcm_fw_nic_2.0.8f-chg_anyos_anycpu.zip for details.) Problems Fixed: - Fcode support was removed for the PXE code for the 44W4465 and 44W4466. This change does not result in a change in the PXE code version number. - Changes were made to the PXE code for the 39Y6066, 42C1780 and 42C1781 to fix a problem where some systems hang when loading PXE code.
package version 2.0.8e (See brcm_fw_nic_2.0.8e-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781 and 44W4479. - Changes were made to the IPMI code for the 7141, 7144, 7233 and 7234. - Changes were made to the UMP code for the 7901 and 7902.
Enhancements: - Added support for the 6388, 7942, 44W4465 and 44W4466.
package version 2.0.8d (See brcm_fw_nic_2.0.8d-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 7141, 7144, 7233 and 7234.
Enhancements: - Added support for the 42C1780 and 42C1781.
package version 2.0.8c (See brcm_fw_nic_2.0.8c-chg_anyos_anycpu.zip for details.) Problems Fixed: - None.
Enhancements: - Added support for the 7901 and 7902
package version 2.0.8b (See brcm_fw_nic_2.0.8b-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the PXE code for the 39Y6066.
Enhancements: - Added support for the 44W4479.
package version 2.0.8a (See brcm_fw_nic_2.0.8a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7141, 7144, 7971, 7972, 7978, 7979, 7985, 7995, 7996, 7997, 8853, 8877, 9228, 9229, 9230 and 39Y6066. - Changes were made to the ASF code for the 6218, 6223, 6225, 6227, 6228, 8488, 8648, 9228, 9229, 9230. - Changes were made to the UMP code for the 39Y6066. - Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401, 39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600, 42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030. - Changes were made to the IPMI code for the 1916, 8014 and 8028.
Enhancements: - Added support for the 7233, 7234, 7940 and 7941.
package version 2.0.7 (See brcm_fw_nic_2.0.7-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401, 39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600, 42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030.
Enhancements: - Added support for the 1916, 8014 and 8028.
package version 2.0.6 (See brcm_fw_nic_2.0.6-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1913, 1914, 7141, 7143, 7144, 7978, 7979, 7996, 7997, 8877 and 39Y6066. - Changes were made to the UMP code for the 39Y6066. - Changes were made to the PXE code for the 39Y6066.
package version 2.0.5 (See brcm_fw_nic_2.0.5-chg_anyos_anycpu.zip for details.) Problems Fixed: - None
Enhancements: - Added support for the 4190, 4191, 4192, 4193, 4194, 4367 and 4368.
package version 2.0.4 (See brcm_fw_nic_2.0.4-chg_anyos_anycpu.zip for details.) Problems Fixed: - None
Enhancements: - Added support for the 7141, 7143 and 7144.
package version 2.0.3 (See brcm_fw_nic_2.0.3-lin-win-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7971, 7972, 7978, 7979, 7985, 7995, 8853, 8877, 39Y6066. - Changes were made to the IPMI code for the 1879, 1880, 1883, 1884, 1887, 4362, 4363, 4364, 4365, 4366, 7362, 7364, 7365, 7367, 7973, 7974, 7975, 7976, 7977, 7981, 7984, 7986, 8485, 8490, 8491, 8832, 8835, 8837, 8840, 8841, 8843, 8848, 8849, 8850, 8863, 8864, 8865, 8866, 8872, 8874, 8878, 8879. - Changes were made to the ASF code for the 6218, 6223, 6225, 6227, 6228, 8488, 8648, 9228, 9229, 9230. - Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401, 39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600, 42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030.
package version 2.0.0b (See brcm_fw_nic_2.0.0b-nx-nx2-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changed the firmware update process to NOT reset the ethernet devices during the firmware update process.
package version 2.0.0 (See brcm_fw_nic_2.0.0-nx-nx2-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the UMP (Universal Management Port) code for the 1885, 7971, 7972, 7995 and 8853.
package version 1.1.1 (See brcm_fw_nic_1.1.1-nx-nx2-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1879, 1880, 1887, 4347, 4348, 4362, 4363, 4364, 4365, 4366, 6218, 6223, 6225, 6227, 6228, 7969, 7973, 7974, 7975, 7976, 7977, 7992, 8485, 8486, 8488, 8490, 8491, 8648, 8837, 8840, 8841, 8849, 39Y6098, 39Y9306, 42C1600, 42C1632 and 73P3501. - Changes were made to the IPMI code for the 1879, 1880, 1887, 4362, 4363, 4364, 4365, 4366, 7969, 7973, 7974, 7975, 7976, 7977, 7992, 8485, 8490, 8491, 8837, 8840, 8841 and 8849. - Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401, 39R8624, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600, 42C1632, 73P3501, 73P4001, 73P4101, 73P4201 and 73P9030.
package version 1.1.0 (See brcm_fw_nic_1.1.0-nx-nx2-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the Boot Code for the 1913, 1914, 4347, 6218, 6223, 6225, 6227, 6228, 7969, 7971, 7972, 7978, 7979, 7985, 7995, 8486, 8648, 8853, 8877, 9228 and 9229. - Changes were made to the ASF code for 6218, 6223, 6225, 6227, 6228, 8648, 9228 and 9229. - Changes were made to the PXE code for the 39Y6066. - Changes were made to the
Enhancements: - Added support for the 1879, 1880, 1883, 1884, 1887, 1913, 22P7801, 31P6301, 31P6401, 39Y9306, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9310, 4348, 4366, 7362, 7364, 7365, 73P3501, 73P4001, 73P4101, 73P4201, 7992, 7995, 8488 and 9230.
package version 1.0.0 (See brcm_fw_nic_1.0.0-nx-nx2-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 8832, 1914, 7971, 7972, 7978, 7979 7985, 8853 and 8877. - Changes were made to the UMP (Universal Management Port) code for the 7971, 7972 and 8853. brcm_fw_nic_2_1_9b_linux_32-64_chg
=============================================== Change History =============================================== Document Name: Change History Document Status: IBM General Avalibility Document Version: 3.2 Latest Driver Version: 3.2.0.0 Document Updated: 12/18/2012 Product: Brocade FC HBA / FCoE CNA
=================================================
Please visit www.brocade.com/hba for full documentation, additional drivers, and management applications.
Version 3.2.0.0 New Features and Feature Enhancement: - For Brocade 8x5/4x5, I/O interrupt latency values are dynamically updated. Changes are effective for all the ports on the given adapter. - Addressed infrequent PSOD in VMware ESX with iSCSI or VLAN configured traffic in DCB enabled network. - Enhanced BR1860 Tape IO performance. - Improved BR1860 initialization on Xen kernel.
Fixes and Enhancements: - BB Credit Recovery - Forward Error Correction (FEC) - Diagnostic Port (D-Port) - LUN Level IO Latency/Stats - UCM (Unified Configuration Manager) - Windows Network Performance and scalability enhancement
Version 3.1.0.0 Key features and enhancements supported for the software release 3.1.0.0 include the following:
New Features: - D-port support between Brocade 16Gb HBAs and Brocade 16Gb FC switch platforms with FOS v7.0.1 and later releases - FC-AL support for direct attach to storage - Ability to assign minimum bandwidth to each vNIC - Queue Depth adjustment - FC QoS set by percentage - Performance enhancements in Ethernet drivers - Technology Preview support of 1860 HBA on Power PC architecture
Fixes or Enhancements: - Resolved an issue where HCM Agent may not start if BR1860 adapter is configured in NIC mode. - Improved stability with Hyper-V and Teaming configurations. - Resolved I/O errors when running traffic with Brocade HBAs(models 415, 425, 815, 825, and 804), if the server’s PCI max read request size is configured to be 2K or greater with PCI Gen2x8.
Version 3.0.0.0 Fixes and Enhancements: - Added support for Brocade 1860 AnyIO Fabric Adapter (User configurable port mode - FC or NIC or CNA) - Added Fibre Channel 16G Support - Enabled Fabric Assigned Address in Fibre Channel Fabric - Added PF based Virtualization – vHBA - Enhanced CLI, HCM GUI and CIM support in inbox drivers. - Added PF based Virtualization - vNIC - Added iSCSI over DCB Support - Added Multiple Tx Priority Queues Support - Added SNMP Support
Version 2.3.0.3 Fixes and Enhancements: - Enhanced SNIA API to report port speed of 4 and 8Gbps in SNIA format. - Enhanced XIV array interoperability that addresses a data integrity corner case. - Enhanced the transmit path handling in Linux Network Driver to avoid a corner case that could lead to transmit path stall. - Enhanced the Linux Adapter Software installer script to update the initrd with the correct name even when there are multiple copies of the OEM specific initrd(s).
Version 2.3.0.0 Enhancements: - Enabled HP DL120 server to support Boot over SAN with two Brocade HBAs installed. - Improved network driver CPU and performance optimization. - Enabled automated target and LUN discovery of enterprise HDS storage once LUN masking has occurred. - Improved Tivoli interoperability to meet device display requirements.
Version 2.2.0.1 Added capability to handle ADISC frames. Unhandled ADISC use can cause SAN boot failure when booting from IBM storage array.
Version 2.2.0.0 Adds support for bootcode updates to Bladecenter 10G Converged Network Adapters
Version 2.1.0.0 Adds support for bootcode updates to 10G Converged Network Adapters
Version 2.0.0.0 Initial release for 4/8G FC HBAs brcd_dd_fc_bfa-3_2_0_0_sles10_32-64_chg
=============================================================================== Emulex FC/FCoE Device Driver for Linux ===============================================================================
Linux FC/FCoE Driver Version 8.2.0.145
Problems Fixed: - Kernel panics with FCoE on HS23 in SLES 11.2 x86_64. Also requires a SLES11.2 kernel update - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service
Interoperability since previous release: - RHEL6.3 GA Kernel
Problems Fixed: - Fixed system crash due to not providing SCSI error-handling host reset handler - Debug helper utility routines for dumping various SLI4 queues - Fix unsol abts xri lookup - Fixed issues with LPe16000 to LPe16000 discovery - Fix driver crash during back-to-back ramp events - Reregister VPI for SLI3 after cable moved to new Saturn port - Fix log message 2597 displayed when no error is detected - Fixed FCP LOG for easier Finisar trace correlation - Fix kernel panic when going into to sleep state - Fix error message displayed even when not an error - Fix Read Link status data - Fix unable to create vports on FCoE SLI4 adapter - Fix initiator sending flogi after acking flogi from target - Fix the case where an array controller does not apply FCP priority rules - Added support for handling SLI4-port XRI resource-provisioning profile change - Change default DA_ID support from disabled to enabled - Fix bug with driver unload leaving a scsi host for a vport around - Update copyright date for files modified in 2012 - Fix bug with mailbox handling of REG_VFI and cable pull - Used PCI configure space read to flush PCI function reset register write - Update copyright date for files modified in 2012 - Fixed system panic when extents enabled with large number of small blocks - Fixed system panic during EEH recovery - Fix resource leak when acc fails for received plogi - Fix SLI4 driver module load and unload test in a loop crashes the system - Fix missing CVL event causing round-robin FCF failover process to stop - Fix deadlock during adapter offline request - Fix same RPI registered multiple times after HBA reset (CR 127176) - Fix driver handling of XRI Aborted CQE response - Fix port and system failure in handling SLI4 FC port function reset - Fix bug with driver not sending a LOGO with vport delete (CR 126625) - Fix KERNEL allocation while lock held - Make BA_ACC work on a fully qualified exchange - Fix for SLI4 Port delivery for BLS ABORT ACC - Fix ndlp nodelist not empty wait timeout during driver unloading - Fix mailbox and vpi memory leaks - Fix for FDISC failures after firmware reset or link bounce (CR 126779) - Limit what management ELS and CT commands can be issued according to latest management specification - Fix for driver using duplicate RPIs after 16Gb/s adapter port reset - Fix discovery problem when in pt2pt - Fixed failure in handling large CQ/EQ identifiers in an IOV environment - Fix Locking code raises IRQ twice - Fix driver not returning when bad ndlp found in abts error event handling - Added more driver logs in area of SLI4 port error attention and reset recovery
- Fix bug with driver returning the wrong ndlp - Fix driver behavior when receiving an ADISC - Fixed PCI loopback diagnostic test through hbaCmd on SLI4 port failure - Fixed unbounded firmware revision string from port caused the system panic - Fix driver does not reset port when reset is needed during - Changed SLI4 FC port internal loopback from outer serDes to inner internal - Fix ELS FDISC failing with local reject / invalid RPI - Fix REG_RPI fails on SLI4 HBA putting NPort into NPR state - Fix NMI seen due to CQE starvation - Fixed SLI4 FC port obtain link type and number dependent on link connection - Fixed SLI4 FC port internal loopback without SFP and external link/loopback plug - Fix driver incorrectly building fcpCdb during scsi command prep - Fixed FCP EQ memory check prevent initialize to single interrupt vector case - Fixed system panic during EEH recovery on SLI4 FC port - Fix FLOGI fails with invalid RPI (0x04) after connecting to a arbitrated loop - Fix ELS SCR failing with local reject / invalid RPI - Fix SLI4 port failures after firmware reset or dump - Fix port reset log messages indicate error when no error is seen - Fixed an issue where HBQ buffers are uninitialized in the base driver - Fixed missing hbalock protection on setting/clearing bit in phba->link_flag - Fixed logging mailbox error log messages during SLI4 FW download using HbaCmd - Fixed illegal state transition during driver unload - Fixed SLI4 FC port Internal and External loopback diagnostic tests - Fix bug with driver erroneously logging a kernel error message - Fix a crash while deleting 256 vports - Fix vport never finished discovery if switch runs out of resources - Fix kernel build warnings - Fix kernel panic when putting board in offline state twice - Fix PCI read failure looks like a over temperature event - Fixed driver event reporting to mgmt on error attention due to forced dump - Fix not displaying firmware rev for BE UCNA boards - Fixed ABTS failure logic not rediscovering targets - Fix bug with driver not byte swapping extended mailbox data - Fix premature ndlp cleanup after second target LOGO - Fix Link pull causes I/O failures - Add loop support for sli4 fc - Fixed OCM failing COMN_READ_OBJECT and COMN_WRITE_OBJECT mailbox pass-through - No longer read fcoe parameters if board is not fcoe - Added restore state and error log when sysfs board_mode attribute access failed - Added support for SLI4_CONFIG non-embedded COMN_GET_CNTL_ADDL_ATTR pass-through - Added support for SLI4 FC port persistent linkdown through config region 23 - Fix for ABTS. Do not free original IOCB whenever ABTS fails - Fixed Linux driver inconsistency in reporting FC host port-state through OCM - Fix firmware upgrade attempt on unsupported adapter - Fix incomplete message number 2889 - Fix system crash when Lancer fails to initialize - Fixed fcpi param length when not using an sgl - Fix virtual fabrics bit set in FLOGI incorrectly - Fix unsupported link speed accepted by SLI4 port - Incremented minor management version to reflect additional "protocol" sysfs attribute - Fix kernel build warnings - Modify WQ handling to use entry_repost - Added a sysfs attribute "protocol" to report SLI4 port link protocol type - Added SLI4 INTF_TYPE and SLI_FAMILY as sub-field to the fwrev sysfs attribute - Added structure to support T10 DIF in SLI4 - Fix performance slowed due to too many register accesses - Fix a possible driver crash when cfg_fcp_eq_count is zero - Fixed non-embedded COMMON_GET_CNTL_ATTR mbox command failed with status 0x4 - Changed the way of SLI4 device detecting physical port name - Fixed FCP policy exchange management rule parsing - Add new check to lpfc_decode_firmware_rev to handle releases that have an 'X' - Fixed RPI leaks in ELS protocol handling - Fix kernel crash during boot with SLI4 card installed - Fixed NPIV FDISC failure on SLI4 if-type 2 ports - Moved fcp policy structs - Fixed driver failed to follow IP reset procedure in SLI4 error attention handler - Fixed fcp underrun reporting - Fix sysfs lists fabric name for port that has been disconnected from fabric - Added support for policy exchange management - Changed the timeout to 300 seconds for SLI_CONFIG (0x9B) mailbox command - Fixed a driver handling IP reset issue when PCI read return error - Fixed casting problem in calculating tx_words statistics - Fixed compiler warning due to uninitialized local variable - Added proper error code return for libdfc calling API to make proper decisions - Fix sli4 mailbox status code. Management software has dependencies - Made proper error code return for libdfc calling API to make proper decisions - Made error log include PCI BAR bitmap from kernel when enable PCI device failed - Fixed incomplete scsi messages displayed - Change log message in lpfc_sli_set_dma_length() - Completed missed FCF priority failover - Fixed not recovering SLI port in handling error attention with RN bit set - Fixed two crash cases when unsolicted ELS ECHO_CMD is received - Fix direct connect does not come up for SLI4 FC ports - Fixed long wait when firmware reset to a SLI port without required privilege - Fix driver firmware update to match new firmware image format - Fix SLI4 CT handling for sequences > 4K - Fixed handling of unsolicited frames for vports - Fixed crash when aborting els IOs - Fixed handling of CVL for vports - Fix up CT and oxid/rxid for unsol rcv frames - Fixed mailbox double free panic - Added fcf priority record selection for fcf failover - Fixed compiler warning for putting large amount of memory on stack - Fixed hbacmd listhbas took very long time when remote initiators present in zone - Fixed driver build not building in debugfs even if kernel CONFIG_DEBUG_FS=y is set - iDiag added SLI4 device PCI BAR memory mapped reigster access methods - iDiag changed command structure data array indexing by using macro defines - Ported iDiag pass-through multi-buffer mbox command capture and dump extension - Ported new SLI4 FC device loopback test and link diagnostic test supports - FLOGI payload has Multiple N_port_ID set when lpfc_enable_npiv clear - Add sysfs logging when writeable parameters are changed - Fixed new ASIC device-mgmt SYSFS pass-through failed multi-buffer fw download - Fixed memory leak due to failure to release mailbox command when completed - Brought debugfs accessing new ASIC extents information into the iDiag framework - Added wait for SLI port status register for readyness following firmware reset - Consolidated duplicating macro definitions - Implement debugfs support for resource extents - iDiag method for read write bitset bitclear access to new ASIC control registers - Fixed failure in pass-through mbox command with multiple number of large buffers - iDiag method for endian explicit dumping at iussue SLI4 mailbox command routine - iDiag ported debugfs method for dumping mbox from SLI4 issue mbox cmd routine - Added request for PCI funndamental reset to support EEH recover on P7 platform - iDiag ported debugfs inline mailbox command capture and dump utility - Fixed failure to enable PCIe AER prevent driver initialize and attach to device - Fix EEH recovery so state is saved after every PCI reset for SLI4 - Moved INIT_LIST_HEAD to the inside of lpfc_mgmt_issue_sli_cfg_ext_mbox routine - New ASIC device management pass-through mbox extension with multi- buffer support - Fix FC Port swap on SLI3 adapters - Fixed Virtual link loss during Face plate failover test - Fix vpi initialization in lpfc_init_vfi - Added driver capability of reseting new ASIC firmware and device from sysfs entry - Added capability of inducing new ASIC firmware dump obj file to flash filesystem - Add firmware upgrade code to driver - Added 100ms delay before driver action following IF_TYPE_2 function reset - Fragment ELS and SCSI SGE lists based on Extent regions - Fixed potential missed SLI4 device initialization failure conditions - Fixed Back to back Flogis sent without a logo - Add model names for new hardware - Fix bug with lpfc driver not updating the wwnn and wwpn after a name change - Set the maximum SGE size to 0x80000000 when HBA does not have any restriction - Fix SLI3 and non-NPIV crashes with new extent code - Fix CT command never completing on Big Endian system - Refactor lpfc_sli4_alloc_extent some more - Restore SLI4_PARAMETER mailbox can fail as nonerror functionality - Do not post RPI Headers to SLI4 port that support extents - Framework for new ASIC device management multi-buffer mbox passthrough support elx_dd_fc_ibm1206-8_2_0_145_sles10_32-64_chg
ServeRAID M and MR10 Series SAS Controller Driver for SLES 10 (also supports MegaRAID 8480 SAS Controller)
Adapters Supported: - ServeRAID M5110 SAS/SATA Controller for IBM System x (81Y4481) - ServeRAID M5110e SAS/SATA Controller for IBM System x - ServeRAID M5120 SAS/SATA Controller for IBM System x (81Y4478) - ServeRAID M5025 SAS/SATA controller (46M0830) - ServeRAID M5016 SAS/SATA Controller for IBM System x (90Y4304) - ServeRAID M5015 SAS/SATA controller (46M0829) - ServeRAID M5014 SAS/SATA controller (46M0916) - ServeRAID M1015 SAS/SATA Controller (46M0831) - IBM ServeRAID MR10il SAS controller (44E8767) - IBM ServeRAID MR10is SAS controller (44E8695) - IBM ServeRAID MR10ie (CIOv) SAS controller (46C7167) - IBM ServeRAID MR10i SAS controller (43W4296) - IBM ServeRAID MR10k SAS controller (43W4280) - IBM ServeRAID MR10M SAS controller (43W4339) - MegaRAID 8480 SAS controller (39R8850)
Version 00.00.06.19 - Suggested ------------------- Fixes: - Fixed an issue where a kernel crash may occur in some cases, when megaraid_sas driver is loaded but controller is not present.
Version 00.00.06.15 - Suggested ------------------- Enhancements: - Add support for fpRead/WriteCapable & fpRead/WriteAcrossStripe
Fixes: - Mask off MFI_FRAME_IEEE, MFI_FRAME_SGL64, MFI_FRAME_SENSE64 in megasas_mgmt_fw_ioctl() to prevent memory scribble issues from incorrectly built MegaCli frames. - Fixed reglockFlags for degraded RAID 5/6.
Version 00.00.06.12 - Suggested ------------------- Enhancement - Add support for ServeRAID M5016
Fixes - LSI Channel fixes
Version 00.00.04.38 - Non-critical ------------------- - Fixed issue where device driver could print message "kernel megasas: Command pool empty!" when the controller and megaraid driver are idle.
Version 00.00.04.37 - Suggested ------------------- - Fixed issue where the ServeRAID M1015 controller will halt during a OCR. - Fixed issue where OCR will not execute when the physical drives are in a power transition mode. - Fix issue where the ServeRAID M1015 controller will halt with a degraded RAID 5 array during IO.
Version 00.00.04.30 - Non-critical ------------------- - Added support for the ServeRAID M5025 SAS/SATA Controller.
Fixes: - Fixed issue where during IO firmware faults at line : MonTask: line 1193 in file ../../raid/1078dma.c - Fixed issue where After 64 VD's are created using MSM the 'fdisk -l' command does not work. - Fixed issue where the firmware faults at line 739 in file ../../raid/1078main.c when rebooting after a recon. - Fixed issue where the drive partition is no longer present on the OS after importing a foreign configuration. - Fixed issue where Linux does not show the correct size of VD the second time if the 'fdisk -l' command is executed.
Version 00.00.04.17 - Non-critical ------------------- - Added support for the ServeRAID M1015 SAS/SATA controllers. - Added support for the ServeRAID M5000 Series Advanced Feature Key.
Version 00.00.04.10 - Non-critical ------------------- - Added logic to support next-gen SAS2 controllers. - Added support for the ServeRAID M5015 and M5014 SAS/SATA controllers.
Version 00.00.03.23 - Non-critical ------------------- - Added support for the IBM ServeRAID MR10ie (CIOv) SAS controller. - Fixed an issue where, on a Xen kernel with guest OSs running, invoking kdump causes a system reboot. - Fixed an issue that results in a kernel panic when kdump is run on a system with heavy drive I/O.
Version 00.00.03.21 - Suggested ------------------- - Added support for the IBM ServeRAID MR10is SAS controller. - Fixed an issue where a command timeout would occur on a particular SAS hard drive, and would not recover. - Added a shutdown DCMD call to the shutdown routine to ensure a graceful shutdown. - Updated the list of required pre-built binaries. - Fixed an issue the could cause unexpected interrupts. - Fixed an issue where a memory sanity check would sometimes fail for a certain pointer on a 64-bit system, causing some enclosure components to not be seen.
Version 00.00.03.18 - Suggested ------------------- - Added support for the IBM ServeRAID MR10il SAS controller. - Fixed an issue where the OS would not reboot when a rebuild was in progress.
Version 00.00.03.13 - Non-critical ------------------- - Added support the IBM ServeRAID MR10i, MR10k, and MR10M SAS controllers. - Fixed an issue where, on boot to Xen kernel on Red Hat Enterprise Linux (RHEL) 5 64-bit, the user would encounter an “Error 13: Invalid or unsupported executable format” error.
Version 00.00.03.06 - Suggested ------------------- - Added diskdump support for Red Hat Enterprise Linux (RHEL) 3 and RHEL 4. - Set the reply_q_sz value to the maximum number of commands supported by the firmware. - On 2.4 kernels: fixed an issue where, when the system was rebooted, the shutdown routine did not get called; added a notifier for the reboot event and initiated a flush command from the reboot event handler. - Fixed issue where, on RHEL 3 Update 6, the driver would not install on AMD64 systems.
Version 00.00.03.01-1 --------------------- - Initial release ibm_dd_sraidmr_00_00_06_19_sles10_32-64_chg
Multi-boot Image for 4Gb FC HBAs Release Notes Package Version MB_1.90-3
This software license applies only to QLogic customers. QLogic Corporation. All rights reserved.
Table of Contents
1. Version 2. 4Gb BIOS 3. 4Gb EFI 4. 4Gb FCode 5. Trademarks 6. Notices 7. Contacting Support
1. Version
These release notes describe the changes, fixes, known issues, and release details that apply to the multi-boot package for 4Gb HBAs, version MB_1.90. This package is a compressed file that contains:
* BIOS version 2.16 * EFI version 2.27 * FCode version 3.13 * Firmware version 5.03.06
Rev 1.00 Jan.20, 2005 Initial release. Rev 1.01 Feb.18, 2005 Added code to put Port ID of device in IOCB. Rev 1.02 Mar.28, 2005 Added support for Serial Link Control. Addded code to display slot, bus number and function in CTRL-Q utility. Rev 1.03 Apr.18, 2005 Fixed bug when no drives attached and connected to switch. Added code to reset ISP if ISP is paused when ISR is called. Rev 1.04 June 8, 2005 Fixed bug in CTRL-Q utility that caused adapter id to be displayed at invalid id's. Added code to set Write Protect in Flash Status reg. Fixed bug in CTRL-Q utility where EAX reg was being corrupted by timer interrupt routine. Fixed bug in setting up LUN field in IOCB. Fixed bug in not setting port ID when connected to a switch. Rev 1.05 Sept 27, 2005 Changed code to suppress padding firmware version with leading zero's. Fixed bug in setting data direction flags in IOCB for 'seek command'. Changed code to not count device if device disabled by system BIOS. Fixed bug in setting flash Write Protect. Rev 1.06 Oct. 13, 2005 Fixed bug where anykey could invoke Fastutil. Rev 1.09 Nov. 22, 2005 Changed buffer request size to 2056 bytes for 'Report Luns' command. Fixed bug where GAN_NXT IN_ID was not always being set to zero causing GAN_NXT to fail. Rev 1.10 an. 31, 2006 Added check for optional boot mode flag to allow code to configure 1 drive/port when enabled. Bit 6 of host parameters in NVRAM is set to enable this mode. Fixed bug when Spinup-Delay and link is down. Added code to not display Data Rate option in CTRL-Q for QME2462. Rev 1.11 Feb. 7, 2006 Added support for interrupt polling. This option is controlled by bit 7 of NVRAM Host Parameters and by new Advanced Settings option in CTRL-Q. Rev 1.12 Feb. 21, 2006 Changed format of PnP string to display when Opt Boot Mode enabled in NVRAM. Added check for ELS reject status from Login IOCB. Rev 1.13 Apr. 04, 2006 Fixed bug in not always setting port id for logout IOCB. Changed code to support up to 16 adapters and 16 drives. Rev 1.14 Apr. 17, 2006 Changed code to ignore CLP '_hss' string. Rev 1.15 Apr. 20, 2006 Added code to wait for Login to complete when login pending status detected. Rev 1.16 May. 4, 2006 Fixed bug in not setting up Luns/Target in CTRL-Q. Added code to support Restore Default option CLP string (PCI3.0 BIOS only). Changed timeout value waiting for Linkup status from 6 seconds to 23 seconds. Rev 1.17 June 29, 2006 Added support for restoring defaults using CLP string (Pci3.0 only). Optimized code waiting for Linkup status. Added code to use Memory Map I/O for PCI express. Added code to check for correct Max Payload Size on QLE2464. Rev 1.18 July 19, 2006 Added code to load Nec switch port 1 and 2 pci config regs offset 68h with port 0 config offset 54h value. Fixed bug where task attributes in IOCB type 7 were not always being initialized. Rev 1.19 July 24, 2006 Fixed bug in CTRL-Q utility configuring Luns using Report Luns data when lun list has more lun entries after lun 255. Rev 1.20 Aug 2, 2006 Added code to support QLE2xx. Rev 1.21 Aug 24, 2006 Fixed bug in CTRL-Q cursor positioning for some user input displays. Rev 1.22 Sept 11, 2006 Added support for 'exit' CLP string. Changed CLP string to support new format: 'PermanentAddresses' was changed to 'PermanentAddress. Rev 1.23 Oct 16, 2006 Fixed bug in not setting rc_hba when different adapter types installed in system. Rev 1.24 Nov 29, 2006 Removed Extended Error Logging option from CTRL-Q. Removed code to use Memory Map I/O for PCI express. Rev 1.25 Dec 12, 2006 Added code so that set Defaults only to restores factory setting when value was modified by CLP string Rev 1.26 Dec 20, 2006 Fixed issue with the handling of CLP WWNN string. Also added code to always set firmware nodename optiom when set Default CLP is received. Rev 1.27 Feb. 26, 2007 Added support for Set Capabilities CLP string. Added code to load PLX switch port 1 and 2 pci config regs offset 68h with port 0 config offset 54h value (this is same code used for NEC switch). Rev 1.28 Apr. 12, 2007 Added code to check if need to restore HBA default portname. Added check for command fail status after login cmd. Restored code to read block 0 to determine drive geometry. Added NVRAM option (host_params bit 8) to enable support for HP boot order. Fixed bug in handling CLP Set Capabilities data. Rev 1.29 May. 22, 2007 Restored CTRL-Q Lun per Target option and changed text from 'Boot order' option to 'Controller order'. Rev 2.00 Dec. 03, 2007 Added support for ISP2532. Rev 2.01 Jan. 17, 2008 Added support for 1Gb data rate for 4Gb HBA. Rev 2.02 Feb. 18, 2008 Changed code to clear 'Disable Serdes' flag for CLP string Restore Default. Rev 2.03 Mar. 12, 2008 Added support for ISP8423. Added code to support new CLP 'set capability' spec. Rev 2.04 Mar. 23, 2008 Changed code to not used bit 13 of Host parameters. This avoids potential confict with inbox driver. Rev 2.05 Jun. 3, 2008 Added code to allow 2 min for link to come up when spinup delay enabled. Added code to poll for keyboard status. Removed external Loopback test option for ISP8432. Added check if IO support valid. Added check to CLP set_capablity string for the correct HBA port. Rev 2.06 Jun. 18, 2008 Added support for new CLP 'set capability' serial link spec for ISP2532. Rev 2.07 Sept. 3, 2008 Added additional error message for Verify Disk utility when device does not support SCSI cmd 2fh. Add support for Extended HBA CLP strings. Rev 2.07.6 Sept. 12, 2008 Fixed bug with 'restore netport defaults' when restoring NPIV's. Added code to reset ISP before accessing NVRAM the first time. Rev 2.07.8 Oct. 22, 2008 Added support for IDT PCIe switch Fixed bug in restoring NPIV after updating with CLP. Rev 2.08 Oct. 30, 2008 Removed TEST ONLY from BIOS banner. Rev 2.09 Dec. 02, 2008 Added code to save some pci data. Added new option to Advanced Option menu in CTRL-Q for Virtual Fabric Enable/Disable. Rev 2.10 Feb. 24, 2008 Added support for ISP8001 Added check for INT Polling before updating interrupt controller(PCI3.0) Fixed bug where eax register was being corrupted in nvram_config routine. Removed option in CTRL-Q for Virtual Fabric Enable. Fixed cosmetic bug in displaying selectable boot lun in CTRL-Q utility. Rev 2.11 Apr. 28,2009 Fixed issue with setting up Init FW MB command for using Extended Init Control Block Added option in CTRL-Q utility for Primary FCF VLAN ID for ISP8001 HBA. Added code to check version field of Extended ICB. Added code to correctly identify pci switch on 4 port HBA's. Changed code to suppport Loopback mode with new version of FW. Rev 2.12 May, 15,2009 Changed code to handle HSS CLP vendor id 3 same as vendor id 2. Rev 2.13 July 16, 2009 Added code to save backup copy of VPD/NVRAM data. Rev 2.14 Oct 9, 2009 Changed code to use FS segment register instead of GS in find_device routine. Change code to preserve MSB of WWPN Set Capablity CLP when updating WWPN/WWNN. Rev 2.15 Nov 23, 2009 Added code to handle 'About FW' mailbox command timeout. adapter. Rev 2.16 Mar 16, 2010 Fixed bug in not setting Write protect for single port adapter.
Driver Name : Fibre Channel Driver for UEFI Version : 2.27 Date : 05/9/2010 OS platform : N/A FW version : See MultiBoot release notes for FW version. Efiutil Version : 2.86
Table of Contents I. Overview II. Enhancements III. Bug Fixes IV. Known Issues V. Additional Information
I. Overview
The following document provides details of the Fibre Channel UEFI driver version 2.27, Efiutil version 2.86.
II. Enhancements
None
III. Bug Fixes
Driver: * Removed Extra character and NULL string message from HII. (ER71174, ER71175) * Add support for 8GB data rate for 25xx family in HII form. (ER71118) * Add fix in driver to avoid to print driver messages on splash screen during system boot up. (ER71099) * Add support for HII Protocol. (ER55486) * Added fix to allow W2K8 boot from local disk when target is mapped in passive path. (ER70069) * Added fix to diplay firmware version info correctly in HII "Adapter info" menu. (ER71412) * Display error message in HII form if invalid HBA parameter value is set (Execution Throttle). (ER71533) * Fixed a bug that caused VPD version numbers to be displayed wrong. (ER70907) * Add fix for NULL string message displayed on Hx5 system. (ER71771) * The "Enable Loop ID" bit in the HII menu is now set correctly. (ER71885) * Rename "Reconnect and Exit from Main Menu" HII entry to "Exit from Main Menu".
Efiutil: * Add fix to avoid, overwriiting of orignal SERDES file, if user give wrong command. (ER69941) * Added fix to avoid, "unaligned reference fault", while updating flash. (ER69793) * Add support, to ignore locked fileds while updating firmware area. (ER69531) * Add fix to display firmware version correctly. (ER71468) * Add fix to display new firmware version correctly while updating multiboot image. (ER71468) * Add support for 82xx family in Adapter list. (ER69230)
IV. Known Issues
* In the HII menus, Adding/Deleting a Target/LUN will require a reboot for changes to take effect.
V. Additional Information
* Efiutil and the EFI Driver are a matched set. Always make sure that Efiutil and the EFI Driver are from the same release package.
Release Notes for 4Gb FC HBAs (FCode) ================================================================
version 3.13 03/26/10 * Change REV_LEVEL in rev_level.m4 from 3.13b9 to 3.13. Offical Release.
version 3.13b9 03/24/10 * Remove Explicit logout to fabric(FLOGO) in close-hardware, put in v3.13b3. * Restructure fcode source files. Add: isp-init.fth, p3-init.fth, mailbox.fth, properties.fth, structs.fth, regs-isp.fth, regs-p3.fth, utils.fth.
Version 3.13b8 03/09/10 * Add Parameter 1 debug display on login IOCB faliure if debug-logi? is set. * Add force-open-ok? test flag in open method. Default = true(no real change). * Change get-to-params to set boot-wt = 8 secs if boot-wait-time is disabled. * Fix bug in VPD fetch, introduced in v3.13b1. vpd-buf increased to 512 bytes. * Change cbuff back to non instance buffer. Instance has no effect on buffer:.
Version 3.13b7 03/04/10 * Remove Hard-RICS-reset from reset-risc method. Causes problems on QMI2582. * Remove Eddy test= Reset RX-Serdes after 5 secs wait for in isp-fw-ready?. * Make old-sb (old sec-buf) an instance value. Problem on M3000 (ER70453).
Version 3.13b6 03/02/10 * Add Reset RX-Serdes after 5 secs wait for in isp-fw-ready?. Plus add debug.
Version 3.13b5 03/01/10 * Add more debugging in isp-fw-ready?. Print fw-state each time in get-state. * Change getnum to use the 'accept' word and make cbuff an 'instance' buffer:.
Version 3.13b4 02/24/10 * Fix Explicit logout-device IOCB to include the ISP PortID and Port WWN. * Changed debug? flags: 4000= Got-R2H-intr, 2000= IOCB-Dump, 800= FW-Ready-wait.
Version 3.13b4 02/22/10 * Fix Explicit logout-device IOCB to include the ISP PortID and Port WWN.
Version 3.13b3 02/19/10 * Use OpenBIOS Toke Tokenizer to make isp2500/8100/8200. isp2400 uses SUN toker. * Add Implicit logout-all and Explicit logout to fabric in close-hardware. * Add setting the FW ICB link-down-NOS/OLS value for isp2400/2500 (ER67806).
Version 3.13b2 02/11/10 * Change set-boot-wait-time to not affect link-down-to (timeout) for Fujitsu. * Change login-devices to not logout with FC_Initiators. * Change logout-device to use implicit Logout, not explicit. (Fix P3P problem)
Version 3.13b1 02/05/10 * Change set-boot-wait-time to be entered/display in decimal, not hex(Fujitsu). * Added OpenBIOS 'toke' Tokenizer to makefile. Now you can make either version. * Fixed bug introduced in ISP2400 v3.10. Defered word fmw_ofs, never defined.
Version 3.12 01/11/10 * No change to isp2400, fixed SSDID for Sun (SUNW,qlc) CNA QLE8142.
Version 3.11 12/11/09 * No change to isp2400, added support for Sun (SUNW,qlc) CNA QEM8152.
Version 3.10 12/02/09 * Change the name of the top level Fcode file from isp2xxx.fth to ispxxxx.fth. * Change makefile to include the creation of P3+ isp8200.xxxx.fc binaries. * Introduced bug for defered word fmw_ofs, never defined for ISP2400.
Version 3.09 10/26/09 * Change REV_LEVEL in rev_level.m4 from 3.09b1 to 3.09. Offical Release.
Version 3.09b1 10/22/09 * Fix Node-Name-Option bit preservation in restore-default-settings. ER68181.
Version 3.08 10/19/09 * Change REV_LEVEL in rev_level.m4 from 3.08b1 to 3.08. Offical Release. * Remove patch of PCI header image size byte at offset 0x2c from init version. * Fix flash-word! bug introduced in veersion 3.08b1. Affects ISP2400 only.
Version 3.08b1 10/14/09 * Fix default WWNN & WWPN preservation in restore-default-settings. ER67924. * Fix stack bug when link down. Introduced in v3.05 set-phandle word. ER67926. * Add standard properties. Use m4 utility to automaticly create date string. * Add file rev_level.m4 which has the revision level strings only. * Add FCoE & 4Gb IBM mezz cards QMI8142 QMC2462 QMI3472 QMI2472 to imezz? word. * Change messages "Login failed" to "Login Abort". "Error Subcode" to "Subcode". * Re-structure Flash/NVRAM access fnv-wd@/! words for the Netxen P3 integration. * Add 'make nx3031' to makefile for Netxen P3. #ifdef P3 used for delineation.
Version 3.08b1 09/25/09 * Add standard properties. Use m4 utility to automaticly create date string. * Add file rev_level.m4 which has the revision level strings only. * First version with some support for the Netxen P3 CNA.
Version 3.07 09/08/09 * Change version string from 3.07b2 to 3.07. Offical Release for IBM and SUN.
Version 3.07b2 09/04/09 * Fix read-cap16-cmd. Used when the LUN size is >2TB (i.e. #blocks > 32-bits). * Fix disk-test to work with large >2TB LUNs, where the LBA >32-bits.
Version 3.07b1 08/28/09 * Remove command retry when 8048 AEN is received. Caused DMA error found by IBM. This was an old workaround put in vers1.08b2, before IOCB timeouts were set.
Version 3.06 08/19/09 * Change version string from 3.06b6 to 3.06. Offical Release for IBM. * Fix qlgc-debug? option for IBM. Use find-method on IBMs and $find on SUNs.
Version 3.06b6 08/18/09 * Add option for qlgc-debug? in nvramrc. If the diag-switch? is true, then the debug? flag is set is set to the value of qlgc-debug?.
Version 3.06b5 08/18/09 * Add lba64 large disk capability (read-blocks64 write-blocks64) for SUN only. * Add support for QEM3572, SSDID = x172, for SUN only. * Add mbox1 & mbox2 display for 8048 interrupt if debug-asyc? flag (01) is on.
Version 3.06b4 08/13/09 * Fix bug in IBM fcp-luns method for the Controller LUN-0 check, lun0-check.
Version 3.06b3 08/12/09 * Check Inquiry Qualifier field of Controller LUN-0 in IBM fcp-luns method.
Version 3.06b2 08/10/09 * Add more IOCB debugging, Add Erase Response-Queue in mapmem. Had stale data.
Version 3.06b1 08/08/09 * Add more debugging for IOCBs, dma-map-in/out, & wait-for-interrupts.
Version 3.05 08/04/09 * Change version string from 3.05b2 to 3.05 Offical Release for IBM.
Version 3.05b2 08/03/09 * Fix set-fc-address issue found with IBM ioinfo. PortID was not getting set. * Re-structure devicepresent.fth. Add set-phandle to set obp-target & obp-portid
Version 3.05b1 07/31/09 * Fix multiple close issue found with IBM ioinfo utility.
Version 3.04 07/22/09 * Add "ibm,write-supported" property to disk child node, as per IBM's request.
Version 3.03 07/13/09 * No change, affected ISP2500 & ISP 8100 Fcode only.
Version 3.02 05/06/09 * No change, affected Schultz ISP8100 Fcode only.
Version 3.01 04/23/09 * No change, affected Schultz ISP8100 Fcode only.
Version 3.00 04/21/09 * Added more debugging information for AEN 8014.
Version 3.00b8 04/01/09 * No functional change, binary files differ. Only ISP2500 Fcode affected.
Version 3.00b7 03/31/09 * No change, Schultz ISP8100 Fcode only.
Version 3.00b6 03/04/09 * Change boot-wait-time to start timer(fw-ready-start) in isp-fw-ready method. * Change fix-rbios to check nvr-bad? before copying nvram to RAM.
Version 3.00b5 02/25/09 * Change link-down-timeout to boot-wait-time if bootwait-enable flag is true. * Add ILT support for SCHULTZ only. No effect on ISP2400 * Changed era-code (used in ldfcode) to use /code to determine #secs to erase. * Add set-cd-base+siz (used for ldfcode) to replace set-ld-base & set-/dlc.
Version 3.00b4 02/11/09 * No change. Changed flash-acc-data & offsets for ISP8100 only.
Version 3.00b3 01/21/09 * No change. Changed reg property for ISP2500 and ISP8100 only.
Version 3.00b2 01/08/09 * Added set-boot-wait-time commnad for all 4 & 8Gb HBAs/CNAs. Add NVRAM Fcode 2-byte parameter, boot-wait-time, at ofs x15a & enable-bit(x20) at ofs x158. This was requested by Fujitsu, for disks that take longer to come online.
Version 3.00b1 12/19/08 * Add Schultz ISP8100 support. No change to ISP2400 methods. * Added more SCSI sense debugging. * Reworked interrupt service routines with more debugging.
Version 2.04 12/03/08 * Change version string from 2.04b2 to 2.04 Offical Release.
Version 2.04b2 12/02/08 * Remove set-bootid, set-boot-wwn, & releated qla only words from IBM version. * Added IBM debugging to BOFM words and set debug?=C00 if diag-switch is true. * Added max-payload bridge fix for 4-port QMI2464 HBA. Used Gil's method. * Fix get-mail to handle Response-Queue interrupts (stat=13) & add debugging.
Version 2.04b1 07/23/08 * Preserve Flash area x40000-x80000 which has FW-Area, Flash Tables, NPIV data * Fix open to always return -1. Returning link-down fw-state fails on Serengetti
Version 2.03 06/30/08 * Change version string from 2.03b1 to 2.03 Offical Release.
Version 2.03b1 06/06/08 * Use complete NVRAM values for fwopt2 and fwopt3 in fw-init, initialize ICB.
Version 2.02 05/07/08 * Change version string from 2.02b3 to 2.02 (Offical Release). * Fix load-image to return error status so you can exit on failure. * Remove stop-fw from isp-probe method. It did nothing since FW is not loaded.
Version 2.02b3 04/17/08 * Change compatible property to append to existing property, if it exists. * Change all references in the Fcode of 'HBA' to 'Adapter' (for QLE8000 CNA).
Version 2.02b2 04/14/08 * Fix compatible prop for IBM. Return DDDD value back to DevID in strings: pciVVVV,DDDD.SSSS.ssss.RR & pciVVVV,DDDD.SSSS.ssss. DDDD was = SSDevID.
Version 2.02b1 03/27/08 * Fix blank lines in list-wwns for set-boot-wwn command in qla-mode. ER59591. * Change the d-mbox (dump-mailbox) word to use the .4z data format macro. * Add Access Menlo Data IOCB to allow displaying & changing Menlo configuration. * Add Menlo version number to the version command (Menlo only).
Version 2.01 03/27/08 * Change version string from 2.01b2 to 2.01 (Offical Release).
Version 2.01b2 03/05/08 * Change SubSystem Device ID from x0169 to x014B for Sun QEM3472 HBA. * Add sunid-bit = x10 to Fcode Parameter word (offset x158) in NVRAM.
Version 2.01b1 03/03/08 * Add support for Sun QEM3472 with SubSystem ID = 0x0169, node name SUNW,qlc. * Add QLE3000 Mercury HBA support. * Fix selftest mem-siz = x20000 (128KB) on IBM CFFe/CFFx mezz cards.
Version 2.00 02/15/08 * Change version string from 2.00b17 to 2.00 (Offical Release).
Version 2.00b17 02/07/08 * Modify ldfcode again to skip copy of WWN and checksum to BIOS-defaults area.
Version 2.00b16 02/05/08 * Modify ldfcode to copy all BIOS-defaults plus copy Model & DID to header. * Fix login-devices to return #ports, including non-target ports. This fixes Sun Bug ID 6645537, ER58525, where LUNs were not listed when Emulex present.
Version 2.00b15 01/29/08 * Fix target login problem with McData switch by adding GID_PT command. ER58769. * Modify ldfcode to poke BIOS default area of the MB-image with Model# & SSID.
Version 2.00b14 01/15/08 * Fix restore-default-setting to skip SSDID, OEM Specific Area, Feature Mask, and Model# copy to NVRAM. Also add revert-wwns on IBM. ER58465 & ER58509. * Replace load-stub-fw with stop-fw mbox command for PCIe 2400 HBAs. Firmware vers 4.00.25 or greater stop-fw command will do the same thing as stub FW. * Fix IBM BOFM bug where the default WWPN is lost if a new WWPN is written twice
Version 2.00b13 12/21/07 * Separate 2400/2500 Fcode into two binary output files (isp2400/isp2500). Remove isp2500? & use #ifdef ISP2500. Resulting in smaller 37KB image size. * Add use-cdb16? flag which is set in read-capacity if the target supports Large LBA. 16-byte CDBs are used only if use-cdb16? is set & LBA > 32-bits. ER58285. * Fix "chrp" string in papr-compliant? word (IBM BOFM support). * Change write-wwnn word to check for new-wwnn=0 (IBM BOFM support). * Add enab-nvr-acc to all 6 BOFM external words so they work on unopened dev.
Version 2.00b12 12/10/07 * Add init-chip? to sns-command & logout-devices for recovery from link-down. * Put ifp-abort back into wait-for-risc-int, which was taken out in vers 1.23.
Version 2.00b11 12/05/07 * Move clearing of flags link-up?, done-fw-init? port-updated? to reset-risc. This was for isp2500 set-boot-wwn failure because FW was stopped. ER58139.
Version 2.00b10 11/30/07 * 2500 change only. ER58002.
Version 2.00b9 11/28/07 * Fix find-image to check for last-image bit and exit loop if found. ER57989. * Fix init-fw problem. If NVRAM is blank, FW Option word-1 is not set in ICB.
Version 2.00b8 11/21/07 * Make BOFM support words external in IBM version. * Change my-wwnn@ to return WWNN based on current adapter WWPN. (IBM version) * Fix stop-risc bug. Clear done-fw-init? flag before calling mail. ER57926.
Version 2.00b7 11/12/07 * Remove 'ibm,' from the BOFM support words for IBM. Also update property. * Add check-managed-wwn which checks for PAPR-compliant & san_wwn string in root prop " ibm,managed-address-types" and then reverts WWNs if necessary.
Version 2.00b6 10/18/07 * Changed makefile to create separate isp2400 & isp2500 images(PCI header only). * Fix drate-val (default Auto Data-Rate value) w/o shift for selftest. * Fix n-port topology device-present problem. obp-portied was not getting set. * Add back architecture check (wrong-arch?) of PCI header DEVID during flashing. * Add rd-ram-wd and wr-ram-wd mailbox commands for debugging purposes. * Add BOFM support for the IBM version Fcode.
Version 2.00b5 09/24/07 * Combined 2400/2500 Fcode into a single binary output isp2x00 file. Use isp2500? word instead of #ifdef ISP2500. Resulting image size is now 38KB. * Changed Connection Mode & Data Rate debug messages during FW initialization.
Version 2.00b4 09/18/07 * Shrink code wherever possible. Remove unused words and shorten value names. * Fix find-fc method to add Func0 bc0_ofs. Otherwise it checksums Func1-fcode.
Version 2.00b3 09/07/07 * Add reset-risc to reopen-hardware method when init_link?=0, for INIT version.
Version 2.00b2 09/06/07 * Fix selftest to always use Auto-negoiate data-rate. ER56565. * Fix open for selftest to return OK status when link-down on a reopen. ER56566.
* Fix version number in PCI header. Should be 2.00.
Version 2.00b1 08/28/07 * Add 2500 support with major change in NVRAM and Flash utilities.
Version 1.27 08/21/07 * Change version string from 1.27b11 to 1.27 (offical release).
Version 1.27b11 07/31/07 * Move init-chip to reopen-hardware so FW loads in show-children if link-down. * Make chip-base, exprom, lun-index and port-update-occurred instance values. * Make link-up a Hard (not instance) so it stays set between instances. ER55858.
Version 1.27b10 07/11/07 * Fix find-dflts and dflt-wd@ to now handle 2-byte alignment in BIOS. ER55660.
Version 1.27b9 07/03/07 * Remove QLE2464 PCIe Dev control reg max-payload-siz set from 1.26b9. ER55588. * Added Data Rate command when debug-init is set, to display actual data rate.
Version 1.27b8 06/22/07 * Add setting WWPN bit-56. This bit is clear in the WWNN. This fixes a potential problem when OEM (DTI) uses oemutil to set the adapter's WWPN. Matches driver. * Add setting FW Option 1 word in ICB. Never reported as a problem, but... * Fix stack bug in login-device when comp-status is invalid(eg. 99). ER55423.
Version 1.27b7 06/11/07 * Fix stack bug created in 1.27b6 on Bad IOCB Entry Status. * Add Execute command error debug level x40 and rework debug levels.
Version 1.27b6 06/05/07 * Remove fc-mode, set-fc-mode (qla-mode) words from IBM version. * Change IOCB fail messages to show only when the debug? 08 bit is set. ER55150.
Version 1.27b5 05/24/07 * Fix restore-default-setting to skip the Adapter WWPN copy into NVRAM. ER55009.
Version 1.27b4 05/14/07 * Add re-login when IOCB status =x29|x28, which will init-chip & login-device. This change was made to handle cable-pulls during boot. ER54837. * Change debug messages: Loop Up/Down to Link Up/Down & add test-unit-ready. * Change makefile to create 256k byte Fcode-only images to be used with SCLI.
Version 1.27b3 05/03/07 * Add back restore-default-settings but restore entire NVRAM from BIOS defaults. * Fix ibm-encode-unit to drop LUN if =0 & remove leading zeros, like 2312 Fcode.
Version 1.27b2 04/03/07 (Sent to Lyle) * First pass at adding NVRAM max-frame-size in FW ICB. Based on vers 1.26b10.
Version 1.27b1 03/22/07 (beta version given to IBM) * Add 16-byte SCSI CDB read/write commands for LBA >2TB. Based on vers 1.26b10.
Version 1.26 05/17/07 * Change version string from 1.26b21 to 1.26 (offical release).
Version 1.26b21 04/26/07 * Remove error messages for 'TUR failed' & SCSI 'Retries exhausted'. ER54516.
Version 1.26b20 04/25/07 * Remove restore-default-settings for 1.26 rel. Put a complete restore in later.
Version 1.26b19 04/25/07 * Change version-prop "Host Adapter Driver" to "Host Adapter FCode". ER54455.
Version 1.26b18 04/24/07 * Fix list-wwns to not call get-portname-db if invalid topology. ER54434.
Version 1.26b17 04/19/07 * Add NVRAM parameters restore-default-settings, with confirm question. ER54346. * Stop using the bios-compatibility-mode bit in NVRAM and remove set-mode command since it is no longer used in the 4Gb FCode (needed for 2Gb only). * Move all of the NVRAM access methods into a separate file, nvram.fth.
Version 1.26b16 04/18/07 * Add show max-frame-size (show-maxfs) to show-settings. * Fix bug in VPD data fetch (vpd@) word. Need to poll ready bit. ER54345.
Version 1.26b15 04/13/07 * Fix max-frame-size typo in menu, should be 1024, was 1048. * Fix version number in PCI header, was 1b(1.27), should be 1a(1.26).
Version 1.26b14 04/13/07 * Change max-frame-size to use a 3 choice menu, 1-512, 2-1024, 3-2048. ER54229.
Version 1.26b13 04/12/07 * Add Fcode usage of NVRAM parameter, max-frame-size in FW initialize ICB. * Add word, set-max-frame-size, for changing this NVRAM parameter. ER53990.
Version 1.26b12 04/10/07 * Fix inquiry? to check for no-data xfer. Problem seen when LUN#>255. ER54103. * Add 16-byte SCSI CDB read/write (x88/x8a) commands for LBA >2TB. IBM request. This change does not effect the old 6-byte & 10-byte SCSI CDB reads/writes.
Version 1.26b11 04/04/07 * Change word show-boot-wwn from being 'external' to 'header', so it is not visible with fcode-debug? flag =false. Requires change to readme.txt. ER53873.
Version 1.26b10 03/02/07 * Fix stack bug, introduced in 1.26b8, in display-luns when report-luns fails. * Remove comp-status=6 error message on commnad timeout in execute-command. * Go back to using tar.Z instead of zip format for release files.
Version 1.26b9 03/01/07 * Set timeout field in IOCB prepare-command. Timeouts were disabled! ER50089. * Change qla-mode use-bid? flag back=0. It does not need to match the bootID. * Add QLE2464 max-payload-size in Device Config Reg, offset x54.
Version 1.26b8 02/07/07 * Remove debug? flag set if diag-switch? environment variable is true. * Add Work-around delay in show-children to give FW time before issuing IOCBs.
Version 1.26b7 02/06/07 * Add login-device in show-loop-devices to fix bug with StorEdge 3511 minnow. * Fix display-inquiry stack bug when inquiry command fails. * Fix sense buffer check for illegal request in report-luns method. * Remove LUN0 inquiry command execution in display-luns, when report-luns fails. * Removed "Warning: NVRAM boot-id should be=" when in qla-mode, & loop topology.
Version 1.26b6 02/01/07 * Reduce /lunbuf to x10000 for MACs. This reduces max-luns from 16k to 8k. * Change to use NVRAM boot-id when in qla-mode for fabric topology, use-bid?=-1.
Version 1.26b5 01/25/07 * Fix bug in fp.fth. logout-device was not present. Needed since v1.25b6. * Start using port-down-rc retry-count in spin-up and rw-blocks scsi commands. * Disallow 0 entry for set-link-timeout set-port-down-count & set-login-count. ER51830 and ER51857.
Version 1.26b4 01/17/07 * Change data-rate menu to use 'Gb/sec' instead of 'Gigabit'. ER51678.
Version 1.26b3 01/12/07 * Add LUN list and lun-present? check to qla-mode set-boot-wwn method. ER51224.
Version 1.26b2 01/05/07 * Add Atmel 26DF081A Flash support. * Fix ldfcode to set DevID field in all PCI image headers.
Version 1.26b1 12/21/06 * Add Fcode usage of NVRAM parameters: login-retry-count, link-down-timeout. Currently port-down-retry-count is still not used by the Fcode. * Add words: set-login-count, set-link-timeout. & set-port-down-count for changing these NVRAM parameters. * Add hidden words: show-logincnt, show-linkto. & show-portdcnt for displaying these NVRAM parameters. * Add these new words to the show-settings list and the show-commands list. * Change display of boot-lun and boot-id to be both hex and (decimal).
Version 1.25 12/11/06 * Change version string for the 1.25 offical release.
Version 1.25b7 12/08/06 * Do not use NVRAM boot-id in qla-mode unless use-bid? flag is set, normally=0.
Version 1.25b6 12/08/06 * Fix qla-mode boot-id bug in fabric-wwn-to-handle. Was not using NVRAM boot-id. * Set limits on qla-mode NVRAM boot-id <= 7ff and on boot-lun <= ff. ER50909. * Add logout-device (of target boot-device) in close of scsidisk child.
Version 1.25b5 12/05/06 * Fix stack bug in login-device. This bug was induced in 1.25b2, LS_RJT fix. * Remove GID_PN fail mesage from fabric-wwn-to-handle & display if debug? on. * Change SN# fetch in show-settings to get it from the VPD data, not the WWN. * Add debugging to fcp-targets and fcp-luns. * In qlc-mode, disallow set-boot-wwn, set-boot-id & don't list in show-commands.
Version 1.25b4 12/02/06 * Fix GID_PN (0x121) & GPN_ID (0x112) SNS commnads to handle a null buffer.
Version 1.25b3 12/01/06 * Fix link-down topology=f case bug in device-present?. * Change ext-loopback-test to separate diag-init-chip & lb-ext (external).
Version 1.25b2 11/29/06 Fix login-devices bug on LS_RJT (found by Lyle), logout to preserve phandles.
Version 1.25b1 11/22/06 * Add show-commands. ER50338. * Add decimal display of target & Lun # in show-children.
Version 1.24 11/13/06 * Change version 1.24b3 string to the official release 1.24. * Change max-luns=16K for qlc-mode. Limit LUN field range to 8-bits in qla-mode.
Version 1.24b3 11/13/06 * Fix report-luns buffer & commnad, add 8 bytes for # of LUNs field. ER50220.
Version 1.24b2 11/09/06 * Change max-luns=256 (max # of LUNs per target) to match the driver. Was 1024. * Change execute-command to check status returned by login-device, & fail if bad * Change selftest to use init-chip which waits for fw-ready, instead of a delay.
Version 1.24b1 11/03/06 * Execute external-LB test from selftest only if in FL-port or NL-port topology. * Create command ext-loopback-test. Allows manual execution of External Loopback * Change ldfcode in flash-pgm to allow flashing of 1MB multi-boot images.
Version 1.23 10/18/06 * Change version 1.23b1 string to the official release 1.23.
Version 1.23b1 10/11/06 * Add ~2 sec. delay before executing show-nport-devices in show-children. * Added Level debugging. * Move tools directory up one level, so we don't keep a copy in every version.
Version 1.22 10/02/06 * Change version 1.22b5 string to the official release 1.22.
Version 1.22b5 09/29/06 * Fix isp2400-probe bug on PCIe HBAs. HBA regs were not mapped when load-stub-fw was executed. Also, moved isp2400-probe execution to the end of ifp.fth.
Version 1.22b4 09/19/06 1 Fixed list-wwns word so set-boot-wwn will work for N-port topology . 2 Fix selftest again so connection-mode always = Auto, during the test.
Version 1.22b3 09/15/06 1 Fixed get-id-list word to work for N-port topology on the ISP2400. 1 Increase max-fab-devs to 2048. 3 Change initial value of topology to x0f. (invalid) 4 Add show-settings word to list the HBA's settings. Make version word external. 5 Fix selftest to work independent of NVRAM connection-mode setting.
Version 1.22b2 09/11/06 1 Fixed processing of get-id-for-fc4type GID_FT buffer to check for null buffer. 2 Changed names of prom output files to isp2400.sun.fc and isp2400.ibm.fc.
Version 1.22b1 08/21/06 1 Add FW initialization stub loader at probe time & in close method. This is done only on PCIe HBAs (i.e. Dev-ID not equal to 2422). 2 The Makefile was changed: The tokenizer directory was changed to tools and a local copy of cpp and makearray are kept in tools. Tokenize and fakeboot are no longer used, and .out files are no longer created, only raw .fc files with no header. ldfcode will not work on older fcode, update with init version
Version 1.21 08/01/06 * Change version to non-beta after testing.
Version 1.21b1 07/18/06 * Change info-count from an instance value to simple value. This will limit the version banner to be displayed only once during the boot process.
Version 1.20 06/22/06 * Prohibit connection-mode change if DevID=54xx. Print: Model # will Auto-negotiate.
Version 1.19 06/14/06 * Release. Add support for QLE210, SSDID=x132(Sun) & SSDID=x13E(Qlgc).
Version 1.19b2 06/13/06 1 Prohibit data-rate change if DevID=54xx. Print: Model # will Auto-negotiate. 2 Add get-model-prop word. For printing model # if data-rate change is rejected.
Version 1.19b1 06/09/06 1 The memory size tested in mem-test will now be cut in half on all HBAs with Device ID = 54xx, such as the QLE220. The word reduce-func? was created. 2 Word for reading config space regs, vid@, did@, ssvid@, & ssdid@ were created.
Version 1.18 05/24/06 * Make v1.18b2 release v1.18
Version 1.18b2 05/23/06 1 Fix problem found on Sun T2000 PCIe. pci-compat-str did not handle dev-id=5432 2 Remove class-code-string2 word. It was producing a bad string pciclass,0400.
Version 1.18b1 05/19/06 1 Add support for several HBAs including the Sun QLE220 HBA with SSDID=x14E. 2 Add restriction of qla-mode change on all SUNW type HBAs. 3 Remove extra version string display during selftest. 4 Fix read-block-ext to only use read-capacity command, not try mode-sense first 5 Add display of non-zero FCP/SCSI status during debug mode. 6 Fix initialization of port-update-occurred flag during wait for isp-fw-ready?
Version 1.17 03/31/06 1 Put in Asif's fix for retry?(scsi.fth) to check sense length before IOCB copy. 2 Make my-wwn value external for IBM users. 3 Put in Asif's fix for ibm-decode-unit, to correctly parse out WWN and LUN# in cases where the LUN# may or may not be specified in the path. 4 Fix IBM set-address to correctly set obp-lun-lo and opb-lun-hi.
Version 1.16b11 03/28/06 * Make qla-mode? value in qlc parent & qla-mode? word in fp child node externel. Before fix, would not work if fcode-debug? = false.
Version 1.16b10 03/20/06 1 Fix fcp-luns for FL-PORT. Add 2dup so WWN is on the stack for f-port-fcp-luns 2 Make qla-mode? not instance value so show-devs will work. 3 Change fnv-access-to back (from x10 to x800) 4 Add set-timeout word back (needed for IBM). It was removed in b1.16b1
Version 1.16b9 03/08/06 * Change Firmware load-image to run faster.(very slow on serengeti) change read-code-segment to rd-code-seg. Change dly-val from 50 to 10. Move FLASH-ERR ifpcsr! to get-addr-len. Change fnv-access-to from x1000 to x10
Version 1.16b8 03/07/06 * Serengeti fix child creation. Put all if statements inside colin definitions. * Move scsicom.fth words into scsidisk.fth
Version 1.16b7 03/03/06 * Mod child creation. Use qla-mode? flag, not the property. Remove prop qla-mode * Change Loop init error message to print only if in debug mode.
Version 1.16b6 02/27/06 * Fix encode-unit to encode the lun target integer pair. Used in qla-mode.
Version 1.16b5 02/23/06 * Swap order of boot-wwn-hi & boot-wwn-lo in NVRAM (hi is now first) Always prompt for boot-target-id in set-boot-wwn.
Version 1.16b4 02/09/06 * Remove periods in display-wwn & display-inquiry,LUN. Now show-children looks the same as it use to. * Add 2-bit fcode-host field to fcode-parameter word (wd offset x56) in NVRAM. Value can be 00-SPARC, 01-IBM, or 10-MAC. This will effect the version string. The 01-IBM value should not be used. The IBM version is still a separte binary
Version 1.16b3 02/03/06 * Change Initiator test in login-device also. Test TARG-BIT of Service params. * Change show-login-devices & show-fabric-devices to skip display-luns if display-port-db fails. Check target bit done in get-port-db. Now FL-port works
Version 1.16b2 01/31/06 * Remove all #ifdef MAC instrustions. Make SUN version the SPARC/MAC version * Fix problem found @SUN w/6920, Change Initiator test in get-portname-db.
Version 1.16b1 01/30/06 * Add support for Apple MAC Fcode, using #ifdefs. Make it 32-bit compatable. * Add disk-test (read-write-read-compare) selected target with sel-dev & sel-lun Moved read-block-ext, timed-spin, r/w-blocks from sd node to parent qlc node.
Version 1.15 Beta_2 12/15/05 * Modify beacon word to flash top and bottom LEDs only!
Version 1.15 Beta_1 12/09/05 * Change node name to QLGC,qla for qla-mode on Sun platforms. * Added boot ID NVRAM modification to the set-boot-wwn method.
Version 1.14 11/04/05 * Added support for qla-mode on Sun platforms. Added NVRAM modification words for Fcode parameter byte (fcode-mode) and Boot Port Name/Boot LUN. Including: set-fc-mode, set-boot-wwn, fc-mode@, boot-wwn@, boot-wwn!, and boot-lun@. * Add creation of qla-mode property if the fcode-mode bit is set. * Modify set-address and device-present? to handle #address-cells =2 in qla-mode * Modify set-address & prepare-command to correctly handle 64-bit LUNs. * Cleaned up code. Got rid of unneeded calls to get-id. Made all constants CAPs. * Added login-devices word to login to all fabric devices and return #ports. * Added display-port-db word used by list-wwns and show-children (fabric & loop) * Modified show-fabric-devices to call login-devices and the call get-port-db
Version 1.13 10/28/05 * Asif fixed retry? in scsi.fth to check sense length before copy to IOCB.
Version 1.12 10/10/05 * Fixed issue with multiple initiators on local loop
Version 1.11 (1.10.13) 10/3/05 * Fixed Sun defect CR 6308066 (ER43414) Boot failed from Pyramid targets * Fixed Sun defect CR 6328443 Failed to boot from SE6920/6130 target * Fixed Sun defect CR 6324644 (ER43580) SE6130 LUN information is not shown correctly
Version 1.10.11 09/28/05 * Fixed ER42627: selftest does not perfrom risc-test. * Populate fcp-luns data struct with LUN values in little-endian byte order.
Version 1.10.09 09/26/05 * Fixed ER42883: Getting illegal instruction following a probe-scsi-all. * Fixed ER43041: device name prop creation SUNW or QLGC or fibre-channel. * Fixed ER42627: risc-test causes unknow error. Incuded init-chip before test. * Fixed ER43571: Version property now includes the model string.
Version 1.10 09/13/05 * Included special steps in reset-risc.
Version 1.09 09/12/05 * Released 1.08.06 for test.
Version 1.08.06 09/09/05 * Fixed Sun defect 6309765 - (ER43064 same issue) Adapter information not printed the second time probe-scsi-all is typed. * Fixed Sun defect 6308468 - boot message is not generic. * Fixed Sun defect 6308071 - probe-scsi-all prints incorrect message if no cable connects to a port. * Fixed ER43133 - Displays Error: Unable to get Adapter ID when executing probe-scsi-all. * Fixed ER43135 - The header info indicate ISP2422 instead of ISP2432. * Fixed ER42880 - Mailbox or IOCB interrupt timeout occurred. * Fixed ER42883 - get-portname-db failed. * fcp-targets and show-children would cause login into initiators, and then subsequent scsi cmds to logged-in initiators would fail/timeout. Checked for device type (target/initiator) in PRLI parameters field in response iocb in words get-port-db and login-device, (performed a logout in the case of login-device word (which is fabric topology case)) and returned failure to ensure that no scsi cmds would be issued to initiator devices. * Device name property string dependent on ISP24xx subsystem-device-id for SPARC platform. * Model property dependent on ISP24xx device-id. * Compatible property string prefixed with "pci" (ISP2422) or "pciex" (ISP2432).
Version 1.08.05 07/29/05 * Fix bug in version-prop method for the IBM version (needed a swap).
Version 1.08.04 07/27/05 * Change version-prop method to concatinate long-string & short-verion string Now the date and version number are contained in one single place! * Make the beacon word external. * Add get-id to init-chip to set the topology. Take get-id out of open. * Reorganize the order of methods in ifp.fth * Fix get-sense (retry?) to use the sense data in completion IOCB, if available. * Modify report-luns to accept an "Illegal Request" unit check response. * Move all SCSI related commnads to hacom.fth and rename it "scsi.fth". *
Version 1.08.03 07/12/05 * Change version property string, Add date to the end. * Put LED test "beacon" word back in. It was removed in Version 1.08b6. * Fix login-device call in f-port-fcp-luns method (fcp-luns.fth). * Comment-out call to logout-device in f-port-fcp-luns. (need to stay logged in) * Add release-history.txt file to release package. * Include tokenizer directory in release package, change makefile to use it.
Version 1.08.02 07/05/05 * Fix show-children hang bug when no devices attached, re-wrote show-fabric-devices method. * Create common get-id method to get adapter's ID & portid, new value my-portid. * Add 8048 Async error retry return code (x99) to the do-cur-iocb method. * Create common method, process-async, called by do-cur-iocb and get-mail. * Implement logout-device and logout-devices. (Was a no-op) * Change login-device to return completion-status, clean-up process-login-err. * Changed mailbox command names from isp- to mbc-. * Shortened some messages and made them common. Shortened some value names.
Version 1.08.01 06/28/05 * Change the version string only, for release to Sun.
Version 1.08b7 06/28/05 * Add Serial-Transmit-Parameter mailbox command, set-isp-stp, to init-image. * Add set-slc method to set the Serial-Link-Control parameters in NVRAM. This allows the operator to change the output swing and output pre-emphasis for 1Gb, 2Gb & 4Gb. * Change FCode checksum to use checksum in FCode Header, we will not use our own checksum byte at offset 0xfffc in Flash. The check-fcode method, which is part of selftest, now works on a combined BIOS/FCode/EFI Flash Image. * Add check for "ISP " signature in NVRAM method, nvr-bad?, which is called before setting connection-mode, data-rate and bios-compatibility-mode. If the NVRAM is bad, default values will be used instead. * Fix NVRAM checksum to be the same as Flasutil. (sum words not bytes to = zero) * Added show-bootid & show-model methods to show the corresponding NVRAM values. * Clean up load-image method. * Got rid of set-adapter-loopid. No reference in NVRAM docs, and never used. * Got rid of starting-id stuff. * Changed makefile to not use fiximage or fill128 utility. Use dd cmd instead!
Version 1.08b6 06/20/05 * Shorten version property for luxadm problem. * Add selftest, including: check-nvram, check-fcode, mem-test, risc-test (isp online selftest) and diag-lb (internal, 10-bit, 1-bit, & external loopback) * Fix image size to pad image to 512 byte boundary, and update PCI header value. * Added map-dma to combined dma-alloc and dma-map-in methods. And add unmap-dma to combined dma-free and dma-map-out methods. * Added init-chip method to initialize & re-load FW, equivalent to re-selecting. * Add fiximage.c utility to calculated FCode checksum for Flash images.
Version 1.08b5 05/26/05 * Fix set-fc-address for IBM. Now "Select Boot/Install device" works! * Fix no-data command during IOCB build in prepare-command method. * Added sav-fc method to save a copy of the FCode to RAM at location x4030. * Moved FCode programming methods to a separate file, flash-pgm.fth.
Version 1.08b4 05/23/05 * Fix report-luns method problem when 0 LUNs is returned. * Add SST25LF080A flash support. Add getpid method to check PROM ID.
Version 1.08b3 05/20/05 (First delivery to Qlogic) * Fix BIOS compatible NVRAM parameter bit bug in set-mode method. * The show-children method is now working for loop (nl) and fabric topology, but n-port (point-to-point) is still not supported!
Version 1.08b2 05/19/05 * Change model = QLGC24xx, name = SUNW,qlc. * Add Asif's multiple IOCB interrupt fix. Using rsq-iocb-valid? method.
Version 1.08b1 05/18/05 * Got manual booting on IBM working! Many changes to fcp-luns & fcp-targets. * Fixed SUN/IBM version banner bug. * Modified verbiage in NVRAM mod? word.
Version 1.08x 05/16/05 * Fixed Endian problem w/phandle, now booting in loop topology on the Sun. * Added fcp-targets and fcp-luns methods for IBM platform compatibility.
Version 1.07 05/13/05 * Initial release with booting fabric device working on Sun. * Add ldfcode utility to program FCode at the OK prompt. * Fixed all of the NVRAM parameter set methods. * Combined various pieces of FCode from 2312 & 24xx code bases. qlgc_fw_fc_4g-mb1_90-3-sysx_linux_32-64_chg
IBM ServeRAID BR10il SAS/SATA Controller v2 BIOS and Firmware Update BIOS Version 6.30.02.00, Firmware Version 1.30.10.00 and BSD Version 3.16.00.06
Adapters Supported: IBM ServeRAID BR10il SAS/SATA Controller v2 (49Y4731)
NOTE TO SERVICE - Reference RETAIN #N/A
NOTE: This change history is common between several of the IBM and LSI Basic or Integrated RAID SAS controllers for non-BOFM enabled, uEFI systems. Not all levels were released for all controllers.
BIOS Fixes:: - Fixed an issue where the controller was hanging during initialization when an adapter was hung in reset with insufficient information to reset itself. - Fixed an issue where the SAS MPT BIOS CU reports wrong array size.
BDD Fixes - Removed the "SAS/SATA missing" warning message when SAS and SATA arrays are present on the same controller. Firmware Fix - Addressed issue where 6Gb SATA drives will only negotiate at 1.5Gb/s instead of 3Gb/s. - Fixed issue where SAS/SATA mixing errors will occur when the controller is setup to allow mixing of devices. - Fixed issue with large topology of SATA drives where media errors on a single drive will cause one phy to hang after IOs to other drives start to timeout. - Fixed discovery Error 0x2 in maximum topology with SATA devices, - Addressed issue where Credit would be stuck at zero until controller resets resulting in a phy becoming hung and IO failing. Only occurs with very high IO.
Fixes: - Addressed issue with SATA devices where the drive could go missing for several minutes. - Fixed issue where incorrect release of scatter gather list could cause issues with pending IO to missing devices. - Addressed issue where IOs to a host with a bad drive could fail.
Fixes: - Fixed issue where Target mode responds with incorrect WWID after ports are swapped. - Fixed issue with Incorrect/Unexpected discovery errors on RAID storage enclosures. - Fixed issue where device added events are not sent to the host on RAID storage enclosures. - Fixed issue where it is possible for a Incorrect/Duplicate Device handle to get assigned to a target that is a SSP Initiator. - Fixed problem of the boot order selection not being saved
Fixes: - Changed BIOS text to state an IS Volume creation can be 1 to 10 drives. - Fixed issue with 2TB and above drives where SAS MPT BIOS CU reports wrong array size. - Addressed an issue that will maintain Target IDs for attached devices to an enclosure if the enclosure is removed for a short time.
Fixes: - Fixed an issue where, after running heavy I/O to NCQ enabled SATA drives, the controller may log false data underruns for read or write I/Os. The PHY on which the I/Os were reported as underrun may eventually lock up.
Fixes: - Fixed an issue where Solid State Drives (SSDs) were not seen after a link reset. - Fixed an issue where direct attached SATA drives were not reported missing after they were removed. This could result in degraded or failed volumes being reported as healthy.
Fixes: - Fixed an issue introduced by new functionality in package 2.50. The issue would cause a dual attached device to be hidden from both the direct connection and the expander connection. - Changed the behavior during drive quiescing/un-quiescing to prevent the drive metadata from being unnecessarily updated. - Fixed an issue where drives might go offline during a firmware update, due to I/O timeouts caused by the length of time needed to update the firmware. - Fixed an issue where volumes can become inactive due to the metadata on the drives getting out of synch with NVSRAM.
Fixes: - Fixed an issue where, on certain drives, it was not possible to create a RAID 0. - Fixed an issue which could cause drive ID0 to go offline. - Fixed an issue with SSD hot spares being reported as Orphaned. - Fixed an issue where hot spares could not be created when the first physical disk of a roaming IME volume is missing. - Fixed a memory leak which could occur in verification of hot spare. - Fixed several issues involving creating a volume or hot spare immediately after deleting a volume or hot spare. - Fixed various issues with hot spare reporting. - Fixed an issue where, in a multi-path environment under heavy I/O, an open timeout can cause Linux file systems to become read-only. - Fixed an issue where drives may go offline during a firmware flash under Windows. - Fixed an issue that caused a 0x7600 fault while running heavy I/O to expander attached disks. - Fixed an issue where, when a driver at a certain volume ID is roamed, the volume ID would change on the next reboot. - Fixed an issue which caused a 0x266D fault on reinsertion of a hotspare. - Fixed an issue where a volume cannot be deleted due to foreign metadata from a new drive. - Fixed an issue where a 0x8055 fault could occur upon insertion of drives with deleted metadata. - Fixed a rare issue where drives could go missing under a heavy load. - Fixed an issue where a 0x800F fault may be seen at startup on large topologies. - Fixed an issue that could cause a 0x0B83 fault when a SATA drive failed to initialize. - Fixed an issue where the LED of a critical drive would revert to the pattern for an optimal drive before the drive was truly optimal again. - Fixed an issue where a resync would resume, rather than restart, when a primary drive was removed and re-inserted. - Fixed an issue that could result in 0x6001 faults while running I/O. - Removed some extraneous error messages, which were triggered by reboots or firmware flashes, from the firmware log. - Fixed an issue which cause a 0x266D fault during volume creation. - Fixed an issue which could cause the operating system's file system to become read only in a multi-path environment.
Functionality: - Initial release for: IBM 3Gb SAS HBA v2 - Added support for EFI (Extensible Firmware Interface) based systems. - Enhanced support for SSDs (Solid State Drives). - Implemented support for single drive RAID 0. - Added a new volume status 'Sync Pending' for a volume that could be resynching, but is waiting for the first volume to complete resync. - Added ability to remove an orphaned hot spare when its associated, missing, volume is deleted. - Implemented some LED blink pattern changes to account for new hardware. - Added the ability to enable/disable data scrubbing on SSDs. - Enabled functionality to update drive firmware on disks in a degraded volume (the update must be done via the IBM Online SAS/SATA HDD Update Program, which must also contain a fix to enable this function).
Fixes: - Fixed an issue where, with dual solid state disks (SSD) installed, hard drive 0 goes defunct or disappears or a RAID 1 mirror becomes degraded. - Fixed an issue which slightly degraded performance in a Large Drive Count (LDC) configuration. - Fixed an issue where SATA drives may fail when alternate paths are removed and reinserted in a multipath configuration. - Fixed a condition which caused a 0x1904/0x1903 fault when issuing a TARGET RESET to certain SATA drives. - Fixed an issue where a 0x0800 fault occurs when an inactive or non-optimal volume is deleted. - Changed a resource allocation so that topology and other discovery related events aren't affected when other resources are heavily stressed. - Fixed an issue where, if a volume is removed, then reinserted, into a SAS topology, the volume becomes inaccessible. - Fixed an issue where discovery appears to hang due to multiple Expander Removed events sent for a single expander. - Fixed an which causes an OS not to boot if one of the hard disks in the boot volume is removed. An error similar to "Adapter LSI RAID 0/1 SAS 4P (0) was 1: Disk (0) missing after reboot". - Fixed an issue where continuous 'device added' events would be sent during discovery when a controller is attached to a topology with more end devices than are supported. - Fixed an issue that could cause I/O timeouts or 0x0900/0x1600 faults with SATA drives under heavy I/O load during any memory deallocation. - Fixed an issue where multiple WRITE BUFFER commands may cause a 0x4202 fault. - Fixed an issue where a 0x1904/0x1903 fault may be seen when a duplicate I/O results in a double completion. - Prevented task management timeouts which occurred when the SATA engine was involved with multiple error handling. - Fixed an issue that could cause the Initiator Command queue to become corrupt, resulting in a 0x6001 fault. - Fixed an issue where some error information was lost during Record Not Found media errors. - Fixed an issue with the reporting/retrieval of some LDC statistics. - Fixed an issue which may cause firmware initialization failure when many (more than 50) SATA targets are attached. - Fixed an issue which, in rare cases, could cause a 0x266D fault. - Fixed an issue which could cause a 0x1904 fault when issuing task management requests during heavy IO. - Fixed an issue that caused a break of the MPI spec in a scenario where an end device fails SATA initialization or an expander is out of routing table entries. - Fixed an issue where a virtual PHY is counted multiple times, resulting in the same Bus/Target ID being assigned to two different devices. - Fixed a stack overflow issue which could result as a 0x0900 fault or a fault code 11h during system initialization. - Enabled modification of Write Cache settings for RAID 0 volumes. - Fixed an issue which caused an "Insufficient Resources" response for an MPT RAID Passthrough command. - Fixed an issue where SMP requests are sent through the SMP passthrough, a 0x4203 fault occurs. - Fixed an issue where drives with SMART errors are not detected as volume members. - Prevented a false "Device Not Responding" event during discovery under heavy I/O. - Fixed an issue where an Activity LED would erroneously blink when a raw hard drive was added to a previously occupied slot. - Fixed an issue which could result in media errors at 51% rebuild point when a hot spare is present. - Fixed I/O timeouts and/or invalid SAS Expander Page #0 content which could occur if a bad link caused rapid linkup/linkdown states on a drive. - Fixed an issue which could result in a 0xBADn fault (where n is the PHY number) after a HARD RESET primitive is received. - Corrected an issue where the swap out status of a drive is always set to 0, rather than to a meaningful value. - Fixed an issue where, if a card enters fail-safe mode due to unreadable or unreachable settings, a fault 0x0700 was seen and the card would never enter READY state. - Fixed an issue where a hotspare which was created through the BIOS would not be correctly reported until after a reboot. - Corrected an issue where media errors would cause unnecessary device resets. - Fixed an issue where, if a disk is hot swapped with an incompatible disk, the new disk would incorrectly be assigned the volume ID as its target ID. - Prevented multiple paths from being returned unless multipathing is specifically enabled in NVDATA. - Fixed an issue which results in a 0x6014 fault during discovery in complex topologies. - Corrected an issue where pulling a drive in a volume would caused a 0x801F fault. - Fixed an issue where a 0x6002 fault is encountered in LDC topologies. - Ensured the MPI_EVENT_IR2_RC_PD_REMOVED event is properly reported when a foreign disk is removed. - Fixed an issue which could result in a 0x0800 fault under heavy I/O. - Corrected an issue which results in 0x4E01 fault when processing multiple simultaneous NCQ errors. - Fixed an issue where, if four or more drives are configured as any mix of volumes or hot spares, when you delete the volume, the associated hot spare(s) are correctly deleted, but the physical drives don't reappear in BIOS until after a reboot. - Fixed an issue where, if the same LUN is issued two active resets, the second reset could be completed before the first reset. - Fixed an issue which causes SATA initialization failure if a WRITE command is processed concurrently with a RESET command. The volume would then change to a FAILED state. - Ensured that metadata size is automatically detected by the firmware. - Fixed an issue where the BIOS stops responding if a rebuilding hard drive is removed. - Fixed an issue where 0x7600 faults were encountered when running heavy I/O to cascaded x12 expanders. - Fixed an issue where, with a 1078 chip, a 0x266D fault may occur when hot spare is reinserted. - Corrected an issue where SAS or SATA drives may be reported missing after a target reset to an end device. - Fixed an issue where, if the drive at the volume ID slot is roamed, the volume ID might change on the next reboot. - Fixed an issue where there is a very low probability of experiencing data corruption while under very heavy I/O stress. - Reworked the firmware download function into an asynchronous operation to allow I/O to continue during the process. - Fixed an issue where a direct-attached SEP device will not be assigned an ID or handle which will prevent communication with the device. - Fixed an issue where a direct-attached SEP will be incorrectly assigned TargetID 0.
Functionality: - Implemented various changes to the LED blink pattern for SGPIO. - New functionality to ensure that, if a dual-ported device is connected via both direct and expander attached connections, only the direct connection is hidden when the HideNonzeroAttachedPhyIdentifiers bit is set.
Firmware Version 2.01a3 (w/ 5.12a5 Universal Boot Code)
New Features
* Enhanced timeout notifications for processing abort failures.
Problems Fixed:
1. All multi-abort I/Os are returned on the same ring from which the ABORT_MXRI command was received.
2. Changed the TRCV response in the abort state to CMD RJT to enable the TRSP to be processed.
3. Corrected an issue with blocked TSEND operations.
4. Corrected a buffer leak issue with RRQ exchanges.
5. Corrected an issue where the TRCV IOCB was de-queued improperly causing a XFR_RDY flood.
6. Corrected an issue where the OXID field was not loaded in the XRI_ABORTED IOCB.
7. Corrected an issue in recognizing whether an EEPROM is present.
Dependencies: - The corresponding FC Storport device driver and OneCommand Manager Core-kit (management) will need to be installed for this package to function properly.
1. 118933 Fixed an issues booting when more than 8 ports are present in the system and fixed an adapter display issue when more than 8 ports are present in the systems 2. 118933 Fixed issues installing and booting O/Ss on ports greater than 8. 3. 121923 Fixed issues installing and booting O/Ss on ports greater than 8. 4. 122286 Fixed some boot time screen display issues.
(2) OpenBoot version 3.10a3
This version of OpenBoot supports FC-AL, Private loop, Public loop, and Fabric Point to Point. Also, it supports multi-initiators and multi-LUNs (0 through 4055)
Problems fixed, features added or other updates:
1. Unrelated to IBM
(3) EFIBoot version 4.12a12
The current EFI (Extensible Firmware Interface) Boot provides 64-bit System boot capability through the use of the EFI Shell. This EFIBoot supports EFI Specification 1.10 and EFI Source Code version 1.10.14.61.
Problems fixed, features added or other updates:
1. Only certain OEM HBAs will locate PlatformToDriverConfigurationProtocolGuid. Others just skip and continue processing 2. UEFI2.3 Hii Configuration Utility changes 3. HII Browser Save option does not work
1. CR105423 - On a port connected to a 3PAR "MBOD" cage, the test runs IO to the disk drives and issues a "controlport offline" command to offline the port while IO is running.
2. CR111194 - While doing target side cable pull testing with Block Guard (T10) Enabled we observed that adapter is not sending RSCN to AIX.
3. CR111625 - *IBM defect 775960 - HBQ ring index pointers?
5. CR111928 - 3PAR - LR with port and subsequent FLOGI failing.
Dependencies: - The corresponding FC Storport device driver and OneCommand Manager Core-kit (management) will need to be installed for this package to function properly. elx_fw_fc_ibm1206-2_01a9_linux_32-64_chg
=============================================================================== Emulex iSCSI Device Driver for Linux ===============================================================================
Linux iSCSI Device Driver Version: 4.2.398.0
Problems Fixed: - Cleaned up a cosmetic problem with warning messages during driver compile from source
- LUN is not getting detected for OEM CNA in SLES 11 SP2 64 bit OS - ioctl semaphore deadlock when running load/unload loop with target - SLES 11 SP2 GMC: Enable support for Lnx iSCSI Driver - RHEL 5.8 GA: Enable support for Lnx iSCSI Driver
- Emulex: Warning messages seen while building Emulex drivers on RHEL platform - Unable to load be2iscsi driver during iSCSI boot OS install - Modprobe be2iscsi hangs when system with max targets login - be2iscsi unload hangs the system - fw rebooted on 1st mbox cmd after driver load > unload > load - Failed to initialize iscsi driver - need to define DMA_32BIT_MASK / DMA_64BIT_MASK in Linux kernel 3.x.x elx_dd_iscsi_ibm1206-4_2_398_0_sles10_32-64_chg
=============================================================================== Multiboot Image for QLogic 10 Gb Converged Network Adapter for IBM System x
Q8Q10042.BIN contains: ---------------------- * BIOS version 2.11 * UEFI version 3.12 * Fcode version 3.02 * Firmware version 5.01.02 * MPI version 1.35.02 * PXE Boot version 1.03 * NIC EFI version 1.02
================================================================================= Original Release Notes from QLogic...
Release Notes
QL24rom BIOS Release notes
Rev 1.00 Jan.20, 2005 Initial release. Rev 1.01 Feb.18, 2005 Added code to put Port ID of device in IOCB. Rev 1.02 Mar.28, 2005 Added support for Serial Link Control. Addded code to display slot, bus number and function in CTRL-Q utility. Rev 1.03 Apr.18, 2005 Fixed bug when no drives attached and connected to switch. Added code to reset ISP if ISP is paused when ISR is called. Rev 1.04 June 8, 2005 Fixed bug in CTRL-Q utility that caused adapter id to be displayed at invalid id's. Added code to set Write Protect in Flash Status reg. Fixed bug in CTRL-Q utility where EAX reg was being corrupted by timer interrupt routine. Fixed bug in setting up LUN field in IOCB. Fixed bug in not setting port ID when connected to a switch. Rev 1.05 Sept 27, 2005 Changed code to suppress padding firmware version with leading zero's. Fixed bug in setting data direction flags in IOCB for 'seek command'. Changed code to not count device if device disabled by system BIOS. Fixed bug in setting flash Write Protect. Rev 1.06 Oct. 13, 2005 Fixed bug where anykey could invoke Fastutil. Rev 1.09 Nov. 22, 2005 Changed buffer request size to 2056 bytes for 'Report Luns' command. Fixed bug where GAN_NXT IN_ID was not always being set to zero causing GAN_NXT to fail. Rev 1.10 an. 31, 2006 Added check for optional boot mode flag to allow code to configure 1 drive/port when enabled. Bit 6 of host parameters in NVRAM is set to enable this mode. Fixed bug when Spinup-Delay and link is down. Added code to not display Data Rate option in CTRL-Q for QME2462. Rev 1.11 Feb. 7, 2006 Added support for interrupt polling. This option is controlled by bit 7 of NVRAM Host Parameters and by new Advanced Settings option in CTRL-Q. Rev 1.12 Feb. 21, 2006 Changed format of PnP string to display when Opt Boot Mode enabled in NVRAM. Added check for ELS reject status from Login IOCB. Rev 1.13 Apr. 04, 2006 Fixed bug in not always setting port id for logout IOCB. Changed code to support up to 16 adapters and 16 drives. Rev 1.14 Apr. 17, 2006 Changed code to ignore CLP '_hss' string. Rev 1.15 Apr. 20, 2006 Added code to wait for Login to complete when login pending status detected. Rev 1.16 May. 4, 2006 Fixed bug in not setting up Luns/Target in CTRL-Q. Added code to support Restore Default option CLP string (PCI3.0 BIOS only). Changed timeout value waiting for Linkup status from 6 seconds to 23 seconds. Rev 1.17 June 29, 2006 Added support for restoring defaults using CLP string (Pci3.0 only). Optimized code waiting for Linkup status. Added code to use Memory Map I/O for PCI express. Added code to check for correct Max Payload Size on QLE2464. Rev 1.18 July 19, 2006 Added code to load Nec switch port 1 and 2 pci config regs offset 68h with port 0 config offset 54h value. Fixed bug where task attributes in IOCB type 7 were not always being initialized. Rev 1.19 July 24, 2006 Fixed bug in CTRL-Q utility configuring Luns using Report Luns data when lun list has more lun entries after lun 255. Rev 1.20 Aug 2, 2006 Added code to support QLE2xx. Rev 1.21 Aug 24, 2006 Fixed bug in CTRL-Q cursor positioning for some user input displays. Rev 1.22 Sept 11, 2006 Added support for 'exit' CLP string. Changed CLP string to support new format: 'PermanentAddresses' was changed to 'PermanentAddress. Rev 1.23 Oct 16, 2006 Fixed bug in not setting rc_hba when different adapter types installed in system. Rev 1.24 Nov 29, 2006 Removed Extended Error Logging option from CTRL-Q. Removed code to use Memory Map I/O for PCI express. Rev 1.25 Dec 12, 2006 Added code so that set Defaults only to restores factory setting when value was modified by CLP string Rev 1.26 Dec 20, 2006 Fixed issue with the handling of CLP WWNN string. Also added code to always set firmware nodename optiom when set Default CLP is received. Rev 1.27 Feb. 26, 2007 Added support for Set Capabilities CLP string. Added code to load PLX switch port 1 and 2 pci config regs offset 68h with port 0 config offset 54h value (this is same code used for NEC switch). Rev 1.28 Apr. 12, 2007 Added code to check if need to restore HBA default portname. Added check for command fail status after login cmd. Restored code to read block 0 to determine drive geometry. Added NVRAM option (host_params bit 8) to enable support for HP boot order. Fixed bug in handling CLP Set Capabilities data. Rev 1.29 May. 22, 2007 Restored CTRL-Q Lun per Target option and changed text from 'Boot order' option to 'Controller order'. Rev 2.00 Dec. 03, 2007 Added support for ISP2532. Rev 2.01 Jan. 17, 2008 Added support for 1Gb data rate for 4Gb HBA. Rev 2.02 Feb. 18, 2008 Changed code to clear 'Disable Serdes' flag for CLP string Restore Default. Rev 2.03 Mar. 12, 2008 Added support for ISP8423. Added code to support new CLP 'set capability' spec. Rev 2.04 Mar. 23, 2008 Changed code to not used bit 13 of Host parameters. This avoids potential confict with inbox driver. Rev 2.05 Jun. 3, 2008 Added code to allow 2 min for link to come up when spinup delay enabled. Added code to poll for keyboard status. Removed external Loopback test option for ISP8432. Added check if IO support valid. Added check to CLP set_capablity string for the correct HBA port. Rev 2.06 Jun. 18, 2008 Added support for new CLP 'set capability' serial link spec for ISP2532. Rev 2.07 Sept. 3, 2008 Added additional error message for Verify Disk utility when device does not support SCSI cmd 2fh. Add support for Extended HBA CLP strings. Rev 2.07.6 Sept. 12, 2008 Fixed bug with 'restore netport defaults' when restoring NPIV's. Added code to reset ISP before accessing NVRAM the first time. Rev 2.07.8 Oct. 22, 2008 Added support for IDT PCIe switch Fixed bug in restoring NPIV after updating with CLP. Rev 2.08 Oct. 30, 2008 Removed TEST ONLY from BIOS banner. Rev 2.09 Dec. 02, 2008 Added code to save some pci data. Added new option to Advanced Option menu in CTRL-Q for Virtual Fabric Enable/Disable. Rev 2.10 Feb. 24, 2008 Added support for ISP8001 Added check for INT Polling before updating interrupt controller(PCI3.0) Fixed bug where eax register was being corrupted in nvram_config routine. Removed option in CTRL-Q for Virtual Fabric Enable. Fixed cosmetic bug in displaying selectable boot lun in CTRL-Q utility. Rev 2.11 Apr. 28,2009 Fixed issue with setting up Init FW MB command for using Extended Init Control Block Added option in CTRL-Q utility for Primary FCF VLAN ID for ISP8001 HBA. Added code to check version field of Extended ICB. Added code to correctly identify pci switch on 4 port HBA's. Changed code to suppport Loopback mode with new version of FW. Rev 2.12 May, 15,2009 Changed code to handle HSS CLP vendor id 3 same as vendor id 2. Rev 2.13 July 16, 2009 Added code to save backup copy of VPD/NVRAM data. Rev 2.14 Oct 9, 2009 Changed code to use FS segment register instead of GS in find_device routine. Change code to preserve MSB of WWPN Set Capablity CLP when updating WWPN/WWNN.
Driver Name : Fibre Channel Driver for UEFI Version : 3.33 Date : 5/9/2010 OS platform : N/A FW version : See MultiBoot release notes for FW version. Efiutil Version : 2.86
Table of Contents I. Overview II. Enhancements III. Bug Fixes IV. Known Issues V. Additional Information
I. Overview
The following document provides details of the Fibre Channel UEFI driver version 3.33 Efiutil version 2.86.
II. Enhancements
None
III. Bug Fixes
Driver: * Rename "Reconnect and Exit from Main Menu" HII entry to "Exit from Main Menu".
Efiutil: * Add fix to display new firmware version correctly while updating multiboot image. (ER71468) * Add support for 82xx family in Adapter list. (ER69230)
IV. Known Issues
Driver: * The driver does not support 24xx/25xx based HBAs. * In the HII menus, Adding/Deleting a Target/LUN will require a reboot for changes to take effect.
V. Additional Information
None
******************* QLogic Fcode for IBM CNAs ***************** Release Notes
This software license applies only to QLogic customers. QLogic Corporation. All rights reserved.
Table of Contents
1. Version 2. Changes 3. Bug Fixes 4. Known Issues 5. Additional Information 6. Trademarks 7. Notices 8. Contacting Support
1. Version
These release notes describe the changes, fixes, known issues, and release details that apply to the multi-boot package for the Converged Network Adapter (CNA).
* Reference the Read1st.txt for the kit version information.
2. Changes
These release notes describe the changes, fixes, known issues, and release details that apply to FCOde version 3.09
Hardware Support
* Supports QMI8142 and p-QLE8142 CNA (requires FCode for PPC) * Supports QLE81xx_FCode (requires FCode for SPARC)
Software Components
N/A
Industry Standards Compliance
N/A
3. Bug Fixes
Version 3.09 * Fix Node-Name-Option bit preservation in restore-default-settings.
Version 3.08 * Fix default WWNN & WWPN preservation in restore-default-settings. * Add standard properties. Use m4 utility to automaticly create date string. * Add file rev_level.m4 which has the revision level strings only. * Remove "SFP state: Unknown" message (.isp) if the adapter is IBM mezz card. * Change messages "Login failed" to "Login Abort". "Error Subcode" to "Subcode". * Remove patch of PCI header image size byte at offset 0x2c from init version.
Version 3.07 * Fix read-cap16-cmd. Used when the LUN size is >2TB (i.e. #blocks > 32-bits). * Fix disk-test to work with large (>2TB) LUNs, where the LBA > 32-bits. * Remove command retry when 8048 AEN is received.
Version 3.06 * Add option for qlgc-debug? in nvramrc. If the diag-switch? is true, then the debug? flag is set is set to the value of qlgc-debug?. * Add lba64 large disk capability (read-blocks64 write-blocks64) for SUN only. * Add mbox1 & mbox2 display for 8048 interrupt if debug-asyc? flag (01) is on. * Fix bug in IBM fcp-luns method for the Controller LUN-0 check, lun0-check. * Check Inquiry Qualifier field of Controller LUN-0 in IBM fcp-luns method. * Add more IOCB debugging, Add Erase Response-Queue in mapmem. Had stale data. * Add more debugging for IOCBs, dma-map-in/out, & wait-for-interrupts.
Version 3.05 * Fix set-fc-address issue found with IBM ioinfo. PortID was not getting set. * Re-structure devicepresent.fth. Add set-phandle to set obp-target & obp-portid * Fix multiple close issue found with IBM ioinfo utility.
Version 3.04 * Add alloc-sec-buf & free-sec-buf words with debugging messages. * Add "ibm,write-supported" property to disk child node, as per IBM's request. * Removed VPD validation from validate-nvram due to bug in update utilities. * Fix enab-nvr-acc to alloc sec-buf & add disab-nvr-acc for BOFM word.
3.03 * Added console messages when validate-nvram finds corruption & copies a sector. * Change validate-nvram to check both FC ports on Dual-port CNAs at probe time. * Fix init-flt-offsets to mask FLT attributes. Now it finds FW & Feature-key. * Added restart-mpi after the beacon test finishes to reset LED functionality. * Add NVRAM backup Sector. Add validate-nvram at probe time to fix corruption.
3.02 Initial release.
4. Known Issues
None
5. Additional Information
6. Trademarks
QLogic, the QLogic logo, QLA, QLE, QMI, SANbox, SANsurfer, and SANblade are registered trademarks of QLogic Corporation.
SANtrack and SAN Express are trademarks of QLogic Corporation.
All other brand and product names are trademarks or registered trademarks of their respective owners.
7. Notices
Information furnished in this document is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications described in this document for any of these products are only for illustrative purposes. QLogic Corporation makes no representation nor warranty that such applications are suitable for the specified use without further testing or modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.
8. Contacting Support
Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods:
Web: http://support.qlogic.com North America Contact Information
Email: support@qlogic.com Phone: (952) 932-4040
Support contact information for other regions of the world is available at the QLogic website: http://support.qlogic.com
(c) Copyright 2010. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.
qlgc_fw_cna_qle8142-1_01_94a_linux_32-64_chg
R E L E A S E N O T E S ============================
Broadcom Linux bnx2 and 10GigE Virtual Bus Drivers(VBD)
Version 2.2.3f 02/06/2013 Copyright (c) 2004 - 2013 IBM Corporation All rights reserved
NOTE: These driver release information is the original from the vendor. They include multiple driver change histories for multiple Linux Operating Systems. Some drivers may or may not pertain to all Linux Operating Systems but are part of this file for references.
==================================================================================================== Original file from Vendor...
Release Notes Broadcom bnx2 Linux Driver Version 2.2.3f 10/25/2012 Broadcom cnic Linux Driver Version 2.5.12e 08/22/2012
Broadcom Corporation 5300 California Avenue, Irvine, CA 92617
Copyright (c) 2004 - 2013 Broadcom Corporation All rights reserved
bnx2 2.2.3f (Oct 25, 2012) ========================== Enhancements ------------ 1. Change: (CQ65960) Make minor compatibility changes to support RHEL6.4
Impact: None.
bnx2 2.2.3e (Aug 27, 2012) ========================== Fixes ----- 1. Problem: ESX 6.0 compile errors seen when disabling NetQueue
Cause: Unused variables were defined in the non-NetQueue path
cnic 2.5.12e (Aug 22, 2012) ========================== Fixes ----- 1. Problem: (CQ 65270): bnx2x IRQ assert on 57712 and newer devices that support iSCSI only.
Cause: Not arming IRQ properly when detecting that the device does not support FCoE. Regression from cnic 2.5.12c enhancement #3.
Change: Added function pointer to arm IRQ correctly based on chip type.
Impact: iSCSI and FCoE on all 10G devices.
cnic 2.5.12d (Aug 21, 2012) ========================== Fixes ----- 1. Problem: (CQ 65249): cnic panic on functions that support FCoE only.
Cause: Code accessing iSCSI resources that aren't initialized or allocated on functions that don't support iSCSI.
Change: Check for valid UIO resource before trying to free it. Always initialize iSCSI OOO resources.
Impact: 10G iSCSI and FCoE.
bnx2 2.2.3d (Aug 15, 2012) ========================== Fixes ----- 1. Problem: (CQ 65163): unhandled NETQUEUE messages 16 and 17 seen in vmkernel logs
Cause: Not properly handling unsupported NetQueue ops
Change: Properly handle the NetQueue ops 16 and 17 without printing the warning message
Impact: ESX only
Enhancements ------------ 1. Change: Try to recover from PCI block reset during TX timeout. Red Hat users have reported PCI block resets that could not be recovered during tx timeout.
Impact: None.
2. Change: Added mk_kernel_patch.sh to patch bnx2 driver into kernel tree.
Impact: None.
cnic 2.5.12c (Aug 15, 2012) ========================== Enhancements ------------ 1. Change: Added firmware dump support for ESX6.0.
Impact: ESX6.0.
2. Change: Reduced maximum iSCSI abort delay to 5 seconds
Impact: iSCSI
3. Change: Allocate FCoE or iSCSI resources on a cnic only if the device supports the protocol. This will reduce memory consumption on multi-function devices.
Impact: iSCSI and FCoE
bnx2 2.2.3c (July 09, 2012) ========================== Fixes ----- 1. Problem: Unmapping the wrong DMA address in bnx2_free_tx_skbs() in rare cases.
Cause: Not skipping the last entry in the tx BD ring.
Change: Use the proper macro to get the next BD entry.
Impact: On systems with IOMMUs enabled, the bug can be triggered when doing resets (ifdown, MTU change) during heavy TX traffic.
cnic 2.5.12b (July 03, 2012) ============================= Enhancements ------------ 1. Change: Updated to bnx2x firmware 7.4.8 HSI for TX BDs.
Cause: Bug in cnic when max OOO resource is reached
Change: Initailized packet descriptor to fix the bug.
Impact: iSCSI only.
bnx2 2.2.3b (June 29, 2012) ========================== Fixes ----- 1. Problem: Compile error in RHEL6.x kernel and similar kernels.
Cause: skb_frag_size() compatibility code not detected properly.
Change: Fixed Makefile to detect it from skbuff.h
Impact: None.
bnx2 2.2.2b (June 24, 2012) ========================== Fixes ----- 1. Problem: (CQ63682)PSOD in ESX upon device open.
Cause: NAPI was not disabled properly upon device close. Thus, ASSERT occurs upon reopening device.
Change: Add NAPI disable upon close and add netif_tx_disable for both linux and ESX build.
Impact: bnx2.
2. Problem: Enableing RSS interferes with RX NETQ feature when compiled for ESX build.
Cause: RSS is enabled by default in bnx2. The RSS feature will lead to firmware bypass NETQ code path.
Change: Disable RSS by default when compiled for ESX.
Impact: ESX.
Enhancements ------------ 1. Change: Partial sync-up with upstream driver. Please see Changelog.
Impact: All
cnic 2.5.11c (June 12, 2012) ============================= Fixes ----- 1. Problem: (CQ62298 Partial fix) When running in INTA mode, MTU change does not work. iSCSI/FCoE does not resume after MTU change.
Cause: During mtu change, bnx2x does not know that cnic is no longer handling IRQs.
Change: Added a new flag to let bnx2x know that cnic is no longer handling IRQ during reset.
Impact: bnx2x iSCSI and FCoE.
2. Problem: (CQ62937) bnx2x asserts during iSCSI test with corrupted TCP NOP-IN.
Cause: Corrupted NOP-IN falls outside of TCP window, causing FW to go into OOO mode. TCP close with outstanding OOO causes problem and the close does not complete.
Change: FW change to return an error in this case and cnic driver change to handle this error by proceeding to clean up the connection.
Impact: bnx2x iSCSI.
cnic 2.5.11b (April 30, 2012) ============================= Fixes ----- 1. Problem: (CQ62298 Partial fix) Fix for CQ62026 in cnic 2.5.9d introduced a regression of clearing the CNIC_UP flag before all CIDs have been deleted. The regression is causing warning messges that some CIDs have not been deleted. After fixing this, we're still encountering further bnx2x error messages in the INTA code path.
Change: Wait for all CIDs to be deleted before clearing CNIC_UP flag.
Impact: iSCSI and FCoE on all bnx2x devices.
bnx2 2.2.1l (April 18, 2012) ============================ Fixes ----- 1. Problem: PSOD on ESX because of inconsistant NetQueue state when the NetQueues are allocated/freed out of order
Cause: The forced freeing of the NetQueue before the NetQueue allocation can cause the incorrect NetQueue to be freed and marked incorrectly.
Change: Remove the freeing of the NetQueue in the allocation path and allow the load balancer to control the error path when NetQueue's could not be allocated/freed.
Impact: ESX only.
cnic 2.5.10c (April 18, 2012) ============================= Enhancements ------------ 1. Change: Added iface_num parameter to cm_create() and iscsi_nl_send_msg()to support bnx2i 2.7.2.2b.
Impact: iSCSI only.
bnx2 2.2.1k (April 04, 2012) ============================ Enhancements ------------ 1. Change: Reduced code size of FTQ dump during tx_timeout.
Impact: None.
cnic 2.5.10b (April 04, 2012) ============================= Enhancements ------------ 1. Change: Added PCI pass through support for bnx2x E2/E3 devices.
Cause: cp->ctx_tbl is NULL during cnic_ctl() call with COMPLETION_CMD.
Change: cnic is registered with the L2 drivers before we allocate the cp->ctx_tbl so it is possible to get called while cp->ctx_tbl is NULL. Added check for CNIC_UP flag before proceeding to dereference cp->ctx_tbl. This together with the RCU code will completely fix the problem.
Cause: Middle-box test corrupts packets and causes iSCSI fw to generate 0x4 (NIC_ERR) completion code. This conflicts with new logic that uses NIC_ERR to convey parity error.
Change: Redefined parity error completion code to be 0x81 for L4, iSCSI, and FCoE.
Impact: FCoE and iSCSI.
bnx2 2.2.1g (Feb 28, 2012) ========================== Fixes ----- 1. Problem: Calling of bnx2_vlan_rx_kill_vid() is not rtnl_lock protected. Change: hold rtnl_lock when execute this routine under ESX4.0 and ESX4.1. Impact: ESX4.0/4.1 only.
bnx2 2.2.1f (Feb 8, 2012) ========================== Fixes ----- 1. Problem: (CQ61327) Unable to pass traffic on RHEL5.x
Cause: bp->num_rx_rings not initialized due to backport errors. This was introduced in 2.2.1e when adding ethtool -l|L support.
Change: Initialized bp->num_rx_rings to 1 on these older kernels.
Impact: RHEL5 and SLES10 only.
cnic 2.5.8f (Feb 06, 2012) ========================== Enhancements ------------ 1. Change: Added VLAN update from iscsiuio. This allows VLAN to be specified in iface.
Impact: iSCSI only.
cnic 2.5.8e (Jan 24, 2012) ========================== Enhancements ------------ 1. Change: Enhanced FCoE parity recovery by sending immediate FW_DESTROY completion with error during parity error recovery.
Impact: FCoE only.
bnx2 2.2.1e (Jan 24, 2012) ========================== Enhancements ------------ 1. Change: Added support for ethtool -[l|L]. Please refer to README.TXT for details.
Impact: 5709 with support for MSIX only.
cnic 2.5.8d (Jan 19, 2012) ========================== Enhancements ------------ 1. Change: Enhanced FCoE driver registration to provide FCoE capabilities to bnx2x driver.
Impact: Systems with Management support of these features. These changes were made to match bnx2x 1.72.07.
2. Change: (CQ60867) Backed out earlier changes related to this CQ. genksyms checksums are based on structure names and type names, so the scheme of using an identical structure with a different name will not work.
Impact: None.
cnic 2.5.8c (Jan 10, 2012) ========================== 1. Problem: (CQ60744) Lose connection to FCoE targets after parity error recovery.
Cause: (Partial) DISABLE_CONN SPQ message does not complete, causing delaying waiting for bnx2fc to timeout.
Change: Added immediate KCQ error completion for FCOE_DISABLE_CONN. when SPQ fails.
Cause: If a TCP connection fails due to parity error, termination sequence does not follow the expedited error recovery path. This causes unnecessary delay during parity error recovery.
Change: Set the HW_ERR bit when TCP connection fails due to SPQ error. Termination will then follow the expedited error recovery path.
Impact: iSCSI on bnx2x.
3. Problem: (CQ60867) Module versioning warning when installing cnic driver on SLES11SP2 without matching bnx2i/bnx2fc.
Cause: cnic_register_driver() stub in cnic.c does not have cnic_ulp_ops structure that matches inbox bnx2i/bnx2fc.
Change: Added dummy cnic_ulp_ops that match RHEL6.2 and SLES11SP2 structures.
Impact: None.
bnx2 2.2.1d (Jan 10, 2012) ========================== Fixes ----- 1. Problem: PSOD seen in TX handling in either bnx2_tx_int() or bnx2_start_xmit() routines
Cause: Memory re-ordering is occuring so that the TX BD is not updated before the ringing of the TX doorbell.
Change: On ESX the wmb() macro is defined to only as a compiler barrier. Redfine the wmb() macro to properly synchronize memory using the sfence instruction.
Impact: ESX only.
cnic 2.5.8b (Jan 05, 2012) ========================== Enhancements ------------ 1. Change: Added CNIC_CTL_FCOE_ENHANCED_STATS_CMD and CNIC_CTL_FCOE_CAPABILITIES_GET_CMD as stubs.
Cause: SPQ errors during parity error recovery was not propagated to L4 and ULP, causing unnecessary long timeouts.
Change: Added immediate KCQ error completion for L4 and iSCSI kwqes if SPQ fails.
Impact: iSCSI on bnx2x.
bnx2 2.2.1c (Dec 21, 2011) ========================== Fixes ----- 1. Problem: (CQ60281) BNX2 hang on ESX 4.1 when changing tx ring size with Ethtool.
Cause: BNX2 set_ringparam() ethtool ops callback attempts to hold rtnl_lock while vmlinux has already held this lock when when invoking this callback. This leads to deadlock situation and driver will hang forever.
Change: Make sure all ethtool ops callbacks don't hold rtnl_lock.
Impact: ESX only.
2. Problem: (BDKL87) PSOD in bnx2 start_xmit() path when stressing with change ring size script on ESX 4.1u2.
Cause: When using ESX4.0/4.1u0-u2, the vmkernel doesn't not check tx queue state properly in certain race condition. This can lead to bnx2 start_xmit() to deference NULL tx buffer.
Change: check tx queue state before proceed with stat_xmit().
Impact: ESX4.0/4.1u0-u2.
cnic 2.5.7h (Dec 08, 2011) ========================== Enhancements ------------ 1. Change: Added iSCSI and FCoE driver status and counters support.
Impact: Systems with Management support of these features.
2. Change: Added upstream patches to sync up with upsteam driver: net: treewide use of RCU_INIT_POINTER net: remove ipv6_addr_copy()
Impact: None.
bnx2 2.2.1b (Dec 08, 2011) ========================== Enhancements ------------ 1. Change: Added several upstream patches to sync up with upsteam driver: net: treewide use of RCU_INIT_POINTER bnx2: fix skb truesize underestimation net: Remove unnecessary driver assignments of ethtool_ringparam fields to zero
Impact: None.
bnx2 2.1.12b (Oct 14, 2011) =========================== Fixes ----- 1. Problem: (CQ59255) iSCSI warning messages appear and performance drops when connected to a lefthand target.
Cause: Packets with invalid TTT generate warnings and exception handling.
Change: Updated to 6.2.3 firmware for 5706 and 6.2.1.b for 5709
Impact: iSCSI
cnic 2.5.7g (Sep 23, 2011) ========================== Enhancements ------------ 1. Change: Added cnic_register_driver()/cnic_unregister_driver stubs so that depmod will not return errors if native bnx2i/bnx2fc drivers have not been updated.
Impact: None.
bnx2 2.1.11e (Sept 19, 2011) =========================== Enhancements ------------ 1. Change: Set the feature, NETIF_F_NO_SCHED, for ESX 5.0 and greater releases only
Impact: ESX only
Fixes ----- 1. Problem: Compile errors on some older kernels.
Cause: Compatibility API pci_is_pcie() requires bool type which may not be defined on older kernels.
Change: Moved bool type compatibility definition above pci_is_pcie().
Impact: None.
bnx2 2.1.11d (Aug 30, 2011) =========================== Enhancements ------------ 1. Change: Integrate Code Review Comments from VMware * Add feature flag to reflect if a device is compliant with network scheduling. * Conditionally move bnx2 drivers to high memory * Remove unused field/code
Impact: ESX only
2. Change: Remove unnecessary read of PCI_CAP_ID_EXP from upstream.
Impact: minor (5709 only).
cnic 2.5.7f (Sep 13, 2011) ========================= Fixes ----- 1. Problem: Duplicate cp local variable in cnic_shutdown_rings().
Cause: Coding error.
Change: Removed duplicate variable.
Impact: None.
cnic 2.5.7e (Aug 8, 2011) ========================= Fixes ----- 1. Problem: (CQ57498) System hangs during bnx2x parity error recovery.
Cause: cnic waits for RAMRODs to complete without timeout. During parity error recovery, all DMAs will stop.
Change: Added timeouts to all RAMRODs.
Impact: iSCSI and FCoE on bnx2x
cnic 2.5.7d (July 28, 2011) =========================== Enhancements ------------ 1. Change: Increased the max number of FCoE sessions to 1024.
Impact: FCoE.
bnx2 v2.1.11c (July 26, 2011) ============================ Enhancements ------------ 1. Change: Upstream sync to use ethtool_cmd_speed API.
Impact: None.
2. Change: Added memory barrier to sync transmit descriptor before updating TX mailbox. We believe that this may fix some very rare panics reported by VMWare.
Impact: bnx2 packet transmit.
cnic 2.5.7c (July 26, 2011) =========================== Fixes ----- 1. Problem: FCOE_DESTROY_FUNC ramrod not completing, causing timeout and OOO cleanup timeout during MTU change.
Cause: FCOE_DESTROY_FUNC was sent before all FCoE CIDs have been deleted.
Change: Wait for all (2 seconds delayed) FCoE CFC_DELETE ramrods to be completed before sending FCOE_DESTROY_FUNC.
Impact: FCoE only.
cnic 2.5.7b (July 19, 2011) =========================== Enhancements ------------ 1. Change: Re-instated vlan_id in ->indicate_netevent(). It is needed by bnx2fc to handle NETDEV_UNREGISTER on VLAN devices.
Impact: bnx2fc.
2. Change: Allocate FCoE CID space only on E2+ devices.
Impact: None.
bnx2 v2.1.11b (July 19, 2011) ============================ Enhancements ------------ 1. Change: Added tx_timeout error handling and made it common with VMWare code.
Impact: bnx2 NETDEV WATCHDOG error handling
2. Change: Fix compile errors on the latest net-next upstream kernel.
bnx2 v2.1.10d (July 12, 2011) cnic 2.5.6c (July 12, 2011) ========================================================= Fixes ----- 1. Problem: Not compiling on 3.0.0 kernel.
Cause: Makefile not recognizing the 3.0.x kernel
Change: Modified Makefile and sync'ed with upstream drivers.
Impact: None.
bnx2 v2.1.10c (July 1, 2011) ============================ Fixes ----- 1. Problem: Not compiling on older kernels (such as RHEL5.4) and newer kernels (such as 2.6.36)
Cause: Problems with compatibility code.
Change: Fixed compatibility code.
Impact: None.
bnx2 v2.1.10b (June 30, 2011) ============================ Enhancements ------------ 1. Change: Added more complete MCP dump during error conditions.
Impact: None.
2. Change: Modified driver messages slightly to match upstream format (by using netdev_printk, netdev_err, etc).
Impact: None.
Fixes ----- 1. Problem: Not reading iSCSI license on 570x devices reliably.
Cause: We were reading from the CP scratch pad before the CP firmware is loaded.
Change: Read from MCP shmem location instead.
Impact: 1G iSCSI on bnx2 devices.
cnic 2.5.6b (June 30, 2011) ============================ 1. Problem: (CQ56522, CQ56259) Unable to connect to iSCSI target, bnx2x firmware assert during iSCSI connection
Cause: iSCSI L2 ring CID has been changed in bnx2x 1.70.14. uIP is using a hardcoded value of 0x11.
Change: cnic now passes the CID to uIP.
Impact: iSCSI on bnx2x devices.
2. Problem: (CQ56230) Cannot compile on some 32-bit systems.
Cause: Passing 64-bit NULL pointer as 32-bit 0 dma_addr_t value.
Change: Use 0 instead of NULL for dma_addr_t values.
Impact: None.
cnic 2.5.5b (June 22, 2011) ============================ Enhancements ------------ 1. Change: Added WWN info to cnic_eth_dev. This is a temporary solution until ndo_fcoe_get_wwn() is implemented.
Impact: None.
bnx2 v2.1.9b (June 22, 2011) ============================ Enhancements ------------ 1. Change: Added del_timer_sync() in bnx2_remove_one() from upstream commit 8333a46ad3877485e4d67ef499c6dda36bfd1f9a. See ChangeLog for details.
Impact: None.
bnx2 v2.1.8c (June 16, 2011) ============================ Enhancements ------------ 1. Change: In ESX, bnx2 will setup int mode during .probe time. However, the dev->name will be finalized only when pci_announce_device is done. So, we assign irq->name in bnx2_request_irq instead of in bnx2_setup_int_mode.
Impact: ESX only.
cnic 2.5.4b (June 1, 2011) ============================ Fixes ----- 1. Problem: (CQ55915) iSCSI does not connect on 57800 in 4-port mode.
Cause: cl_qzone_id was wrong on the 3rd and 4th port. uIP also has some problems determining 4-port mode.
Change: Fixed the QZONE_ID macro.
Impact: bnx2x iSCSI.
bnx2 2.1.8b (June 1, 2011) ============================ Fixes ----- 1. Problem: (CQ55422) NCSI firmware version displayed backwards on PPC.
Cause: Endian bug when reading the data from shared memory.
Change: Fixed byte swapping issue.
Impact: None.
2. Problem: bnx2 does not compile on some PPC distros.
Cause: pci_enable_pcie_error_reporting() not properly defined in some distros.
Cause: Added #ifdef to prevent compiling pci_enable_pcie_error_reporting() on PPC since it uses EEH instead of AER.
cnic 2.4.5b (May 16, 2011) ========================== Enhancements ------------ 1. Change: Check CFC delete error code during completion. If it is set, do not reuse the CID. This change is only compatible with bnx2x 1.64.30 or newer.
Cause: TCP reset request may not complete if there is a race with firmware receiving a remote RST.
Change: Added code to handle TCP reset racing with remote RST and TCP close racing with remote FIN.
Impact: iSCSI
cnic 2.4.3b (April 28, 2011) ============================ Fixes ----- 1. Problem: cnic may lose interrupts after processing 64 kcq entries.
Cause: The driver handles a maximum of 64 entries before calling the ulp drivers. If the chip has more entries, the driver does not handle the rest but acknowledges the latest status block index.
Change: Changed the logic to keep looping until all kcq entries are handled.
Impact: iSCSI and FCoE on all devices.
cnic 2.4.2b (April 21, 2011) ============================ Fixes ----- 1. Problem: (CQ54715, CQ54717) XSEMI parity error detected during iSCSI login on 57712 in NPAR mode.
Cause: Statistic counter ID greater than MAX_STAT_COUNTER_ID_E2 in client init data for iSCSI L2 ring.
Change: Check client ID against MAX_STAT_COUNTER_ID_EXX before enabling statistics.
cnic 2.4.1c (April 11, 2011) ============================ Fixes ----- 1. Problem: (CQ49586) iSCSI reboot test fails after a few iterations.
Cause: TCP port 60000 is used every time during boot. During reset, the TCP connection is never terminated so using the same port to connect to the target during reboot will not work.
Change: Added randomization of the first TCP port to use.
Impact: iSCSI.
bnx2 v2.1.6b (April 6, 2011) ============================ Enhancements ------------ 1. Change: Get iSCSI license information to prevent cnic from registering if there is no license. This will make it consistent with 10G behavior.
Impact: iSCSI only.
cnic 2.4.1b (April 6, 2011) =========================== Fixes ----- 1. Problem: (CQ53236) FCoE HBA not functional after reloading bnx2x.
Cause: In some distros, NETDEV_UP can happen immediately after NETDEV_REGISTER while bnx2x module is still in init state. At this time, cnic will not be able to symbol_get() from bnx2x, preventing the cnic from registering.
Change: Check all events, and we should be able to catch NETDEV_CHANGE abd register cnic.
cnic 2.4.0b (Mar 29, 2011) ========================== Enhancements ------------ 1. Change: Updated cnic to with with bnx2x 1.70.x and added support for 578xx devices.
Cause: Race condition between cnic driver and hardware DMA'ing a new status block with new iSCSI events. The bug was introduced when adding FCoE support.
Change: 1. Add proper memory barrier after reading status block. 2. After servicing FCoE EQ, we must loop back and check the iSCSI EQ again because we may have a newer status block index that is read after servicing the iSCSI EQ.
Impact: 57712 iSCSI and FCoE.
bnx2 v2.1.5c (Feb 15, 2011) cnic 2.3.5c (Feb 15, 2011) ====================================================== Enhancements ------------ 1. Change: Updated 5709 firmware to 6.2.1a, with netq fixes and iSCSI performance regression fixes.
Impact: 5709.
bnx2 v2.1.5b (Feb 08, 2011) cnic 2.3.5b (Feb 08, 2011) ====================================================== Fixes ----- 1. Problem: iSCSI does not connect in DCB environment.
Cause: iSCSI packets are tagged with the wrong ethertype.
Change: Added initialization of xstorm's reserved_vlan_type field.
Cause: BNX2_NETQ_HW_OPENED bit was not properly set.
Change: When the NetQueue device is openned properly set the BNX2_NETQ_HW_OPENED bit in the netq_flags field.
Impact: ESX NetQueue
2. Problem: NetQueue could possibly get out of sync with the uppper layers
Cause: The queue cleanup code between the driver and upper layer is not synchronized
Change: Introduce the NetQueue lock to synchronize the cleaning of the queues between the vmkernel and the bnx2 driver.
Impact: ESX NetQueue
3. Problem: iSCSI may not work if multi-function is disabled in NPAR NICs.
Cause: Bug in logic in detecting NPAR mode.
Change: Offload bit should not be checked if iSCSI MAC address is invalid.
Impact: iSCSI on 57712 NPAR NIC.
bnx2 v2.0.22c (Jan 6, 2011) cnic 2.2.12c (Jan 6, 2011) ========================================================= Enhancements ------------ 1. Change: Updated to 6.2.1a firmware for 5709. It has fixes for CQ51953 (ESX netqueue issue) and CQ51894 (iSCSI performance).
Impact: 5709 iSCSI and L2.
bnx2 v2.0.22b (Jan 4, 2011) cnic 2.2.12b (Jan 4, 2011) ========================================================= Enhancements ------------ 1. Change: Send netlink IF_DOWN message during cnic_unregister_device(). This fixes the problem of bnx2i referencing freed hba when we used to send the netlink message during cnic_unregister_driver().
Impact: iSCSI.
2. Change: Upstream fix for memory leak in cnic_alloc_uio_rings() when we cannot allocate all the memory.
Impact: None.
3. Change: Upstream fix to remove flush_scheduled_work() since it is obsolete.
Impact: None.
4. Change: Do not allow iSCSI on bnx2x devices in MF mode. The hardware does not yet support it.
Impact: iSCSI.
Fixes ----- 1. Problem: SPQ RAMROD type field does not consistently contain the function ID.
Change: Fixed in cnic_submit_kwqe_16() for HSI 6.0 and above.
Impact: iSCSI in NPAR mode.
bnx2 v2.0.21b (Dec 21, 2010) cnic 2.2.11b (Dec 21, 2010) ========================================================= Enhancements ------------ 1. Change: Call cm_connect_complete() when an invalid path_response netlink message is received. This will speed up iscsid in disconnecting the connection. This helps to resolve CQ49665.
Cause: Referencing the cp->kcq1 pointer before checking that the device is up.
Change: Fixed logic so that the cp->kcq1 pointer will only be refernced after checking the device is up.
Impact: iSCSI.
Enhancements ------------ 1. Change: Added retry logic in iscsi_nl_send_msg() to retry netlink messages to userspace.
Impact: iSCSI.
bnx2 v2.0.20f (Dec 09, 2010) cnic 2.2.10f (Dec 09, 2010) ========================================================= Fixes ----- 1. Problem: (CQ51544) Unable to connect to iSCSI targets on 57712 NPAR LOMs with NPAR disabled.
Cause: ff:ff:ff:ff:ff:ff iSCSI MAC address was used in this case.
Change: Add code to detect invalid MAC address and use port MAC address instead. That's the only to determine NPAR is disabled.
Impact: 57712 iSCSI.
2. Problem: MTU change in INTA mode crashes occasionally.
Cause: Status block may be accessed if INTA is shared with another device during reset. There is a short period that the status block is freed.
Change: Free IRQ before freeing status block.
Impact: bnx2 MTU change/ring size change.
3. Problem: Heap corruption reported by VMWare.
Cause: list_del() is called after kfree() in OOO code.
Fix: call list_del() before kfree().
Impact: iSCSI OOO.
bnx2 v2.0.20e (Dec 06, 2010) cnic 2.2.10e (Dec 06, 2010) ========================================================= Enhancements ------------ 1. Change: Adjusted hc timeout for EQ to use the T6.0 value of 4. This will match T5.x HC timeout values.
Impact: 10G iSCSI only.
2. Change: Minor changes to match upstream code.
Impact: None.
bnx2 v2.0.20d (Nov 16, 2010) cnic 2.2.10d (Nov 16, 2010) ========================================================= Fixes ----- 1. Problem: VMware NetQueue not working properly on 5709.
Cause: HSI mismatch.
Change: Updated HSI to match T6.0 bnx2 firmware.
Impact: NetQueue on 5709.
Enhancements ------------ 1. Change: Adjusted kernel compatibility code to compile on RHEL5.6.
Impact: bnx2 and cnic.
bnx2 v2.0.20c (Oct 28, 2010) cnic 2.2.10c (Oct 28, 2010) ========================================================= Fixes ----- 1. Problem: NMI occurs during repeated load/unload of bnx2 driver on 5709.
Cause: The 5709 chip's DMA block wasn't stopped properly before reset.
Change: Fixed by clearing DMA_ENABLE in NEW_CORE_CTL register and polling for pending bus transactions to stop.
Impact: 5709.
Enhancements ------------ 1. Change: Update 5706/5708/5709 firmware to 6.2.1.
Impact: All 1G devices.
2. Change: Fixed one circular lock dependency issue with bnx2i when making up call to send iSCSI NL message.
Enhancements ------------ 1. Change: (CQ49858) Support KVM pass-through mode by eliminating config cycles to non-standard PCI registers (PCICFG_MISC_CONFIG, PCICFG_REG_WINDOW*).
Impact: All chips.
bnx2 v2.0.18c (Sep 13, 2010) cnic 2.2.6c (Sep 13, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49832) bnx2 flow control not working
Cause: Mistakenly disabled in firmware in 2.0.17j to fix CQ46393.
Change: Re-enabled RV2P flow control with additional fixes to for a number of odd flow control issues. New firmware versions are 6.0.15 for 5706/5708 and 6.0.17 for 5709.
Impact: 5706/5708/5709.
Enhancements ------------ 1. Change: Added zeroing of the iSCSI L2 ring's RX BD page to help signal ring shutdown to uIP.
Cause: A mismatch was found in the txbd where the hw prod idx did not match the sw prod idx (via the vlan_id field). The problem will show when uIP restarts without cnic reload. Since uIP restarted, it has lost all previous history about the uio ring.
Change: Added cnic_shutdown_rings to the uio_close path so whenever uio_open is called from uIP, the rings will start off fresh.
Impact: 570X/5771X iSCSI.
2. Problem: (CQ49211) Connection via bnx2i path fails in SuSE 11 SP1
Cause: For 5708/09, the previous firmware set did not take the l2 frame header length into account in the placement filter.
Change: Updated to 5706/08 fw 6.0.14 and 5709 fw 6.0.16 which addresses this issue.
Impact: 570X iSCSI.
bnx2 v2.0.17k (Aug 18, 2010) cnic 2.2.5k (Aug 18, 2010) ========================================================= Fixes ----- 1. Problem: iSCSI sessions do not recover when running under heavy stress conditions with the socket layer.
Cause: The NetLink buffer would get congested, so that the response to the PATH_UPDATE back to uIP would not be delivered.
Change: Use CNIC to throttle the number of outstanding PATH_REQ's to uIP, easing the congestion on the Netlink buffer.
Cause: RV2P firmware was set to drop input packets at a rate which is slower than input line rate when the host stops posting buffers. This has caused the rxp ftq to backup which eventually led to the rxp ftq hw to assert PAUSE and flood the network.
Change: RV2P firmware was modified to disable any waiting before dropping the input packet when the host doesn't post buffers.
Cause: cnic_wq destroyed while cnic_delete_task() is still queued in the workqueue.
Change: Call destroy_workqueue() after cnic_release() which waits for the cnic_delete_task() to finish.
Impact: 10G iSCSI.
bnx2 v2.0.17f (July 30, 2010) cnic 2.2.5f (July 30, 2010) ========================================================= Fixes ----- 1. Problem: iSCSI license not read correctly on 57712 in NIC partitioning mode.
Cause: Missing NIC partitioning license logic.
Change: Added NIC partitioning license logic.
Impact: 10G iSCSI.
Enhancements ------------ 1. Change: Updated 5709 firmware to 6.0.13. The new 5709 firmware has additional rx and tx performance improvements.
Impact: 5709.
bnx2 v2.0.17e (July 29, 2010) cnic 2.2.5e (July 29, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49117, CQ49111) Soft locup when unloading bnx2x with cnic and bnx2fc/bnx2i loaded.
Cause: cnic_cm_stop_bnx2x_hw() thread under rtnl_lock() and pci_bus_sem has to wait for cnic_delete_task() to finish the 2-second wait and CFC DELETE of every FCoE or iSCSI connection. There may be work structs scheduled on the common workqueue ahead of cnic_delete_task() that require the same semaphores, leading to the soft lockup.
Change: Use a dedicated workqueue for cnic_delete_task().
Impact: 10G iSCSI and FCoE.
2. Problem: (CQ49113) Compilation error with bnx2x 1.60.30. (CQ48828) lediag fails with cnic loaded.
Cause: license_key structure changed to use all 32-bit fields. This change is to fix CQ48828 (lediag fails with cnic loaded). 16-bit access causes lediag failure.
Change: Made corresponding change to read 32-bit values for the iSCSI license.
Impact: 10G iSCSI.
3. Problem: (CQ49097) cnic panics when loading on 5708.
Cause: The driver uses NULL OOO ring pointers to initialize OOO for 5708.
Change: Skip OOO completely on 5708.
Impact: bnx2 iSCSI.
bnx2 v2.0.17d (July 28, 2010) cnic 2.2.5d (July 28, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49071) Soft lockup during system shutdown after logging in to 10G iSCSI sessions.
Cause: This was introduced in 2.2.5c when fixing CQ49003. flush_scheduled_work() can deadlock because we're holding rtnl_lock and linkwatch_event may be on the workqueue.
Change: Fixed by using flags to wait for the cnic_delete_task() to finish.
Impact: 10G iSCSI.
2. Problem: cnic driver does not load on 5708 devices.
Cause: Bug in driver that skips devices without OOO support.
Change: OOO setup has been changed so that cnic initialization will continue even if OOO fails for whatever reason on all chips.
Impact: iSCSI.
Enhancements ------------ 1. Change: Updated 5708 firmware to 6.0.11 and 5709 firmware to 6.0.12. The new 5709 firmware fixes small packet rx performance issue. Some adiitional fixes for iSCSI and OOO.
Impact: All bnx2 chips.
bnx2 v2.0.17c (July 23, 2010) cnic 2.2.5c (July 23, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49003) Panic in cnic_free_bnx2x_conn_resc() during ifdown with many 10G iSCSI active sessions.
Cause: cancel_work_sync() is not available in RHEL5.x kernels to wait for cnic_delete_task() to finish before freeing the device's data structures (in particular the csk table).
Change: Use flush_scheduled_work() to wait instead.
Cause: UIO device deleted before userspace has closed the device, causing various failures including kernel panic.
Change: Separated UIO structure from cnic_dev structure so that we can wait until UIO is closed before unregister and deleting UIO.
Impact: iSCSI. This change should have possitive impact on ifup/ifdown, MTU change/selftest/hotplug/etc with active iSCSI sessions.
Enhancements ------------ 1. Change: Allocate the actual number of MSI-X vectors instead of always 9. Also, keep trying if the number of vectors is less than the desired number.
Impact: 5709 networking and iSCSI.
bnx2 v2.0.16c (July 12, 2010) cnic 2.2.4c (July 12, 2010) ========================================================= Enhancements ------------ 1. Change: Added VLAN_TAG_PRESENT to distinguish between physical and VLAN netevents in cnic.
Impact: FCoE.
bnx2 v2.0.16b (July 8, 2010) cnic 2.2.4b (July 8, 2010) ========================================================= Fixes ----- 1. Problem: (CQ48753) cnic will not compile with bnx2x 1.60.27.
Cause: IGU symbols not defined without ELINK_DEBUG defined.
Change: Added ELINK_DEBUG.
Impact: None.
2. Problem: (CQ48717) Kernel panic in bnx2x during ifdown with active iSCSI sessions.
Cause: uio_close() is called after the device is already down. bnx2x will crash when we try to shutdown the iSCSI ring.
Change: Shutdown the iSCSI ring even if uio_close() is not called in the shutdown path.
Impact: 10G iSCSI.
Enhancements ------------ 1. Change: Always run in MSI-X mode on 5709.
Impact: 5709.
2. Change: Added wait of 2 seconds when sending PATH_REQ if UIO has not been opened yet. This improves the liklihood of login success during the first login if using older iscsid.
Cause: pci_save_state()/pci_restore_state incompatibility in older kernel. DECLARE_PCI_UNMAP_ADDR() caused dma mapping field to be undefined on kernels not using IOMMU.
Change: Do not use pci_save_state()/pci_restore_state() on older kernels. Use dma_addr_t to declare mapping fields.
Impact: None.
bnx2 v2.0.15j (June 30, 2010) cnic 2.2.3j (June 30, 2010) ========================================================= Fixes ----- 1. Problem: bnx2x firmware asserts if cnic is loaded on 57711E (MF) functions 2 and higher and the device is brought up.
Cause: Statistics for iSCSI ring not implemented, casuing firmware to assert when the iSCSI ring is initialized.
Change: Do not enable statistics if the clien ID is bigger than MAX_STAT_COUNTER_ID.
Impact: bnx2x iSCSI on 57711E.
2. Problem: cnic terminations for iSCSI and FCoE connections may panic or hang during repeated ifdown/ifup.
Cause: Data structures may be freed while cnic is still waiting for the 2 second CFC_DELETE wait time.
Change: Use cancel_work_sync() to wait for the completion of the cnic_delete_task(). Check that the CTX_FL_DELETE_WAIT flag has been set before waiting.
Impact: bnx2x iSCSI and FCoE.
3. Problem: (CQ48642) Compile errors on older kernels.
Cause: VMWARE_ESX_DDK_VERSION not defined in Linux.
Cause: Race condition between bnx2i initiated TCP close and an asynchronous RESET_COMP from firmware.
Change: Re-structured cnic code that handles close, abort, and various completion events to ensure all scenarios are accounted for with no race conditions.
Impact: All iSCSI connection termination scenarios.
Enhancements ------------ 1. Change: Added host iSCSI IP address to the cnic_dev structure so that bnx2i can report it to sysfs. This is needed for iSCSI boot during pivot_root.
Cause: PCI MSIX attributes not defined in kernel .h files.
Change: Added compatibility code.
Impact: None.
bnx2 v2.0.15d (June 2, 2010) cnic 2.2.3d (June 2, 2010) ========================================================= Fixes ----- 1. Problem: (CQ47942) rmmod hangs if the device has been opened and closed more than once.
Cause: netif_napi_add() called once during every ->open(). netif_napi_del() is only called once during rmmod.
Change: Call netif_napi_del() in ->close().
Impact: None.
bnx2 v2.0.15c (May 21, 2010) cnic 2.2.3c (April 21, 2010) ========================================================= Fixes ----- 1. Problem: service iscsid restart on 5709 does not work.
Cause: Not restarting KWQ correctly due to stale context.
Change: Fixed by correctly zeroing KWQ/KCQ/RX context memory.
Impact: bnx2 iSCSI.
2. Problem: iSCSI license not read correctly on 57711E in single function mode.
bnx2 v2.0.15b (May 12, 2010) cnic 2.2.3b (April 12, 2010) ========================================================= Fixes ----- 1. Problem: iSCSI does not work on 57712.
Cause: License checking always disabled on 57712.
Change: Added proper checking for 57712 iSCSI license.
Impact: None.
2. Problem: (CQ47360) Compile errors on older kernels not supporting UIO and latest iSCSI.
Cause: New cnic driver will only compile on kernels newer than 2.6.31 and some selected distros that have the backport.
Change: Makefile changes to compile cnic only on supported kernels.
Impact: None.
Enhancements ------------ 1. Change: Changed bnx2_cnic_probe() to bnx2_cnic_probe2() so that out-of-tree driver componenets will not inter- operate with upstream components. This avoids compatibility problems that often lead to kernel crashes.
Impact: Out-of-tree cnic will not operate with upstream L2 drivers and vice versa.
2. Change: Revert the PRS_REG_NIC_MODE change done in 2.0.11h. Newer bnx2x driver (1.60.18+) do not require this setting.
2. Change: Added VLAN ID to netdev event callback.
Impact: bnx2i.
bnx2 v2.0.13b (April 22, 2010) cnic 2.2.1c (April 30, 2010) ============================================================ Enhancements ------------ Add debug code to dump all KWQE's (RAMROD) posted to 5771x chipset. This feature can be enabled/disabled using module parameter, by default this feature is disabled. Also a exported function is introduced to dump 3 pages worth of KCQE's
bnx2 v2.0.13b (April 22, 2010) cnic 2.2.1b (April 22, 2010) ============================================================ Enhancements ------------ 1. Change: cnic has been updated to be similar to the upstream versions using UIO with added T6.0 iSCSI support for 10G and other bug fixes.
Impact: iSCSI now requires UIO, new bnx2i, and bnx2x 1.60.16+.
bnx2 v2.0.11j (April 22, 2010) cnic 1.10.2j (April 22, 2010) ============================================================ Fixes ----- 1. Problem: (CQ47298) Does not compile with bnx2x 1.60.16.
Cause: cnic_if.h has changed.
Change: Updated code to be compatible with new cnic_if.h.
Impact: None.
bnx2 v2.0.11i (April 15, 2010) cnic 1.10.2i (April 15, 2010) ============================================================ Fixes ----- 1. Problem: (RHBZ 511368) Driver loses one MSI-X vector after many hours of traffic.
Cause: Chip timing out on write cycle to the MSI-X mask bit, causing the unmask operation to be dropped.
Change: Increase GRC timeout in register 0x8cc. (Same fix from 2.0.8e).
Impact: bnx2x MSI-X mode.
2. Problem: (RHBZ 554706) scheduling while atomic warning when bonding and VLANs are used with cnic loaded.
Cause: bond_del_vlans_from_slave() holds bond->lock when calling ndo_vlan_rx_register(). bnx2 calls bnx2_netif_stop() to stop the rx handling while changing the vlgrp. The call also calls bnx2_cnic_stop() which has many sleeping functions.
Change: Do not stop cnic when VLANs are changed. Since there is no reset during VLAN change, there is no need to stop cnic. (Same fix from 2.0.8e).
Impact: VLAN and iSCSI.
3. Problem: (CQ46940) Poor small packet performance on 5709.
Cause: FTQ discards caused by bottlenecks in firmware.
Change: Upgraded to 5.0.0.j15 MIPS firmware for 5709. (Same fix from 2.0.8c)
Impact: 5709.
Enhancements ------------ 1. Change: Improved rx performance by prefetching next entry's descriptor header and SKB.
Impact: All chips.
2. Change: Updated cnic interface to support out-of-order processing. This is needed for bnx2x 1.60.15 but the feature is not available in cnic yet.
bnx2 v2.0.11b (Jan 28, 2010) cnic 1.10.2b (Jan 27, 2010) ======================================================== Enhancements ------------ 1. Change: Saved bnx2 statistics block before MTU change, ring change, etc.
Impact: bnx2 statistics.
bnx2 v2.0.10b (Jan 12, 2010) cnic 1.10.1b (Jan 12, 2010) ======================================================== Enhancements ------------ 1. Change: Improved cnic's MTU change/reset logic to fix multiple problems in VMWare.
Impact: iSCSI.
2. Change: Converted to bnx2x T6.0 HSI.
Impact: bnx2x iSCSI.
bnx2 v2.0.8e (April 13, 2010) cnic 1.9.13b (Dec 16, 2009) ========================================================= Fixes ----- 1. Problem: (RHBZ 511368) Driver loses one MSI-X vector after many hours of traffic.
Cause: Chip timing out on write cycle to the MSI-X mask bit, causing the unmask operation to be dropped.
Change: Increase GRC timeout in register 0x8cc.
Impact: bnx2x MSI-X mode.
2. Problem: (RHBZ 554706) scheduling while atomic warning when bonding and VLANs are used with cnic loaded.
Cause: bond_del_vlans_from_slave() holds bond->lock when calling ndo_vlan_rx_register(). bnx2 calls bnx2_netif_stop() to stop the rx handling while changing the vlgrp. The call also calls bnx2_cnic_stop() which has many sleeping functions.
Change: Do not stop cnic when VLANs are changed. Since there is no reset during VLAN change, there is no need to stop cnic.
Impact: VLAN and iSCSI.
bnx2 v2.0.8d (April 02, 2010) cnic 1.9.13b (Dec 16, 2009) ========================================================= Enhancements ------------ 1. Change: Improved rx performance by prefetching next entry's descriptor header and SKB.
Cause: Stale status block with old KCQ index after restarting hardware.
Change: Added some additional cleanup and initialization steps including zeroing the status block.
Impact: None.
Enhancements ------------ 1. Change: Updated RV2P P1 for 5709 to 5.0.0.j10 to address a flow control issue that can lead to context corruption. Flow control watermarks have also been optimized.
Impact: 5709 flow control.
bnx2 v2.0.6b (Dec 4, 2009) cnic 1.9.11b (Nov 19, 2009) ======================================================= Fixes ----- 1. Problem: (CQ44801) Unable to compile bnx2 on most 2.6 kernels.
Cause: print_mac() kernel compatibility not defined correctly.
Fix: Simple compatibility fix.
Impact: None.
bnx2 v2.0.5b (Dec 4, 2009) cnic 1.9.11b (Nov 19, 2009) ======================================================= Enhancements ------------ 1. Change: Sync'ed up with latest upstream bnx2 driver. Please see ChangeLog for details.
Impact: Yes, Linux and VMWare.
bnx2 v1.9.42b (Dec 1, 2009) ======================================================= Fixes ----- 1. Problem: Compile error against the VMware ESX 4.0 DDK
Cause: vmk_IscsiNetHandle is not defined with the VMware ESX 4.0 DDK
Change: Added compile flag
Impact: None.
Enhancements ------------
1. Change: Add BMAPILNX ioctl to allow for FW upgrade
2. Problem: (CQ42096) iSCSI sessions do not recover after running selftest/ifdown/etc with max sessions connected.
Cause: cnic_lock mutex has circular dependency, causing deadlock when iscsid tries to cleanup connections.
Change: Merged in upstream cnic patches to avoid circular dependency.
Impact: None.
Enhancements ------------ Change: (CQ43088) Changed the firmware version string format.
Impact: None.
bnx2 v1.9.40b (Nov 18, 2009) cnic 1.9.10b (Nov 12, 2009) ======================================================= Fixes ----- 1. Problem: (CQ44528) Kernel runs out of memory after load/unload bnx2.
Cause: RX SKB buffers were not freed.
Change: Fixed the regression introduced by VMWare development.
Impact: None.
2. Problem: (CQ44399) iLAB 5.10 connection establishment test failure.
Cause: Firmware SYN-ACK handling issue.
Change: Updated firmware to 5.0.0.j6 in bnx2_fw.h and 5.0.0.j9 in bnx2_fw2.h.
Impact: iSCSI.
Enhancements ------------ Change: (CQ43088) Added VPD-R V0 firmware version string to ethtool -i.
Impact: None.
bnx2 v1.9.39b (Nov 6, 2009) cnic 1.9.10b (Nov 12, 2009) ======================================================= Fixes ----- 1. Problem: (CQ44470) Kernel panics when bnx2/bnx2x is unloaded with active iSCSI sessions.
Cause: NETDEV_UNREGISTER will cause bcm570x_* transport to be destroyed while sessions may still be active.
Change: Use module referencing to prevent bnx2/bnx2x from unloading. This is a simple interim solution to revert back to the old behavior. In T6.0, we will migrate to the upstream driver architecture and network drivers will be able to be unloaded again.
Impact: None.
Enhancements ------------ Change: Added a short register dump during NETDEV_WATCHDOG.
bnx2 v1.9.35b (Oct 22, 2009) ======================================================= Fixes ----- 1. Problem: If only 1 queue is used on VMware ESX, iSCSI offload would fail.
Cause: The inboxed VMware driver would only use 1 MSI-X vector. Because of this the driver would not setup MSI-X
Change: Always setup MSI-X reguardless of the number of MSI-X vectors used.
Impact: 5709 iSCSI on VMware
bnx2 v1.9.34b (Oct 20, 2009) ======================================================= Fixes ----- 1. Change: Updated xinan firmware to 5.0.0.j8 Nop timeout tuning (VMware PR467194) Added a new data fw heartbeat to work with the new bootcode and also handle older bootcode.
1. Change: Make NetQueue module parameters more explict.
Impact: bnx2 VMware NetQ.
bnx2 v1.9.32b (Oct 8, 2009) cnic v1.9.7c (Oct 8, 2009) ======================================================= Fixes ----- 1. Problem: CNIC unable to handle an unsolicited RESET COMPLETE which would result in a hung session.
Cause: The CNIC driver couldn't handle unexpected SYN.
Change: The CNIC driver will now handle an unsolicited RESET COMPLETE and cleanup properly.
Impact: cnic
Enhancements ------------
1. Change: Allow the default NetQueue options to be controlled through the macro, BNX2_ENABLE_NETQUEUE.
Impact: bnx2 VMware NetQ.
bnx2 v1.9.31b (Oct 6, 2009) ======================================================= Fixes ----- 1. Problem: PSOD would occur when alloc()'ing NetQueue's
Cause: With the removal of the global 'disable_netq' parameters, the NetQueue CID's weren't being mapped in some cases
Change: Always map the NetQueue CID's
Impact: bnx2 VMware ESX NetQueue
bnx2 v1.9.30b (Oct 5, 2009) ======================================================= Fixes ----- 1. Problem: PSOD would occur because of TX timeouts
Cause: The VMware netdev watchdog timer was ran before the reset task got a chance to run on a loaded system.
Change: Elongated the TX timeout value for VMware ESX only to allow for the reset task to run.
Impact: bnx2 VMware ESX
Enhancements ------------
1. Change: Updated vmkernel module parameter, 'force_netq', to allow NetQueue setting to be adjusted per function rather then globally for all functions.
Impact: bnx2 VMware ESX
bnx2 v1.9.29b (Oct 1, 2009) ======================================================= Fixes ----- 1. Change: Updated xinan firmware to 5.0.0.j7 and teton firmware to 5.0.0.j4 which will fix L2 hang due to iSCSI PDU's padding byte extended to another TCP segment
Impact: 5706/5708/5709.
bnx2 v1.9.28b (Sep 25, 2009) ======================================================= Fixes ----- 1. Change: Updated firmware to 5.0.0.j6 which will add the corresponding flow control trip point.
Impact: 5709.
bnx2 v1.9.27b (Sep 24, 2009) cnic v1.9.7b (Sep 24, 2009) ======================================================= Fixes ----- 1. Problem: For the cnic users would see in the kernel logs:
Cause: The function was not taking into account the wrapping of the software and hardware producer indexes.
Change: Recaculate the difference between the index with wrapping taken into account.
Impact: cnic
Enhancements ------------
1. Change: Updated firmware to 5.0.0.j5 which increased the rxpq depth from 32 to 256 to enhance the performance on systems without flow control.
Impact: 5709.
bnx2 v1.9.26c (Sep 17, 2009) ======================================================= Enhancements ------------ 1. Change: Cleanup the VMware NetQueue code. Eliminate unneeded RX flush routine, fix the number of queues to be the same on 1500 and 9000 MTU sized packets.
Impact: bnx2 VMware NetQ.
bnx2 v1.9.26b (Sep 14, 2009) ======================================================= Fixes ----- 1. Problem: VMware PSOD on MTU change
Cause: MSI-X window was remapped to the beginning of the PCI config space. The driver would disable the bar space because the MSI-X window was remapped incorrectly. This would eventually cause a PSOD.
Change: Before the chip reset, the driver would disable MSI-X, after the chip reset, MSI-X is re-enabled.
Cause: If the driver is unable to allocate memory for the buffers, the device is not properly shutdown.
Change: Added logic to shutdown device if unable to allocate buffers and complete the setup of the device.
Impact: bnx2, changing MTU and ring sizes.
Enhancements ------------ 1. Change: Updated firmware to 5.0.0.j3 for better small packet rx performance. Firmware also fixes header digest error during I/O.
Enhancements ------------ 1. Change: If a TX timeout occurs, there could be the possiblity that the chip is hung. By printing chip state into the kernel ring buffer, it will be easier to determine this.
Impact: bnx2 iSCSI.
2. Change: The bnx2 firmware should always be matched with the proper bnx2 driver. The bnx2 firmware version string are now printed. It will be easier to identify the running firmware.
Impact: bnx2
3. Change: When a TX timeout occurs and the chip is reset, the ability to debug the chip further is lost. This is because the chip state information is lost during the reset. The users have a choice to prevent the chip reset.
Impact: bnx2
4. Change: Add a check to see if there was a KCQ overflow was in the bnx2x firmware. Now this check has been moved to the CNIC so that the driver could control the cleanup/recovery.
Impact: bnx2 iSCSI.
bnx2 v1.9.21b (July 16, 2009) ========================================================== Enhancements ------------ 1. Change: Updated firmware to 5.0.0.j2 to fix remote reset problem
Impact: bnx2 iSCSI.
bnx2 v1.9.20b (July 09, 2009), cnic v1.9.3 (July 09, 2009) ========================================================== Fixes ----- 1. Problem: (CQ42534) cnic.c does not compile on older kernels.
Cause: Some iscsi_proto constants not defined in
Change: Added the constant definitions if not already defined.
Impact: None.
Enhancements ------------ 1. Change: Updated firmware to 5.0.0.j to fix TMF releated iSCSI issues.
Cause: cnic driver sets the MSS without knowing the actual MSS option and timestamp option during TCP connection.
Change: Changed driver to set MSS to 0xffff so that firmware can calculate MSS on its own.
Impact: bnx2x iSCSI.
2. Problem: 1G iSCSI fails when initiator and target MTUs don't match and timestamp is enabled.
Cause: Firmware was not adjusting for the 12-byte timestamp option if MSS was reduced by MSS option.
Change Updated firmware to 5.0.0.i
Impact: bnx2 iSCSI.
3. Problem: (CQ42353) Unable to disable TCP timestamp on 10G iSCSI.
Cause: Timestamp was hardcoded to be enabled for 10G.
Change: Update global timestamp option during each TCP connection.
Impact: bnx2x iSCSI.
4. Problem: (CQ42329) bnx2x MC assert during IPv6 login/logout.
Cause: EQ filled with more than 128 L4 kcqes without MSI-X interrupt for 2 seconds. The driver can only buffer 128 L4 kcqes.
Change: Increased L4 kcqe buffer to 256 entries as a temporary solution. Need to understand the delayed interrupt issue.
Impact: None.
bnx2 v1.9.18b (June 25, 2009), cnic v1.9.1 (June 24, 2009) ========================================================== Enhancements ------------ 1. Change: Added FTQDiscard counter to the list of counters being reported. During small packet test, there may be FTQ overflow and this counter is very useful.
Impact: None.
2. Change: Updated firmware to 5.0.0.h to improve small packet L2 performance and to enhance iSCSI TMF handling.
Impact: 5706/5708/5709.
bnx2 v1.9.17b (June 24, 2009), cnic v1.9.1 (June 24, 2009) ========================================== Fixes ----- 1. Problem: Leaking NetQueues if the firmware did not respond in time
Cause: System might be clogged and there is not enough time to process the KCQ
Change: Updated driver/firmware to allow the calling of the free RX queue request before a RX alloc request is issued
Impact: 5709
2. Problem: An offloaded iSCSI connection would get stuck
Cause: Issing an offload request might fail, and this was not handled properly.
Change: Updated driver/firmware to return the proper return code and handle offload connection failures.
Impact: 5706/5708/5709
3. Problem: tasklet_init() is being called on a task that is scheduled
Cause: When the CNIC calls register_device(), that task might already be schedled.
Change: tasklet_disable() is insufficient because the tasklet remains scheduled and stays on the tasklet list, instead tasklet_kill() is now used.
Impact: 5706/5708/5709
bnx2 v1.9.16b (June 10, 2009), cnic v1.9.0 (June 10, 2009) ========================================================== Enhancements ------------ 1. Change: (CQ38228) Use symbol_get() for ipv6 symbols so that the cnic driver will load without necessarily loading ipv6 modules.
Impact: iSCSI over IPv6.
2. Change: Updated 5706/08/09 MIPS firmware to 5.0.0.g.
Impact: 5706/08/09.
3. Change: Backported some dma_mapping_error() checking.
2. Change: In the cnic driver, save the last allocated TCP port during unregistration so that previously used TCP ports will not be immediately re-used.
bnx2 v1.9.13b (May 18, 2009) ========================================== Fixes ----- 1. Problem: Potentially exceeding the NetQueue limit recommendations by VMware which could stress system resources
Cause: When system resources are strained.
Change: There are now limits on the number of NetQueues which the driver will request: When the MTU is 1500 the max number of queues per port is 8 When the MTU is 9000 the max number of queues per port is 4
Impact: NetQueue enabled version of VMware ESX
2. Problem: Getting conflicting NetQueue and iSCSI completions
Cause: When MSI-X is not used on a 5709, NetQueue is still enabled
Change: NetQueue is not disabled is MSI-X is not used.
Impact: NetQueue enabled version of VMware ESX
bnx2 v1.9.12b (May 13, 2009) ========================================== Fixes ----- 1. Problem: Potentially returning a negative number of NetQueues
Cause: When calculating the number of rings, we use the calculation from the number of msi-x vectors returned, The number of NetQueues returned could potentially be negitive if only 1 vector was returned. This is because the driver was subtracting 2 instead of subtracting 1 (for the default queue) from the total number of rings.
Change: Return the proper number of queues not including the default queue.
Impact: NetQueue enabled version of VMware ESX
bnx2 v1.9.11b (May 12, 2009), cnic v1.8.5 (May 13, 2009) ======================================================== Fixes ----- 1. Problem: TCP Delay ACK not working on bnx2x iSCSI
Cause: Disabled in cnic driver.
Change: Fixed csk->tcp_flags definitions and enabled the proper storm bit for delay ACK.
bnx2 v1.9.10b, cnic v1.8.4 (May 11, 2009) ========================================== Fixes ----- 1. Problem: NetQ and iSCSI do not work in Vmware environment.
Cause: 1. cnic driver is overwriting CP and COM mailbox bit values newly defined to support multiple kcqs.
2. Firmware is completing some iSCSI kcqes on the NetQ's kcq.
Change: Fixed cnic driver to only set and clear bit 0 of the CP and COM mailbox.
Firmware has been updated to 5.0.0d. This firmware also supports TCP timestamp option for iSCSI connections.
Impact: 5706/5708/5709 iSCSI, NetQ.
bnx2 v1.9.9b (May 1, 2009) ========================================== Fixes ----- 1. Problem: There is link, but can't pass traffic on ESXi
Cause: Bits in the RX context are being trampled during the renegotiation of the link.
Change: RX context offset 0x6 should only be initialized once during init and not be updated during run-time. Offset 4 contains the BIDX that's mapped to the mailbox.
Impact: VMware with NetQueue
bnx2 v1.9.8b, cnic v1.8.2 (April 27, 2009) ========================================== Enhancements ------------ 1. Change: Updated cnic driver to support 1.50.x HSI as well as the older 1.48.107 HSI. A compile flag will be used to select one or the other.
Impact: iSCSI on bnx2x.
2. Change: Spec file and Makefile changes detect the proper module install directory.
Impact: installation.
bnx2 v1.9.7b, cnic v1.8.1 (April 22, 2009) ========================================== Fixes ----- 1. Problem: Compile error with redfinition of struct kwqe.
Cause: Both the CNIC and bnx2 defined this structure.
Change: Because the bnx2 definition is L2 specific, it was renamed to struct l2_kwqe.
Impact: None.
2. Problem: Add context memory DMA alignment for 57710.
Cause: For the 57710 context memory needs to be 16k aligned. Without this alignment you will see errors when trying to establish more then 5 iSCSI connections on VMware ESX 4.0 U1.
Change: Properly aligned the context memory by allocating a bigger chunk of memory and then finding the proper alignment. This reduces the number of possible connections in half but now we can properly establish more then 5 connections on VMware.
Impact: iSCSI.
bnx2 v1.9.6b (April 17, 2009) ============================= Enhancements ------------ 1. Change: Added NetQueue support for VMware.
Impact: 5709.
bnx2 v1.9.5b (April 17, 2009) ============================= Enhancements ------------ 1. Change: Updated to 5.0.0.a firmware with NetQ support and iSCSI max connection license information. RV2P firmware unchanged: 4.6.16 for 5706, 4.6.15 for 5709.
Impact: All chips.
2. Change: Set USE_INT_PARAM on 5709. This will switch the chip in use "interrupt mode" coalescing after MSI/MSI-X.
Impact: 5709.
3. Change: Included 5706 when doing statistics block DMA workaround.
Impact: 5706.
bnx2 v1.8.8b (March 12, 2009) ============================= Enhancements ------------ 1. Change: Updated to latest 4.6.17 CP firmware for 5709.
Impact: iSCSI licensing on 5709.
bnx2 v1.8.7b, cnic v1.7.8 (March 10, 2009) ========================================== Enhancements ------------ 1. Change: Reverted 5706/5708 firmware to 4.6.16. Low latency interrupt mode does not work on 5706/5708.
Impact: None.
2. Change: VMWare changes to expose max. number of iSCSI connections in the cnic_device structure.
Cause: msi related symbols undefined because CONFIG_PCI_MSI is not enabled on Xen kernels.
Change: Added CONFIG_PCI_MSI around the msi related code.
Impact: None.
2. Problem: (CQ39818) iSCSI targets do not reconnect after running self test.
Cause: Interrupt is disabled by bnx2 before notifying CNIC to clean up and stop. As a result, bnx2i will not receive interrupts when closing the connections if sharing INTA/MSI with network.
Change: Disable interrupt after notifying CNIC to stop.
Impact: iSCSI.
bnx2 v1.8.6b, cnic v1.7.7 (March 2, 2009) ========================================= Enhancements ------------ 1. Change: Updated to new 5706 firmware (4.6.17) and 5709 firmware (4.6.16). New interrupt coalescing mode for improved latency and iSCSI cache line fix on 5709.
Cause: Bug in bnx2_free_rx_mem(). The jumbo page ring memory was freed incorrectly using the wrong local variable as array index.
Change: Fixed bug by using the correct variable as array index.
Impact: Jumbo frames.
2. Problem: (CQ38965) iSCSI connection timeout on bnx2x.
Cause: During CFC Delete RAMROD completion handling, the wrong (older) iSCSI connection ID can sometimes be retrieved using the harware CID. The CID in the mapping table was not cleared after the CID was freed.
Fix: Adding clearing of the CID in the data structure after a CID is freed.
Impact: bnx2x iSCSI.
Enhancements ------------ 1. Change: (CQ38744) Reduced R2TQ memory usage to match new firmware interface (firmware 4.8.9). This reduces the amount of kernel memory substantially for each iSCSI connection on bnx2x.
bnx2 v1.8.2b, cnic v1.7.2 (Nov 25, 2008) ======================================== Fixes ----- 1. Problem: bnx2x iSCSI does not work on functions 2 or above.
Cause: This was caused by multiple problems: a) Status block ID specified by bnx2x was wrong. b) MSI-X vector assigned to CNIC was wrong. c) New method to ack. status block using HC register was not implemented. d) Status block ID in CSTORM status block is always 0, and as a result, the status block ID used to ack. the status block was wrong.
All these problems only affect functions 2 and above.
Change: All problems fixed in bnx2x and cnic.
Impact: bnx2x iSCSI.
bnx2 v1.8.2b, cnic v1.7.1 (Nov 15, 2008) ======================================== Enhancements ------------ 1. Change: Added CNIC support for Multi function bnx2x iSCSI.
Impact: bnx2x iSCSI.
bnx2 v1.8.2b, cnic v1.6.2 (Nov 12, 2008) ======================================== Enhancements ------------ 1. Change: Updated to latest 4.6.13 5709 firmware to fix context corruption with flow control enabled.
Impact: 5709.
2. Change: Added support for 5716S PCI ID.
Impact: None.
Fixes ----- 1. Problem: (CQ35904) Netdump does not work.
Cause: Problem introduced by MSI-X multiqueue. IRQ handlers were changed to take bnx2_napi parameter instead of netdev parameter.
Change: Fixed by passing proper parameter to IRQ handler from netpoll. All IRQ handlers are called when using multiple MSI-X vectors.
Impact: 5709 netpoll.
bnx2 v1.8.1f, cnic v1.6.1 (Nov 5, 2008) ======================================== Fixes ----- 1. Problem: All TSO packets corrupted on 5706/5708.
Cause: Firmware bug zeroing the wrong field in IP header.
Change: Updated to latest 4.6.11 5706/5708 firmware and 4.6.12 5709 Firmware.
Impact: 5706/5708/5709.
2. Problem: bnx2x chip asserts when trying to make iSCSI connection to an unknown IP address.
Cause: When connection fails, the driver sends a command to an unitialized CID.
Change: Added logic to only send deletion commands to initialized CIDs.
Impact: bnx2x iSCSI.
Enhancements ------------ 1. Change: Added support for one single VLAN to a bnx2x iSCSI interface.
Impact: bnx2x iSCSI.
bnx2 v1.8.1e, cnic v1.6.0 (Oct 27, 2008) ======================================== 1. Change: Updated to latest 5709 firmware to fix iSCSI data integrity problem.
Impact: 5709.
bnx2 v1.8.1d, cnic v1.6.0 (Oct 23, 2008) ======================================== Enhancements ------------ 1. Change: Updated to latest bnx2 firmware to fix iSCSI data integrity problem.
Impact: 5706/5708/5709.
2. Change: Updated to the latest bnx2x HSI files.
Impact: bnx2x iSCSI.
bnx2 v1.8.1c, cnic v1.5.9 (Oct 13, 2008) ======================================== Fixes ----- 1. Problem: (CQ37905) Unable to compile on SLES10 SP2.
Cause: DIV_ROUND_UP macro not defined in this kernel.
Change: Added it for compatibility.
Impact: None.
Enhancements ------------ 1. Change: Updated to latest 5709 firmware that fixes an NCSI problem.
Impact: 5709.
2. Change: Handle TCP reset in the middle of TCP close more appropriately.
Impact: iSCSI.
3. Change: Handle iSCSI license checking in the same way as 5708/5709.
Impact: iSCSI on bnx2x.
bnx2 v1.8.1b, cnic v1.5.8 (Oct 13, 2008) ======================================== Fixes ----- 1. Problem: bnx2x iSCSI CIDs may be allocated outside the range of allocated host memory.
Cause: CID range bigger than the amount of allocated host context memory.
Change: Changed to match the CID range with memory range.
Impact: bnx2x iSCSI.
Enhancements ------------ 1. Change: Sync'ed with the latest upstream driver bnx2 1.8.1.
Impact: None.
2. Change: Implemented iSCSI connection license enforcement for bnx2x devices.
Impact: bnx2x iSCSI.
bnx2 v1.8.0j, cnic v1.5.7 (Oct 6, 2008) ======================================== Fixes ----- 1. Problem: (CQ37610) Chip hangs when changing MTU with active iSCSI connections.
Cause: Both cnic and bnx2 drivers setting up the chip at the same time.
Change: Added check so that the register_cnic function will fail if the bnx2 driver is in reset.
Impact: iSCSI.
2. Problem: (CQ37762) Able to unload bnx2/bnx2x drivers while there are active iSCSI connections.
Cause: CNIC driver does not have a reference count on the BNX2/BNX2X drivers.
Change: This became a problem after the register_cnic function was no longer exported. To solve the problem, the CNIC driver will now get an explicit reference during register_cnic.
Impact: iSCSI.
3. Problem: (CQ37429) MMIO access while the chip is in D3hot state.
Cause: The driver does not check if_running state consistently during ethtool operations.
Change: Added proper checks to all ethtool and multicast change functions.
Impact: ethtool operations and multicast operations.
Enhancements ------------ 1. Change: Simplified ipv4 TSO logic in the driver. This was made possible with newer 5708 firmware.
Impact: 5708 TSO and other traffic.
2. Change: ethtool -p now blinks forever. This is the standard behavior in most other net drivers.
Impact: ethtool -p.
bnx2 v1.8.0i, cnic v1.5.5 (Sep 30, 2008) ======================================== Fixes ----- 1. Problem: (CQ36787) iSCSI login/logout commands fail on 5709 after a while.
Cause: Not handling the KWQ completion properly on 5709 in INTA/MSI mode.
Change: Changed to handle KWQ completions by checking the cmd_consumer_index instead of the rx_quick_index15.
Impact: 5709 ISCSI in INTA/MSI mode.
2. Problem: (CQ37497) CNIC driver does not compile on powerpc.
Cause: csum_ipv6_magic() not defined.
Change: Added #include
Impact: None.
v1.8.0g (Sep 24, 2008) ======================== Fixes ----- 1. Problem: (CQ37511) System locks up when loading cnic driver on 2.6.16 kernel.
Cause: symbol_put_addr() in 2.6.16 tries to acquire the same lock twice.
Change: Workaround by using __symbol_put() which does not have the same problem.
Impact: None.
v1.8.0f (Sep 23, 2008) ======================== Fixes ----- 1. Problem: (CQ37405) Kernel panic when performing ifup/ifdown with iSCSI connections on bnx2x devices.
Cause: Sending searcher delete to bnx2x devices when connection was not established (due to Spanning Tree or other reasons).
Change: Check PG offload state before sending searcher delete.
Impact: iSCSI on bnx2x.
v1.8.0e (Sep 22, 2008) ======================== Enhancement ----------- 1. Change: Updated to latest driver firmware 4.6.6 for 5709.
Impact: 5709.
2. Change: Updated cnic so that it will not crash even if using older bnx2/bnx2x drivers without CNIC support. The net driver can also be loaded after cnic and it will still work without crashing.
Impact: iSCSI.
3. Change: (CQ 37381) Updated driver to check Vaux PRESET before allowing WoL. This is needed to support 5709 quad-port boards.
v1.8.0c (Aug 25, 2008) ======================== Fixes ----- 1. Problem: Does not compile on older kernels.
Cause: "__maybe_unused" undefined on older kernels. "num_online_cpus()" undefined on 2.4 kernels.
Change: Added compatibility code to workaround.
Impact: None.
v1.8.0b (Aug 25, 2008) ======================== Enhancement ----------- 1. Change: Updated to latest driver firmware 4.6.2 for 5709.
Impact: 5709.
v1.7.9c (Aug 5, 2008) ======================== Fixes ----- 1. Problem: bnx2 does not compile on older kernels.
Cause: is missing on 2.6.19 and older kernels.
Change: Added compatibility code to check for kernel version before including the file.
Impact: none.
v1.7.9b (Aug 5, 2008) ======================== Enhancements ------------ 1. Change: Added multi-tx ring for 5709. This fetaure is available on 2.6.27 kernel when using MSI-X.
Impact: 5709
2. Change: Added support for 57710 iSCSI in the CNIC driver.
v1.7.7b (July 9, 2008) ======================== Enhancements ------------ 1. Change: Added probe function so that the CNIC driver can get the pci_device pointer earlier before registration.
Impact: iSCSI.
2. Change: Added support for 5716.
Impact: None.
v1.7.6c (June 6, 2008) ======================== Enhancements ------------ 1. Change: Added multi-ring RX support on 5709 using MSI-X. This feature is only available on 2.6.24 and newer kernels running on SMP machines.
Impact: 5709.
2. Change: Added secondary unicast address support. We now support up to 5 unicast addresses. This feature is only available on 2.6.23 and newer kernels.
Impact: All chips.
v1.7.6b.1 (Aug 14, 2008) ======================== Fixes ----- 1. Problem: (CQ36808) VLAN tagged packets received by host stack without the VLAN tag.
Cause: If no VLANs are set up using vconfig, and if the driver configures the chip to strip the VLAN tag, the problem can happen. With IPMI or UMP enabled, the driver is likely to configure the chip to strip the VLAN tag.
Change: Modified the driver to re-insert the VLAN tag when necessary. I.e. when IPMI/UMP is enabled and vconfig has not setup any VLANs.
Impact: All chips receiving VLAN traffic.
v1.7.6b (May 29, 2008) ======================== Fixes ----- 1. Problem: IPv4 TSO generates bad packet when the TSO packet size is 1-MSS.
Cause: Probably firmware does not expect this boundary condition.
Change: Detect this 1-MSS condition in driver and skip the TSO logic. 1-MSS TSO packet will be treated like a regular TX checksum offload packet.
Impact: TSO on all chips.
2. Problem: Cannot disable VLAN stripping even when management firmware is disabled.
Cause: The new logic to check firmware VLAN stripping capability was buggy.
Change: Fixed the code so that VLAN stripping can always be disabled if management firmware is disabled.
Impact: VLAN/management firmware.
v1.7.5d (May 13, 2008) ======================== Enhancements ------------ 1. Change: Incorporated latest firmware 4.4.18. Bug fix is in RV2P.
Impact: All chips.
v1.7.5c (May 7, 2008) ======================== Enhancements ------------ 1. Change: Incorporated latest firmware 4.4.17. Bug fix is in RV2P.
Impact: All chips.
v1.7.5b (May 5, 2008) ======================== Fixes ----- 1. Problem: (CQ35080) Hard lock when running ethtool -s on the device that is in the down state.
Cause: I/O to the device to set link speed in D3-hot state can cause lockup because the chip does not respond to I/O.
Change: ethtool -s will just store the new settings without configuring the new speed. When the device is later brought up, the new speed will be set as part of chip init.
Impact: All chips.
2. Problem: (CQ35075 CQ35042) Various compile errors on SuSE SLES 9 and SLES 10 distro kernels.
Cause: ip_hdr() and __le32/__le32 backported to the distro kernels.
Change: Adjusted compatibility defines.
Impact: None.
Enhancements ------------ 1. Change: Incorporated latest 5709 firmware 4.4.16. Timer context scanning is reduced with this firmware to 500us. With this, the temporary enhancement in 1.7.4c #2 has been removed.
Impact: 5709 iSCSI.
v1.7.4e (April 26, 2008) ======================== Fixes ----- 1. Problem: (CQ34841) 5709 does not link up on some remote PHY systems.
Cause: No initial link interrupt.
Change: Added code to poll for link when remote PHY is present.
Impact: Remote PHY systems.
2. Problem: (CQ34767) Kernel panic on 5709 when using jumbo frames with NCSI traffic.
Cause: RV2P bug causing RX packets to overwrite kernel memory.
Change: Updated to latest RV2P code for 5709 and 5708.
Impact: 5706/5708/5709.
v1.7.4d (April 17, 2008) ======================== Fixes ----- 1. Problem: IPv6 iSCSI does not work.
Cause: Added code in the last version 1.7.3c to check for CONFIG_IPV6 before enabling the IPv6 CNIC support. This failed to check for CONFIG_IPV6_MODULE if IPv6 is configured as module in the kernel configuration.
Change: Changed the checking to CONFIG_IPV6 or CONFIG_IPV6_MODULE.
Impact: None.
v1.7.4c (April 16, 2008) ======================== Fixes ----- 1. Problem: (CQ34814, CQ33984) Driver does not compile on 2.4 kernels.
Cause: __le32 and __be32 not defined in 2.4 kernels.
Change: Defined these as u32 on 2.4 kernels.
Impact: 2.4 kernels.
Enhancements ------------ 1. Change: Incorporated latest 5709 4.4.12 firmware to fix various iSCSI problems.
Impact: 5709.
2. Change: Slowed down the timer block reload time. It was noticed that after the CNIC driver was unloaded, the timer context memory was reloaded in a tight loop by the chip. This issue needs to be properly addressed in the firmware at a future date.
Impact: iSCSI.
v1.7.4b (April 11, 2008) ======================= Enhancements ------------ 1. Change: Incorporated latest 5709 4.4.11 firmware to fix various iSCSI problems.
Impact: 5709.
v1.7.3k (April 9, 2008) ======================= Enhancements ------------ 1. Change: Incorporated latest 5709 4.4.10 firmware to fix various iSCSI problems. CID ranges are now read directly from shared memory.
v1.7.3g (March 10, 2008) ======================= Enhancements ------------ 1. Change: Updated to latest 5709 firmware version 4.4.7.
Impact: 5709.
v1.7.3f (March 10, 2008) ======================= Fixes ----- 1. Problem: CNIC takes a long time to resolve ARP, causing iSCSI to fail.
Cause: NETEVENT_NEIGH_UPDATE event notifier sometimes takes a long time to be called.
Change: This is under investigation. For now, the workaround is to use the existing neighbour entry if it is in NUD_VALID state. Previously, we would only use it if it was in NUD_CONNECTED state.
Impact: iSCSI neighbour resolution.
2. Problem: iSCSI sometimes fails to initialize.
Cause: The KWQ is in full condition and prevents any KWQE to be sent to the firmware. This is caused by the KWQ consumer index in the status block not initializing to 0.
Change: Added workaround to skip the KWQ full condition check when sending the first KWQE. This should be properly fixed in firmware.
Impact: None.
v1.7.3d (February 15, 2008) ============================ Fixes ----- 1. Problem: System hangs with iSCSI traffic.
Cause: Infinite loop in NAPI poll.
Change: Fixed the problem of not comparing the CNIC tag properly when determining whether there is more work in NAPI poll.
Impact: None.
2. Problem: iSCSI does not work on 5709
Cause: Not initializing 5709 properly for iSCSI. The chip_id field was not propagated to the CNIC driver.
Change: Fixed the chip_id field.
Impact: None.
v1.7.3c (February 09, 2008) ============================ Enhancements ------------ 1. Change: Updated 5708 and 5709 firmware to version 4.4.2.
Impact: All devices.
2. Change: Updated RV2P firmware to the latest. This may fix the jumbo frame issue.
Impact: All devices, especially jumbo frames on 5709 Bx.
3. Change: Modified CNIC interface in preparation for 57710 devices.
Impact: iSCSI.
v1.7.2f (February 04, 2008) ============================ Fixes ----- 1. Problem: Temporary workaround for one prototype 5709S mezz. card not working.
Cause: The driver was looking at the wrong shared memory location to identify the card.
Change: Fixed the code to check the correct BNX2_SHARED_HW_CFG_CONFIG location.
2. Change: Added temporary workaround for one prototype 5709S mezz. card. The workaround will be removed once newer cards are available.
Impact: 5709S.
v1.7.1e (January 14, 2008) ============================ Enhancements ------------ 1. Change: Updated 5709 firmware to 4.1.1 for IPv6 iSCSI support.
Impact: 5709.
2. Change: Updated 5708 RXP firmware to 4.1.1.
Impact: 5706/5708.
3. Change: Updated RV2P firmware for 5709.
Impact: 5709.
4. Change: Added IPv6 support to CNIC driver.
Impact: New BNX2I driver must be used with this new CNIC driver.
v1.7.1d.3 (February 7, 2008) ============================ Fixes ----- 1. Problem: 5706S continues to not link down occasionally on some blade systems.
Cause: In some cases, even turning off the tx current does not cause the link to go down.
Change: Link transition can be triggered based on the SYNC_FAILED bit in the AN_DEBUG register when all else fails.
Impact: 5706S.
v1.7.1d.1 (February 1, 2008) ============================ Fixes ----- 1. Problem: 5706S still not linking down occasionally on some blade systems when the switch blade is disconnected.
Cause: Occasionally, all the bits that we check will falsely indicate link up and trigger the parallel detect logic on this blade platform. Once in parallel detect mode with autoneg disabled, the driver will never detect link down.
Change: Disabled parallel detect on this platform by checking PCI sub IDs to identify the device.
Impact: Parallel detect not supported on this vendor device.
v1.7.1d (January 25, 2008) ============================ Fixes ----- 1. Problem: 5706S still not linking down on some blade systems when the switch blade is disconnected.
Cause: This is the same problem that was fixed in 1.7.0b. After switch module is removed, the SYNC_FAILED bit sometimes toggles low, and this causes the parallel detect logic in the driver to trigger and disable autoneg. Disabling autoneg causes false link to come up immediately.
Change: It seems that the RUDI_INVALID bit can be used to prevent the above from happening. Modified parallel detect code to additionally check the RUDI_INVALID bit and trigger only when the bit is cleared.
Impact: Parallel detect logic in 5706S.
v1.7.1c (December 27, 2007) ============================ Fixes ----- 1. Problem: Driver crashes when adding VLAN and bonding.
Cause: Bonding calls driver's VLAN function in interrupt context with lock held. We recently added a VLAN feature in 1.6.8b which requires chip reset when VLANs are added or removed. The reset will call vmalloc/vfree which must not be called in interrupt context.
Change: Reverted the VLAN feature for now. Will workaround it in the future.
Impact: 5709 only. This new VLAN feature is no longer available.
v1.7.1b (December 24, 2007) ============================ Fixes ----- 1. Problem: Driver crashes when using jumbo frames on 5709 A1.
Cause: RV2P firmware problem.
Change: Disabled jumbo page ring on 5709 Ax chips.
Impact: Jumbo receive page rings not supported on 5709 Ax.
2. Problem: CNIC driver prints "Failed waiting for ref count to go to zero" when unloading the driver. This is a minor cosmetic issue.
Cause: Minor bug in driver comparing ref_count to 1 instead of zero during exit.
Change: Fixed the code to check for ref_count == 0.
Impact: None.
v1.7.0b (December 12, 2007) ============================ Fixes ----- 1. Problem: (CQ33032) CPU utilization increases dramatically when TSO is enabled.
Cause: Driver is spending a lot of unnecessary time in TX handling code when TSO is enabled. This regression was introduced when the TX handling code was changed to match the RX handling code. The RX handling code was changed to fix a packet rot problem. When TSO is enabled, the tx index can stop at non-packet boundaries and the code will keep waiting until it gets to the next packet boundary.
Change: Fixed it to handle this condition properly.
Impact: None.
2. Problem: 5706S does not link down in some blade systems.
Cause: Hardware problem.
Change: Added workaround logic to check periodically and force a link down when the PHY reports SYNC status failed. This only works when autoneg is enabled.
Impact: 5706S.
v1.6.8e (December 10, 2007) ============================ Fixes ----- 1. Problem: When using jumbo MTU with large RX ring sizes, system will crash or the driver won't load.
Cause: Bug in driver where the page descriptor array was declared too small.
Change: Fixed the array size.
Impact: None.
2. Problem: CNIC driver won't compile on kernels without CONFIG_PCI_MSI.
Cause: Some code needs to be conditionally compiled only when CONFIG_PCI_MSI is set.
Change: Added #ifdef CONFIG_PCI_MSI where necessary.
Impact: None.
3. Change: Disabled iSCSI on 5709 until next release.
Impact: None.
v1.6.8d (December 07, 2007) ============================ Change: Reverted the 5706S workaround made in 1.6.8c because it was unreliable.
Cause: RV2P firmware incorrectly placed jumbo data into SKB.
Change: New RV2P firmware.
Impact: Jumbo frames on all hardware.
2. Problem: (CQ32817) ethtool loopback test fails. 3. Problem: (CQ32842) Chariot test fails.
Cause: RX buffer size too small to contain MTU-sized frame. This was introduced by the new Jumbo RX logic.
Change: Fixed RX buffer size logic.
Impact: Traffic on all hardware.
4. Problem: (CQ32862) Fails to compile on RH9u9.
Cause: Kernel API skb_fill_page_desc() backported to RH kernel causing duplicate definition.
Change: Adjusted compatibility code.
Impact: None.
5. Problem: (CQ32866) ISCSI driver fails to compile with 1.6.8b.
Cause: print_mac() multiply defined when bnx2.h is included in the bnx2i driver.
Change: Changed print_mac() to static inline.
Impact: None.
6. Problem: 5706S does not link down in some blade systems.
Cause: Hardware problem.
Change: Added workaround logic to check periodically.
Impact: 5706S.
Enhancements ------------ 1. Change: Added flow control logic on 5709.
Impact: 5709.
2. Change: Updated all firmware to 4.0.5.
Impact: All hardware.
v1.6.8b (November 28, 2007) ============================ Enhancements ------------ 1. Change: Added MSIX support for 5709 B0.
Impact: 5709 B0.
2. Change: Added multi-page buffer support for Receive Jumbo frames.
Impact: All chips. This feature is experimental at this point.
3. Change: Allow VLAN tags in receive packets when management firmware is enabled.
Impact: 5709 only. This feature is experimental and requires new boot code and UMP/IPMI code.
4. Change: Updated firmware to 4.0.3.
Impact: All chips.
v1.6.7b (October 16, 2007) ============================ Fixes ----- 1. Problem: (CQ31861) Remote copper PHY does not link up if WoL is enabled.
Cause: bnx2_set_power_state() assumes that only copper devices support WoL and proceeds to configure the copper PHY to 10/100 Mbps. This assumption is no longer valid after Serdes WoL support was added in 1.6.3c.
Change: Fixed the code to take check for Serdes and copper when setting up the PHY for WoL.
v1.6.5b (September 25, 2007) ============================ Fixes ----- 1. Problem: (CQ30086) 5709 A1 does not link up when connected to some Broadcom devices.
Cause: Early DAC wakeup workaround needed for 5709 A1.
Change: Added workaround.
Impact: None.
Enhancements ------------ 1. Change: Added CNIC support for iSCSI.
Cause: Link test and loopback test were not modified to support remote PHY.
Change: Added remote PHY support to link test and changed the code to skip PHY loopback on remote PHY since it's not supported.
Impact: None.
2. Problem: (CQ30625) ethtool speed settings are lost after ifdown.
Cause: The remote PHY settings stored in firmware is not the same as the driver's last setting.
Change: Modified the code to keep the driver's setting unless there's is change in the remote PHY media.
Impact: ethtool -s on remote PHY systems.
Enhancements ------------ 1. Change: Change ethtool's wol setting to NVRAM's default and add support for Serdes WoL if NVRAM supports it.
Impact: ethtool wol's default setting.
v1.6.3b (July 13, 2007) ======================= 1. Problem: Problems reading and writing flash on 5709.
Cause: Hardware changes in 5709.
Change: Rearranged current flash code to properly support 5709.
Impact: Changes will impact flash operations on 5706/5708/5709 devices.
2. Problem: (CQ30516) Management firmware version string disappears on 2nd modprobe of the driver.
Cause: The 2nd modprobe will program the device back to D0 from D3hot. This causes a reset and it will take some time before the management firmware information will be available.
Change: Added a proper wait loop to wait for the firmware information to be deposited in shared memory.
Impact: None.
v1.6.2f (July 3, 2007) ======================= 1. Problem: The fix for CQ29488 in the previous version is problematic and needs to be reverted.
Cause: Adding the netif_carrier_off() call before register_netdev() in bnx2_init_one() can cause problems if register_netdev() fails. netif_carrier_off() can queue a link watch event that can run later. If register_netdev() fails, the netdev structure will be freed and the link watch event may panic when it is scheduled to run.
Change: Moving the netif_carrier_off() to after register_netdev() also will not work as it can cause race conditions with the interrupt handler. So the best thing to do is to revert the earlier fix and not address the CQ29488 issue.
Impact: CQ29488 is not fixed.
v1.6.2e (July 3, 2007) ======================= Fixes: ------ 1. Problem: (CQ29528) Link does not come up using remote PHY (continued).
Cause: ifup script may be using mii-tool to obtain link status, and interfering with remote PHY firmware.
Change: Block mii-tool ioctl access when remote PHY firmware is present.
Impact: None.
2. Problem: (CQ29488) Driver reports link up in ethtool before the interface is brought up.
Cause: The netdevice structure's initial link setting is up and that gets reported directly by ethtool.
Change: Added netif_carrier_off() call in bnx2_init_one().
Impact: None.
v1.6.2d (June 22, 2007) ======================= Fixes: ------ 1. Problem: (CQ29528) Link does not come up using remote PHY.
Cause: The fix in 1.6.2b still has a problem. The copper or Serdes default link setting does not follow the correct port when the port is changed during chip reset.
Change: Fix the code to always refresh the port and link setting during chip reset.
Impact: None.
2. Problem: (CQ30181) Cannot compile on 2.4 kernels.
Cause: USEC_TO_SEC constant is not defined on older kernels.
Change: Added conditional #define for this constant on older kernels.
Impact: None.
Enhancements: ------------- 1. Change: Update 5709 firmware to 3.7.1.
Impact: 5709 devices.
v1.6.2b (June 21, 2007) ======================= Enhancements: ------------- 1. Change: Added management firmware version to ethtool -i.
Impact: None.
Fixes: ------ 1. Problem: (CQ29528) Link does not come up using remote PHY.
Cause: The driver is using the wrong port when setting up the remote PHY link.
Change: Fixed bug to always use the correct requested port or default port when setting remote PHY link.
Impact: None.
2. Problem: (CQ30028) Advertised Autoneg not set in ethtool.
Cause: Remote PHY code is not setting the flag which is for information only.
Change: Added code the set the flag for consistency.
Impact: None.
v1.6.1c (May 22, 2007) ===================== Enhancements: ------------- 1. Change: (CQ28907) Added support for setting copper and fibre speeds.
v1.5.10c (May 4 , 2007) ======================= Fixes: ------ 1. Problem: Extremely low TSO performance when destination has a smaller MSS than the source.
Cause: Packets smaller than MTU are not processed as TSO packets.
Change: Removed the SKB length check when doing TSO.
Impact: None.
v1.5.10b (May 1, 2007) ========================= Enhancements: ------------- 1. Change: Removed Remote PHY until next release.
Impact: No Remote PHY support.
2. Change: Added check for 2.5G capability before enabling 2.5G on 5709S.
Impact: None.
Fixes: ------ 1. Problem: (CQ28438) NETDEV WATCHDOG after OS boot.
Cause: The mailbox queue is halted after the OS reads config. register 0x94.
Change: Set MQ_CONFIG_HALT_DIS in register MQ_CONFIG on 5709 A0 and A1.
Impact: None.
v1.5.9b (April 20, 2007) ======================= Enhancements: ------------- 1. Change: Enhanced remote PHY support for 5708S.
Impact: None.
Fixes: ------ 1. Problem: (CQ29056) Driver does not compile on SLES 10 SP1 kernel.
v1.5.1b (November 15, 2006) =========================== Enhancement: ------------ 1. Change: Added support for 5709.
Impact: None.
v1.4.52c (March 07, 2007) ========================= Enhancement: ------------ 1. Change: Increase maximum receive ring size to 4080. The default is kept the same at 255.
Impact: None.
v1.4.51b (December 21, 2006) ============================ Fixes: ------ 1. Problem: (CQ27802) Cannot enable flow control in some cases.
Cause: In some cases when flow control is forced to on, the driver detects no changes in advertisement, and as a result, will not re-autoneg. Without the link change, flow control settings will not change.
Change: Added some code to setup flow control when no other PHY settings are made. This will ensure that flow control changes will take effect immediately.
Impact: None.
v1.4.50b (December 15, 2006) ============================ Fixes: ------ 1. Problem: (CQ27424) Panic when writing to nvram.
Cause: Bug in driver when an alignment buffer is used
Change: Fixed the bug so that the alignment buffer is freed with the correct pointer.
Impact: None.
v1.4.49b (December 13, 2006) ============================ Fixes: ------ 1. Problem: (CQ27459) Driver reports link down when link is up.
Cause: Hotplug scripts can cause bnx2_open() to be called immediately after bnx2_init_one() calls register_netdev(). The initial link state set after register_netdev() may overwrite the actual link state set by the link handler on SMP systems.
Change: Move all initial state setup code to before calling register_netdev().
Cause: Bug in determining tx ring space when the tx ring is completely full.
Change: Fixed the flawed logic in bnx2_tx_avail().
Impact: None.
2. Problem: (CQ27424) Buffer overflow when writing to nvram.
Cause: Bug in driver when the beginning NVRAM offset is not 4-byte aligned.
Change: Fixed the bug to allocate enough buffer space.
Impact: None.
3. Problem: (CQ27543) Loopback failed if MAC address is changed.
Cause: Driver uses permanent MAC address for loopback which may be different from a locally administered address.
Change: Fixed by alwaysing using the current MAC address in the netdevice structure.
Impact: None.
v1.4.47b (November 02, 2006) =========================== Fixes: ------ 1. Problem: (CQ25922) 5708S does not pass PHY loopback test on some blade servers.
Cause: It takes longer (about 100msec) to link up in some backplane environments when the Serdes is set to PHY loopback mode.
Change: Increase delay loop to up to 1 sec when waiting for link up after PHY loopback. Previous wait time was 100usec.
Impact: None.
v1.4.46b (October 30, 2006) =========================== Fixes: ------ 1. Problem: (CQ25916) Device does not receive packets when configured by the Xen bridge script and when IPMI is enabled.
Cause: Firmware does not forward packets to the host when the device is in promiscuous mode in some cases.
Change: Firmware change and driver change to enable the BNX2_RPM_SORT_USER0_PROM_VLAN bit when going into promiscuous mode.
Impact: None.
v1.4.45b (October 19, 2006) =========================== Enhancement: ------------ 1. Change: Added software parallel detection on 5708S to link at 1000Mbps or 2500Mbps automatically if the link partner is forced at 2500Mbps.
Impact: None.
2. Change: Added 2500Mbps forced speed setting. Setting it requires a future version of ethtool or custom apps.
Impact: None.
3. Change: Port driver to compile on 2.6.19 kernel.
Impact: None.
Fixes: ------ 1. Problem: Driver does not complile on 2.4 kernels.
Cause: TSO symbols not defined in 2.4 kernels.
Change: Added #ifdef for compatibility.
Impact: None.
2. Problem: MSI doesn't work on 5706 when the host bridge is AMD8132.
Cause: Compatibility issue.
Change: Added code to disable MSI when 5706 is on a systems with AMD8132.
Impact: 5706 cannot use MSI on such systems.
v1.4.44b (August 10, 2006) ========================== Fixes: ------ 1. Problem: A rare tx race window exists in the tx path.
Cause: CPU re-ordering can cause the tx queue to be stopped forever when the tx ring is full in a very rare condition. See ChangeLog for more details.
Change: Fixed the race condition with memory barriers. See ChangeLog for more details.
Impact: None.
Enhancement: ------------ 1. Change: Increase default rx ring size to 255 to prevent packet drops under heavy load.
Impact: Higher memory usage.
2. Change: Port driver to run on 2.6.18 kernel.
Impact: None.
v1.4.43b (June 26, 2006) ======================= Enhancement: ------------ 1. Change: (CQ25508) Use DRV_MSG_CODE_UNLOAD_LNK_DN message on 5708 B1 and older chips so that the link will turn off after ifdown.
Impact: None.
v1.4.42b (June 2, 2006) ======================= Fixes: ------ 1. Problem: (CQ22585) WoL cannot be enabled on 5708 B2.
Cause: Hardware limitation in previous 5708 versions required driver to always disable driver WoL on 5708.
Change: With the issue fixed in B2, the driver was changed to allow 5708 B2 and above to support driver WoL.
Impact: None.
2. Problem: (CQ21779) Driver does not report dropped receive packets.
Cause: Packets dropped by firmware are reported in a scratch pad location in memory separate from other counters.
Change: Added code to report this firmware counter.
Impact: None.
Enhancements: ------------- 1. Change: (CQ24690) Allow driver to be compiled for non-running kernels.
Impact: None.
v1.4.41b (May 17, 2006) ======================= Fixes: ------ 1. Problem: Driver writes wrong data to non-buffered flash.
Cause: Bug in driver causing the unchanged portion of the page to be corrupted.
Change: Fixed bug.
Impact: None.
v1.4.40b (April 17, 2006) ========================= Enhancements: ------------- 1. Change: Combine 2 small memory allocations into 1.
Impact: None.
2. Change: Separate tx consumer and producer entries into separate cache lines for better performance.
Impact: None.
3. Change: Compress firmware data to reduce driver size.
Impact: Driver now requires zib_inflate library which should be available on most vendor kernels.
v1.4.39b (Mar. 10, 2006) ======================= Fixes: ------ 1. Problem: (CQ23181) Driver loses track of link changes in some cases.
Cause: In some cases, the status block gets a link change indication that contradicts with the MII link status. This is due to transient link signals during link changes.
Change: Add coalesce_now at the end of link change interrupt to flush out the transient behavior.
Impact: None.
2. Problem: 5708 only supports 40-bit DMA addresses.
Cause: Limitation of the built-in PCIE-to-PCIX bridge.
Change: Add workaround code to make sure all DMA addresses are less than 40 bits.
Impact: Some minor impact on performance on some 64-bits systems. There should be practically no performance impact on i386 and x86_64 systems.
3. Problem: "Copyright" deprecated in RPM spec file.
Change: Changed to "License".
Impact: Should be none on the distributions that we support.
v1.4.38b (Feb. 10, 2006) ======================= Fixes: ------ 1. Problem: Setting rx ring size to 255 causes memory allocation errors.
Cause: Multiple bugs that do not handle the full ring properly.
Change: Fixed all bugs related to full ring handling and changed maximum ring size from 4080 to 1020 after discussion with Dave Miller.
Impact: Maximum rx ring size is now smaller.
2. Problem: Compile warnings and panic on IA64.
Cause: not included.
Change: Added include .
Impact: None.
v1.4.36b (Jan. 19, 2006) ======================= Version number update.
v1.3.36 (Jan. 17, 2006) ======================= Fixes: ------ 1. Problem: (CQ22827) bnx2 does not compile on 2.6.6 and earlier kernels.
Cause: Introduced bug while fixing CQ22666.
Change: Fix compatibility code.
Impact: None.
2. Problem: (CQ22823) bnx2 reports extra .5 at the end of firmware version string.
Change: Skip the last digit in the firmware version string.
Impact: None.
3. Problem: (CQ22585) WoL still does not work on 5708.
Cause: New WoL mechanism introduced in 1.3.34 has a flaw.
Change: Removed the workaround code and disabled WoL support on 5708. During shutdown and suspend, the driver will shutdown the device and WoL will be setup by the bootcode according to the nvram's out-of-box WoL setting.
Impact: 5708 will not support driver-initiated (ethtool-intiated) WoL.
v1.3.35 (Jan. 17, 2006) ======================= Fixes: ------ 1. Problem: (CQ22666) bnx2 driver does not compile on RHEL3 U7.
Cause: if_mii() back-ported to RHEL3 U7.
Change: Adjusted the compatibility code.
Impact: None.
2. Problem: (CQ22718) UMP connection is lost after enabling WoL.
Cause: FORCE LINK was mistakenly set during WoL setup.
Change: Do not set FORCE LINK.
Impact: None.
v1.3.34 (Jan. 13, 2006) ======================= Fixes: ------ 1. Problem: (CQ22585) WoL does not work on 5708.
Cause: Internal bridge not in proper PME state.
Change: Added new firmware message to allow bootcode to help set up WoL.
Impact: None.
Enhancements: ------------- 1. Change: Added compile option to include crc32 function for RH2.4 boot kernels.
Impact: None.
2. Change: Updated TSO firmware to handle ECN.
Impact: None.
v1.3.33 (Dec. 12, 2005) ======================= Enhancements: ------------- 1. Change: Increased firmware hand-shake timeout from 50 msec to 100 msec. Also changed the delay from busy-wait udelay to non-busy-wait msleep.
Impact: None.
2. Change: Added code to read nvram size from shared memory if available. Otherwise, the size will come from the flash table which only gives the smallest size for that type of flash.
Impact: None.
3. Change: Added workaround to issue 2 separate IOs for interrupt acknowledgement. The workaround is only used for INTA (non-MSI) interrupts.
Impact: Slightly higher overhead for INTA interrupts.
v1.3.32 (Dec. 01, 2005) ======================= Enhancements: ------------- 1. Change: Added PHY loopback to the loopback selftest.
2. Change: Enabled customized pre-emphasis and other serdes control settings on 5708S backplane devices. A special PHY register will be programmed according to the NVRAM value.
Impact: None.
3. Change: Modified Makefile to check for the source symbolic link in the kbuild environment.
Impact: None.
4. Change: Improved NAPI poll processing so that all events will be processed before interrupts are re-enabled. This will reduce the number of unnecessary interrupts.
Impact: None.
5. Change: Add support for ETHTOOL_GPERMADDR (from John Linville)
Impact: None.
Fixes: ------ 1. Problem: Bug in irq handler causing extra register read.
Cause: Bug in bnx2_interrupt() reading BNX2_PCICFG_MISC_STATUS register when it is not necessary.
Change: Fixed the logic bug and added prefetch of status block in msi handler.
Impact: None.
v1.3.25 (Aug. 22, 2005) ======================= Fixes: ------ 1. Problem: Ethtool register and memory tests fail on 5708.
Cause: Some code was not merged properly many versions ago.
Change: Merged in properly code.
Impact: None.
Enhancements: ------------- 1. Change: Slow down flash clock speeds
Impact: None.
2. Change: Code re-sync'ed with upstream driver.
Impact: None.
v1.3.24 (Aug. 16, 2005) ======================= Enhancements: ------------- 1. Change: Changed all spin_lock_irqsave locks to spin_lock_bh for better overall system performance. All code requiring spin_lock runs in BH or user context.
Impact: None.
2. Change: Removed atomic operations in the transmit fast path. Code should run a bit faster as atomic operations can be quite slow.
Impact: None.
v1.3.23 (Aug. 10, 2005) ======================= Enhancements: ------------- 1. Change: Added reporting of link speed to firmware.
Impact: None.
2. Change: Added shared memory base look-up.
Impact: None.
3. Change: Possible sparse fixes (from Peter Hagervall) - use C99 struct initializers - make a few arrays and structs static - remove a few uses of literal 0 as NULL pointer - use convenience function instead of cast+dereference in bnx2_ioctl() - remove superfluous casts to u8 * in calls to readl/writel
Impact: None.
4. Change: Updated documentation with the crc32 library requirement and other minor updates.
Impact: None.
v1.3.22 (July 25, 2005) ======================= Enhancements: ------------- 1. Change: Added check for default link speed setting in shared memory. This allows some blade servers that don't support autoneg to default to forced speed to speed up link-up time.
Impact: None.
2. Change: Changed timer code to speed up the timer after serdes autoneg. This speeds up the time for parallel detection when the link partner does not autoneg. After autoneg or parallel detction completes, timer goes back to normal 1 HZ interval. With the new scheme, link should be detected up using parallel detection in less than 0.7 seconds. Autoneg normally completes in 120 msec exchanging base pages and 3 next pages.
Impact: None.
v1.3.21 (July 21, 2005) ======================= Enhancements: ------------- 1. Change: Updated firmware to properly handle TSO packets with ECN bits set.
Impact: None.
2. Change: Updated to latest rxp firmware.
Impact: None.
3. Change: Added check for the 2.5G capability in shared memory.
Impact: None.
4. Change: Expanded nvram support for 5708.
Impact: None.
Fixes: ------ 1. Problem: (CQTO1511) Downing a team of bnx2 adapters causes hang.
Cause: Deadlock when the second adapter's close routine calls flush_scheduled_work() because the linkwatch_event is scheduled on the work queue when the first adapter is closed. The linkwatch_event will try to get the rtnl_lock which is already held by the bnx2_close routine.
Change: Fixed by not calling flush_scheduled_work(). Instead, use a flag to indicate work is pending and wait until the flag is cleared.
Impact: None.
2. Problem: (CQTO1439) ethtool -S on 5708 causes oops.
Cause: A pointer is not initialized if the device is 5708.
Change: Added proper initialization.
Impact: None.
3. Problem: Some error counters are mis-reporting.
Cause: The workaround for the hw errata is not applied properly on the chips with the errata.
Change: Added proper checks for the workaround.
Impact: None.
4. Problem: High BER on 5708 SerDes.
Cause: hardware errata.
Change: Added workaround for 5708 A0 and B0.
Impact: None.
v1.3.19 (May 27, 2005) ======================= Enhancements: ------------- 1. Change: Merged 5708 code with the latest 1.1.19.
Impact: None.
Fixes: ------ 1. Problem: (CQTO1260) 5708S does not link at 1000Mbps when forced. It links at 2500Mbps when connected back-to-back with another 5708S.
Cause: 2.5G bit is still turned on.
Change: Fixed by turning off 2.5G when the speed is forced.
Impact: None.
v1.1.19 (May 26, 2005) ======================= Enhancements: ------------- 1. Change: Made significant changes to merge into the kernel. Among them, consolidate all source files into bnx2.[ch] and bnx2_fw.h, change structure style register definitions to offset based.
Impact: None.
Fixes: ------ 1. Problem: Excessive stack usage.
Cause: Use of local variable array.
Change: Fix excessive stack usage in bnx2_alloc_bad_rbuf() by replacing local variable array with kmalloc array. Also changed function to return error code, and changed some of the callers to check for the return code.
Impact: None.
2. Problem: Bug in receive checksum.
Cause: Software bug.
Change: Fix bug in rx checksum by indicating CHECKSUM_UNNECESSARY only when the hw calculated checksum is 0xffff.
Impact: None.
3. Problem: Excessive busy loop.
Cause: Software bug.
Change: Replaced one excessive udelay of 15msec with msleep since the calling context is always process.
Impact: None.
4. Problem: Need to call flush_scheduled_work() and bnx2_netif_stop().
Cause: Bug in bnx2_close().
Change: Fix bug in bnx2_close() by calling flush_scheduled_work() since we are using a work queue in netdev watchdog. Also added bnx2_netif_stop() call in bnx2_close().
Impact: None.
5. Problem: Some symbols do not have bnx2 prefix and are not static.
Change: Add bnx2_ prefix to some remaining names and mark some remaining names static.
Impact: None.
v1.1.17 (Apr. 7, 2005) ======================= Fixes: ------ 1. Problem: Driver does not compile on 2.6.12 kernel.
Cause: pci_dev->slot_name has been deprecated.
Change: replaced with pci_name.
Impact: None. All kernels supported by bnx2 including 2.4.21-*EL have pci_name defined.
v1.1.16 (Mar. 16, 2005) ======================= Fixes: ------ 1. Problem: (CQTO936 & 1004) Tx carrier and rx_byte_errors reported during normal operations.
Cause: 5706 hardware errata on these 2 statistics counters.
Change: Modified driver to skip these 2 counters.
Impact: These 2 counters will always report 0 and not the true statistics.
v1.1.15 (Mar. 09, 2005) ======================= Enhancements: ------------- 1. Change: Added code to program proper phy settings for jumbo frames on copper and serdes devices.
Impact: None.
2. Change: Changed INTx ISR to handle a valid case where INTx arrives before status block update.
Impact: None.
3. Change: Added a separate ISR for MSI to handle subtle differences between INTx and MSI.
Impact: None.
v1.1.14 (Mar. 03, 2005) ====================== Fixes: ------ 1. Problem: netdump does not work on latest RH3EL errata kernel.
Cause: #define RED_HAT_LINUX_KERNEL removed from kernel include files, causing netdump poll function to be compiled wrong for RH kernels.
Change: Changed Makefile to workaround the problem.
Impact: None.
v1.1.12 (Feb. 25, 2005) ====================== Fixes: ------ 1. Problem: (CQTO1062) Driver allows ethtool to set illegal speed/duplex on fiber cards.
Cause: Missing checks for the case where autoneg is off.
Enhancements: ------------- 1. Change: The code to handle tx queue full condition was redone to properly handle all boundary and race conditions.
Impact: Minimum tx ring size is now MAX_SKB_FRAGS+1.
2. Change: Tx timeout code was changed to work queue context. This allows netif to be shutdown gracefully before chip reset.
Impact: None.
3. Change: Added memory barriers to ISR and NAPI poll for correctness.
Impact: None.
v1.1.8 (Feb. 01, 2005) ====================== Fixes: ------ 1. Problem: (CQTO969) No interupts on a system that does not support MSI.
Cause: On this system, the MSI generated in the MSI test terminates with Master Abort which is a fatal condition for the chip.
Change: A chip reset is added when MSI test fails to bring the chip back to normal operations again (in INTx mode).
Impact: None.
Enhancements: ------------- 1. Change: Removed register 0x84 from the ethtool register test. This is an interrupt control register that should not be touched to prevent unwanted interrupts.
Impact: None.
v1.1.7 (Jan. 28, 2005) ====================== Enhancements: ------------- 1. Change: Added interrupt test when MSI is enabled. If MSI test fails, driver will fallback to INTx mode.
Impact: None.
2. Change: Added test for certain chipsets where MSI is known to fail, and disable MSI unconditionally when such chipsets are found.
Impact: None.
3. Change: Removed support for 1000 Mbps half duplex.
Impact: 1000 Mbps half duplex will no longer work.
v1.1.6 (Jan. 26, 2005) ====================== Fixes: ------ 1. Problem: (CQTO940) MTU size not set properly when device is down.
Cause: bnx2_change_mtu only handled the "up" case.
Change: Simple fix to handle the "down" case as well.
Impact: None
2. Problem: (CQTO926) 5706S does not autoneg properly after the tx cable is pulled.
Cause: If the link partner is autonegotiating, autoneg will fail when the tx cable is pulled. The software will turn off autoneg seeing that the rx cable is still attached with SIGNAL_DETECT. When the tx cable is re-attached, autoneg is still off and the link partner will not establish link.
Change: Added code to poll another PHY register to check if configs are received when autoneg is disabled.
Impact: None
Enhancements: ------------- 1. Change: Added OEM product name strings.
Impact: None.
v1.1.5 (Jan. 25, 2005) ====================== Fixes: ------ 1. Problem: PCI-X bus speed may not be detected correctly by the driver, causing failure because certain register settings are done based on bus speed.
Cause: hardware problem.
Change: Use a different register to detect PCI-X speed.
Impact: None.
v1.1.4 (Jan. 17, 2005) ====================== Fixes: ------ 1. Problem: 5706S does not reliably detect link up or down.
Cause: hardware problem.
Change: Enabled hardware workaround which is effective in A2 and newer chips only.
Impact: None.
v1.1.3 (Jan. 13, 2005) ====================== Fixes: ------ 1. Problem: netdump does not work.
Cause: poll_controller routine does not work in NAPI mode.
Change: Fixed poll_controller routine for NAPI mode.
Impact: None.
Enhancements: ------------- 1. Change: Added the new mmiowb macro which is used mainly in NUMA machines to guarantee PCI ordering.
Impact: None.
2. Change: Added OEM product name strings.
Impact: None.
3. Change: Changed ONE_TDMA workaround on systems with P64H bridge to PING_PONG_DMA on all systems using PCI.
Impact: Better performance and better compatibility on all PCI systems.
4. Change: Added "disable_msi" parameter to allow disabling MSI.
Impact: None.
5. Change: Reduced default tx coalescing parameters for better tx only performance such as ttcp.
Impact: None.
6. Change: Changed NIC detection console message to display more information.
Impact: None.
7. Change: Cleaned up some Linux .h files that are not needed.
Impact: None.
8. Change: Cleaned up the nvram routines.
Impact: None.
v1.1.2 (Nov. 11, 2004) ====================== Fixes: ------ 1. Problem: Unable to load the driver on more than 2 or 3 devices.
Cause: Default register space is too big. System fails to map the register space on the 3rd or 4th device.
Change: Changed driver to map a smaller register space as the higher registers are not needed for standard operations.
Impact: None.
v1.1.1 (Nov. 9, 2004) ====================== Fixes: ------ 1. Problem: (CQTO656) One remaining ethtool parameter can be set out of range.
Cause: Wrong upper bounds in code.
Change: Fixed upper bound.
Impact: None.
1. Problem: 5706 A1 cannot be run on a PCI bus.
Cause: Hardware errata.
Change: Added workaround to detect 5706 A1 on PCI bus and abort.
Impact: Driver will not load 5706 A1 on PCI bus.
v1.1.0 (Oct. 29, 2004) ====================== Fixes: ------ 1. Problem: (CQTO663) No link on fiber NIC set to autoneg when the link partner is set to forced speed.
Cause: No code to handle this case.
Change: Added code to check SIGNAL DETECT when autoneg fails, and turn off autoneg when appropriate. Also added code to force a link down when speed settings are changed.
Impact: None.
2. Problem: (CQTO649) ifconfig up/down can cause system to hang on 2.6 kernels using mmconfig.
Cause: Dummy read in the kernel's pci_mmcfg_write routine may cause system to hang during D3hot -> D0 transition. The PLL may lose lock during the internal D0 transition chip reset and cause the dummy read to hang.
Change: The PLL problem will be fixed in A2. Meanwhile, the driver is changed to go into D3hot only if wol is enabled.
Impact: Minor impact in increased power consumption when the driver is shutdown with wol disabled.
3. Change: Changed to use pci_get_device as pci_find_device will be deprecated soon.
Impact: None.
4. Problem: (CQTO656) Some ethtool parameters can be set out of range.
Cause: Wrong upper bounds in code or documentation.
Change: Fixed code and documentation.
Impact: None.
v1.0.15 (Oct. 15, 2004) ====================== Fixes: ------ 1. Problem: (CQTO644) Data corruption when sending FTP traffic on Dell Precision 530MT.
Cause: PCI bridge errata.
Change: Added code to enable ONE_TDMA workaround when P64H PCI bridge is detected.
Impact: Slower tx performance on systems using P64H bridge.
2. Problem: (CQTO643) Driver allows MTU to be set up to 9004.
Cause: Driver used the wrong upper bound limit.
Change: Fixed the upper bound.
Impact: None.
3. Problem: Driver does not support forced speed on 5706S.
Cause: Missing software logic.
Change: Added code to support forced 1000 Full and Half duplex.
Impact: None.
4. Change: Added workaround to disable PERR generation on 5706 A1 when it is in PCI 64-bit slot.
Impact: None.
v1.0.14 (Oct. 05, 2004) ====================== Fixes: ------ 1. Problem: Driver load/unload hangs on some machines.
Cause: Transition delay required during D3hot -> D0 transition.
Change: Added necessary delay.
Impact: None.
v1.0.12 (Oct. 04, 2004) ====================== Fixes: ------ 1. Problem: (CQTO609) New flow control parameter does not take effect until ifdown/ifup or link down/up.
Cause: New flow control settings are only configured during link up. The driver did not check flow control advertisement changes and therefore no re-negotiation and no link down.
Change: Fixed logic so that link will always go down whenever there is a change a flow control advertisement.
Impact: None.
2. Problem: (CQTO612) VLAN packet reception not working.
Cause: VLAN #define not setup properly.
Change: Fixed #define for VLAN.
Impact: None.
3. Problem: (CQTO628) WoL not functioning correctly.
Cause: Multiple problems in the WoL code.
Change: Fixed by: 1. using sort mode. 2. setting up mac address correctly.
Impact: None.
Enhancements: ------------- 1. Change: Added support for non-dword and non-aligned write access to eeprom, allowing ethtool -E to work.
Impact: None.
v1.0.11 (Sep. 24, 2004) ====================== Fixes: ------ 1. Problem: (CQTO600) Kernel panic when attempting to ftp on Fedora kernel.
Cause: skbuffs are 4-byte aligned on Fedora, causing the rx headers to be misaligned. skbuffs are 16-byte aligned on other standard kernels.
Change: Removed any assumptions about skbuff alignment and added code to align all rx skbuffs to 8-byte boundaries.
Impact: None.
Enhancements: ------------- 1. Change: Added netif_carrier_off to Driver init code so that the initial link state is off.
Impact: None.
v1.0.10 (Sep. 23, 2004) ====================== Fixes: ------ 1. Problem: (CQTO599) Driver fails to compile on RH 3.0ES.
Cause: Bug in poll_bcm5706 where bp is referenced without being defined.
Change: Fixed the minor bug.
Impact: None.
v1.0.9 (Sep. 23, 2004) ====================== Fixes: ------ 1. Problem: Jumbo frames not working reliably.
Cause: Bug in bcm5706_reuse_rx_skb.
Change: Fixed the bug so that the host address is properly copied from one BD to the other.
Impact: None.
Enhancements: ------------- 1. Change: Change the locking scheme for more reliable open/close/ioctl operations where the spinlock is needed.
Impact: None.
2. Change: Added minimum MTU size check for MTU changes.
Impact: None.
v1.0.8 (Sep. 20, 2004) ====================== Fixes: ------ 1. Problem: (CQTO561) Kernel panic on RH30EL after repeated driver load/unload.
Cause: Occasionally, the system is unable to map device registers, causing subsequent register access to fail.
Change: Added check for the return value from ioremap, and exit gracefully if it fails.
Impact: None.
2. Problem: (CQTO574) NETDEV WATCHDOG when running 5706 A1 on PCIX 133MHz slot.
Cause: Some hw register setup required for 133 Mhz.
Change: Added the register setup code.
Impact: None.
3. Problem: (CQTO468) Link does not go down after changing from 10Mbps full (forced) to 10Mbps half (forced) and vice versa when the link partner is also using forced speed.
Cause: Delay not long enough for the link to go down.
Change: Not practical to increase delay as a very long delay is needed for the link to go down. Added code to record the proper link speed and duplex when speed is forced so that ethtool will return the proper speed without the link going down. Note that the link will go down if the link partner has autoneg turned on, ensuring that the link partner will see the link change.
Impact: None.
Enhancements: ------------- 1. Change: Added power management and WOL during device close. This will allow WOL to work after Linux shutdown.
Impact: None.
2. Change: Changed driver so that ethtool will report invalid speed after ifdown.
Impact: None.
3. Change: Updated tpatfw.h
Impact: None.
v1.0.7 (Sep. 14, 2004) ====================== Fixes: ------ 1. Problem: (CQTO523) 5706 A1 hangs after a thousand iterations of load/ifup/ifdown/unload.
Cause: The driver may be servicing an interrupt within 15 msec of chip reset, causing the chip to hang. The problem was aggravated by the timer mode coalescing which created an excessive number of interrupts (hardware problem).
The Driver may also occasionally see the wrong firmware signature that will cause it to abort.
Change: Added synchronization to make sure all pending interrupts are serviced before resetting the chip. Also changed to collect mode coalescing. The firmware signature problem will be fixed in boot code.
Impact: The use of collect mode coalescing may affect performance.
2. Problem: (CQTO558) Unable to load driver on some early 2.6 kernels.
Cause: pci_dma_sync_single_for_* routines not defined on early 2.6 kernels.
Change: Added compatibility defines for earlier kernels.
Change: Added 15 msec delay after chip reset for A1.
Impact: None.
2. Problem: (CQTO468) Link does not go down after changing from 10Mbps full (forced) to 10Mbps half (forced) and vice versa.
Cause: Not enough delay after forcing link down.
Change: Added proper delay for link to go down.
Impact: None.
v1.0.5 (Sep. 02, 2004) ====================== Enhancements: ------------- 1. Change: Added support for ethtool -c, ethtool -C, ethtool -p, and firmware version for ethtool -i.
Impact: None.
Fixes: ------ 1. Problem: 5706C not advertising 1000 half duplex.
Cause: 1000 full duplex overwrites 1000 half duplex.
Change: Fixed the bug so that the 2 bits are or'ed together.
Impact: None.
2. Problem: ethtool -A does not change the flow control settings in all cases.
Cause: Flow control settings not zeroed out before setting new values.
Change: Minor bug fix to zero out the value.
Impact: None.
v1.0.4 (Sep. 02, 2004) ====================== Fixes: ------ 1. Problem: (CQTO504) Multiple NFS transfers will hang some connections.
Cause: Driver discards some receive packets when the error status is non-zero.
Change: Changed the driver to only discard receive packets when the defined error bits in the error status are non-zero.
Impact: None.
v1.0.3 (Sep. 01, 2004) ====================== Enhancements: ------------- 1. Problem: Driver does not support ethtool -t self test and ethtool -S statistics.
Change: Added ethtool self test and statistics.
Impact: None.
Fixes: ------ 1. Problem: (CQTO478) Kernel still panics when transmitting certain files using NFS after many iterations
Cause: Tx DMA stalls on certain UDP packets, causing NFS client to stall.
Change: More fixes made in firmware.
Impact: None.
v1.0.2 (Aug. 26, 2004) ====================== Enhancements: ------------- 1. Problem: Driver does not work on big endian machines.
Change: Ported and tested on SPARC64 machine.
Impact: None.
Fixes: ------ 1. Problem: (CQTO478) Kernel panics when transmitting certain files using NFS.
Cause: Tx DMA stalls on certain UDP packets, causing NFS client to stall.
Change: Fixed in firmware.
Impact: None.
2. Problem: (CQTO469) Unable to modify flow control parameters
Cause: Did not call setup_phy after the parameters are changed.
Change: Added call to setup_phy after parameters are changed.
Impact: None.
3. Problem: (CQTO467) 5706 does not autonegotiate properly after changing settings with ethtool.
Cause: This is an ethtool limitation as the proper advertising parameters are not passed to the driver properly.
Change: Implemented a new scheme to work around the problem to allow users to specify full autoneg, single speed autoneg, and fixed speed.
Impact: None.
4. Problem: ethtool -e does not work.
Cause: Various bugs in the nvram routines.
Change: Fixed and tested nvram routines on little endian and big endian machines.
Impact: None.
v1.0.1 (Aug. 18, 2004) ====================== Fixes: ------ 1. Problem: (CQTO459) 5706 NIC does not get link.
Cause: Boot code timing out in WAIT2 state before driver is ready.
Change: Moved the WAIT2 state ahead in the driver reset sequence as a temporary workaround until it is fixed in boot code.
Impact: None.
2. Problem: (CQTO463) Kernel panics when loading the driver on RH30EL (2.4.21-4.EL)
Cause: Older kernel used different API to allocate and register netdev.
Change: Added older APIs to be used on older kernels.