Integrated Management Module II (IMM2) Firmware Update Change History
Version 3.86, 1AOO56V - Critical - Critical Fix for x3500 M4 -- Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198
Version 3.73, 1AOO56D - Critical Fix for dx360 M4, x3650 M4, x3550 M4, x3500 M4, x3100 M4, x3250 M4, x3750 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.71, 1AOO52W - Critical Fix for x3550 M4: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882) -- Fixed a problem system may shut down with new Mezz card installed
Version 3.70, 1AOO52Q - Critical Fix: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882)
Version 3.67, 1AOO50G - Supports System x3650 M4 BD, Machine Type: 5466
Version 3.65, 1AOO50D NOTE: If you have a System x3550 M4 with the "Emulex VFA Mezz card" and a ==== single processor, don't update the IMM2 with this firmware - Critical Fix: -- Fixed a problem on the System x3650 M4 server where the system shuts down due to a false temperature event from the ambient temperature sensor - Fixed a problem where the IMM2 may erroneously report a fan fault in the x3630 M4 when the system is powering on. See RETAIN tip H207461 for the description of the original problem - Fixed a screen refresh problem where it occurs after resetting IMM2 - Fixed a firmware problem that may cause the IMM2 to reset unexpectedly - Fixed a problem where the IMM2 SNMP interface may intermittently be unavailable if the system is running VMWARE ESXi 5.x - Fixed a problem where the CPU may potentially throttle in the x3650 M4 system with two 550 watt power supplies and one hard drive backplane
Version 3.60, 1AOO50C - Added support for the Intel IvyBridge-EP CPU on the HS23 blade - Fixed a problem where the HS23 hard drive number reported in the AMM event did not match the drive number on the physical blade enclosure - Fixed an intermittent problem where the UXSPI update utility may erroneously report that the firmware image is not meant for the HS23 system - Fixed a problem that causes the AMM web interface to not display properly when drives are removed or inserted - Fixed a problem where the IMM2 may not detect an over temperature condition for a DIMM
Version 3.56, 1AOO50K - Fixed a Flex Systems Manager (FSM) Configuration Patterns problem where configuration deployments would fail with an activation job error message: ERROR: LDAP failed with rc=102 ERROR: LDAP failure: SYSPROF_LDAP_BIND_FAIL INFO
Version 3.55, 1AOO50E - Fixed an issue so a fully qualified domain name can be used for a syslog collector in addition to an IP address - Fixed an issue to allow a user the ability to specify the port to use for syslog notifications, rather than only supporting the default port
Version 3.50, 1AOO50B - Fixed an issue where the default static IPv4 address was assigned to the IMM2 management interface instead of the user configured static IPv4 address in DHCP fallback to static mode, if the DHCP server was not available - Prevent a VLAN from being configured on the IMM2 management interface for Flex nodes - Fixed a problem where the CPU throttling state recovery indication to the FSM might not be properly reported - Corrected an issue with the launch of the IMM2 Remote Console operation that required a restart of the IMM2 - Corrected the firmware to apply the inactivity timeout to web pages that automatically refresh - Updated the web browser support. The following web browsers are supported: Firefox 3.6-20 Chrome 13-26 Internet Explorer 8-10 - Added support for the S3 Sleeping State to the IMM2 user interfaces on those servers that include the S3 feature - Added changes to use the minimum TLS version setting that is provisioned by the CMM in Flex for encrypted communication - Enhanced the content of the service data file to assist in problem determination - Added a option to have the IMM2 automatically copy the firmware from its primary bank into the backup bank after the firmware has been run for a period of time and proven itself to be stable - Enhanced the IMM2 firmware to automatically restore itself without the need for user intervention if the firmware becomes corrupted - Added new commands on the command line interface to stop a serial redirection operation that is currently in progress, and to report the user names that have a serial redirection operation started - Added changes to use the DNS settings that are provisioned by the CMM in Flex to support use of an LDAP hostname for authentication - Updated the firmware to log hardware inventory change informational messages - Added support for the Service Advisor feature on stand alone rack servers to automatically call for service when a repair is needed - Added support to configure the Ethernet-over-USB IP address using ASU - Added changes to support the thermal requirements for new Solid State Drives used with the ServeRAID M5100 Series IBM Flex System Flash Kit v2 - Updated the IMM2 date and time web page on Flex nodes to only display the current date and time - Updated the SSH firmware to address various OpenSSH vulnerabilities that have been identified by security community - Added changes to support the Web Services-Management protocol
Version 3.40, 1AOO48M - Supports System x3250 M5, Machine Type: 5458
Version 3.37, 1AOO48P - Added support for the IBM NeXtScale Storage Native Expansion (NeX) Tray for IBM NeXtScale nx360 M4
Version 3.36, 1AOO48Q - Fixed a problem on System x iDataPlex dx360M4 where a CIM client cannot get needed event information for asserted events
Version 3.35, 1AOO48N - Critical Fix: -- Corrected a problem on the System x3650 M4 and x3650 M4 HD servers causing the system to shut down due to an erroneous critical temperature event reported by the ambient temperature sensor
Version 3.30, 1AOO48L - Fixed a problem on System x iDataPlex dx360M4 where nodes shutdown due to a critical temperature event from the Ambient Temp sensor
Version 3.20, 1AOO48K - Supports System NeXtScale nx360 M4, Machine Type: 5455
Version 3.10, 1AOO48H - Added support for System x3650 M4 HD, Machine Type 5460 - Added support for newer CPUs in the System x iDataPlex dx360M4, x3500M4, x3550M4, and x3650M4 servers - Added a feature on the System x3550 M4 and x3650 M4 to fail over from the dedicated systems management network port to the shared port when the dedicated network link is not available - Fixed a problem where an NTP update message is logged every 1440 minutes - Fixed a problem where the IMM2 web interface won't accept an NTP hostname string that starts with a numeric character - Fixed a problem where the LDAP Group Filter authentication does not work as expected - Fixed a problem where the IMM2 reports 0 Watts when the System x iDataPlex dx360M4 is DC cycled or resumes from the S3 sleep state - Fixed an Ethernet problem that may cause an IMM2 failure to establish a link when the Ethernet speed and duplex settings are not configured to use auto-negotiation
Version 2.60, 1AOO42Y NOTE: For increased security, only high strength ciphers are now supported when using https.
==== Your browser must support one of the following cipher suites: | HE-RSA-AES256-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(256) Mac=SHA256 DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 AES256-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA256 AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 DHE-RSA-AES128-SHA25 TLSv1.2 Kx=DH Au=RSA Enc=AES(128) Mac=SHA256 DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1 AES128-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA256 AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1
- Added support for the IBM Flex System x222 Compute Node - Improved Remote Presence (keyboard, mouse and virtual media)and in-band management (LAN-over-USB) performance - Changed the default file name for the Service Data file (First Failure Data Capture or FFDC) on the web interface to incorporate the machine type, serial number and a timestamp - Updated the IMM2 PCIe Bridge Firmware to support Windows 2012 Certification - Improved IMM2 Reliability, Availability, Serviceability (RAS) Features: - Added component and system VPD integrity checking & reporting - Enhanced Service Data collection (FFDC)
- Enhanced the configuration of UEFI settings via the CIM interface for applications like IBM Systems Director - Added Sub-manufacturer inventory support for mezz card and Sub-manufacturer inventory support for the system for IBM Systems Director - Added the UUID for the PCIe Expansion Node and the Storage Expansion Node to the SLP attributes reported by the IMM2 - Added the number of enabled CPU core and the Static power savings mode support for IBM Systems Director - Enhanced the alert recipient email notification, firmware update, event log, log out, and hardware information web pages to improve usability - Added support for IPMI & SNMPv3 accounts to be centrally managed by the Flex Chassis Management Module - Fixed a problem where an invalid configuration was erroneously reported for an unpopulated CPU socket in the IBM Flex System x440 - Enabled users to configure a longer trespass message - Increased the length of the LDAP group filter field to 511 characters - Corrected a problem with ServeRAID M5115 SAS/SATA Controller for IBM Flex Systems energy pack monitoring - Corrected a problem with ServeRAID M5115 SAS/SATA Controller for IBM Flex Systems LED management - Added IPMI command to configure the LAN-over-USB IP address
Version 2.52, 1AOO42E - Critical Fix: -- Fixed a problem on the System x3300 M4 servers causing the system to shut down due to a critical temperature event reported by the ambient temperature sensor
Version 2.50, 1AOO40Z - Added support for the Solarflare SFN5162F MR Dual Port 10GbE SFP+ Adapter, and Solarflare SFN6122F LL Dual Port 10GbE SFP+ Adapter for System x3550 M4 and x3650 M4 NOTE: UEFI also needs to be upgraded to D7E128B (v 1.40 or newer, for the x3550 M4) or VVE128B (v1.40 or newer, for the x3650 M4) to support these cards - Added support for the Mellanox ConnectX-3 Dual Port QDR/FDR10 mezzanine card and Mellanox ConnectX-3 VPI Single-port QSFsorry.P FDR14/40GbE HCA on System x3550 M4, and x3650 M4 - Added optional Fan Zone support for single CPU systems (x3550 M4 and x3650 M4) with an installed with Qlogic Dual Port 10GbE SFP+ Embedded VFA - Fixed an intermittent problem where a Gratuitous ARP is not sent successfully - Fixed a problem where after the IMM2 firmware is flashed, there is a slight chance that the IMM2 web server can't be accessed when AC power is reapplied - Disabled the weak cipher suit used in the SSL/TLS firmware with the https protocol to avoid potential security vulnerabilities - Fixed a problem on the System x3750 M4 where the IMM2 shared mode network connection will be lost after upgrading the firmware of the onboard Emulex BE3 controller - Fixed a problem on the HS23 where the OS watchdog timer doesn't work - Fixed a problem on the HS23 where the Fault LED occasionally lights when the chassis is powered on with the BPE4 - Fixed a problem on the HS23 where the server may shut down after resetting the IMM2 - Enhanced the messaging mechanism between the BladeCenter AMM and the IMM2 - Added power management capability in the IMM2 web interface
Version 2.06, 1AOO42B - Corrected the firmware to prevent users from disabling the IPv6 interface - Fixed a problem that caused the IMM2 to reset itself after running for a period of time - Corrected the SNMP request to disable the IMM2 IPv4 interface so that it disables only IPV4, instead of both IPv4 and IPv6 - Fixed a problem that occasionally caused the server to shut down when the IMM2 is reset - Fixed a problem where the IMM2 incorrectly reported a battery voltage error - Corrected a problem where repeated frequent IMM2 resets causes the IMM2 to run the firmware in its backup partition - Corrected a problem report where the IMM2 did not report a failure to the system profiles script when the chassis UUID is unavailable
Version 2.00, 1AOO40E - Critical Fix: -- Improves the reliability of the CPU and/or memory VRDs. This improvement lowers the occurrence of CPU & memory VRD failures on the x3300 M4 and x3750 M4 -- IMM2 improved error reporting for missing/down CPU in invalid CPU configuration for x4440 M4 - Corrected a problem that caused 3.3V and 5V faults to be reported by IMM2 firmware level 1aoo34z(1.85) on the HS23E blade - Eagle Ray SAS controller LED fault support improvements added for all ITE platforms
Version 1.97, 1AOO36R - Critical Fix: -- Improves the reliability of the CPU and/or memory VRDs. This improvement lowers the occurrence of CPU & memory VRD failures on x3650 M4, x3550 M4 and x3500 M4 - Thermal behavior enhancement on System x iDataPlex dx360 M4
Version 1.95, 1AOO36P (for System x iDataPlex servers) - Added support for NVIDIA K1,K2,K20,K20x GPUs on System x iDataPlex dx360 M4
Version 1.88, 1AOO40A (for PureFlex System Compute Nodes) - Critical Fix: -- Fixed a potential security vulnerability with node management user accounts (Reference to Security Bulletin CVE-2012-4838) - Fixed a problem on Flex Systems where the SNMP get and set authority levels did not work - Fixed a problem on Flex Systems where mounting of remote media in a Linux environment showed a USB error - Fixed a problem on Flex Systems that caused the Remote Control Video Viewer window on a RHEL5.8 client to move when the arrow key is pressed - Fixed a problem on Flex Systems where the SMTP "Test Connection" button did not work when the SMTP port is changed - Fixed a problem on Flex Systems where the SNMP get and set authority levels did not work - Fixed a problem on Flex Systems where mounting of remote media in a Linux environment showed a USB error - Fixed a problem on Flex Systems that caused the Remote Control Video Viewer window on a RHEL5.8 client to move when the arrow key is pressed - Fixed a problem on Flex Systems where the SMTP "Test Connection" button did not work when the SMTP port is changed - Corrected the Mezzanine card power fault monitoring on the Flex System x440 Compute Node - Corrected a problem with IBM Fabric Manager configuration from the Flex Chassis Management Module - Added support to retrieve configuration settings from an LDAP server - Added support for the Flex Storage Expansion Node - Added support for CIM indications over https - Added fingerprint checking for SFTP transfers - Added automatic recovery of corrupted UEFI firmware - Added support for authenticated SMTP alerts - Added a display of the users who have a Remote Control session in progress - Provided a request to a Remote Control client to disconnect the session - Added support for the server S3 (sleep) state - Changed the default NTP sync interval from 3 minutes to 24 hours - Fixed a problem where the ambient temperature is only displayed in degrees Fahrenheit - Fixed a problem on the web interface where 'local' is not accepted as a top level domain name in the email format when configuring event recipients - Corrected an IMM2 SNMP trap OID to match the prior IMM format - Fixed a problem that prevented an external USB device from being remotely mounted as a floppy drive in Windows Server 2003 - Changed the blue Location led behavior to not blink when a firmware update is in progress
Version 1.85, 1AOO34Z (for BladeCenter blades and System x Servers) - Critical Fix: -- Fixed a potential security vulnerability with node management user accounts (Reference to Security Bulletin CVE-2012-4838) - Fixed a problem where a Blade Open Fabric Manager uncorrectable error can occur when booting the HS23 - Fixed a problem that IMM IPMI command periodically timed out when using HS23 in Chassis with the management network being disabled in some special configurations - Added support for the HS23 to recognize NEBS/Enterprise Mode for Telco chassis (this feature needs Advanced Management Module Firmware BPET62U or later) - Fixed a problem where the ambient temperature is only displayed in degrees Fahrenheit - Fixed a problem where on rack systems that have 2 power supplies installed, the 'Redundancy Power unit has been restored' event is logged every time that the IMM2 is reset - Fixed a problem where a Fan Tach going low (lower critical) event is intermittently asserted when configuring the IMM2 to use an NTP server - Fixed a problem on the web interface where 'local' is not accepted as a top level domain name in the email format when configuring event recipients - Corrected an IMM2 SNMP trap OID to match the prior IMM format - Fixed a problem that prevented an external USB device from being remotely mounted as a floppy drive in Windows Server 2003 - Changed the blue Location led behavior to not blink when a firmware update is in progress - Fixed a problem on the HS23E that causes Preboot DSA to hang in CLI mode when a user accesses it using Serial over LAN - Fixed a problem on rack servers where ASU cannot set IMM.GRP_GroupName.1 and IMM.GRP_GroupName.2 if the string length is 16 characters or longer. The firmware was corrected to allow a maximum length of 64 characters - Added support for CIM indications over https - Added fingerprint checking for SFTP transfers - Added automatic recovery of corrupted UEFI firmware - Added support for authenticated SMTP alerts - Added a display of the users who have a Remote Control session in progress - Provided a request to a Remote Control client to disconnect the session - Added support for the server S3 (sleep) state
Version 1.85, 1AOO34Y (for PureFlex System V7000 Storage Node) - Added support for Flex System V7000 Storage Node
Version 1.79, 1AOO36F - Thermal behavior enhancement on System x iDataPlex dx360 M4
Version 1.78, 1AOO36E - Thermal behavior enhancement for 115W & 95W CPU on System x iDataPlex dx360 M4 - Added support for the Intel KNC 5110p card
Version 1.77, 1AOO32X - Thermal behavior enhancement for 115W CPU on System x iDataPlex dx360 M4
Version 1.75, 1AOO32S - Fixed a problem that a PCI uncorrectable error occurs when using HS23 with CFFh card (44W4479) in the BCS chassis - Fixed a problem where an "Unsupported blade/blower combination" error is reported when using the HS23 in the BCHT chassis configured in Enterprise mode - Fixed a problem in System x3530 M4, where the reported Active Energy Manager input/output power readings are inaccurate - Fixed a problem in System x3530 M4, x3630 M4, where an LDAP account can not login using the AD_CrossDomain tree - Fixed a problem in System x3530 M4, x3630 M4, where a user cannot use the "DNS to Find LDAP server/Extract search domain from login ID" setting from the IMM2 web to access an eDirectory server - Added support for Common Form Factor power supplies Oversubscription in System x3750 M4, Machine Types: 8722, 8733
Version 1.65, 1AOO32O - Support the power supply Over-Subscription feature - Support the 750 Watt DC power supply for System x3650 M4,x3550 M4 - Support IBM 1.2TB High IOPS MLC Mono Adapter, IBM 2.4TB High IOPS MLC Duo Adapter for System x3650 M4, x3550 M4 - Support IBM LLM-SM Dual Port 10GbE SFP+ Adapter for System x3650 M4 - Fixed an abnormal Fan Zone recovery problem - Fixed a problem that IMM2 Email notification doesn't support an e-mail address with the underscore '_' character - Fixed a power policy "Restore" problem - Fixed a problem where the LDAP hostname can't be changed by ASU - Fixed a problem that the length of email address (for SNMP notification) is limited to 32 characters
Version 1.60, 1AOO32P - Fixed a problem where the Chassis Management Module cannot correctly get the Mezzanine card information for the Flex System x220 Compute Node - Fixed a problem where the PreBoot DSA firmware could not be updated under VMWare ESXi 5 through the Flex System Manager's Update Manager - Fixed a problem where an IMM2 communications error can occur if an unexpected response causes VMware to spawn multiple processes when it does not receive the data it expects from the IMM2
Version 1.59, 1AOO32K - Supports System x3300 M4, Machine Types: 7382
Version 1.53, 1AOO30Z - Included an update to the FPGA that fixes an intermittent issue where the CPUs do not show up in a system with a RAID card installed, when the AC is removed and reapplied from the server without allowing sufficient time for the system hardware to completely discharge
Version 1.52, 1AOO34A - Added redundant power supply and hot swap hard drive support in System x3100 M4
Version 1.51, 1AOO30Y - Support for NVIDIA Tesla K10, M2070Q, M2090 GPU cards on System x iDataPlex dx360 M4 - Fixed a problem in System x iDataPlex dx360 M4 where the password expires after creating a new user in the IMM2 web interface - Fixed a problem in System x iDataPlex dx360 M4, when the memory sensor changes from 'critical' to 'warning,' but the severity is not updated in the syslog or the email notification
Version 1.50, 1AOO30W - Supports System HS23, Machine Types: 7875,1929 - Supports System x3650 M4, Machine Types: 7915 - Supports System x3550 M4, Machine Types: 7914 - Supports System x3500 M4, Machine Types: 7383 - Added support for the Intel Xeon E5-2643 processor on the HS23 in BCH-R3, BCS and BCHT chassis - Fixed a problem where the IMM2 incorrectly logged an "Unsupported blade/blower combination" on the HS23 in the BC-E 8677 chassis - Fixed a power restore problem on systems that have 2 Delta power supplies installed - Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where OpenLDAP Group Authentication filtering function doesn't work - Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where LDAP account can not login using the AD_CrossDomain tree
Version 1.45, 1AOO28S - Fixed a problem in Flex System x220 where the Chassis Management Module (CMM) Command Line Interface can't display the Mezzanine card information - Fixed a problem in Flex System x220 and x240 where the prebootDSA firmware cannot be updated through Flex System Manager's Update Manager
Version 1.40, 1AOO30T - Supports System x3750 M4, Machine Types: 8722, 8733
Version 1.38, 1AOO30D - Supports System x3630 M4, Machine Type: 7158 - Supports System x3530 M4, Machine Type: 7160
Version 1.36, 1AOO30P - Fixed an intermittent remote media failure in system HS23E - Fixed a problem in system HS23E where remote media does not work when two or more users have concurrent remote control sessions
Version 1.34, 1AOO28Q - Supports Flex System Manager Node, Machine Type: 8731 - Supports Flex System x240 Compute Node, Machine Types: 7863, 8737, 8738 - Supports Flex System x220 Compute Node, Machine Types: 2585, 7906
Version 1.32, 1AOO28N - Supports System x3630 M4, Machine Type: 7158 - Supports System x3530 M4, Machine Type: 7160 - Fixed a problem that may see unexpected fan events after power on in x3100 M4 and x3250 M4 systems - Enhanced robustness on I2C bus test
Version 1.30, 1AOO28M - Supports System HS23E, Machine Types: 8038,8039
Version 1.26, 1AOO26N - Supports System x3650 M4, Machine Types: 7915
Version 1.25, 1AOO26K - Supports System x3550 M4, Machine Types: 7914 - Supports System x3500 M4, Machine Types: 7383 - Supports System x iDataPlex dx360 M4, Machine Types: 7912,7913
Version 1.22, 1AOO26O - Supports System HS23, Machine Types: 7875,1929 Problems Fixed: - Fixed a problem where the BOFM configuration may be lost after a blade power cycle - Fixed an LED error indication that occurs on the BPE4 - Fixed a problem where the Info LED lights during the discovery stage - Fixed a problem where an ABR event is not logged - Fixed an intermittent communication problem between the AMM and IMM2 - Fixed a problem that causes the remote media function to hang when a second user attempts to mount remote media - Fixed a problem where the 'break' keyboard function doesn't work with Serial Over LAN
Version 1.21, 1AOO26L - Supports System HS23, Machine Types: 7875,1929
Version 1.10, 1AOO24B - Supports System dx360 M4, Machine Types: 7918,7919
Version 1.05, 1AOO10K - Fixed the false alert issue in redundant PSU model
Version 1.00, 1AOO10I - Initial Release - Supports System x3250 M4, Machine Types: 2583,2587 - Supports System x3100 M4, Machine Types: 2582,2586
(C) Copyright International Business Machines Corporation 2008 - 2014. All rights reserved.
ibm_fw_imm2_1aoo56v-3_86_anyos_noarch_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)
Enhancement - Reduce the boot time for UEFI driver for large configurations Fixes: - Fixed an issue that caused the Integrated Management Module (iMM) in System x servers to report Warning: Sensor GPT Status has transitioned from normal to non-critical state. - Fixed an issue where 4k sector size drives with 512e reporting enabled show wrong physical size when running a read capacity 16 command. - Fixed an issue where speed negotiation for 3Gig SATA drives is not handled properly. - Added Support for Report Luns Command - Fixed an issue where OS hang during install of Linux system to a SSD - Fixed an issue where SAS device page 0 may still be present for Initiator devices that have been removed from the topology. - Fixed an issue where RHEL 6.3 hangs during boot with IBM 600GB High IOPS MLC Modular Adapter - Fixed an issue where a non-PI volume made up of all PI capable drives, may come up as PI enabled after a controller reset. - Fixed an issue where a fault 0X8808 occurs when a reset is issued to the controller that has max number of active/inactive volumes - Fixed an issue where "Device Present" Flag of SAS device page0 is not set for initiator controller in then target controller when two controllers are connected to each other in initiator/target mode. - Fixed an issue where extended tags and PCIe upconfigure capability are disabled in SAS2208 and SAS2308. - Fixed an issue where force full discovery does not trigger rediscovery of an expander after the initial expander discovery fails. - Fixed an issue where single RAID0 volume activation was succeeding, even though controller does not support single drive RAID0. - Fixed an issue where RAID1 volume of Non-PI drives moves to optimal state when a PI drive is hotplugged and 'Enable PI mixing' not enabled. - Fixed an issue where Locate LED's stop automatically after 3-4 minutes before user issues command to turn off the Locate LED's. - Fixed an issue where fault 0x8618 is seen when a new volume is created in the presence of another volume which is undergoing resync along with IO. - Fixed an issue background initialization does not start on RAID0 volume with PI drives, after removing and reinserting a volume member.
BIOS - Fixed an issue where core BIOS displays warning message when it fails to add all of the drives connected to int13 chain, then waits for user to press any key to continue further, rather than continuing after 3 seconds. - Fixed an issue where incorrect adapter is being tagged as the first adapter found. - Fixed an issue where the save or discard changes prompt appears after a failed attempt to set volume as the boot device in BIOS CU. - Fixed an issue where BIOS CU provides incorrect device pointer when checking for raid disk to allow/disallow setting boot device. - Fixed an issue where device properties screen is invoked from a direct attach device using Alt+D in SAS topology screen, device traversing [Alt+N & Alt+P] is restricted within the direct attach device and expander attach devices are not traversed. - Fixed an issue where the drive status field does not show 'Max dsks' when trying to select 11th drive for RAID10 volume. - Fixed an issue maximum Int13 devices settings does not get honored, when the value is set as 0 in BIOS CU - Fixed an issue where drive size of 1.088GiB was showing as 1.880GiB. - Fixed an issue current boot device set to device at slot 4" message Not displaying for Adaptors with boot order other than 0. - Fixed an issue where the BIOS CU navigates to create new volume screen instead of back to raid properties screen. - Fixed an issue where BIOS banner showed 'FF' for slot information. - Fixed an issue where the drive's SMART status is always shown as no irrespective of drive's SMART status, under Pred Fail column of the manage hot spare screen and create new volume screen. - Fixed an issue where SAS2 BIOS: volume size shows inconsistent value in the create new volume' screen after selecting the last volume member. - Fixed an issue where a disabled adapter causes the second adapter status to show as unavailable even though the second adapter is enabled. Uefi Enhancement 1/2 - Added capability to create an IR RAID volume in non-PI mode, even when all member drives are PI Capable. - Added PI info and ability to control creation of PI Volume in UCM of BSD HII. - Added new form manage PHY settings to support enabling or disabling of a controller PH Fixes: - Fixed an issue view foreign volume option is disabled with a foreign volume in the configuration.
BIOS Changes Enhancement(s): - Core BIOS and BIOS configuration utility will display "FF" as the PCI slot number when proper slot information is not available. - Increased the disk drive spin-up timeout value to accommodate disk drives having larger spin up times.
Fix(es): - Fixed an issue where the adapter order does not get written to NVM and "Updating Adapter Order" displays on every reboot. - Fixed issue where zero sized volume was showing "4. 0 GiB." - Fixed issue where devices, which are not attached to adapter 0, could not be promoted to positions in the boot order when they were selected in the configuration utility. - Fixed an issue where IOS Banner(POST) not showing SAS Discovery error when more than one HBA is connected to the host system. - Fixed an issue where the SMART status is not correctly displayed for bare drives. - Fixed an issue in SAS topology where a RAID disk is highlighted and attempted to set as preferred boot device or alternate boot device, the configuration utility displays a SAVE/DISCARD prompt. - Fixed an issue where the firmware was showing a large elapsed time when a format operation crosses midnight in the system clock.
Firmware Changes Enhancement(s): - Added support for 4GB DIMM - Added the ability for user the enable/disable of the drive write cache during the BIOS start up.
Fix(es): - Fixed an issue where a request sense command, which is executed after a SATA drive is in active state is moved to idle power condition state, has no 'Additional Sense' information set. - Fixed an issue where protected information error "Logical block reference tag check failed" is received when an IR volume is deleted. - Fixed an issue Self-Test Results log page where values for update parameter code, format and linking, and parameter length are not recorded. - Fixed an issue sending vital product data inquiry with vital product data page set as invalid (0xFF) while diagnostic is running on a SATA drive results in segmentation fault 0x1901. - Fixed an issue where input/output is sent to SATA drives before the drives are ready. - Fixed an issue where fault 8405 was being hit while disabling and enabling the phy to which secondary drive is connected with IOs active. - Fixed an issue where subsequent commands sent to a SATA drive fail after a write same command failure until NCQ error handling is triggered or the device is reset. - Fixed an issue where Report Luns command sent to SATA drive fails if the drive is spun down. - Fixed an issue where hotspare does not resynch with second raid volume when both volumes are in degraded state. - Fixed an issue where incorrect sense data is populated when Security Protocol IN/OUT command is sent to supported drive. - Fixed an issue where allocation length for inquiry SCSI Command is not handled Properly during SATA Drive Format. - Fixed an issue during SATA drive format where vital product data inquiry command is executed for SATA drive with invalid page code, and the command is passed with no data instead for failing with CC and sense data. - Fixed an issue where the host will not indicate the existence of the expander attached drives if the direct attached device re-ordering feature is enabled. - Fixed an issue where protected information errors are observed on a RAID 1 volume its BGI is not completed, and its member physical disks are removed and inserted. - Fixed an issue where the TM response was set to failed if the device is missing due to the DO NOT SEND TASK IU flag being enabled. - Fixed an issue where DMD (Device Missing Delay) timer is not set to the default time when the total Report Device Missing Delay is greater than 0x7F seconds. - Fixed an issue where RAID1 volume fails to resynch when a new compatible bare drive is available in the primary drive slot. - Fixed an issue where error handling for errors, that cause the DMA engines to halt, are not handled properly and multithreaded IOs can hang if the same control block is used too soon. - Fixed an issue where a third hotspare is created even if the number of hotspares currently present in the RAID Configuration is 2. - Fixed an issue where inactive foreign volume information cannot be seen in SASBIOS when a native volume is deleted.
UEFI Changes Enhancement(s) - Additional information such as vendor id and product id added to the HII Create Configuration Screen. - Added ability to check to detect missing hotspares to HII. - Modified to be obtained PCI Slot Number information from the system firmware protected information. - Additional character "M" will be displayed as part of the device display identifier of a multipathed disk. - Ability in HII to detect missing hotspares and provide a facility to delete the missing hotspares. - Implemented Configuration Summary and Simple Virtual Disk Creation Support for Unified Configuration Management. - Modified UEFI driver to wait for a maximum of 10 seconds for the controller to become ready, so controller gets discovered in the OS.
Fix(es): - Fixed an issue where Enable/Disable write cache does not work for SAS drives. - Fixed an issue where HII Configuration utility does not allow the user to create a RAID0 with single disk present in the topology. - Fixed an issue in Create Configuration menu where additional drive information is not getting updated appropriately in HELP area. - Modified to prevent Write Cache settings options from appearing for the IR firmware. - Fixed an issue where SATA volume members and hotspare drives are labeled as 'M' in a multipathed environment. - Fixed an issue to prevent HII from allowing the option to enable/disable write cache for SATA drives. - Fixed an issue where multipathing is disabled in Manufacturing page settings, but volume members and hotspare drives are labeled as "M." - UEFI driver modified to check BIOS Options in order to determine if is should manage the controller.
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.
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.
Integrated Management Module II (IMM2) Firmware Update Change History
Version 4.31, 1AOO58T - Critical - Critical Fix for x3650M4, x3550M4, x3500M4, dx360M4, x3100 M4, x3250m4, x3750M4, x3650M4 HD, x3630M4, x3530M4, x3300M4, x3250M5 -- Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198 - Added option to export the certificate signing request in PEM format - Various Remote Presence enhancements including: -- Support for a MAC OS-x client -- Scaled video viewer window -- ASU set up of Remote Presence hot keys -- Virtual media mounting via URL - Removed potentially sensitive information from the service data file - Fixed a problem on x3650 M4, x3550 M4, x3500 M4, x3650 M4 HD where the IMM2 may not detect a loss of power supply redundancy - Fixed a problem where the LDAP group filter does not support a full DN - Fixed a problem where the syslog alert fields "Msg Type" and "Severity" did not follow RFC 5424 - Fixed a problem where the IMM2 only supported the default network port for syslog notifications - Fixed a problem where the SNMP "sysName" query always returns the string "SNMP Service" instead of the system name - Fixed a problem where the Global Login Settings changes were lost after an IMM2 restart
Important: Before you flash the IMM2 firmware back to version 3.82 or older, set the IMM2 Security option to use the Basic Compatibility Mode. This will prevent a possible loss of access to the IMM2.
Version 4.15, 1AOO58K - Suggested - Added support for the BIE (Blade IO Expansion Board) on the HS23, HS23E - Fixed a problem that prevented the AMM from controlling power when local power control is disabled on the HS23, HS23E
Version 3.91, 1AOO58G - Critical - Supports System x3750 M4, Machine Type: 8752, 8718 - Add a feature to allow users to block power control from the power button on the x3750M4
Version 3.73, 1AOO56D - Critical - Critical Fix for dx360 M4, x3650 M4, x3550 M4, x3500 M4, x3100 M4, x3250 M4, x3750 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.71, 1AOO52W - Critical - Critical Fix for x3550 M4: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882) -- Fixed a problem system may shut down with new Mezz card installed
Version 3.70, 1AOO52Q - Critical - Critical Fix: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882)
Version 3.67, 1AOO50G - Initial Release - Supports System x3650 M4 BD, Machine Type: 5466
Version 3.65, 1AOO50D - Suggested NOTE: If you have a System x3550 M4 with the "Emulex VFA Mezz card" and a ==== single processor, don't update the IMM2 with this firmware - Critical Fix: -- Fixed a problem on the System x3650 M4 server where the system shuts down due to a false temperature event from the ambient temperature sensor - Fixed a problem where the IMM2 may erroneously report a fan fault in the x3630 M4 when the system is powering on. See RETAIN tip H207461 for the description of the original problem - Fixed a screen refresh problem where it occurs after resetting IMM2 - Fixed a firmware problem that may cause the IMM2 to reset unexpectedly - Fixed a problem where the IMM2 SNMP interface may intermittently be unavailable if the system is running VMWARE ESXi 5.x - Fixed a problem where the CPU may potentially throttle in the x3650 M4 system with two 550 watt power supplies and one hard drive backplane
Version 3.60, 1AOO50C - Suggested - Added support for the Intel IvyBridge-EP CPU on the HS23 blade - Fixed a problem where the HS23 hard drive number reported in the AMM event did not match the drive number on the physical blade enclosure - Fixed an intermittent problem where the UXSPI update utility may erroneously report that the firmware image is not meant for the HS23 system - Fixed a problem that causes the AMM web interface to not display properly when drives are removed or inserted - Fixed a problem where the IMM2 may not detect an over temperature condition for a DIMM - Corrected a problem that caused the IMM to report an "Unsupported blade/blower combination" error on HS23
Version 3.56, 1AOO50K - Critical - Fixed a Flex Systems Manager (FSM) Configuration Patterns problem where configuration deployments would fail with an activation job error message: ERROR: LDAP failed with rc=102 ERROR: LDAP failure: SYSPROF_LDAP_BIND_FAIL INFO
Version 3.55, 1AOO50E - Suggested - Fixed an issue so a fully qualified domain name can be used for a syslog collector in addition to an IP address - Fixed an issue to allow a user the ability to specify the port to use for syslog notifications, rather than only supporting the default port
Version 3.50, 1AOO50B - Suggested - Fixed an issue where the default static IPv4 address was assigned to the IMM2 management interface instead of the user configured static IPv4 address in DHCP fallback to static mode, if the DHCP server was not available - Prevent a VLAN from being configured on the IMM2 management interface for Flex nodes - Fixed a problem where the CPU throttling state recovery indication to the FSM might not be properly reported - Corrected an issue with the launch of the IMM2 Remote Console operation that required a restart of the IMM2 - Corrected the firmware to apply the inactivity timeout to web pages that automatically refresh - Updated the web browser support. The following web browsers are supported: Firefox 3.6-20 Chrome 13-26 Internet Explorer 8-10 - Added support for the S3 Sleeping State to the IMM2 user interfaces on those servers that include the S3 feature - Added changes to use the minimum TLS version setting that is provisioned by the CMM in Flex for encrypted communication - Enhanced the content of the service data file to assist in problem determination - Added a option to have the IMM2 automatically copy the firmware from its primary bank into the backup bank after the firmware has been run for a period of time and proven itself to be stable - Enhanced the IMM2 firmware to automatically restore itself without the need for user intervention if the firmware becomes corrupted - Added new commands on the command line interface to stop a serial redirection operation that is currently in progress, and to report the user names that have a serial redirection operation started - Added changes to use the DNS settings that are provisioned by the CMM in Flex to support use of an LDAP hostname for authentication - Updated the firmware to log hardware inventory change informational messages - Added support for the Service Advisor feature on stand alone rack servers to automatically call for service when a repair is needed - Added support to configure the Ethernet-over-USB IP address using ASU - Added changes to support the thermal requirements for new Solid State Drives used with the ServeRAID M5100 Series IBM Flex System Flash Kit v2 - Updated the IMM2 date and time web page on Flex nodes to only display the current date and time - Updated the SSH firmware to address various OpenSSH vulnerabilities that have been identified by security community - Added changes to support the Web Services-Management protocol
Version 3.40, 1AOO48M - Initial Release - Supports System x3250 M5, Machine Type: 5458
Version 3.37, 1AOO48P - Suggested - Added support for the IBM NeXtScale Storage Native Expansion (NeX) Tray for IBM NeXtScale nx360 M4
Version 3.36, 1AOO48Q - Critical - Fixed a problem on System x iDataPlex dx360M4 where a CIM client cannot get needed event information for asserted events
Version 3.35, 1AOO48N - Critical - Critical Fix: -- Corrected a problem on the System x3650 M4 and x3650 M4 HD servers causing the system to shut down due to an erroneous critical temperature event reported by the ambient temperature sensor
Version 3.30, 1AOO48L - NonCritical - Fixed a problem on System x iDataPlex dx360M4 where nodes shutdown due to a critical temperature event from the Ambient Temp sensor
Version 3.20, 1AOO48K - Initial Release - Supports System NeXtScale nx360 M4, Machine Type: 5455
Version 3.10, 1AOO48H - NonCritical - Added support for System x3650 M4 HD, Machine Type 5460 - Added support for newer CPUs in the System x iDataPlex dx360M4, x3500M4, x3550M4, and x3650M4 servers - Added a feature on the System x3550 M4 and x3650 M4 to fail over from the dedicated systems management network port to the shared port when the dedicated network link is not available - Fixed a problem where an NTP update message is logged every 1440 minutes - Fixed a problem where the IMM2 web interface won't accept an NTP hostname string that starts with a numeric character - Fixed a problem where the LDAP Group Filter authentication does not work as expected - Fixed a problem where the IMM2 reports 0 Watts when the System x iDataPlex dx360M4 is DC cycled or resumes from the S3 sleep state - Fixed an Ethernet problem that may cause an IMM2 failure to establish a link when the Ethernet speed and duplex settings are not configured to use auto-negotiation
Version 2.60, 1AOO42Y - NonCritical NOTE: For increased security, only high strength ciphers are now supported when using https.
==== Your browser must support one of the following cipher suites: | HE-RSA-AES256-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(256) Mac=SHA256 DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 AES256-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA256 AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 DHE-RSA-AES128-SHA25 TLSv1.2 Kx=DH Au=RSA Enc=AES(128) Mac=SHA256 DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1 AES128-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA256 AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1
- Added support for the IBM Flex System x222 Compute Node - Improved Remote Presence (keyboard, mouse and virtual media)and in-band management (LAN-over-USB) performance - Changed the default file name for the Service Data file (First Failure Data Capture or FFDC) on the web interface to incorporate the machine type, serial number and a timestamp - Updated the IMM2 PCIe Bridge Firmware to support Windows 2012 Certification - Improved IMM2 Reliability, Availability, Serviceability (RAS) Features: - Added component and system VPD integrity checking & reporting - Enhanced Service Data collection (FFDC)
- Enhanced the configuration of UEFI settings via the CIM interface for applications like IBM Systems Director - Added Sub-manufacturer inventory support for mezz card and Sub-manufacturer inventory support for the system for IBM Systems Director - Added the UUID for the PCIe Expansion Node and the Storage Expansion Node to the SLP attributes reported by the IMM2 - Added the number of enabled CPU core and the Static power savings mode support for IBM Systems Director - Enhanced the alert recipient email notification, firmware update, event log, log out, and hardware information web pages to improve usability - Added support for IPMI & SNMPv3 accounts to be centrally managed by the Flex Chassis Management Module - Fixed a problem where an invalid configuration was erroneously reported for an unpopulated CPU socket in the IBM Flex System x440 - Enabled users to configure a longer trespass message - Increased the length of the LDAP group filter field to 511 characters - Corrected a problem with ServeRAID M5115 SAS/SATA Controller for IBM Flex Systems energy pack monitoring - Corrected a problem with ServeRAID M5115 SAS/SATA Controller for IBM Flex Systems LED management - Added IPMI command to configure the LAN-over-USB IP address
Version 2.52, 1AOO42E - Critical - Critical Fix: -- Fixed a problem on the System x3300 M4 servers causing the system to shut down due to a critical temperature event reported by the ambient temperature sensor
Version 2.50, 1AOO40Z - Suggested - Added support for the Solarflare SFN5162F MR Dual Port 10GbE SFP+ Adapter, and Solarflare SFN6122F LL Dual Port 10GbE SFP+ Adapter for System x3550 M4 and x3650 M4 NOTE: UEFI also needs to be upgraded to D7E128B (v 1.40 or newer, for the x3550 M4) or VVE128B (v1.40 or newer, for the x3650 M4) to support these cards - Added support for the Mellanox ConnectX-3 Dual Port QDR/FDR10 mezzanine card and Mellanox ConnectX-3 VPI Single-port QSFsorry.P FDR14/40GbE HCA on System x3550 M4, and x3650 M4 - Added optional Fan Zone support for single CPU systems (x3550 M4 and x3650 M4) with an installed with Qlogic Dual Port 10GbE SFP+ Embedded VFA - Fixed an intermittent problem where a Gratuitous ARP is not sent successfully - Fixed a problem where after the IMM2 firmware is flashed, there is a slight chance that the IMM2 web server can't be accessed when AC power is reapplied - Disabled the weak cipher suit used in the SSL/TLS firmware with the https protocol to avoid potential security vulnerabilities - Fixed a problem on the System x3750 M4 where the IMM2 shared mode network connection will be lost after upgrading the firmware of the onboard Emulex BE3 controller - Fixed a problem on the HS23 where the OS watchdog timer doesn't work - Fixed a problem on the HS23 where the Fault LED occasionally lights when the chassis is powered on with the BPE4 - Fixed a problem on the HS23 where the server may shut down after resetting the IMM2 - Enhanced the messaging mechanism between the BladeCenter AMM and the IMM2 - Added power management capability in the IMM2 web interface
Version 2.06, 1AOO42B - Critical - Corrected the firmware to prevent users from disabling the IPv6 interface - Fixed a problem that caused the IMM2 to reset itself after running for a period of time - Corrected the SNMP request to disable the IMM2 IPv4 interface so that it disables only IPV4, instead of both IPv4 and IPv6 - Fixed a problem that occasionally caused the server to shut down when the IMM2 is reset - Fixed a problem where the IMM2 incorrectly reported a battery voltage error - Corrected a problem where repeated frequent IMM2 resets causes the IMM2 to run the firmware in its backup partition - Corrected a problem report where the IMM2 did not report a failure to the system profiles script when the chassis UUID is unavailable
Version 2.00, 1AOO40E - Critical - Critical Fix: -- Improves the reliability of the CPU and/or memory VRDs. This improvement lowers the occurrence of CPU & memory VRD failures on the x3300 M4 and x3750 M4 -- IMM2 improved error reporting for missing/down CPU in invalid CPU configuration for x4440 M4 - Corrected a problem that caused 3.3V and 5V faults to be reported by IMM2 firmware level 1aoo34z(1.85) on the HS23E blade - Eagle Ray SAS controller LED fault support improvements added for all ITE platforms
Version 1.97, 1AOO36R - Critical - Critical Fix: -- Improves the reliability of the CPU and/or memory VRDs. This improvement lowers the occurrence of CPU & memory VRD failures on x3650 M4, x3550 M4 and x3500 M4 - Thermal behavior enhancement on System x iDataPlex dx360 M4
Version 1.95, 1AOO36P (for System x iDataPlex servers) - Suggested - Added support for NVIDIA K1,K2,K20,K20x GPUs on System x iDataPlex dx360 M4
Version 1.88, 1AOO40A (for PureFlex System Compute Nodes) - Critical - Critical Fix: -- Fixed a potential security vulnerability with node management user accounts (Reference to Security Bulletin CVE-2012-4838) - Fixed a problem on Flex Systems where the SNMP get and set authority levels did not work - Fixed a problem on Flex Systems where mounting of remote media in a Linux environment showed a USB error - Fixed a problem on Flex Systems that caused the Remote Control Video Viewer window on a RHEL5.8 client to move when the arrow key is pressed - Fixed a problem on Flex Systems where the SMTP "Test Connection" button did not work when the SMTP port is changed - Fixed a problem on Flex Systems where the SNMP get and set authority levels did not work - Fixed a problem on Flex Systems where mounting of remote media in a Linux environment showed a USB error - Fixed a problem on Flex Systems that caused the Remote Control Video Viewer window on a RHEL5.8 client to move when the arrow key is pressed - Fixed a problem on Flex Systems where the SMTP "Test Connection" button did not work when the SMTP port is changed - Corrected the Mezzanine card power fault monitoring on the Flex System x440 Compute Node - Corrected a problem with IBM Fabric Manager configuration from the Flex Chassis Management Module - Added support to retrieve configuration settings from an LDAP server - Added support for the Flex Storage Expansion Node - Added support for CIM indications over https - Added fingerprint checking for SFTP transfers - Added automatic recovery of corrupted UEFI firmware - Added support for authenticated SMTP alerts - Added a display of the users who have a Remote Control session in progress - Provided a request to a Remote Control client to disconnect the session - Added support for the server S3 (sleep) state - Changed the default NTP sync interval from 3 minutes to 24 hours - Fixed a problem where the ambient temperature is only displayed in degrees Fahrenheit - Fixed a problem on the web interface where 'local' is not accepted as a top level domain name in the email format when configuring event recipients - Corrected an IMM2 SNMP trap OID to match the prior IMM format - Fixed a problem that prevented an external USB device from being remotely mounted as a floppy drive in Windows Server 2003 - Changed the blue Location led behavior to not blink when a firmware update is in progress
Version 1.85, 1AOO34Z (for BladeCenter blades and System x Servers) - Critical - Critical Fix: -- Fixed a potential security vulnerability with node management user accounts (Reference to Security Bulletin CVE-2012-4838) - Fixed a problem where a Blade Open Fabric Manager uncorrectable error can occur when booting the HS23 - Fixed a problem that IMM IPMI command periodically timed out when using HS23 in Chassis with the management network being disabled in some special configurations - Added support for the HS23 to recognize NEBS/Enterprise Mode for Telco chassis (this feature needs Advanced Management Module Firmware BPET62U or later) - Fixed a problem where the ambient temperature is only displayed in degrees Fahrenheit - Fixed a problem where on rack systems that have 2 power supplies installed, the 'Redundancy Power unit has been restored' event is logged every time that the IMM2 is reset - Fixed a problem where a Fan Tach going low (lower critical) event is intermittently asserted when configuring the IMM2 to use an NTP server - Fixed a problem on the web interface where 'local' is not accepted as a top level domain name in the email format when configuring event recipients - Corrected an IMM2 SNMP trap OID to match the prior IMM format - Fixed a problem that prevented an external USB device from being remotely mounted as a floppy drive in Windows Server 2003 - Changed the blue Location led behavior to not blink when a firmware update is in progress - Fixed a problem on the HS23E that causes Preboot DSA to hang in CLI mode when a user accesses it using Serial over LAN - Fixed a problem on rack servers where ASU cannot set IMM.GRP_GroupName.1 and IMM.GRP_GroupName.2 if the string length is 16 characters or longer. The firmware was corrected to allow a maximum length of 64 characters - Added support for CIM indications over https - Added fingerprint checking for SFTP transfers - Added automatic recovery of corrupted UEFI firmware - Added support for authenticated SMTP alerts - Added a display of the users who have a Remote Control session in progress - Provided a request to a Remote Control client to disconnect the session - Added support for the server S3 (sleep) state
Version 1.85, 1AOO34Y (for PureFlex System V7000 Storage Node) - Added support for Flex System V7000 Storage Node
Version 1.79, 1AOO36F - Suggested - Thermal behavior enhancement on System x iDataPlex dx360 M4
Version 1.78, 1AOO36E - Suggested - Thermal behavior enhancement for 115W & 95W CPU on System x iDataPlex dx360 M4 - Added support for the Intel KNC 5110p card
Version 1.77, 1AOO32X - Critical - Thermal behavior enhancement for 115W CPU on System x iDataPlex dx360 M4
Version 1.75, 1AOO32S - Suggested - Fixed a problem that a PCI uncorrectable error occurs when using HS23 with CFFh card (44W4479) in the BCS chassis - Fixed a problem where an "Unsupported blade/blower combination" error is reported when using the HS23 in the BCHT chassis configured in Enterprise mode - Fixed a problem in System x3530 M4, where the reported Active Energy Manager input/output power readings are inaccurate - Fixed a problem in System x3530 M4, x3630 M4, where an LDAP account can not login using the AD_CrossDomain tree - Fixed a problem in System x3530 M4, x3630 M4, where a user cannot use the "DNS to Find LDAP server/Extract search domain from login ID" setting from the IMM2 web to access an eDirectory server - Added support for Common Form Factor power supplies Oversubscription in System x3750 M4, Machine Types: 8722, 8733
Version 1.65, 1AOO32O - Suggested - Support the power supply Over-Subscription feature - Support the 750 Watt DC power supply for System x3650 M4,x3550 M4 - Support IBM 1.2TB High IOPS MLC Mono Adapter, IBM 2.4TB High IOPS MLC Duo Adapter for System x3650 M4, x3550 M4 - Support IBM LLM-SM Dual Port 10GbE SFP+ Adapter for System x3650 M4 - Fixed an abnormal Fan Zone recovery problem - Fixed a problem that IMM2 Email notification doesn't support an e-mail address with the underscore '_' character - Fixed a power policy "Restore" problem - Fixed a problem where the LDAP hostname can't be changed by ASU - Fixed a problem that the length of email address (for SNMP notification) is limited to 32 characters
Version 1.60, 1AOO32P - Suggested - Fixed a problem where the Chassis Management Module cannot correctly get the Mezzanine card information for the Flex System x220 Compute Node - Fixed a problem where the PreBoot DSA firmware could not be updated under VMWare ESXi 5 through the Flex System Manager's Update Manager - Fixed a problem where an IMM2 communications error can occur if an unexpected response causes VMware to spawn multiple processes when it does not receive the data it expects from the IMM2
Version 1.59, 1AOO32K - Initial Release - Supports System x3300 M4, Machine Types: 7382
Version 1.53, 1AOO30Z - Critical - Included an update to the FPGA that fixes an intermittent issue where the CPUs do not show up in a system with a RAID card installed, when the AC is removed and reapplied from the server without allowing sufficient time for the system hardware to completely discharge
Version 1.52, 1AOO34A - Suggested - Added redundant power supply and hot swap hard drive support in System x3100 M4
Version 1.51, 1AOO30Y - Critical - Support for NVIDIA Tesla K10, M2070Q, M2090 GPU cards on System x iDataPlex dx360 M4 - Fixed a problem in System x iDataPlex dx360 M4 where the password expires after creating a new user in the IMM2 web interface - Fixed a problem in System x iDataPlex dx360 M4, when the memory sensor changes from 'critical' to 'warning,' but the severity is not updated in the syslog or the email notification
Version 1.50, 1AOO30W - Suggested - Supports System HS23, Machine Types: 7875,1929 - Supports System x3650 M4, Machine Types: 7915 - Supports System x3550 M4, Machine Types: 7914 - Supports System x3500 M4, Machine Types: 7383 - Added support for the Intel Xeon E5-2643 processor on the HS23 in BCH-R3, BCS and BCHT chassis - Fixed a problem where the IMM2 incorrectly logged an "Unsupported blade/blower combination" on the HS23 in the BC-E 8677 chassis - Fixed a power restore problem on systems that have 2 Delta power supplies installed - Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where OpenLDAP Group Authentication filtering function doesn't work - Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where LDAP account can not login using the AD_CrossDomain tree
Version 1.45, 1AOO28S - NonCritical - Fixed a problem in Flex System x220 where the Chassis Management Module (CMM) Command Line Interface can't display the Mezzanine card information - Fixed a problem in Flex System x220 and x240 where the prebootDSA firmware cannot be updated through Flex System Manager's Update Manager
Version 1.40, 1AOO30T - Initial Release - Supports System x3750 M4, Machine Types: 8722, 8733
Version 1.38, 1AOO30D - Initial Release - Supports System x3630 M4, Machine Type: 7158 - Supports System x3530 M4, Machine Type: 7160
Version 1.36, 1AOO30P - Initial Release - Fixed an intermittent remote media failure in system HS23E - Fixed a problem in system HS23E where remote media does not work when two or more users have concurrent remote control sessions
Version 1.34, 1AOO28Q - Initial Release - Supports Flex System Manager Node, Machine Type: 8731 - Supports Flex System x240 Compute Node, Machine Types: 7863, 8737, 8738 - Supports Flex System x220 Compute Node, Machine Types: 2585, 7906
Version 1.32, 1AOO28N - Critical - Supports System x3630 M4, Machine Type: 7158 - Supports System x3530 M4, Machine Type: 7160 - Fixed a problem that may see unexpected fan events after power on in x3100 M4 and x3250 M4 systems - Enhanced robustness on I2C bus test
Version 1.30, 1AOO28M - Supports System HS23E, Machine Types: 8038,8039
Version 1.26, 1AOO26N - Initial Release - Supports System x3650 M4, Machine Types: 7915
Version 1.25, 1AOO26K - Initial Release - Supports System x3550 M4, Machine Types: 7914 - Supports System x3500 M4, Machine Types: 7383 - Supports System x iDataPlex dx360 M4, Machine Types: 7912,7913
Version 1.22, 1AOO26O - Suggested - Supports System HS23, Machine Types: 7875,1929 Problems Fixed: - Fixed a problem where the BOFM configuration may be lost after a blade power cycle - Fixed an LED error indication that occurs on the BPE4 - Fixed a problem where the Info LED lights during the discovery stage - Fixed a problem where an ABR event is not logged - Fixed an intermittent communication problem between the AMM and IMM2 - Fixed a problem that causes the remote media function to hang when a second user attempts to mount remote media - Fixed a problem where the 'break' keyboard function doesn't work with Serial Over LAN
Version 1.21, 1AOO26L - Initial Release - Supports System HS23, Machine Types: 7875,1929
Version 1.10, 1AOO24B - Supports System dx360 M4, Machine Types: 7918,7919
Version 1.05, 1AOO10K - Initial Release - Fixed the false alert issue in redundant PSU model
Version 1.00, 1AOO10I - Initial Release - Initial Release - Supports System x3250 M4, Machine Types: 2583,2587 - Supports System x3100 M4, Machine Types: 2582,2586
(C) Copyright International Business Machines Corporation 2008 - 2014. All rights reserved.
Firmware Version: 2.82x6 (w/ 5.12a13 Universal Boot Code) (Supported for IBM System x & BladeCenter)
Problems Fixed: - Emulex FC Adapter does not auto-enable SAN boot mode when boot target configuration is made via IFM (BOFM) - Emulex FC configuration utility is in the wrong F1 setup screen
- Multiple adapters connected to same PCIe bridge port can request more I/O space than system can allocate. - Updated firmware kernel code so Saturn based HBA and mezz cards do not use or advertize need for system I/O Space.
Enhancement - Reduce the boot time for UEFI driver for large configurations Fixes: - Fixed an issue that caused the Integrated Management Module (iMM) in System x servers to report Warning: Sensor GPT Status has transitioned from normal to non-critical state. - Fixed an issue where 4k sector size drives with 512e reporting enabled show wrong physical size when running a read capacity 16 command. - Fixed an issue where speed negotiation for 3Gig SATA drives is not handled properly. - Added Support for Report Luns Command - Fixed an issue where OS hang during install of Linux system to a SSD - Fixed an issue where SAS device page 0 may still be present for Initiator devices that have been removed from the topology. - Fixed an issue where RHEL 6.3 hangs during boot with IBM 600GB High IOPS MLC Modular Adapter - Fixed an issue where a non-PI volume made up of all PI capable drives, may come up as PI enabled after a controller reset. - Fixed an issue where a fault 0X8808 occurs when a reset is issued to the controller that has max number of active/inactive volumes - Fixed an issue where "Device Present" Flag of SAS device page0 is not set for initiator controller in then target controller when two controllers are connected to each other in initiator/target mode. - Fixed an issue where extended tags and PCIe upconfigure capability are disabled in SAS2208 and SAS2308. - Fixed an issue where force full discovery does not trigger rediscovery of an expander after the initial expander discovery fails. - Fixed an issue where single RAID0 volume activation was succeeding, even though controller does not support single drive RAID0. - Fixed an issue where RAID1 volume of Non-PI drives moves to optimal state when a PI drive is hotplugged and 'Enable PI mixing' not enabled. - Fixed an issue where Locate LED's stop automatically after 3-4 minutes before user issues command to turn off the Locate LED's. - Fixed an issue where fault 0x8618 is seen when a new volume is created in the presence of another volume which is undergoing resync along with IO. - Fixed an issue background initialization does not start on RAID0 volume with PI drives, after removing and reinserting a volume member.
BIOS - Fixed an issue where core BIOS displays warning message when it fails to add all of the drives connected to int13 chain, then waits for user to press any key to continue further, rather than continuing after 3 seconds. - Fixed an issue where incorrect adapter is being tagged as the first adapter found. - Fixed an issue where the save or discard changes prompt appears after a failed attempt to set volume as the boot device in BIOS CU. - Fixed an issue where BIOS CU provides incorrect device pointer when checking for raid disk to allow/disallow setting boot device. - Fixed an issue where device properties screen is invoked from a direct attach device using Alt+D in SAS topology screen, device traversing [Alt+N & Alt+P] is restricted within the direct attach device and expander attach devices are not traversed. - Fixed an issue where the drive status field does not show 'Max dsks' when trying to select 11th drive for RAID10 volume. - Fixed an issue maximum Int13 devices settings does not get honored, when the value is set as 0 in BIOS CU - Fixed an issue where drive size of 1.088GiB was showing as 1.880GiB. - Fixed an issue current boot device set to device at slot 4" message Not displaying for Adaptors with boot order other than 0. - Fixed an issue where the BIOS CU navigates to create new volume screen instead of back to raid properties screen. - Fixed an issue where BIOS banner showed 'FF' for slot information. - Fixed an issue where the drive's SMART status is always shown as no irrespective of drive's SMART status, under Pred Fail column of the manage hot spare screen and create new volume screen. - Fixed an issue where SAS2 BIOS: volume size shows inconsistent value in the create new volume' screen after selecting the last volume member. - Fixed an issue where a disabled adapter causes the second adapter status to show as unavailable even though the second adapter is enabled. Uefi Enhancement 1/2 - Added capability to create an IR RAID volume in non-PI mode, even when all member drives are PI Capable. - Added PI info and ability to control creation of PI Volume in UCM of BSD HII. - Added new form manage PHY settings to support enabling or disabling of a controller PH Fixes: - Fixed an issue view foreign volume option is disabled with a foreign volume in the configuration.
- Fixed issue where acceptable indistro device drivers may not pass minium driver check. BIOS Changes Enhancement(s): - Core BIOS and BIOS configuration utility will display "FF" as the PCI slot number when proper slot information is not available. - Increased the disk drive spin-up timeout value to accommodate disk drives having larger spin up times.
Fix(es): - Fixed an issue where the adapter order does not get written to NVM and "Updating Adapter Order" displays on every reboot. - Fixed issue where zero sized volume was showing "4. 0 GiB." - Fixed issue where devices, which are not attached to adapter 0, could not be promoted to positions in the boot order when they were selected in the configuration utility. - Fixed an issue where IOS Banner(POST) not showing SAS Discovery error when more than one HBA is connected to the host system. - Fixed an issue where the SMART status is not correctly displayed for bare drives. - Fixed an issue in SAS topology where a RAID disk is highlighted and attempted to set as preferred boot device or alternate boot device, the configuration utility displays a SAVE/DISCARD prompt. - Fixed an issue where the firmware was showing a large elapsed time when a format operation crosses midnight in the system clock.
Firmware Changes Enhancement(s): - Added support for 4GB DIMM - Added the ability for user the enable/disable of the drive write cache during the BIOS start up.
Fix(es): - Fixed an issue where a request sense command, which is executed after a SATA drive is in active state is moved to idle power condition state, has no 'Additional Sense' information set. - Fixed an issue where protected information error "Logical block reference tag check failed" is received when an IR volume is deleted. - Fixed an issue Self-Test Results log page where values for update parameter code, format and linking, and parameter length are not recorded. - Fixed an issue sending vital product data inquiry with vital product data page set as invalid (0xFF) while diagnostic is running on a SATA drive results in segmentation fault 0x1901. - Fixed an issue where input/output is sent to SATA drives before the drives are ready. - Fixed an issue where fault 8405 was being hit while disabling and enabling the phy to which secondary drive is connected with IOs active. - Fixed an issue where subsequent commands sent to a SATA drive fail after a write same command failure until NCQ error handling is triggered or the device is reset. - Fixed an issue where Report Luns command sent to SATA drive fails if the drive is spun down. - Fixed an issue where hotspare does not resynch with second raid volume when both volumes are in degraded state. - Fixed an issue where incorrect sense data is populated when Security Protocol IN/OUT command is sent to supported drive. - Fixed an issue where allocation length for inquiry SCSI Command is not handled Properly during SATA Drive Format. - Fixed an issue during SATA drive format where vital product data inquiry command is executed for SATA drive with invalid page code, and the command is passed with no data instead for failing with CC and sense data. - Fixed an issue where the host will not indicate the existence of the expander attached drives if the direct attached device re-ordering feature is enabled. - Fixed an issue where protected information errors are observed on a RAID 1 volume its BGI is not completed, and its member physical disks are removed and inserted. - Fixed an issue where the TM response was set to failed if the device is missing due to the DO NOT SEND TASK IU flag being enabled. - Fixed an issue where DMD (Device Missing Delay) timer is not set to the default time when the total Report Device Missing Delay is greater than 0x7F seconds. - Fixed an issue where RAID1 volume fails to resynch when a new compatible bare drive is available in the primary drive slot. - Fixed an issue where error handling for errors, that cause the DMA engines to halt, are not handled properly and multithreaded IOs can hang if the same control block is used too soon. - Fixed an issue where a third hotspare is created even if the number of hotspares currently present in the RAID Configuration is 2. - Fixed an issue where inactive foreign volume information cannot be seen in SASBIOS when a native volume is deleted.
UEFI Changes Enhancement(s) - Additional information such as vendor id and product id added to the HII Create Configuration Screen. - Added ability to check to detect missing hotspares to HII. - Modified to be obtained PCI Slot Number information from the system firmware protected information. - Additional character "M" will be displayed as part of the device display identifier of a multipathed disk. - Ability in HII to detect missing hotspares and provide a facility to delete the missing hotspares. - Implemented Configuration Summary and Simple Virtual Disk Creation Support for Unified Configuration Management. - Modified UEFI driver to wait for a maximum of 10 seconds for the controller to become ready, so controller gets discovered in the OS.
Fix(es): - Fixed an issue where Enable/Disable write cache does not work for SAS drives. - Fixed an issue where HII Configuration utility does not allow the user to create a RAID0 with single disk present in the topology. - Fixed an issue in Create Configuration menu where additional drive information is not getting updated appropriately in HELP area. - Modified to prevent Write Cache settings options from appearing for the IR firmware. - Fixed an issue where SATA volume members and hotspare drives are labeled as 'M' in a multipathed environment. - Fixed an issue to prevent HII from allowing the option to enable/disable write cache for SATA drives. - Fixed an issue where multipathing is disabled in Manufacturing page settings, but volume members and hotspare drives are labeled as "M." - UEFI driver modified to check BIOS Options in order to determine if is should manage the controller.
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 HBA/LSI Onboard 6Gb SAS/SATA/SSD Driver for Linux
NOTE TO SERVICE - Reference RETAIN N/A
Supported Controllers: - IBM N2125 SAS/SATA Controller (46C9011) - IBM N2115 SAS/SATA Controller (46C8989) - IBM 300 GB High IOPS MLC Modular Adapter (90Y4361) - IBM 600 GB High IOPS MLC Modular Adapter (90Y4365) - IBM 800 GB High IOPS MLC Modular Adapter (90Y4369) - IBM 300 GB High IOPS SLC Modular Adapter (90Y4373) - ServeRAID H1110 SAS/SATA Controller for IBM System x (81Y4492) - IBM 6Gb SAS HBA (46M0907) - IBM 6Gb SSD HBA (68Y7362) - Onboard LSI 2004 SAS
Version 18.00.01.00 - Suggested ------------------ Enhancement: - Added support for SLES 11 SP 3. - Turn off the Predictive Failure LED when a drive is removed. - Added support to issue a Start Stop Unit command (stopping the target) to all non-IR direct-access SATA devices before the driver is shut down or unloaded.
Fixes: - Fixed an issue where the driver message logs contains an entry "mpt2sas0: _base_get_ioc_facts: failed going to ready state, when the controller is in operational state. - Fixed an issue where a kernel panic observed after issuing controller diagnostic reset. - Fixed an issue where a kernel panic observed when an enclosure is removed load while the driver module is loading. - Fixed and issue where component drives of a volume go missing once the volume is deleted. - Fixed and issue where the mapping of reply queues used for IO requests coming from each CPU is not balanced when number of CPU cores are greater than the number of MSI-X vectors. - Fixed and issue where the set_affinity.sh script fails on the systems having more than 32 CPU cores. - Fixed an issue where device entries are removed when async scanning mode is enabled and device scanning is in progress. Version 15.00.00.00 - Suggested ------------------ Enhancements: - Added support for SLES 11 SP 2 - Added support for N2115/N2125 SAS/SATA, 300GB MLC (90Y4362), 600GB MLC (90Y4366), 800GB MLC (90Y4370) and 300GB SLC (90Y4374)
Fixes: - Fixed issue where the phy disks are not discovered when the volume members are hot removed, and added while performing diag reset. - Fixed issue where SAS HBA 6Gb adapters fails Read Capacity 16 command sent to Tape drives. - Fixed issue where a device scan following a host reset could get stuck in an infinite loop. - Fixed issue where driver goes into a infinite loop when the REPORT_LUNS command gets a check condition. - Fixed issue where driver does not comply with the updated timing requirements for issuing a Hard Reset. - Fixed issue where missing delay was not getting set during system boot-up kernels 2.6.20 and newer.
Version 10.30.00.00 - Suggested ------------------ Fixes: - Use a different method for blocking IO request from SCSI Mid Layer when using the SysFS shost attribute called task_management. - Fixed issue to not allow IOCTLS to be processed when tge device driver is loading, which could cause a kernel panic. - Added support in asynchronous scanning logic to handle faults during discovery when loading the driver. - Allocate only one msix vector for the controllers that do not support multi-reply queues and NUMA IO. - Added per lun delete flag to addres an issue where a cable is removed and added back within the DMD timer expired timeout. - Fixed issue with reading raid configuration information for inactive volumes - Fixed issue where a Stack trace seen in message log after cable pull and host reset. - Fixed issue where The configuration pages are failing if raid volume is configured while issuing a host reset - Fixed issue where the Devices are not removed after "cable pull". - Fixed issue when devices are behind two deep cascaded expanders, they don't get added if the "cable add" is done while host reset is active. - Fixed a failure message displayed in the log messages during host reset while removing devices - Fixed issue where drives are not getting removed when the enclosure cable is pulled out from the expander and Port Reset is issued. - Fixed issue where the Chip Resets results in repeated timeouts. - Fixed issue with expanders where a hang occurs when there is smart error.
Version 4.30.01.00 - Initial release ------------------ ibm_dd_mpt2sas_18_00_01_00_sles11_32-64_chg
=============================================================================== Emulex NIC Device Driver for Linux ===============================================================================
Device Driver Version: 10.2.377.26 Supported On: System x and Bladecenter
Device Driver Version: 10.2.363.0 Supported On: System x and BladeCenter
Problems Fixed: - Multiple performance improvements in virtualized environments (SR-IOV,UMC) - Resetting Transparent Vlan to Default Vlan is not working - Cleanup ethtool set settings code - ARI on IBM x3650M4: All functions are not displayed in Linux
Device Driver Version: 10.2.261.0 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Provide link state control for VFs - ethtool shows port as fibre though copper cable is connected. - Multi channel config should be determined via port resource descriptor - Showing WoL supported in ethtool for BE3 where it is not supported - be2net driver crash when umc enabled - ip link show command shows vlan for vfs although vlan creation is failed on the vfs - Emulex be2net driver does not support IOMMU pass through mode
Device Driver Version: 10.0.800.0 Supported On: IBM System x
Problems Fixed: - Low bi-di throughput seen on 1g ports of HS-23 LOM - Multiple performance improvements - Bonding driver takes approx 20 seconds to be ready
Incremental Interoperability: - RHEL 5.10 - RHEL 6.5 - XE-102 and XE-104 ASIC (OCx14xxx) - Support for set and get channels ethtool operation
Known Issues: - SR-IOV is supported with the following Linux distributions: * RHEL 6.4 and above 64-bit with KVM * SLES11 SP3 and above 64-bit with KVM
NOTE: Guest operating system support is dependent on the Emulex driver version installed in the guest.
Device Driver Version: 4.6.267.4 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 KVM configurations - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 SR-IOV configurations - SR-IOV configuration section of the Linux NIC Driver Documentation has been modified to improve clarity
Incremental Interoperability: - S3 Resume on IBM Flex - SLES 11.3 on IBM System x and BladeCenter
Known Issues: - SR-IOV is supported with the following Linux distributions: * RHEL 6.3 and 6.4 64-bit with KVM * SLES11 SP2 and SP3 64-bit with KVM
NOTE: Guest operating system support is dependent on the Emulex driver version installed in the guest.
- Use of SR-IOV with the XEN hypervisor is not supported at this time.
- Use of SR-IOV with the KVM hypervisor requires the use of macvlan network interfaces.
Device Driver Version: 4.6.148.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - Ethernet performance issues in a variety of workloads - VFs are not displayed after driver re-load when is VFs attached to VM - vLAN tagging in Switch Agnostic vNIC mode
Incremental Interoperability: - RHEL 5.9 - RHEL 6.4 - Network performance varies with workload. An ethernet driver tuning script and instructions is now included with the be2net driver. - Switch Independent Mode within hypervisor OS's
Known Issues: - Multi-channel is not supported in RHEL5.x XEN. This is a kernel limitation - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 KVM configurations - Under certain conditions, performance issues may be seen with multi-channel in RHEL6.4 SR-IOV configurations - SR-IOV is not supported with RHEL5.x XEN
Device Driver Version: 4.4.180.0 Supported On: IBM Flex
Device Driver Version: 4.2.389.0 Supported On IBM System x and BladeCenter
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
Device Driver Version: 4.1.413.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - 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
Device Driver Version: 4.1.334.39 Supported On: IBM System x and BladeCenter
Problems Fixed: - 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
Please visit www.qlogic.com for full documentation, additional drivers, and management applications.
Version 3.2.5.1 New Features and Feature Enhancement: - References to Brocade changed to QLogic - Support for RHEL5.11 and RHEL7.0
Version 3.2.4.0 New Features and Feature Enhancement: - Support for RHEL5.10 and RHEL6.5
Version 3.2.3.0 New Features and Feature Enhancement: - Support for patching firmware via boot image - Support for Linux PTP - Support for UEFI Health Check Protocol - Support for SLES11SP3
Version 3.2.1.0 New Features and Feature Enhancement: - Support for "IBM Flex System FC5024D 4-port 16Gb FC Adapter" PART_NUMBER "95Y2381" - Support for RHEL5.9 and RHEL6.4
Fixes and Enhancements: - Enhanced Linux driver data path to properly handle IPv6 packets. - Enhanced Linux driver to make sure user configured path tov value is persistent and is not changed due to change in dev_loss_tmo.
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_5_1_sles11_32-64_chg
======================================================= Change History for Qlogic Linux iSCSI driver for 10 GbE Converged/Intelligent Ethernet Adapter ======================================================= Document Name: Change History Document Status: IBM General Avalibility Latest Package Version: 5.4.1.9 Latest Driver Version: 5.04.01.09 Document Updated: 09/25/2014 Product: Qlogic iSCSI Linux Device Driver
Defect/Enhancement: Defect Problem: Adapter initialization failure during driver load time Solution: The get_sys_info mailbox command was changed in firmware that caused the mailbox command to fail thus failing the adapter initialization. Added fix to handle the get_sys_info mailbox command to validate the size of data returned in the mailbox command response. Introduced: Firmware v5.02.04 Impact: HW: ISP8032 OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Defect Problem: Driver module parameter ql4xdontresethba=2 does not allow context resets [ER00000000100932] Solution: Added fix to set the DONTRESET_BIT0, in case ql4xdontresethba==2. Also changed the ql4xdontresethba description, if parameter value is set to 1. Introduced: Day One Impact: HW: ISP8032 OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Enhancement Problem: Different activities are performed on link events while loopback diagnostics is in progress Solution: Fix is to quiesce all driver activities like re-login to devices, dynamic lun scan, iSNS checks etc. while loopback diagnostics is in progress. Introduced: Day One Impact: HW: ISP8032 OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Enhancement Problem: Loopback mode request on same physical port from same or other protocol drivers must not be permitted Solution: Added fix to invalidate loopback request on same physical port Introduced: Day One Impact: HW: ISP8032 OS: RHEL 5.6/5.7/5.8, RHEL 6.0, RHEL 6.1, Citrix 5.6 FP1, Citrix 6.0, SLES 11 SP1, SLES 10 SP3/SP4 Protocol: iSCSI
Defect/Enhancement: Enhancement Problem: Failure of restoration of loopback port configuration to original configuration Solution: If restoring of original port configuration fails then reset the chip. Failure to do so may not restore the link state and other driver instances sharing the physical port would be left in a non-operational state. Introduced: Day One Impact: HW: ISP8032 OS: RHEL 5.6/5.7/5.8, RHEL 6.0, RHEL 6.1, Citrix 5.6 FP1, Citrix 6.0, SLES 11 SP1, SLES 10 SP3/SP4 Protocol: iSCSI
Defect/Enhancement: Enhancement Problem: ISP4xx and ISP82xx firmware may assert if given more IOCBs than it can handle Solution: The driver was updated to throttle the number of active IOCBs based on the total # of IOCB buffers received from GetFirmwareStatus mbx_sts[2]. Introduced: Day One Impact: HW: ISP4xxx/ISP82xx OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Defect Problem: Failure to re-register IRQ handlers while retrying of adapter initialization Solution: Added fix to re-register the interrupt handler when adapter initialization is retried. Introduced: Day One Impact: HW: ISP8022/ISP8032 OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Enhancement Problem: Driver unable to collect forceful firmware dump [ER0000000097083] Solution: Added support to forcefully collect firmware dump using command, "echo 2 > /sys/class/scsi_host/hostX/device/fw_dump" For ISP83xx case, check if ISP83xx can perform reset before setting reset owner and firmware hang flags. Introduced: Day One Impact: HW: ISP8022/ISP8032 OS: All supported Linux flavors Protocol: iSCSI
v5.03.01.07.xx.xx-x0 ---------------------
Defect/Enhancement: Defect Problem: Minidump collected using QLogic application gives warning messages when verified using minidump verification tool Solution: Added fix to return the total minidump size to the application and sync the coredump data structure with the application data structure. Introduced: Day One Impact: HW: ISP8022/ISP8032 OS: RHEL 5.6/5.7/5.8, RHEL 6.0, RHEL 6.1, Citrix 5.6 FP1, Citrix 6.0, SLES 11 SP1, SLES 10 SP3/SP4 Protocol: iSCSI
Defect/Enhancement: Defect Problem: Compilation warnings were seen on SLES 10 32-bit arch Solution: Fixed compilation warnings of 32-bit kernel flavors Introduced: Day One Impact: HW: All supported Hardware OS: SLES 10 SP3/SP4 Protocol: iSCSI
Defect/Enhancement: Enhancement Problem: Unknown AENs were seen in log messages Solution: Added debug statements to print the received AENs instead of unknown AENs Introduced: Day One Impact: HW: ISP8032 OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Defect Problem: System panic was seen while collecting Minidump using QLogic application Solution: Added fix to collect minidump specific to ISP83xx instead of older method used for ISP40xx. Introduced: Day One Impact: HW: ISP8032 OS: RHEL 5.6/5.7/5.8 Protocol: iSCSI
v5.03.01.06.xx.xx-x0 ---------------------
Defect/Enhancement: Defect Problem: Mailbox command timeout seen just after completion of adapter reset Solution: Added fix to enable mailbox/AEN interrupts before initializing the firmware to make sure mailbox/AEN interrupts are processed in interrupt mode. Introduced: Day One Impact: HW: ISP8032 OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Enhancement Problem: Kernel panic while driver is trying relogin to targets after completion of adapter resets Solution: Added fix to handle stale DDB entries after reinitialization of DDB list and 8014 AENs for new devices. Introduced: Day One Impact: HW: All supported Hardware OS: RHEL 5.6/5.7/5.8, RHEL 6.0, RHEL 6.1, Citrix 5.6 FP1, Citrix 6.0, SLES 11 SP1 Protocol: iSCSI
Defect/Enhancement: Defect Problem: Target scan took longer time when driver loaded in legacy interrupt mode Solution: Added fix to complete the scsi command as early as possible from the legacy interrupt handler context instead of waiting for completion from the DPC context Introduced: Day One Impact: HW: ISP8032 OS: SLES10 SP3/SP4 Protocol: iSCSI
Defect/Enhancement: Defect Problem: Adapter reset seen for ACB old state as VALID and new state as ACQUIRING Solution: Added fix to perform context reset instead of adapter reset for ACB states ACB_STATE_VALID and ACB_STATE_ACQUIRING Introduced: Day One Impact: HW: ISP8032 OS: RHEL 5.6/5.7/5.8, RHEL 6.2, SLES 11 SP2, SLES 10 SP3/SP4 Protocol: iSCSI
Defect/Enhancement: Defect Problem: Retries for initialize adapter seen if driver probe failure encountered due to mailbox timeout Solution: Added fix to clear AF_IRQ_ATTACHED and fail probe adapter if initialize adapter fails and thus avoid multiple reties of initialize adapter. Introduced: Day One Impact: HW: ISP8032 OS: RHEL 5.6/5.7/5.8 Protocol: iSCSI
Defect/Enhancement: Defect Problem: IPv6 targets do not come back online after cable pulls (LINK DOWN/UP) Solution: Set options field of ddb_entry struct to identify IPv6 target. After driver DDB allocation, options field of ddb_entry struct was not populated. So IPv6 targets behaved like IPv4 targets and issued relogin on IPv4 targets instead of IPv6 targets. Set options field of ddb_entry struct to identify IPv6 target. Introduced: Day One Impact: HW: All supported Hardware. OS: RHEL 5.6/5.7/5.8 Protocol: iSCSI
Defect/Enhancement: Enhancement Problem: Pause flood causes switch port to disable Solution: Added Disable Pause Frame support Introduced: Day One Impact: HW: ISP8032 OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Enhancement Problem: Udev fw_dump file nomenclature mismatch across multiple protocols Solution: Use standard nomenclature for udev fw_dump file Introduced: Day One Impact: HW: ISP8022/ISP8032 OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Defect Problem: Mailbox command timeouts seen intermittently Solution: Fix double clearing of RISC interrupt in polling mode Introduced: Day One Impact: HW: ISP8032 OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Enhancement Problem: IDC lock recovery in PCIe AER error recovery path Solution: Fix recursive IDC locking in PCIe AER recovery path Introduced: Day One Impact: HW: ISP8022/ISP8032 OS: All supported Linux flavors Protocol: iSCSI
Defect/Enhancement: Defect Problem: Firmware relogin failure on adapter reset causes IOs to halt Solution: Retrieve the firmware device state to check if relogin is necessary Introduced: Day One Impact: HW: ISP8022/ISP8032 OS: RHEL 5.6/5.7/5.8 Protocol: iSCSI
Version 5.03.01.05 Initial release of Qlogic iSCSI Device Driver for 10 Gb Adapter.
qlgc_dd_iscsi_qla4xxx-5_04_01_09_sles11_32-64_chg
uEFI Flash Update Version 1.82 (BuildID D7E146C) Change History
Version 1.82 - BuildID: D7E146C ------------------------------------------------- Problem(s) Fixed: - Memory Latency issue. Incorporated Intel Microcode Update (MCU) MED 306E4_00000428. - Addressed a Unified Change Management (UCM) issue that was overwriting configuration changes made via 3rd party utilities - Turn off High Precision Event Timer (HPET) from uEFI setting. - Updated UEFI to address these vulnerabilities: CVE-2014-3571, CVE-2014-3569, CVE-2014-3572, CVE-2014-8275, CVE-2014-3570
Enhancements: Limitations: - When flashing UEFI from version 1.30 or later to a version earlier than 1.30, a "Boot Configuration Error" message will be logged into the UEFI error log. This error does has no impact on the system configuration or operation. No errors are logged when flashing from an earlier version to version 1.30 or newer. Dependencies: - The IMM firmware must be at BUILDID: 1AOO58T Version: 4.31 (ibm_fw_imm2_1aoo58t-4.31_anyos_noarch) or higher prior to installing UEFI version 1.70. If the IMM level is lower, the UEFI update module will be rejected as invalid because of additional security features features implemented in this release.
Version 1.71 - BuildID: D7E142A ------------------------------------------------- Problem(s) Fixed: - Fixed an issue with continuous reboots when applied new LSI FW and the Remote Console setting is Enabled. Enhancements: Limitations: Dependencies:
Version 1.70 - BuildID: D7E140Z ------------------------------------------------- Problem(s) Fixed: - Fixed the system boot failure due to low PCI memory-mapped resource for a VGA device - Incorporated Intel Microcode Update (MCU) MED 306E4_00000427 to address Intel Erratum Enhancements: - Enhanced memory SPD logging for Intel E5-2600 v2 processors - Enhanced error logging for memory-mirroring mode configurations - Support Memory Reference Code Release version 2.0.0.3 - Support AES enable/disable by ASU - Enhanced IBM boot manager - Enhanced TPM Physical Presence lock algorithm Limitations: - When flashing UEFI from version 1.30 or later to a version earlier than 1.30, a "Boot Configuration Error" message will be logged into the UEFI error log. This error does has no impact on the system configuration or operation. No errors are logged when flashing from an earlier version to version 1.30 or newer. Dependencies: - The IMM firmware must be at BUILDID: 1AOO58N Version: 4.30 (ibm_fw_imm2_1aoo58n-4.30_anyos_noarch) or higher prior to installing UEFI version 1.70. If the IMM level is lower, the UEFI update module will be rejected as invalid because of additional security features features implemented in this release.
Version 1.60 - BuildID: D7E136W ------------------------------------------------- Problem(s) Fixed: 1. Can not boot up from IMM Remote Mount with USB key. 2. Fixed that LR-DIMM 1333Mhz 1.35V memory speed is incorrect at Balanced mode Enhancements: 1. Support two DIMM Per Channel run at 1866Mhz for 16GB RDIMM 1.5V DR x4 & 32GB LRDIMM QR x4 2. Variable store self-healing. Limitations: 1. When flashing UEFI from version 1.30 or later down to version 1.20 or lower, a "Boot Configuration Error" message will be logged into the UEFI error log. This error does has no impact on the system configuration or operation. No errors are logged when flashing from an earlier version to version 1.30. Dependencies: 1. The IMM firmware must be at BUILDID: 1AOO50D Version: 3.65 (ibm_fw_imm2_1aoo50d-3.65_anyos_noarch) or higher prior to installing UEFI version 1.60. If the IMM level is lower, the UEFI update module will be rejected as invalid because of additional security features features implemented in this release.
Version 1.50 - BuildID: D7E134E ------------------------------------------------- Problem(s) Fixed: 1. Corrected IPv6 reboot problems 2. Corrected 64bit resouce allocation problems 3. Fix CPU frequence lockdown when UEFI recalibrates the power levels during first cold boot Enhancements: 1. Add support for Intel Xeon processor E5-2600 v2 product family 2. Add notification when UEFI detects GPT corruption during POST 3. Add support to configure the "Next Boot to F1 setup" function out of band 4. Add long text support in F1 setup help string 5. Implement LAN Fail-Over function Limitations: Dependencies:
Version 1.40 - BuildID: D7E128D ------------------------------------------------- Problem(s) Fixed: 1. Fixed that IB mezz card still shows "Standby Power Enable/Disable item" in uEFI setup menu 2. Fixed that can not enter F1 setup menu after 3x POST failure occurred. 3. Correct the PCIE link control of Active-State Power Management(ASPM) setting to result the PCI/NMI problem 4. Fix that UA-101 audio device hang at legacy mode Enhancements: 1. Multiple PCIe adapter BARs 2. Configurable MMIO base 3. Support Firmware first feature 4. Add informational messages when existing UEFI F1 setup menu 5. Add OEM SPD feature 6. Fixed the Preboot Execution Environment(PXE) function with Emulex 10 GbE Virtual Fabric Adapter III Limitations: Dependencies:
Version 1.30 - BuildID: D7E124C ------------------------------------------------- Problem(s) Fixed: 1. Fixed that some USB device hang at legacy mode (UA-101 USB audio device) 2. Disable CPU C-state and phase shedding for Volterra EOS issue Enhancements:
Limitations: Dependencies:
Version 1.30 - BuildID: D7E124A ------------------------------------------------- Problem(s) Fixed: 1. UEFI option 43 failed to work 2. ITP can't trigger CPU2 IERR 3. MBE WHEA-log can't match ECC Uncorrectable event 4. iMM lost connection with shared NIC on Intel mezz card (Meteorite) after power cycle Enhancements: 1. Change UDIMM 2DPC@1333Mhz 1.35V algorithm to meet performance specification requirement 2. Support ROM Recovery feature (Auto Promotion under Backup Bank Management Method) Limitations: Dependencies:
Version 1.20 - BuildID: D7E120C ------------------------------------------------- Problem(s) Fixed: 1. Sevaral uEFI OS boot failed with F12 boot menu HDD0. 2. Console Switch 1754A2X with KB & Mouse are not responding in EFI Web BIOS 3. Multiple issues caused by USB over current, including: 3.1 Unable to use front USB Port to flash firmware, load operating system or install a keyboard/mouse. 3.2 VMWare Purple Screen of Death (PSOD) during OS installation or booting. 3.3 Intermittent USB configuration change under Windows. 4. Fan speed goes to 100% after enable several TPM settings. 5. TPM 1.2 UEFI Preboot Interface Test (found CPU error) Enhancements: 1. Enable DRAM phase shedding 2. Support FastSetup feature 3. Support UDIMM 2DPC@1333Mhz running at 1.35V Limitations: Dependencies:
Version 1.10 - BuildID: D7E116A ------------------------------------------------- Problem(s) Fixed: 1. E5-2690 cannot run frequency at 2.9GHz(only 2.8GHz) when turn off Turbo mode. 2. Instruction for TPM enablement has type error. 3. CPU can not enter deep C status with uEFI 11I under RHEL5.7 64 4. Failed to boot from CDDVD ROM with uEFI OS 5. Best Card cannot link with Gen3 on Mezz Card slot 6. BestCard expr_mess_fatal and expr_mess_nonfatal would not get PCI error event and PCI error LED was off 7. iSCSI ISID mismatch under uEFI BIOS Settings. 8. TCG TPM Integration Test (Manual) random failed under WIN2K8 R2 SP1 with uEFI_11L 9. QPI link speed and Turbo mode show incorrect with M1 stepping CPU. 10.The format of System Event Log is uncorrected 11.Legacy Thunk Support is malfunctional 12.DIMM slot 13-24 can NOT indicate which memory was falut when trigger MBE on Mirror mode by bugged DIMM 13.ASUT74H can't find any iscsi item 14.BestCard ASB_Wiz stress test is failed with Gen 3 link speed 15.Fail to set some of PXE items with ASU76h 16.Can not boot into WinPE in RAID HDD on Crossfield 17.Personality can not be switched in OCM tool no matter FOD is imported 18.Processor speed is incorrect when system is idle 19.VLAN ID can be configured to ID 0 20.PCIX Best Card cannot get software NMI when trigger some of PCIX command 21.10G PCIe slot got incorrect slot error event by PCI-E Best Card 22.PCIe BestCard expr_flow got IERR 23.PCI led on and uEFI report OUT_OF_RESOURCES when system plug-in BussardE 10GbE adapter. 24.Processor speed is incorrect when system is idle w/ E5-2637 M1 25.Console redirection can not work normally with com2com. 26.No screen output with SOL connection 27.iSCSI Attempt will disapper when system reboot several times. 28.BestCard expr_mess_fatal and expr_mess_nonfatal would not get PCI error event on Internal RAID Slot 29.Purple Screen of Death when boot/install ESXi 5.0 to Hypervisor key
Enhancements: 1. Open Optimized Boot setup item with default enable 2. Open Legacy Thunk support setup item 3. Change Operating Mode from Custom Mode to Efficiency - Favor Performance 4. Remove USB port0 OverCurrent Mapping 5. Add DriverCodeDisplay error code on screen function
Limitations: Dependencies:
Version 1.00 - BuildID: D7E112J (Initial Release) ------------------------------------------------- Problem(s) Fixed: 1. High failure rate on front USB cable position/design cause all USB device disappear and could not flash via UXSPI
Enhancements: Limitations: Dependencies:
ibm_fw_uefi_d7e146c-1_82_anyos_32-64_chg
Firmware Update for IBM High IOPS Modular Adapter
Controller Supported: - IBM 300 GB High IOPS MLC Modular Adapter (90Y4361) - IBM 600 GB High IOPS MLC Modular Adapter (90Y4365) - IBM 800 GB High IOPS MLC Modular Adapter (90Y4369) - IBM 300 GB High IOPS SLC Modular Adapter (90Y4373)
Version 7.30.05.00-1 - Non Critical -------------------- - Added Support in RHEL 5.9 indistro device driver
Version 7.30.05.00 - Initial release ------------- ibm_fw_mpt2sas_hiop-7_30_05_00-1_linux_x86-64_chg
See readme for a list of changes qlgc_fw_nic_7_12b_4_2e_linux_32-64_chg
IBM Online SAS/SATA Hard Disk Drive Update Program Version 1.14.04 Build ID: SAS11404
NOTE TO SERVICE - Reference RETAIN TIP H29851 ******************************************* IBM SAS Hard Disk Drive Update Program Version 1.14.04 Critical Release Reference RETAIN TIP H29851
This package includes updates to drives with product ID strings of:
- TXA2D20200GA6I, TXA2D20400GA6I, TXA2D20800GA6I, TXA2D21600GA6I to GB76 - fixes ACK/NAK timeout and IT Nexus lost issues. In addition a change to the BLOCKLIMITSVPDPAGE field in Vital Product Data (VPD) page 0xB0 to limit the size of an UNMAP command. see Retain Tip H211424.
SAS 2.5"
Initial code Release - SMK3001GRDB, SMK6001GRDB, SMK9001GRDB to SB35
SATA 2.5"
- SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to NA36 - SSDSC2BB120G4I, SSDSC2BB240G4I, SSDSC2BB400G4I, SSDSC2BB800G4I to NB37 - fix to prevent possible drive lock up during format.
SATA 1.8"
Initial Code Release - SSDSC1NA200G3I, SSDSC1NA400G3I to NA36 - SSDSC1NB080G4I, SSDSC1NB240G4I, SSDSC1NB400G4I to NB37 - fix to prevent possible drive lock up during format.
=================================================================== IBM Online SAS/SATA Hard Disk Drive Update Program Version 1.14.03-2 Build ID: SAS11403-2
NOTE TO SERVICE - Reference RETAIN TIPS H211424 & H211667 ******************************************* IBM SAS Hard Disk Drive Update Program Version 1.14.03-2 Critical Release Reference RETAIN TIP H211424 & H211667
This package includes updates to drives with product ID strings of:
SAS 3.5"
Initial Code Releases - ST1000NM0023, ST2000NM0023, ST3000NM0023, ST4000NM0023 to BC5B - ST2000NM0043, ST4000NM0043 to EC59 - WD1001FYYG-23S, WD2001FYYG-23S, WD3001FYYG-23S, WD4001FYYG-23S to XA35
Other - ST1000NM0001, ST2000NM0001 to BC4A - support persistent reservation - HUS723020ALS64, HUS723030ALS64 to J3K8 - servo adjustments
SAS 2.5"
Initial Code Releases - ST300MM0006, ST600MM0006, ST900MM0006 to B56H - ST300MM0026, ST600MM0026, ST900MM0026 to E568 - TXA2D20200GA6I, TXA2D20400GA6I, TXA2D20800GA6I, TXA2D21600GA6I to GB76 - see Retain Tip H211424. - HUC101212CSS60 to J2M7 - HUC101212CSS61 to N2M7 - T1200MM0007 to B576 - T1200MM0017 to E574 - ST600MX0001 to BH13 - WD3002BKTG-23E, WD6002BKTG-23E, WD9002BKTG-23E to ZC31 - ST9500431SS to ED12 - ST9146703SS to E536 - ST973352SS to E625 - ST9300553SS to E636 - HUC109030CSS61E, HUC109060CSS61E, HUC109090CSS61E to N2EF - MK3001GRDB, MK6001GRDB, MK9001GRDB to SB35 - drive Que depth fix; see Retain Tip H211667. - HUC109030CSS60, HUC109060CSS60, HUC109090CSS60 to J2EF - HUC109030CSS61E, HUC109060CSS61E, HUC109090CSS61E to N2EF
Other - WD3001BKHG-23D, WD6001BKHG-23D, WD9001BKHG-23D to ZA32 - performance, non-critical fixes and robustness changes.
- ST9600204SS to B54A with maintainance fixes and performance improvements.
- MBD2147RC, MBD2300RC to SB1B - drive Que depth fix; - MBE2073RC, MBE2147RC to SC18 - drive Que depth fix; - MBF2300RC, MBF2600RC to SB2F - drive Que depth fix; - MK1401GRRB, MK3001GRRB to SC2E - drive Que depth fix; see Retain Tip H211667.
- ST9500620SS, ST91000620SS to BD2F - support persistent reservation and maintainance fixes.
SATA 3.5"
Initial Code Release - WD801ABYS-23C0A0, WD1601ABYS-23C0A0 to 06.06H05 - WD5003ABYX-23 to WC38 - added mfg. parameters. - WD2000FYYZ-23UL, WD3000FYYZ-23UL, WD4000FYYZ-23UL to WD36 - ST1000NM0033, ST2000NM0033, ST3000NM0033, ST4000NM0033 to BB58
Other
SATA 2.5"
Initial Code Release - SG9XCS2D50GEIBM to SE6H - WD3000BLHX-23V7BV to YA31 - SSDSC2BA200G3I, SSDSC2BA400G3I, SSDSC2BA800G3I to NA34 - SSDSC2BB120G4I, SSDSC2BB240G4I, SSDSC2BB400G4I, SSDSC2BB800G4I to NB34
Other - ST9250610NS, ST9500620NS, ST91000640NS to BE29 - maintainance updates. - MTFDDAK064MAR-1J1AA, MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA, MTFDDAK512MAR-1K1AA to MA57 - added mfg. parameters.
SATA 1.8"
Initial Code Release - SSDSC1NA200G3I, SSDSC1NA400G3I to NA34 - SSDSC1NB080G4I, SSDSC1NB240G4I, SSDSC1NB400G4I to NB34
Other - MTFDDAA064MAR-1J1AB, MTFDDAA128MAR-1J1AB, MTFDDAA256MAR-1K1AB, MTFDDAA512MAR-1K1AB to MA57 - added mfg. parameters.
=================================================================== Version 1.13.01 Build ID: SAS_113
NOTE TO SERVICE - Reference RETAIN H207993
******************************************* IBM SAS Hard Disk Drive Update Program Version 1.13.01 Critical Release Reference RETAIN H207993
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- HUS723020ALS64 to J3K7 Additions to VPD information used by manufacturing and fixes for overall robustness.
- HUS723030ALS64 to J3K7 Initial Code Release
- ST31000424SS, ST32000444SS to BC2D - ST1000NM0001, ST2000NM0001 to BC49 Fixes for overall robustness.
- ST33000650SS to BC3E Initial Code Release
SAS 2.5"
- MK1401GRRB, MK3001GRRB to SC29 Fixes for overall robustness.
- MBF2300RC, MBF2600RC to SB2C Initial Code Release.
- ST9300605SS, ST9600205SS, ST9900805SS to B55D ST9146853SS, ST9300653SS to B63B ST9500620SS, ST91000640SS to BD2E ST9300505SS, ST9600105SS, ST9900705SS to E557 ST9146753SS to E636 Additions to VPD information used by manufacturing and fixes for overall robustness.
SATA 3.5"
- ST500NM0011, ST2000NM0011, ST1000NM0011 to BB4A ST3500514NS, ST31000524NS, ST32000644NS to BB2C Reliability improvements, Additions to VPD information used by manufacturing
- ST33000650NS to BB3A Initial Code Release
- WD5003ABYX-23 to WC36, WD1003FBYX-23Y7B0 to WB35, WD2003FYYS-23W0B0 to WA35 Reliability improvements, Additions to VPD information used by manufacturing
- HUA723020ALA640 to MK7OA910 Additions to VPD information used by manufacturing.
- HUA723030ALA640 to MKAOA910 Initial Code Release
- HUA722050CLA330, HUA722010CLA330 to A3PH Initial Code Release
SATA 2.5"
- TE22D10100GE8IBM to SR3B Initial Code Release
- MTFDDAK064MAR-1J1AA, MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA, MTFDDAK512MAR-1K1AA to MA55 Initial Code Release
- ST9250610NS, ST9500620NS, ST91000640NS to BE28 Fixes for overall robustness.
SATA 1.8"
- MTFDDAA064MAR-1J1AB, MTFDDAA128MAR-1J1AB, MTFDDAA256MAR-1K1AB, MTFDDAA512MAR-1K1AB to MA55 Initial Code Release
- TX21B10100GE8IBM, TX21B10200GE8IBM, TX21B10400GE8IBM to SP3A Initial Code Release
Version 1.12.01 Critical Release Reference RETAIN #H207740
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
- TX21B10200GE1IBM, TX21B10400GE1IBM, TX21B10100GE8IBM to PRO6SP36 TE22D10100GE8IBM to PRO6SR36 Initial Code Release
- 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.
- 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
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
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 - ST9146803SS, ST9300603SS toB53B - 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) MBE2073RC, MBE2147RC to SC16 (Critical) 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 Initial Release
IBM SAS Hard Disk Drive Update Program 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)
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) 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.
- 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 release 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.
=============================================================== IBM SAS Hard Disk Drive Update Program Version 1.05
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
MBD2xxxRC to SB14 - Initial release
SAS 3.5"
ST3xxxxx6SS to BA49 ST3750630SS to BC1D - This code improves the robustness of write cache operations.
SATA 3.5"
WDC WD2502ABYSxxxxx tp 02.03B04 - Fixes incorrect VPD data
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. =================================================================
IBM SAS Hard Disk Drive Update Program Version 1.04
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 - Fixes an issue where a drive may prematurely report a PFA trip
GNAxxxxxx to BH0J - Fixes 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 tp 02.03B04 - Fixes incorrect VPD data
SATA 2.5"
WD3000xxxxx to 04.04V04 - Fixes 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 spinup of the drive may be overwritten rendering the drive inoperable on a subsequent warm or cold system reboot.
- Fixes a issue with an internal timer that may cause drive to go offline when used in a non-raid environment.
IBM SAS Hard Disk Drive Update Program Version 1.03
Added support for the following controllers:
IBM ServeRAID MR10il SAS Controller IBM ServeRAID MR10is SAS Controller IBM ServeRAID BR10i SAS Controller IBM ServeRAID BR10il SAS/SATA Controller IBM SAS/SATA RAID Kit IBM SAS Expansion Card (CFFv) for IBM BladeCenter IBM SAS Connectivity Card (CFFv) for IBM BladeCenter
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
ST3250621NS, ST3500631NS, ST3750641NS to 4AEV
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 =============================================================
IBM SAS Hard Disk Drive Update Program Version 1.02
Support of ServeRaid 8s Raid controller Support of ServeRaid 10i Raid controller Support of ServeRaid 10k Raid controller Support of ServeRaid 10m Raid controller Support of LSI 1078 SAS controller Support of SATA drives attached to SAS controllers
Support and updates to drives with product ID strings of:
VPAxxxxxx to A650 Change to improve performance in sequential write workloads Improvements to internal drive logging and media checking. Critical Fix: This code addresses a rare potential for data loss This code update should be applied to prevent the event from occurring.
ST340XXXAS and ST380XXXAS to 3.48 Fix to address Read Log Command abort error.
ST340XXXAS, ST380XXXAS and ST3160XXXAS to 3.05 Fix to address intermittent hard drive no-shows after system comes out of hibernation.
ST3500641NS to 3.AES Changes to the refresh rate of the DRAM used on the drive.
ST3500640NS to 3.AEJ Initial release.
HDTXX... & HDSXX... codes go to Masked ROM version. HDS725050KLA360 to AQ1A to also Fix an issue that occurs while running in NCQ mode with write cache disabled.
ST3xxxx4SS to BA26 Improves intialization times with some ServeRaid controllers Performance improvements under some sequential workloads.
ST3xxxx5SS to BA35 Improves intialization times with some ServeRaid controllers
ST9xxx51SS to B612 Intial release of firmware
ST9xxxx2SS to B526 Improves intialization times with some ServeRaid controllers
MAUxxxx and MAXxxxx Added support for new SAS features required by new SAS controllers.
IBM SAS Hard Disk Drive Update Program Version 1.01 Please refer to RETAIN tip H186019.
Support of ServeRaid 8e Raid controller Support of ServeRaid 8k Raid controller Support of ServeRaid 8l Raid controller Support of on-board LSI 1064 controller IBM MegaRaid 8480 Raid Controller
Firmware updates to drives with Product ID strings:
GNAxxxx and BBAxxxx to BH0G Picks up the latest network roll of firmware fixes to improve performance under some sequential workloads and improvements to signal quality parameters.
ST9xxxx to B51D amd ST3xxxx to BA18 Picks the latest network roll of firmware fixes to address unexpected system hangs and some performance improvements.
MAVxxxx to S116 and MAYxxxx to T107 Picks up the latest network roll of firmware fixes and to improve signal quality parameters.
MAXxxxx to T904 Initial release ============================================================
IBM SAS Hard Disk Drive Update Program Version 1.00 Initial Release
Support of Adaptec 48xxx based controllers Support of ServeRaid 8i Raid controller Support and updates to drives with product ID strings of: ST936701SS ST973401SS ST336754SS ST373454SS GNAxxxxx BBAXXXXX
ibm_fw_hdd_sas-1_14_04-1_linux_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
uEFI Flash Update Version 1.92 (BuildID VVE144C) Change History
Version 1.92 - BuildID: VVE144C ------------------------------------------------- Problem(s) Fixed: - Memory Latency issue. Incorporated Intel Microcode Update (MCU) MED 306E4_00000428 - Addressed a problem where the PCI Generation setting was missing in the UEFI setup menus for Mezz adapters. - Addressed a Unified Change Management (UCM) issue that was overwriting configuration changes made via 3rd party utilities - Updated UEFI to address these vulnerabilities: CVE-2014-3571, CVE-2014-3569, CVE-2014-3572, CVE-2014-8275, CVE-2014-3570 Enhancements: Limitations: - When flashing UEFI from version 1.30 or later to a version earlier than 1.30, a "Boot Configuration Error" message will be logged into the UEFI error log. This error does has no impact on the system configuration or operation. No errors are logged when flashing from an earlier version to version 1.30 or newer. Dependencies: - The IMM firmware must be at BUILDID: 1AOO58T Version: 4.31 (ibm_fw_imm2_1aoo58t-4.31_anyos_noarch) or higher prior to installing UEFI version 1.92. If the IMM level is lower, the UEFI update module will be rejected as invalid because of additional security features features implemented in this release.
Version 1.80 - BuildID: VVE142E ------------------------------------------------- Problem(s) Fixed: - Corrected an issue which might cause system get an NMI event with PCIe device installed on PCIe slot 5. Enhancements: Limitations: Dependencies:
Version 1.73 - BuildID: VVE142D ------------------------------------------------- Problem(s) Fixed: - Fixed an issue with continuous reboots when applied new LSI FW and the Remote Console setting is Enabled. Enhancements: Limitations: Dependencies:
Version 1.71 - BuildID: VVE142B ------------------------------------------------- Problem(s) Fixed: Enhancements: - Supported IBM eXFlash DDR3 Storage DIMM firmware version 1.4.7. Limitations: Dependencies:
Version 1.70 - BuildID: VVE142A ------------------------------------------------- Problem(s) Fixed: - Fixed the system boot failure due to low PCI memory-mapped resource for a VGA device - Incorporated Intel Microcode Update (MCU) MED 306E4_00000427 to address Intel Erratum Enhancements: - Enhanced memory SPD logging for Intel E5-2600 v2 processors - Enhanced error logging for memory-mirroring mode configurations - Support Memory Reference Code Release version 2.0.0.3 - Support AES enable/disable by ASU - Enhanced IBM boot manager - Enhanced TPM Physical Presence lock algorithm - Supported IBM eXFlash DDR3 Storage DIMM Limitations: - When flashing UEFI from version 1.30 or later to a version earlier than 1.30, a "Boot Configuration Error" message will be logged into the UEFI error log. This error does has no impact on the system configuration or operation. No errors are logged when flashing from an earlier version to version 1.30 or newer. Dependencies: - The IMM firmware must be at BUILDID: 1AOO58N Version: 4.30 (ibm_fw_imm2_1aoo58n-4.30_anyos_noarch) or higher prior to installing UEFI version 1.70. If the IMM level is lower, the UEFI update module will be rejected as invalid because of additional security features features implemented in this release.
Version 1.60 - BuildID: VVE136A ------------------------------------------------- Problem(s) Fixed: - Fix Can not boot up from IMM Remote Mount with USB key. - Fix CPU frequence lockdown when UEFI recalibrates the power levels during first cold boot - Fix that LR-DIMM 1333Mhz 1.35V memory speed is incorrect at Balanced mode
Enhancements: - Prevent the system unexpected shutdown with HCDIMM - Variable store self-healing
Limitations: Dependencies:
Version 1.51 - BuildID: VVE134T ------------------------------------------------- Problem(s) Fixed: - System doesn't boot to HII after Pressing 'C' with missing configuration.
Enhancements: - IVB Support. - Prevent the system unexpected power off with sensor planar voltage fault
Limitations: Dependencies:
Version 1.50 - BuildID: VVE134S ------------------------------------------------- Problem(s) Fixed: - Reboot to UEFI setup using ASU or Windows 2012 - Enable help string scroll when the help text cannot show all at current page. - Add notification and recovery option when UEFI detects GPT corruption during POST - Implement LAN Fail-Over function Enhancements: - IVB Support. Limitations: Dependencies:
Version 1.40 - BuildID: VVE128B ------------------------------------------------- Problem(s) Fixed: - IB Card show "Standby Power Enable/Disbale item" in uEFI setup menu - Can Not enter F1 setup menu after POST failure occur. - Correct the PCIE link control of Active-state power Management(ASPM) setting to result the PCI/NMI problem
Enhancements: - Multiple PCIe adapter BARs - Configurable MMIO base - Support Firmware first feature - Add informational messages when existing UEFI F1 setup menu - Add OEM SPD feature Limitations: Dependencies:
Version 1.30 - BuildID: VVE124A ------------------------------------------------- Problem(s) Fixed: - iSCSI Out of Band Configuration Fails. - Failed to change the value of some memory settings with ASU(ASUT78C). - MBE WHEA-log can't match ECC Uncorrectable event. - System administrator password is set but system still can get fully access right in F1 uEFI without asking password if press and then press . - Update uEFI README file. - IMM lost connection with shared NIC on Intel mezz card. - Onboard NIC 4 doesn't work when boot Linux OS with paramet. - System hang after memory multibit error occurred and then system reboot. - System could be hang if Intel Network adapter is installed (Dallas). - TPM setting would not be applied in ESC+SAVE issue . - The Pre-Boot value cannot set MUX switch to BMC by uEFI SETUP menu. - Kingston manufactory ID will shown as "Unknown" in SMBIOS type 17. - Fixed TCG TPM Integration manual test failed in Windows 2012. - System hang at IBM LOGO with Broadcom Dual Runner card. - Cause [W.3938002]Boot Config Error. - Disable CPU C-State and Phase Shedding to prevent Voltage Regulator EOS issue. - UEFI setting on F1 menu doesn't sync with ASU setting when boot mode=legacy only.
Enhancements: - SMBIOS type17s support 2133 data rate for dimm maximum speed. - Remove some unuseful code due to IMM changed flow when uefi primary bank integrity check failure. - Enabled DCA item in processors menu of uEFI SETUP. - Improve clock timing for Netlist 16GB HCDIMM. - Add a workaround to patch an yellow mark(AHCI) shown on Windows 2012. - Improve FoD (Feature On Demand) by Transition Table update . - Improve thermal limitation in SSD adapter (LSI High IOP, QLogic ). - Improve behavior of PCI-X error handling.
Limitations: Dependencies:
Version 1.20 - BuildID: VVE120C ------------------------------------------------- Problem(s) Fixed: - Invalid slot usage state showed on RENAI Riser card. - Incorrect slot error event on JOJO Riser. - Fail to return to Boot menu if boot fail. - Further updates to the fatal error handler to report QPI errors during runtime. - iSCSI Attempt will disapper when system reboot several times. - F6 function key is malfunction. - Remove unnecessary information from ReadMe file. - Fails to report logging limit errors on spared DIMM. - FAN speed is pull up if TXT enabled in uEFI. - Fail on Windows 2012 TPM WHQL validation.
Enhancements: - Improve 2DPC@1333MHz detection algorithm. - Improve CPU detect algorithm. - Support 4GB PCI inventory access. - Support UDIMM 2DPC@1333MHz run on 1.35V by automatic. - Remove unnecessary warm reset to improve uEFI boot time.
Limitations: Dependencies:
Version 1.11 - BuildID: VVE116C ------------------------------------------------- Problem(s) Fixed: - Fail to install VMWare 5.0 if Intel TXT function is enabled.
Enhancements: Limitations: Dependencies:
Version 1.10 - BuildID: VVE116A ------------------------------------------------- Problem(s) Fixed: - Fixed issue to allow PXE/iSCSI to be configured out-of-band - Processor speed is incorrect when system is idle w/ E5-2637 M1. - Serial Console Redirection function can not work if SP Redirection is Disabled. - No Screen output by Serial Over Lan connection. - Fix Intel E5-2637 speed is incorrect. - DIMM slot 13-24 can NOT indicate which memory was falut. - Fix SMBios Type 4 External Clock information incorrect. - Fixed issue that caused the ASU tool to occasionally fail to update the Processors.CoresinCPUPackage value
Enhancements: - Improve PCIe error reporting. - Improve Fatal Error Handle. - Improve Legacy PXE function. - Remove Intel 130W CPU limitation. - Improve PCIe error reporting. - Support Heping riser card - Improve ME Update mechanism - Improve ACPI: C-States - Added support for using Features On Demand with Optimized Boot enabled - Updated thermal threshold values for DIMMs - Reduce boot time (reduce unnessary reset in POST).
IBM 7383 (IBM system x 3500 M4) uEFI Flash Update Version 1.82 (BuildID Y5E142CUS) Change History
Version 1.82 - BuildID: Y5E142C ------------------------------------------------- Problem(s) Fixed: - Memory Latency issue. Incorporated Intel Microcode Update (MCU) MED 306E4_00000428. - Addressed a Unified Change Management (UCM) issue that was overwriting configuration changes made via 3rd party utilities - Updated UEFI to address these vulnerabilities: CVE-2014-3571, CVE-2014-3569, CVE-2014-3572, CVE-2014-8275, CVE-2014-3570 Enhancements: Limitations: - When flashing UEFI from version 1.30 or later to a version earlier than 1.30, a "Boot Configuration Error" message will be logged into the UEFI error log. This error does has no impact on the system configuration or operation. No errors are logged when flashing from an earlier version to version 1.30 or newer. Dependencies: - The IMM firmware must be at BUILDID: 1AOO56v Version: 3.86 (ibm_fw_imm2_1aoo56v-3.86_anyos_noarch) or higher prior to installing UEFI version 1.70. If the IMM level is lower, the UEFI update module will be rejected as invalid because of additional security features features implemented in this release.
Version 1.70 - BuildID: Y5E140A ------------------------------------------------- Problem(s) Fixed: - Incorporated Intel Microcode Update (MCU) MED 306E4_00000427 to address Intel Erratum Enhancements: - Enhanced memory SPD logging for Intel E5-2600 v2 processors - Enhanced error logging for memory-mirroring mode configurations - Support Memory Reference Code Release version 2.0.0.3 - Support AES enable/disable by ASU - Enhanced IBM boot manager - Enhanced TPM Physical Presence lock algorithm Limitations: - When flashing UEFI from version 1.30 or later to a version earlier than 1.30, a "Boot Configuration Error" message will be logged into the UEFI error log. This error does has no impact on the system configuration or operation. No errors are logged when flashing from an earlier version to version 1.30 or newer. Dependencies: - The IMM firmware must be at BUILDID: 1AOO56v Version: 3.86 (ibm_fw_imm2_1aoo56v-3.86_anyos_noarch) or higher prior to installing UEFI version 1.70. If the IMM level is lower, the UEFI update module will be rejected as invalid because of additional security features features implemented in this release.
Version 1.60 - BuildID: Y5E136A ------------------------------------------------- Problem(s) Fixed: 1. Can not boot up from IMM Remote Mount with USB key. 2. Fixed the Incorrect Uniphy Recipe programmed for S-step IVX Enhancements: 1. Variable store self-healing. Limitations: 1. When flashing UEFI from version 1.30 or later than 1.20 to version earlier than 1.20, a "Boot Configuration Error" message will be logged into the UEFI error log. This error does has no impact on the system configuration or operation. No errors are logged when flashing from an earlier version to version 1.30 or newer. Dependencies: 1. The IMM firmware must be at BUILDID: 1AOO50D Version: 3.65 (ibm_fw_imm2_1aoo50d-3.65_anyos_noarch) or higher prior to installing UEFI version 1.60. If the IMM level is lower, the UEFI update module will be rejected as invalid because of additional security features implemented in this release.
Version 1.51 - BuildID: Y5E134G ------------------------------------------------- Problem(s) Fixed: - Fixed system unexpected power off with sensor planar voltage fault - Fixed Performance drop issue
Enhancements: - The 2DPC@1866 especially for 16G DIMM formal code Limitations: Dependencies:
Version 1.50 - BuildID: Y5E134F ------------------------------------------------- Problem(s) Fixed: - Corrected IPv6 reboot problems - Corrected 64bit resouce allocation problems - Fix CPU frequence lockdown when UEFI recalibrates the power levels during first cold boot Enhancements: - Add support for Intel Xeon processor E5-2600 v2 product family - Add notification when UEFI detects GPT corruption during POST - Add support to configure the "Next Boot to F1 setup" function out of band - Add long text support in F1 setup help string Limitations: Dependencies:
Version 1.40 - BuildID: Y5E128D ------------------------------------------------- Problem(s) Fixed: - Incorporated Microcode Update (MCU) M6D206D7_00000710 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. Enhancements: Limitations: Dependencies:
Version 1.40 - BuildID: Y5E128B ------------------------------------------------- Problem(s) Fixed:
- Fixed that can not enter F1 setup menu after 3x POST failure occurred. - Correct the PCIE link control of Active-State Power Management(ASPM) setting to result the PCI/NMI problem - Fix that UA-101 audio device hang at legacy mode Enhancements: - Multiple PCIe adapter BARs - Configurable MMIO base - Support Firmware first feature - Add informational messages when existing UEFI F1 setup menu - Add OEM SPD feature - Improved handling of memory in high stress application/usage Limitations: Dependencies:
Version 1.30 - BuildID: Y5E124B ------------------------------------------------- Problem(s) Fixed: - UEFI option 43 fails to work - Disable phase shedding and Default to disable CPU C-states - ITP can't trigger CPU2 IERR - MBE WHEA-log can't match ECC Uncorrectable event Enhancements: - Change UDIMM 2DPC@1333Mhz 1.35V algorithm to meet performance specification requirement - Support ROM Recovery feature (Auto Promotion under Backup Bank Management Method) Limitations: Dependencies:
Version 1.20 - BuildID: Y5E120D ------------------------------------------------- Problem(s) Fixed: - Sevaral uEFI OS boot failed with F12 boot menu HDD0. - Console Switch 1754A2X with KB & Mouse are not responding in EFI Web BIOS - Fail to return to Boot menu if boot fail. - IMM menu location is changed. - F6 function key is malfunction. - FAN speed is pull up if TXT enabled in uEFI. Enhancements: - Support the Trusted Computing Group's Memory Overwrite Request function. - Improve fatal error handler to report QPI errors during runtime. - Support FastSetup feature - Enable DRAM phase shedding - Support 4GB PCI inventory access. - Support UDIMM 2DPC@1333MHz run on 1.35V by automatic. - Improve messages while booting up. - Enable Phase Shedding to improve memory performance. - Improve PCIe Slot# for WidgetGetDeviceLocation procedure - Remove unnecessary warm reset to improve uEFI boot time.
Limitations: Dependencies:
Version 1.10 - BuildID: Y5E116A ------------------------------------------------- Problem(s) Fixed: - Fixed E5-2690 cannot run frequency at 2.9GHz(only 2.8GHz) when turn off Turbo mode. - Fixed fnstruction for TPM enablement has type error. - Fixed CPU can not enter deep C status with uEFI 11I under RHEL5.7 64 - Fixed failed to boot from CDDVD ROM with uEFI OS - Fixed iSCSI ISID mismatch under uEFI BIOS Settings. - Fixed TCG TPM Integration Test (Manual) random failed under WIN2K8 R2 SP1 with uEFI_11L - Fixed QPI link speed and Turbo mode show incorrect with M1 stepping CPU. - Fixed the format of System Event Log is uncorrected - Fixed Legacy Thunk Support is malfunctional - Fixed DIMM slot 13-24 can NOT indicate which memory was falut when trigger MBE on Mirror mode by bugged DIMM - Fixed ASUT74H can't find any iscsi item - Fixed Fail to set some of PXE items with ASU76h - Fixed Can not boot into WinPE in RAID HDD on Crossfield - Fixed Personality can not be switched in OCM tool no matter FOD is imported - Fixed fail to set some of PXE items with ASU76h - Fixed Processor speed is incorrect when system is idle - Fixed VLAN ID can be configured to ID 0 - Fixed Processor speed is incorrect when system is idle w/ E5-2637 M1 - Fixed Console redirection can not work normally with com2com. - Fixed No screen output with SOL connection Enhancements: - Added Legacy Thunk support setup item - Change Operating Mode from Custom Mode to Efficiency - Favor Performance - Added DriverCodeDisplay error code on screen function - Improve PCIe error reporting. - Improve Fatal Error Handle. - Improve Legacy PXE function. - Remove Intel 130W CPU limitation. - Improve PCIe error reporting. - Support Heping riser card - Improve ME Update mechanism - Improve ACPI: C-States - Added support for using Features On Demand with Optimized Boot enabled - Updated thermal threshold values for DIMMs - Reduce boot time (reduce unnessary reset in POST). Limitations: Dependencies:
**************************************************************** | | | Tape LTO firmware update | | | | | | (C) Copyright International Business Machines Corporation | | 2000-2012 . 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: 1/29/2013 | | | ****************************************************************
Change History
ver 1.7 To update the LTO 3 v2 firmware to C7RD To update the LTO 4 v1 firmware to C7Q5 To update the LTO 4 v2 firmware to C7RD To update the LTO 5 v1/v2 firmware to C7RD
ver 1.6_01 To update the initilialization file for reflash tool and the new version of LTO Gen 4 v1 firmware into BBH5.
ver 1.6_00 updated firmware for LTO42 to BBNF updated firmware for LTO32 to BBNF ver 1.5_00 updated firmware for LTO 3 to BBNF updated firmware for LTO 4 to BBNF updated firmware for LTO 5 to BBNM
ver 1.4_04
updated firmware for LTO 5 to BBNB
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_7_linux_32-64_chg
QLogic 10 GbE Converged Network Adapter MultiFlash Update for System x IBM P3P Firmware Change History QLogic Corporation. All rights reserved.
Package Version 2.20.22
Release Version: 2.20.22
Table of Contents 1. Version 2. Changes 3. Limitations 4. Known Issues 5. Additional Information 6. Trademarks 7. Notices 8. Contacting Support
1. Version
The files contained in this Flash image package are zipped into a file that will expand to provide the following versions for the 3200/8200 Series Adapters.
* Flash Image Version 2.20.22
P3P22022.BIN contains: ---------------------- * NIC PXE (3200/8200 Series) PXE 3.0 version 2.0.2.37 PXE EFi version 2.6.19 signed * FCoE BIOS (8200 Series only) BIOS 3.0 version 3.27 uEFI version 6.09 Signed * iSCSI BIOS (8200 Series only) BIOS 3.0 version 2.19 uEFI version 2.04.12 signed * Firmware - v4.16.151 * Pegtune - v4.16.32 * Bootloader - v4.16.05 * CRBinit - v4.12.07
Hardware Support Standard Servers with PCIe 1.1 and 2.0 x8
3. Limitations
None
Industry Standards Compliance N/A
4. Known Issues
5. Additional Information None
6. Trademarks Accelera, Accelerating Cluster Performance, InfiniCon Systems, InfiniNIC, InfiniPath, InfiniView, QLA, QLogic, the QLogic logo, ReadyPath, SANdoctor, SANsurfer, and SilverStorm are registered 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 Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached at:
Gary Stift gary.stift@qlogic.com
(c) Copyright 2014. 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_sysx-2_20_22_linux_32-64_chg
=================================================== Change History =================================================== Document Name: Change History Document Status: IBM General Avalibility Document Version: 3.2.5.5 Latest Driver Version: 3.2.5.5 Document Updated: 04/20/2015 Product: QLogic BR Series FC/NIC/CNA
Please visit www.qlogic.com for full documentation, additional drivers, and management applications.
Version 3.2.5.5 Fixes and Enhancements: - Boot FW, UEFI, HCM related fixes - MCP work around
Version 3.2.5.0 New Features and Feature Enhancement: - Support for RHEL5.11, RHEL6.6 and RHEL7.0
Version 3.2.4.0 New Features and Feature Enhancement: - Support for RHEL5.10 and RHEL6.5
Version 3.2.3.0 New Features and Feature Enhancement: - Support for patching firmware via boot image - Support for Linux PTP - Support for UEFI Health Check Protocol - Support for SLES11SP3
Version 3.2.1.0 New Features and Feature Enhancement: - Support for "IBM Flex System FC5024D 4-port 16Gb FC Adapter" PART_NUMBER "95Y2381" - Support for RHEL5.9 and RHEL6.4
Fixes and Enhancements: - Enhanced Linux driver data path to properly handle IPv6 packets. - Enhanced Linux driver to make sure user configured path tov value is persistent and is not changed due to change in dev_loss_tmo.
Version 3.2.0.0 Release for FC/NIC/CNA
New Features and Feature Enhancement: - Updated code for Brocade 1867 IBM Flex System FC5022 FC Adapter for x22 - 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_5_5_linux_32-64_chg
Firmware Version: 2.82x6 (w/ 5.12a13 Universal Boot Code) (Supported for IBM System x & BladeCenter)
Problems Fixed: - Emulex FC Adapter does not auto-enable SAN boot mode when boot target configuration is made via IFM (BOFM) - Emulex FC configuration utility is in the wrong F1 setup screen
- Multiple adapters connected to same PCIe bridge port can request more I/O space than system can allocate. - Updated firmware kernel code so Saturn based HBA and mezz cards do not use or advertize need for system I/O Space.
**************************************************************** | | | | | 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: 1/28/2013 | | | ****************************************************************
CONTENTS:
Change History
ver 1.6
To release FW v0195. The change from v0185 is to refine the code and no function change for system x.
ver 1.5
Update to fix the failure in FW updating with cartridge inserted in the drive (from v0145 up to v0185). The way to make drive FW update in the VMware environments is added in the readme.
ver 1.4
Initial release of the Tandberg Data RDX USB 3 backup drives. This FW update cover the drives of the IBM P/N 362532Y, 362550Y, 36251TY, 00D2786,00D2787 and 00D2788.
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
ver 1.0
This firmware will change the firmware of your RD drive to the latest available, unless it is already at the latest level.
This is the initial release of the RD package file, so there are no changes to describe. ibm_fw_tape_rd-1_6_linux_32-64_chg
ServeRAID M5100 Series SAS/SATA Controller Firmware Update for Linux
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)
NOTE TO SERVICE - Reference RETAIN #N/A
Version 23.33.0-0018 - High Impact/High Probability of Occurrence ----------- Fixes: - Incorporated MegaRAID FW stack 5.13 - Fixed an issue where drive temperature cannot be displayed for a drive in Failed or Foreign state (SCGCQ00693959) - Fixed an issue where after creating an LD via StorCLI or MSM the firmware writes into saved power condition mode page (0x1a) of all PDs in the LD and enables their idle timers (SCGCQ00658701) - Fixed an issue where Patrol Read would sporadically correct the same defective LBA repeatedly (SCGCQ00729591) - Fixed an issue where importing a Foreign array onto a new controller may fail with "Cannot force emulate VD to 512E since enable512Esupport is false" error in firmware log (SCGCQ00721106) - Fixed an issue where the controller may enter MegaMon sporadically (SCGCQ00776409) - Fixed an issue where MSM may not report a Full Initialization Aborted error until system rebooted (SCGCQ00759100) - Fixed an issue where the firmware may allow the OS to change VD cache settings (SCGCQ00842350) - Fixed an issue where Link Speed may show UNKNOWN when attaching a 3G or 6G SATA drive (SCGCQ00803522) - Fixed an issue where StorLib may return 0x00ff (fail) code even though operation succeeds when creating a VD out of an existing drive group (SCGCQ00827685) - Fixed an issue where format process of SSD may take much longer than in previous firmware (SCGCQ00674388) - Fixed an issue where controller must have cleared config to enable 240VD unless existing config only included single-drive RAID0 VDs (SCGCQ00559643) - Fixed an issue where some commands would timeout with CDB=ff ff ff ff (SCGCQ00459760) - Fixed an issue where slot ordering in iMR mode might differ from slot numbering in MR mode (SCGCQ00559274) - Blocked CacheCade deletion when multiple CacheCade volumes are associated with Virtual Drives, preventing data issues (SCGCQ00830977) (RETAIN TIP H214323)
Features/enhancements: - Added support for 512e drives (SCGCQ00425363) Enhanced Event Log to include CVPM health details after every Learn Cycle to allow closer monitoring of CVPM health (SCGCQ00819877) - Implemented a retry for reads of CVPM data to avoid erroneous event 386 or 150 in the Event Log (SCGCQ00392439) - Added ability for firmware to report the temperature for all SAS/SATA HDD/SSD (SCGCQ00490819) - Implemented ability for firmware to read drive temperature immediately following SAS discovery (SCGCQ00602573) - Added ability to clear the MaintainPdFailHistory (SCGCQ00474559)
Version 23.29.0-0015 - Critical ------------------- Enhancement - Provide mechanism to disable PCIe backchannel training via SBR. Fixes: - Fixed an issue where the ‘cli set securitykey=Lsi@12345’ command fails with error code 1001 and error message invalid key. - Fixed an issue where foreign configuration import could fail. - Fixed an issue where storcli.exe /c0 show all command repeatedly prints to termlog with respect to upgradekey presence. - Fixed an issue where boot message ‘cached data was lost,’ even when there was no battery present. - Fixed an issue where the order of the first 64 VDs in the POST is not the same sequence as returned from the firmware. - Fixed storCLI adpfwflash option crash and adpallinfo option failure. - Reduced the bootblock Init time, which effectively reduces the configuration retry time to approximately 700 mS.
Version 23.22.0-0024 - Non-Critical ------------------- Enhancement(s): - Display the Native Command Queuing (NCQ) enabled/disabled status of every SATA disk drive in the output of StorCLI and MegaCLI. - Added support for ServeRAID M5100 Series 2GB Flash/RAID 5. Fix(es): - Disable PI CRC checking when the drive is not initialized during a CC. - Increased the SuperCap learn time out value for 2GB TMM-B solution. - Fixed an issue for 2GB memory modules where SuperCap does not get connected to the controller and hence cache offload fails. - Fixed an issue where cache policy of virtual drives(VD) does not change to write through(WT) mode even after detecting a bad supercap. - Fixed an issue where a RAID configuration created with physical disks in powersave mode could be lost after rebooting the system. - Fixed an issue where an invalid frame sent during a PIO-mode SATA passthrough command results in resetting the drive. - Fixed an issue where the system is not allocating memory correctly when MR and iMR controllers are in the same system. - Fixed an issue where deep learn does not start immediately when the relative state of charge (RSOC) is just equal to 95%. - Fixed an issue where performing a re-key operation in external key management (EKM) mode without doing a reboot, and then switching to local key management Mode(LKM) results in the Firmware logs showing that a drive security key was created but HII says the key is incorrect. - Fixed an issue where on a local key management (LKM) enabled controller, the user is asked to enter the security key to unlock and import a foreign drive, which is locked and has external key management (EKM) enabled.
Version 23.16.0-0027 - Critical ------------------- Fix(es): - Addressed data exposure issue when using CacheCade - Fixed issue where Supercap shows 0 Capacitance - Fixed iBBU09 battery issue that caused a VD cache policy to remain in write-through mode after a manual relearn - Fixed iBBU09 battery issue that caused a VD cache policy to periodically toggle between write-back/write-through mode - The limits for iBBU09 battery charging were not updating properly in a learn cycle - Ensures a single supercap pack is not supported on 2GB memory module. - Resolves a firmware crash seen while doing continuous sas cable pulls. - Ensures OpROM loads even if segment address is 0xC0000. - Fixed an issue where the adapter is running iMR machine checking after requesting host memory. - Fixed an issue where HII does not allow the user to make use of the remaining free capacity to configure additional VD for R50/R10. - Fixed an issue where an HII: empty warning prompt is given when creating a CacheCade VD with forced writeback option. - Fixed and issue where Windows cannot install without a VGA device on board. - Fixed and issue in EFI WebBIOS were consistency check is still shown in progress after 1 PD is removed from a R1 array.
Version 23.16.0-0018 - Suggested ------------------- Fix(es): - Fixed an issue where the adapter is running iMR machine checking after requesting host memory. - Fixed an issue where HII does not allow the user to make use of the remaining free capacity to configure additional VD for R50/R10. - Fixed an issue where an HII: empty warning prompt is given when creating a CacheCade VD with forced writeback option. - Fixed and issue where Windows cannot install without a VGA device on board. - Fixed and issue in EFI WebBIOS were consistency check is still shown in progress after 1 PD is removed from a R1 array.
Version 23.12.0-0016 - Suggested ------------------- Fix(es): - Added isync to prevent speculative execution while memory is being allocated. - Delayed enablement of POM until AFTER valid memory range is provided by host system.
Version 23.12.0-0011 - Suggested ------------------- Enhancement(s): - Support for 512e and 4k SAS/SATA hard drives added - Implemented Limited Band Charging for iBBU09 (RETAIN tip H21631) - Changed BIOS check to determine if running in HAMR, in order to ensure nothing gets broken when user has an iButton which is not programmed. - Changed controller status for safe mode to show controller status as safe mode and disable debug message logging in serial port.
Fix(es): - Addressed an issue where deeply discharged Cache Vault Power Modules would be prematurely be marked as failed. - Fixed an issue where HII hangs when trying to enter configuration management while in safe mode. Changed the safe mode warning message as below: "Controller is running in safe mode. Safe mode is used for diagnostic purposes only. Limited operations such as Configuration Preview, Clear Configuration and View/Change Controller Properties are allowed in this mode. Other operations such as Create Configuration, Import and Clear Foreign Configurations are not allowed. To exit safe mode, correct the fault, and reboot your computer." - Fixed an issue where having more than three adapters results in a calculation error for the offset to store physical disk info for fourth adapter, due to BIOS not clearing upper byte of AX (that is AH which is containing some non zero value). - Fixed an issue where the Wrong spanned drive group size is displayed by WebBIOS (Ctrl-H).
Version 23.7.1-0010 - Suggested ------------------- Fixes: - Fix an issue related to the where the TSOC (EEPROM) is not able to read or write from the firmware which will result in the message "Incompatible secondary iButton present." - Fix a HII broswer issue where Cachecade virtual drive can be selected as a boot device. - Fix a HII broswer issue where the user is unable to clear the controller configuration when there are no drives attached. - Fix an issue where the BIOS doesn't display the RAID level and VD size correctly at BIOS POST.
Version 23.7.1-0009 - Suggested ------------------- Fixes: - Fixed an issue where SoH is bad after a learn cycle but iBBUI shows good status. - Fixed an issue where hi-temp warning was not being displayed.
Version 23.7.0-0037 - Suggested ------------------- Fixes: - Corrected differential signals for Phys 2 and 3 that caused slot numbers in simple swap configurations to be incorrect. - Fixed an issue when 'maintain PD failed history' is enabled, and a cable is removed while a drive is added, the drives state goes to optimal instead of foreign unconfigured bad. - Fixed a problem where a capacity change is reported after a rebuild completes on a Cache Cade volume. - Fixed a controller firmware hang when the recovery of a medium error takes to long. - Fixed an issue where the SATA BBM (Bad Block Manager) list was being corrupted. - Fixed an issue where FoD (Feature on Demand) Options were being lost because of errors while accessing the TSOC. - Fixed a problem where the controller firmware would crash and drives would go offline when a bad block entry was created during a check consistency operation. - Fixed a problem where drives were being marked unconfigured bad (foreign) on reboot. - Fixed problem where a member of a CacheCade volume did not get marked as foreign when the drive was pulled with 'maintain PD failed history' enabled. - Fixed a problem where during a rebuild, a former hot spare that was now in a state of unconfigured good, moved back to the state hot spare, which then automatically started a copyback operation, causing the rebuild to restart. - Fixed a problem where a controller fault occurred during a reboot while a physical device was in progress of a PD Erase.
Version 23.7.0-0029 - Suggested ------------------- Enhancements: - Added support for Cache Cade 2.1 - Added Support for PI Drives
Fixes: - Fixed an issue where the firmware reports device initialization completion status to be greater than 100% at startup. - Fix an issue where when a secure foreign drive was present, VD creation fails because firmware becomes unresponsive - Added a check for the presence of PD before writing the data arms of a protected LD during BGI. - Fixed Firmware asserts in CacheMemAllocForPrebootApps() when memory was allocated twice by BIOS. - Fixed an issue with USB Cacheoffload restore fails after multiple power cycles onServeRAID M51xx controllers. - Fixed an issue where querying SMART / PFA Status returns "all zeros" in Sense Data. - Fixed an issue where the import of a config from MR to iMR resulted in a firmware crash. - Fixed an issue where iMR firmware crashed while creating 8/16/32 KB stripe size Lds. - Fixed background initialization watermark conversion to PD LBA. - Fixed write protected R1E data arms during initialization. - Fixed an issue where MR firmware crashed while discarding pinned cache. - Fixed an issue where a dirty LD dependency information of SSD pd has stale entries. - Corrected an issue during system booting from pinned cache, firmware goes to loop message BootMsgDcmd - Fixed an issue where a BGI was aborted and restarted, elapsed time was not reset. - Fixed an issue where the start ref for a shared cache line was not an indicator of the offset into the stripe. - Fixed an issue where the firmware hangs while running CC on a rebuilt R1 VD with SBBM. - Fixed an issue where the firmware was wrongly adding puncture entries. - Fixed an issue where rebuild was ran twice on a target drive with 100% full SBBM table. - Fixed an issue where the firmware was generating powersave change event when DS3 was not enabled, due to this application are not parsing the event. - Fixed an issue where recon from R0 to R1 using 3 TB drive causes firmware to report excessive unexpected sense events. - Fixed an issue, in which the bbuMode would revert to the factory default value of 5, when automatic learn cycle was enabled. - Fixed an issue where cache offload firmware reports unnecessary High Temp Event due to incorrect temp value. - Fixed an issue in which a Patrol Read may not start under certain conditions. - Fixed an issue where the firmware hits montask after discarding the cache when a snapshot VD was involved. - Fixed an issue where the firmware hangs during pin cache destage as dirty lines in that map never become zero. - Fixed an issue where CC fails to correct media error at 2TB location on 2 3TB SATA drives that support WU. - Fixed an issue where a new XML file was added to the nvdata, the buffer to hold the uncompressed nvdata overflowed. - Fixed an issue where an imported drive becomes unconfigured good when secure VD erase was running. - Fixed an issue where CC stops progressing on a R6 VD with media errors. - Fixed an issue where 3TB Hitachi HDD failed in immunity test (Electrostatic Noise test). - Fixed an issue where controller features are lost if RAID Key was not detected. - Fixed an issue where performance degraded in RAID 5 Sequential Writes due to command Out-of Ordering. - Fixed an issue where "Native configuration is no longer supported" message in post. - Fixed an issue where (DDR3) Initialization fails with fault 0x91a1 - initial DFIRL selected too low. - Fixed an issue where subsequent drives are dropped when all drives in the stagger spin up drives fails on boot sequence.
Version 23.2.1-0043 - Suggested ------------------- Fixes: - Fixed an issue where "Potential non-optimal configuration due to drive PD commissioned as emergency spare" alarm would trigger erroneously. - Fixed an issue where Copyback does not progress upon inserting drives. - Fixed an issue When allowMixInLD is Disabled, and causes Copyback Fails after Rebuild to Emergency Hot Spare. - Fixed an issue where the Firmware faults while flashing. - Fixed an issure where querying SMART / PFA Status to Return all zeros in Sense Data. - Fixed an issue where the Re-inserted Drives becomes Unconfigured_good causing auto rebuilds to fail to start.
Version 23.2.1-0033 ------------------- - Initial release ibm_fw_sraidmr_5100-23_33_0-0018_linux_32-64_chg
BIOS and Firmware Update for ServeRAID M5200 Series SAS/SATA Controllers
Adapters Supported: ServeRAID M5225-2GB SAS/SATA Controller ServeRAID M5210e SAS/SATA Controller for IBM System x ServeRAID M5210 SAS/SATA Controller
NOTE TO SERVICE - Reference RETAIN #N/A
Version 24.7.0-0052 - High Impact/High Probability of Occurrence ------------------- Fixes: Incorporated MegaRAID FW stack 6.6 Fixed an issue where a drive reporting itself as 0MB shows up as Unconfigured Good (SCGCQ00784319) Fixed an issue where the firmware might hang during error handling of sense code 0b/47/xx (SCGCQ00701744) Fixed an issue where some SSDs may cause the system to hang at POST (SCGCQ00595506) Fixed an issue where an iMR RAID config may fail to import to 12gbps MR (SCGCQ00833765) Fixed an issue where R0, R5 and R6 read bandwidth dropped abruptly at 256K block size with 24drive SATA SSD config (SCGCQ00609808) Fixed an issue where RAID10 performance is under-performing (SCGCQ00794773) Fixed an issue where in some cases the LSI chip would convert an incoming chip reset to a system reset (SCGCQ00664261) Fixed an issue where many pRdm/pRequest/pReply messages would appear in LSI firmware log (SCGCQ00752195) Fixed an issue where when a consistency check is aborted, the adapter may reset (SCGCQ00819811) Fixed an issue where Patrol read does not start and gives incorrect warning message (SCGCQ00728404) Fixed an issue where the controller may reset unexpectedly during error handling (SCGCQ00825126) Fixed an issue where StorCLI may report Enclosure Not Found (SCGCQ00843146) Fixed an issue where x880 nodes may report excessive 'SCL STUCK Low! While I2C Rx Receiving Data' in LSI firmware log (SCGCQ00728935) (Retain TIP H213891) Fixed an issue where the command timeout for FED (SED) drives is too short, resulting in 05/2C codes (SCGCQ00797355) Fixed an issue where bandwidth falls as queue depth increases on R5/R6 24/40 drive SAS HDD configs at 256k block size (SCGCQ00701768) Fixed an issue where some drives may get bad PI CRC even though data is correct resulting in drive failure (SCGCQ00819314) Fixed an issue where the firmware may exposed more than 240VDs to host even if host driver doesn't support that many (SCGCQ00829214) Fixed an issue where MSM may display an error message if 'Schedule Consistency Check' is selected (SCGCQ00832908) Blocked CacheCade deletion when multiple CacheCade volumes are associated with Virtual Drives, preventing data issues (SCGCQ00838953) (Retain TIP H214323) Fixed an issue where the MegaRAID POST may display "The native configuration is not supported by current firmware" (SCGCQ00812842) Fixed an issue where the EFI Driver Health Protocol will show Fail when more than 64VDs are configured (SCGCQ00830918) Fixed an issue where OS may BSOD when upgrading firmware on a controller the OS has booted from if Online Controller Reset is performed (SCGCQ00825725) Fixed an issue where controller wouldn't go to halt state after multibit ECC errors detected (SCGCQ00783186) Fixed an issue where Opal-compliant FDE (SED) drives were being marked as FDE/SED when they shouldn't be (SCGCQ00788250) Fixed an issue where correctable ECC error interrupts were being masked (SCGCQ00814997) Fixed an issue where reconstructed VDs were not being reflected in MSM until system reboot (SCGCQ00839018) Fixed an issue where controller commands may fail when an LD is deleted during reconstruction (SCGCQ00821693) Fixed an issue where firmware would go to MonTask when making VDs offline while a Rebuild is occurring under IO (SCGCQ00825775) Fixed an issue where commands to FDE (SED) drives may not respond within 500ms (SCGCQ00844445) Fixed an issue where the firmware may allow the OS to change VD cache settings (SCGCQ00844447) Fixed an issue where HDD/SSD microcode updates may report fail even though they succeeded (SCGCQ00553252) Fixed an issue where slot numbers may be wrong systems with 32 drive slots (SCGCQ00529592)
Features and Enhancements Improved Jetstress / Exchange latencies (SCGCQ00717161) Added support for Learn Cycle debug commands in firmware (SCGCQ00814991) Added ability to clear the MaintainPdFailHistory (SCGCQ00474559) Improved drive rebuild performance (SCGCQ00427581) Improved Cache Offload error handling on read from the flash interface (SCGCQ00524419) Improved average latency and max latency in Windows operating systems (SCGCQ00671670) Implemented power throttling (SCGCQ00457280) Improved load balancing on >2 drive R1 VD of SSDs (SCGCQ00593588) Added ability for firmware to report the temperature for all SAS/SATA HDD/SSD (SCGCQ00490822) Added support for communicating with multiple controllers over I2C (SCGCQ00485924) Added a retry of IO commands as LDIO if raid map sync is failed with MFI_STAT_CONFIG_SEQ_MISMATCH (SCGCQ00651680) Added support for Self-Encrypting Drives in JBOD mode (SCGCQ00399739) Improved accuracy of ROC temperature display (SCGCQ00575037) Increased range of priorities for background tasks, CC/PR/Rebuild/Migrate/BGI (SCGCQ00313882) Added support for 512e drives (SCGCQ00619363) Prevented a situation where there may be excessive overtemp warnings in the firmware log (SCGCQ00820067) Improved DDR3 signalling margin during heavy I/O workloads (SCGCQ00824711)
Version 24.2.1-0052 - Non-Critical ------------------- Enhancement(s): - Added a special handling for interactive password. - Implemented mechanism to allow system BIOS to put entries for iMR memory allocation into proper table. Fixes: - - Fixed an issue where boot message ‘cached data was lost,’ even when there was no battery present. - Fixed an issue where the ‘cli set securitykey=Lsi@12345’ command fails with error code 1001 and error message invalid key.resent. - Fixed an issue where foreign configurations fails to import maximum number of configurations. - Fixed simpleswap port mapping. - Fixed an issue where 'Cli show all' command fails with error msg 'Error! App exec failed in FW PCLIError! Internal.' - Fixed an issue where ‘Cli show all’ command fails with error message ‘Error! App exec failed in FW PCLIError! Internal.’ - Fixed an issue where Coherency bit was not enabled in SRAM TLBs.
Version 24.2.1-0045 - Non-Critical ------------------- Fixes: - Fixed an issue where cache offload failured with pinned cache on R5 VD. - Fixed an issue where using upper case characters in command 'cli set securitykey' fails with error code '1001' and error message 'invalid key.' - Fixed an issue where system would not boot into legacy mode. - Fixed an issue where default setting of VD doesn't reflect MFC's setting. - Fixed an issue where ‘Cli show all’ command fails with error msg ‘Error! App exec failed in FW PCLIError! Internal.’ - Fixed an where ServeRAID M5210 showed the wrong slot numbers in both MR and iMR, in both HII and MSM.
Version 24.2.1-0027 - Non-Critical ------------------- Enhancment(s): - Added support for ServeRAID M5200 Series 4GB Flash/RAID 5 Upgrade for IBM System x (47C8668) - Added event in firmware to indicate that an INIT operation was halted due to reboot or other failure Fixes: - Increase backplane support to 32 slots. - Enable 512E support. - Fixed an issue where system is not allocating memory correctly when MR and iMR are in the same configuration - Fixed an issue where the user is Unable to create a RAID10 through Ctrl R using 4k drives. - Fixed an issue where on a local key management (LKM) enabled controller, the user is asked to enter the security key to unlock and import a foreign drive, which is locked and has external key management (EKM) enabled. - Fixed an issue where switching between external key management (EKM) and Local Key Management (LKM) without rebooting results in the current secret key string becoming invalid/null. - Fixed an issue where cache memory size is listed as zero in controller Information. - Fixed an issue where re-keying a controller with External key management (EKM) enabled and rebooting the system results in a corrupted key ID and an error message "Unable to communicate with EKMS ..." is displayed. - Fixed an issue where performing an online firmware update or online controller reset (OCR) on a controller with External key management (EKM) enabled, results in all secured drives marked as foreign. - Fixed an issue where CacheCade volumes, which are not supported, could be created using 4K SSD's. - Fixed an issue where removing the last physical drive of arrays could result in a firmware fault. - Fixed an issue where MegaRAID Storage Manager does not show an option to create virtual drives when the first drive in the array is missing in a partial virtual drive where all drives are configured. - Fixed an issue where switching the security mode from external key management (EKM) to local key management (LKM) on iMR controller will result in a corrupted controller key. - Fixed an issue where performing a re-key operation in external key management (EKM) mode without doing a reboot, and then switching to local key management Mode(LKM) results in the Firmware logs showing that a drive security key was created but HII says the key is incorrect.
Version 24.0.2-0013 ------------------- -Initial release ibm_fw_sraidmr_5200-24_7_0-0052_linux_32-64_chg
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.13.1-0200 - Critical ------------------- Enhancement: - Support LSI iMR Private Interface for Intel iOMMU/VT-d Support when combined with latest system uEFI - Display drive speed for 12 GB Seagate hard drives in MSM. - List battery status in BIOS as N/A for iMR controllers Fixes: - Fixed incompatibility issue with System x3200/3250 M3 causing hang condition (RETAIN Tip H211826) - Fixed an issue where self-encrypting (SED) hard disk password fails to allow access to virtual disk configurations. - Fixed an issue where the ‘cli set securitykey=Lsi@12345’ command fails with error code 1001 and error message invalid key. - Fixed an issue where WebBIOS advanced software option locks the server. - Changed patrol read completion time calculation to include time for associated IO operations. - Fixed SGPIOs signal issue.
Version 20.11.1-0184 - Suggested ------------------- Fixes: - Updated SBR to avoid an errata that could cause correctable CPU errors on some systems. - Fixed an issue where NULL events may show in event log, preventing capture of controller event logs.
Version 20.11.1-0137 - Suggested ------------------- Enhancement(s): - Update recovery mode page (WriteRetryCount and recoveryTimeLimit) during discovery of a drive and during spinup recovery when sense 6/29 is received.
Fixes: - Fixed an issue where certain drives were reporting a temperature of 65 degrees Celsius. - Fixed an issue where systems with SSD HDD will pop up an error message after creating a virtual drive via HII on M1115. - Fixed an issue where the drive state is not modified when a recon virtual drive is created from the reboot path.
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_1000-20_13_1-0200_linux_32-64_chg
======================================================= Change History for Qlogic NIC Driver for SLES 11 ======================================================= Document Name: Change History Document Status: IBM General Avalibility Document Name: Change History Document Status: IBM General Avalibility Document Version: 5.3.6.1 Package Version: 5.3.61.1 Latest Driver Version: 5.3.61.1 Document Updated: 09/25/2014 Product: Qlogic Linux NIC Device Driver
======================================================= Please visit www.qlogic.com/hba for full documentation, additional drivers, and management applications.
Version 5.3.61.1
Package version: 5.2.46.4.c Package version updated due to updated tools within package.
Please visit www.qlogic.com/hba for full documentation, additional drivers, and management applications.
Driver Version: 5.2.46.4
Driver Version: 5.0.29.4 Initial release of Qlogic NIC Driver for SLES 11
qlgc_dd_nic_qlcnic-5_3_61_1_sles11_32-64_chg
Broadcom NetXtreme I Firmware Update Utility for IBM servers and options using the Broadcom NetXtreme I ethernet adapters.
Version 17.0.4.5a, June 08, 2015
This update package supports the following Broadcom devices: =========================================================== - BCM5717 NetXtreme I LOM - BCM5718 NetXtreme I LOM - BRCM5718 NetXtreme I Gigabit Ethernet Adapter / Product No: 49Y7900 - BCM5719 NetXtreme I LOM - BCM5719 NetXtreme I Gigabit Ethernet Adapter / Product No: 90Y9352 - BCM5720 NetXtreme I Gigabit Ethernet Adapter / Product No: 90Y9370
This update packages updates your Broadcom LOM/Adapter Firmware Code to the levels shown below: Firmware code: Version Previous ==================== ======== ========== Bootcode for 5717 1.63 1.63 Bootcode for 5717C0 2.07 2.07 Bootcode for 5718 1.63 1.63 Bootcode for 5719 1.41 1.41 Bootcode for 5720 1.36 1.36 EFI Undi 16.8.4* << 16.8.4 iSCSI Boot 7.10.4 7.10.4 PXE NX1 16.8.0 16.8.0 NCSI Firmware NX1 1.3.04 1.3.04
Note: An asterisk (*) following a version number represents a certified driver. Arrows (<<) between versions indicate the component has been updated from the previous released software kit.
brcm_fw_nic_17_0_4_5a_linux_32-64_chg
BIOS/FW/UEFI Update for IBM N2200 Series SASC/SATA HBA Controllers
Controller Supported: IBM N2215 SAS/SATA HBA for IBM System x (47C8676) IBM N2225 SAS/SATA HBA for IBM System x (00AE912) IBM N2226 SAS/SATA HBA for IBM System x (00AE916)
Ehhanncements: - Add support for N2225 and N2226 SAS/SATA HBA Controllers Fixes: - Fixed an issue where SAS SSDs may not show up in the uEFI configuration Utility (HII)
ÿþS e r v e R A I D M 1 2 1 5 S A S / S A T A C o n t r o l l e r F i r m w a r e U p d a t e
A d a p t e r s S u p p o r t e d : S e r v e R A I D M 1 2 1 5 S A S / S A T A C o n t r o l l e r f o r I B M S y s t e m x ( 4 6 C 9 1 1 5 )
N O T E T O S E R V I C E - R e f e r e n c e R E T A I N # N / A
V e r s i o n 2 4 . 7 . 0 - 0 0 5 2 - H i g h I m p a c t / H i g h P r o b a b i l i t y o f O c c u r r e n c e
- - - - - - - - - - - - - - - - - - -
F i x e s :
I n c o r p o r a t e d M e g a R A I D F W s t a c k 6 . 6
F i x e d a n i s s u e w h e r e a d r i v e r e p o r t i n g i t s e l f a s 0 M B s h o w s u p a s U n c o n f i g u r e d G o o d ( S C G C Q 0 0 7 8 4 3 1 9 )
F i x e d a n i s s u e w h e r e t h e f i r m w a r e m i g h t h a n g d u r i n g e r r o r h a n d l i n g o f s e n s e c o d e 0 b / 4 7 / x x ( S C G C Q 0 0 7 0 1 7 4 4 )
F i x e d a n i s s u e w h e r e s o m e S S D s m a y c a u s e t h e s y s t e m t o h a n g a t P O S T ( S C G C Q 0 0 5 9 5 5 0 6 )
F i x e d a n i s s u e w h e r e a n i M R R A I D c o n f i g m a y f a i l t o i m p o r t t o 1 2 g b p s M R ( S C G C Q 0 0 8 3 3 7 6 5 )
F i x e d a n i s s u e w h e r e R 0 , R 5 a n d R 6 r e a d b a n d w i d t h d r o p p e d a b r u p t l y a t 2 5 6 K b l o c k s i z e w i t h 2 4 d r i v e S A T A S S D c o n f i g ( S C G C Q 0 0 6 0 9 8 0 8 )
F i x e d a n i s s u e w h e r e R A I D 1 0 p e r f o r m a n c e i s u n d e r - p e r f o r m i n g ( S C G C Q 0 0 7 9 4 7 7 3 )
F i x e d a n i s s u e w h e r e i n s o m e c a s e s t h e L S I c h i p w o u l d c o n v e r t a n i n c o m i n g c h i p r e s e t t o a s y s t e m r e s e t ( S C G C Q 0 0 6 6 4 2 6 1 )
F i x e d a n i s s u e w h e r e m a n y p R d m / p R e q u e s t / p R e p l y m e s s a g e s w o u l d a p p e a r i n L S I f i r m w a r e l o g ( S C G C Q 0 0 7 5 2 1 9 5 )
F i x e d a n i s s u e w h e r e w h e n a c o n s i s t e n c y c h e c k i s a b o r t e d , t h e a d a p t e r m a y r e s e t ( S C G C Q 0 0 8 1 9 8 1 1 )
F i x e d a n i s s u e w h e r e P a t r o l r e a d d o e s n o t s t a r t a n d g i v e s i n c o r r e c t w a r n i n g m e s s a g e ( S C G C Q 0 0 7 2 8 4 0 4 )
F i x e d a n i s s u e w h e r e t h e c o n t r o l l e r m a y r e s e t u n e x p e c t e d l y d u r i n g e r r o r h a n d l i n g ( S C G C Q 0 0 8 2 5 1 2 6 )
F i x e d a n i s s u e w h e r e S t o r C L I m a y r e p o r t E n c l o s u r e N o t F o u n d ( S C G C Q 0 0 8 4 3 1 4 6 )
F i x e d a n i s s u e w h e r e x 8 8 0 n o d e s m a y r e p o r t e x c e s s i v e ' S C L S T U C K L o w ! W h i l e I 2 C R x R e c e i v i n g D a t a ' i n L S I f i r m w a r e l o g ( S C G C Q 0 0 7 2 8 9 3 5 ) ( R e t a i n T I P H 2 1 3 8 9 1 )
F i x e d a n i s s u e w h e r e t h e c o m m a n d t i m e o u t f o r F E D ( S E D ) d r i v e s i s t o o s h o r t , r e s u l t i n g i n 0 5 / 2 C c o d e s ( S C G C Q 0 0 7 9 7 3 5 5 )
F i x e d a n i s s u e w h e r e b a n d w i d t h f a l l s a s q u e u e d e p t h i n c r e a s e s o n R 5 / R 6 2 4 / 4 0 d r i v e S A S H D D c o n f i g s a t 2 5 6 k b l o c k s i z e ( S C G C Q 0 0 7 0 1 7 6 8 )
F i x e d a n i s s u e w h e r e s o m e d r i v e s m a y g e t b a d P I C R C e v e n t h o u g h d a t a i s c o r r e c t r e s u l t i n g i n d r i v e f a i l u r e ( S C G C Q 0 0 8 1 9 3 1 4 )
F i x e d a n i s s u e w h e r e t h e f i r m w a r e m a y e x p o s e d m o r e t h a n 2 4 0 V D s t o h o s t e v e n i f h o s t d r i v e r d o e s n ' t s u p p o r t t h a t m a n y ( S C G C Q 0 0 8 2 9 2 1 4 )
F i x e d a n i s s u e w h e r e M S M m a y d i s p l a y a n e r r o r m e s s a g e i f ' S c h e d u l e C o n s i s t e n c y C h e c k ' i s s e l e c t e d ( S C G C Q 0 0 8 3 2 9 0 8 )
F i x e d a n i s s u e w h e r e t h e M e g a R A I D P O S T m a y d i s p l a y " T h e n a t i v e c o n f i g u r a t i o n i s n o t s u p p o r t e d b y c u r r e n t f i r m w a r e " ( S C G C Q 0 0 8 1 2 8 4 2 )
F i x e d a n i s s u e w h e r e t h e E F I D r i v e r H e a l t h P r o t o c o l w i l l s h o w F a i l w h e n m o r e t h a n 6 4 V D s a r e c o n f i g u r e d ( S C G C Q 0 0 8 3 0 9 1 8 )
F i x e d a n i s s u e w h e r e O S m a y B S O D w h e n u p g r a d i n g f i r m w a r e o n a c o n t r o l l e r t h e O S h a s b o o t e d f r o m i f O n l i n e C o n t r o l l e r R e s e t i s p e r f o r m e d ( S C G C Q 0 0 8 2 5 7 2 5 )
F i x e d a n i s s u e w h e r e c o n t r o l l e r w o u l d n ' t g o t o h a l t s t a t e a f t e r m u l t i b i t E C C e r r o r s d e t e c t e d ( S C G C Q 0 0 7 8 3 1 8 6 )
F i x e d a n i s s u e w h e r e O p a l - c o m p l i a n t F D E ( S E D ) d r i v e s w e r e b e i n g m a r k e d a s F D E / S E D w h e n t h e y s h o u l d n ' t b e ( S C G C Q 0 0 7 8 8 2 5 0 )
F i x e d a n i s s u e w h e r e c o r r e c t a b l e E C C e r r o r i n t e r r u p t s w e r e b e i n g m a s k e d ( S C G C Q 0 0 8 1 4 9 9 7 )
F i x e d a n i s s u e w h e r e r e c o n s t r u c t e d V D s w e r e n o t b e i n g r e f l e c t e d i n M S M u n t i l s y s t e m r e b o o t ( S C G C Q 0 0 8 3 9 0 1 8 )
F i x e d a n i s s u e w h e r e c o n t r o l l e r c o m m a n d s m a y f a i l w h e n a n L D i s d e l e t e d d u r i n g r e c o n s t r u c t i o n ( S C G C Q 0 0 8 2 1 6 9 3 )
F i x e d a n i s s u e w h e r e f i r m w a r e w o u l d g o t o M o n T a s k w h e n m a k i n g V D s o f f l i n e w h i l e a R e b u i l d i s o c c u r r i n g u n d e r I O ( S C G C Q 0 0 8 2 5 7 7 5 )
F i x e d a n i s s u e w h e r e c o m m a n d s t o F D E ( S E D ) d r i v e s m a y n o t r e s p o n d w i t h i n 5 0 0 m s ( S C G C Q 0 0 8 4 4 4 4 5 )
F i x e d a n i s s u e w h e r e t h e f i r m w a r e m a y a l l o w t h e O S t o c h a n g e V D c a c h e s e t t i n g s ( S C G C Q 0 0 8 4 4 4 4 7 )
F i x e d a n i s s u e w h e r e H D D / S S D m i c r o c o d e u p d a t e s m a y r e p o r t f a i l e v e n t h o u g h t h e y s u c c e e d e d ( S C G C Q 0 0 5 5 3 2 5 2 )
F i x e d a n i s s u e w h e r e s l o t n u m b e r s m a y b e w r o n g s y s t e m s w i t h 3 2 d r i v e s l o t s ( S C G C Q 0 0 5 2 9 5 9 2 )
F e a t u r e s a n d E n h a n c e m e n t s
I m p r o v e d J e t s t r e s s / E x c h a n g e l a t e n c i e s ( S C G C Q 0 0 7 1 7 1 6 1 )
A d d e d a b i l i t y t o c l e a r t h e M a i n t a i n P d F a i l H i s t o r y ( S C G C Q 0 0 4 7 4 5 5 9 )
I m p r o v e d d r i v e r e b u i l d p e r f o r m a n c e ( S C G C Q 0 0 4 2 7 5 8 1 )
I m p r o v e d a v e r a g e l a t e n c y a n d m a x l a t e n c y i n W i n d o w s o p e r a t i n g s y s t e m s ( S C G C Q 0 0 6 7 1 6 7 0 )
I m p l e m e n t e d p o w e r t h r o t t l i n g ( S C G C Q 0 0 4 5 7 2 8 0 )
I m p r o v e d l o a d b a l a n c i n g o n > 2 d r i v e R 1 V D o f S S D s ( S C G C Q 0 0 5 9 3 5 8 8 )
A d d e d a b i l i t y f o r f i r m w a r e t o r e p o r t t h e t e m p e r a t u r e f o r a l l S A S / S A T A H D D / S S D ( S C G C Q 0 0 4 9 0 8 2 2 )
A d d e d s u p p o r t f o r c o m m u n i c a t i n g w i t h m u l t i p l e c o n t r o l l e r s o v e r I 2 C ( S C G C Q 0 0 4 8 5 9 2 4 )
A d d e d a r e t r y o f I O c o m m a n d s a s L D I O i f r a i d m a p s y n c i s f a i l e d w i t h M F I _ S T A T _ C O N F I G _ S E Q _ M I S M A T C H ( S C G C Q 0 0 6 5 1 6 8 0 )
A d d e d s u p p o r t f o r S e l f - E n c r y p t i n g D r i v e s i n J B O D m o d e ( S C G C Q 0 0 3 9 9 7 3 9 )
I m p r o v e d a c c u r a c y o f R O C t e m p e r a t u r e d i s p l a y ( S C G C Q 0 0 5 7 5 0 3 7 )
I n c r e a s e d r a n g e o f p r i o r i t i e s f o r b a c k g r o u n d t a s k s , C C / P R / R e b u i l d / M i g r a t e / B G I ( S C G C Q 0 0 3 1 3 8 8 2 )
A d d e d s u p p o r t f o r 5 1 2 e d r i v e s ( S C G C Q 0 0 6 1 9 3 6 3 )
P r e v e n t e d a s i t u a t i o n w h e r e t h e r e m a y b e e x c e s s i v e o v e r t e m p w a r n i n g s i n t h e f i r m w a r e l o g ( S C G C Q 0 0 8 2 0 0 6 7 )
V e r s i o n 2 4 . 2 . 1 0 0 5 2 M o d e r a t e I m p a c t / L o w P r o b a b i l i t y o f O c c u r r e n c e
E n h a n c e m e n t ( s ) :
A d d e d a s p e c i a l h a n d l i n g f o r i n t e r a c t i v e p a s s w o r d .
I m p l e m e n t e d m e c h a n i s m t o a l l o w s y s t e m B I O S t o p u t e n t r i e s f o r i M R m e m o r y
a l l o c a t i o n i n t o p r o p e r t a b l e .
F i x e s :
F i x e d a n i s s u e w h e r e b o o t m e s s a g e c a c h e d d a t a w a s l o s t , e v e n w h e n t h e r e
w a s n o b a t t e r y p r e s e n t .
F i x e d a n i s s u e w h e r e t h e c l i s e t s e c u r i t y k e y = L s i @ 1 2 3 4 5 c o m m a n d f a i l s
w i t h e r r o r c o d e 1 0 0 1 a n d e r r o r m e s s a g e i n v a l i d k e y . r e s e n t .
F i x e d a n i s s u e w h e r e f o r e i g n c o n f i g u r a t i o n s f a i l s t o i m p o r t m a x i m u m n u m b e r
o f c o n f i g u r a t i o n s .
F i x e d s i m p l e s w a p p o r t m a p p i n g .
F i x e d a n i s s u e w h e r e ' C l i s h o w a l l ' c o m m a n d f a i l s w i t h e r r o r m s g ' E r r o r !
A p p e x e c f a i l e d i n F W P C L I E r r o r ! I n t e r n a l . '
F i x e d a n i s s u e w h e r e C l i s h o w a l l c o m m a n d f a i l s w i t h e r r o r m e s s a g e
E r r o r ! A p p e x e c f a i l e d i n F W P C L I E r r o r ! I n t e r n a l .
F i x e d a n i s s u e w h e r e C o h e r e n c y b i t w a s n o t e n a b l e d i n S R A M T L B s .
V e r s i o n 2 4 . 2 . 1 - 0 0 5 1 - N o n - C r i t i c a l
- - - - - - - - - - - - - - - - - - -
F i x e s :
- F i x e d s i m p l e s w a p p o r t m a p p i n g .
- F i x e d a n i s s u e w h e r e t h e c l i s e t s e c u r i t y k e y = L s i @ 1 2 3 4 5 c o m m a n d f a i l s
w i t h e r r o r c o d e 1 0 0 1 a n d e r r o r m e s s a g e i n v a l i d k e y .
- F i x e d a n i s s u e w h e r e r e s t a r t i n g t h e s y s t e m a f t e r a n O C R ( o n l i n e c o n t r o l l e r
r e s e t r a t e ) o p e r a t i o n c o u l d r e s u l t i n a n o t h e r O C R o p e r a t i o n .
- F i x e d a n i s s u e w h e r e / c 0 / p a l l s h o w a n d L i n k s p e e d i n f o r m a t i o n i s n o t i n
s a m e i n C t r l - R .
- F i x e d a n i s s u e w h e r e C l i s h o w a l l c o m m a n d f a i l s w i t h e r r o r m e s s a g e
E r r o r ! A p p e x e c f a i l e d i n F W P C L I E r r o r ! I n t e r n a l .
- E n a b l e d m e m o r y c o h e r e n c y b i t i n S R A M T L B s
V e r s i o n 2 4 . 2 . 1 - 0 0 4 5 - N o n - C r i t i c a l
- - - - - - - - - - - - - - - - - - -
F i x e s :
- F i x e d a n i s s u e w h e r e c a c h e o f f l o a d f a i l u r e d w i t h p i n n e d c a c h e o n R 5 V D .
- F i x e d a n i s s u e w h e r e u s i n g u p p e r c a s e c h a r a c t e r s i n c o m m a n d ' c l i s e t
s e c u r i t y k e y ' f a i l s w i t h e r r o r c o d e ' 1 0 0 1 ' a n d e r r o r m e s s a g e ' i n v a l i d k e y . '
- F i x e d a n i s s u e w h e r e s y s t e m w o u l d n o t b o o t i n t o l e g a c y m o d e .
- F i x e d a n i s s u e w h e r e d e f a u l t s e t t i n g o f V D d o e s n ' t r e f l e c t M F C ' s s e t t i n g .
- F i x e d a n i s s u e w h e r e C l i s h o w a l l c o m m a n d f a i l s w i t h e r r o r m s g E r r o r !
A p p e x e c f a i l e d i n F W P C L I E r r o r ! I n t e r n a l .
- F i x e d a n w h e r e S e r v e R A I D M 5 2 1 0 s h o w e d t h e w r o n g s l o t n u m b e r s i n b o t h M R
a n d i M R , i n b o t h H I I a n d M S M .
V e r s i o n 2 4 . 2 . 1 - 0 0 2 7
- - - - - - - - - - - - - - - - - - -
- I n i t i a l r e l e a s e ibm_fw_sraidmr_1215-24_7_0-0052_linux_32-64_chg
BIOS/FW/UEFI Update for IBM N2115 SAS/SATA Controller
Controller Supported: IBM N2115 SAS/SATA Controller (46C8989)
Enhancement - Reduce the boot time for UEFI driver for large configurations Fixes: - Fixed an issue that caused the Integrated Management Module (iMM) in System x servers to report Warning: Sensor GPT Status has transitioned from normal to non-critical state. - Fixed an issue observed with formatting hard disk drives with capacities greater than 2.2 TB.(RETAIN H212436) - Fixed an issue where 4k sector size drives with 512e reporting enabled show wrong physical size when running a read capacity 16 command. - Fixed an issue where speed negotiation for 3Gig SATA drives is not handled properly. - Added Support for Report Luns Command - Fixed an issue where OS hang during install of Linux system to a SSD - Fixed an issue where SAS device page 0 may still be present for Initiator devices that have been removed from the topology. - Fixed an issue where RHEL 6.3 hangs during boot with IBM 600GB High IOPS MLC Modular Adapter - Fixed an issue where a non-PI volume made up of all PI capable drives, may come up as PI enabled after a controller reset. - Fixed an issue where a fault 0X8808 occurs when a reset is issued to the controller that has max number of active/inactive volumes - Fixed an issue where "Device Present" Flag of SAS device page0 is not set for initiator controller in then target controller when two controllers are connected to each other in initiator/target mode. - Fixed an issue where extended tags and PCIe upconfigure capability are disabled in SAS2208 and SAS2308. - Fixed an issue where force full discovery does not trigger rediscovery of an expander after the initial expander discovery fails. - Fixed an issue where single RAID0 volume activation was succeeding, even though controller does not support single drive RAID0. - Fixed an issue where RAID1 volume of Non-PI drives moves to optimal state when a PI drive is hotplugged and 'Enable PI mixing' not enabled. - Fixed an issue where Locate LED's stop automatically after 3-4 minutes before user issues command to turn off the Locate LED's. - Fixed an issue where fault 0x8618 is seen when a new volume is created in the presence of another volume which is undergoing resync along with IO. - Fixed an issue background initialization does not start on RAID0 volume with PI drives, after removing and reinserting a volume member.
BIOS - Fixed an issue where core BIOS displays warning message when it fails to add all of the drives connected to int13 chain, then waits for user to press any key to continue further, rather than continuing after 3 seconds. - Fixed an issue where incorrect adapter is being tagged as the first adapter found. - Fixed an issue where the save or discard changes prompt appears after a failed attempt to set volume as the boot device in BIOS CU. - Fixed an issue where BIOS CU provides incorrect device pointer when checking for raid disk to allow/disallow setting boot device. - Fixed an issue where device properties screen is invoked from a direct attach device using Alt+D in SAS topology screen, device traversing [Alt+N & Alt+P] is restricted within the direct attach device and expander attach devices are not traversed. - Fixed an issue where the drive status field does not show 'Max dsks' when trying to select 11th drive for RAID10 volume. - Fixed an issue maximum Int13 devices settings does not get honored, when the value is set as 0 in BIOS CU - Fixed an issue where drive size of 1.088GiB was showing as 1.880GiB. - Fixed an issue current boot device set to device at slot 4" message Not displaying for Adaptors with boot order other than 0. - Fixed an issue where the BIOS CU navigates to create new volume screen instead of back to raid properties screen. - Fixed an issue where BIOS banner showed 'FF' for slot information. - Fixed an issue where the drive's SMART status is always shown as no irrespective of drive's SMART status, under Pred Fail column of the manage hot spare screen and create new volume screen. - Fixed an issue where SAS2 BIOS: volume size shows inconsistent value in the create new volume' screen after selecting the last volume member. - Fixed an issue where a disabled adapter causes the second adapter status to show as unavailable even though the second adapter is enabled. Uefi Enhancement 1/2 - Added capability to create an IR RAID volume in non-PI mode, even when all member drives are PI Capable. - Added PI info and ability to control creation of PI Volume in UCM of BSD HII. - Added new form manage PHY settings to support enabling or disabling of a controller PH Fixes: - Fixed an issue view foreign volume option is disabled with a foreign volume in the configuration.
Multi-boot Image for 8Gb FC HBAs Release Notes version MB_3.11.06
This software license applies only to QLogic customers. QLogic Corporation. All rights reserved.
Table of Contents
1. Version 2. 8Gb BIOS 3. 8Gb EFI 4. 8Gb 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 8Gb HBAs. This package is a compressed file that contains:
Kit Version 3.11.06
Q25A6311.BIN contains: ---------------- * BIOS version 3.27 * UEFI version 6.12 signed * Firmware version 7.04.00 FlasUtil version 1.89 VPD version 10.01a Efiutil version 3.17
* Added code to not configure any targets when FA Boot LUN enabled but FA BOOT LUN not found. ER133769. * Added code to allow FA Boot LUN when FA WWPN enabled * Added options in CTRL-Q utility to enable FA WWPN and FA BOOT LUN. * Fix minor cosmetic error in display of Fcode/EFI versions for show port CLP.(ER133294) * Added support FA BOOT LUN * Added 8G support for show port clp * Changed VLAN ID max value from 4095 to 4094. * Removed spinup option from CTRL-Q. * Changed CTRL-Q to allow max value for Login Retry, * Port Down Retry, Link Down Count of 65535.ER(116099) * Removed Helga support * Added support for show port clp. * Remove EV boot order option from OEM BIOS. * Added CTRl_Q option to set VLAN_ID for FCoE HBA's(ER110593). * Changed Banner to display 'FCoE' for Schultz (ER110784). * Added additional time to login target when called * after EFI driver unloads. (ER110755,ER110855) * Added code to handle boot LUN Greater Than 255 (ER109195). * Added code to display message when 64 bit address is detected. * Removed port number from HII formset title. This fixes a UCM parsing issue. (ER134560).
========================================================================== Change History ==========================================================================
Kit Version 3.11.01
Q25A1311.BIN contains: ---------------- * BIOS version 3.24 * UEFI version 6.10 * Firmware version 7.04.00 FlasUtil version 1.89 VPD version 10.01a Efiutil version 3.17
* Changed Banner to display 'FCoE' for Schultz (ER110784). * Added additional time to login target when called after EFI driver unloads. (ER110755,ER110855) * Added code to handle boot LUN Greater Than 255 (ER109195). * Added code to display message when 64 bit address is detected. * Added support for Execution Throttle for P3P (ER106372) * Added code to not display connection options for Hilda Trinity adapter. * Checked for invalid LUN in CTRL-Q scan devices.
============================================================ Kit Version 3.10.09
Q25A9310.BIN contains: ---------------- * BIOS version 3.24 * UEFI version 6.09 * Firmware version 7.02.00 FlasUtil version 1.89 VPD version 10.01 Efiutil version 3.17
1. Change History 2. Known Issues 3. Notices 4. Contacting Support
1. Change History
These release notes describe the changes, fixes, known issues, and release details that apply to the FC-FCoE BIOS version 3.24.
This section contains:
* 1.1 Version * 1.2 Changes * 1.3 Bug Fixes
1.1
Version 3.24 * Removed Beta Banner
Version 3.24 Beta 1 Changed Banner to display 'FCoE' for Schultz (ER110784). Added additional time to login target when called after EFI driver unloads. (ER110755,ER110855)
Version 3.23 * Removed Beta Banner
Version 3.23 Beta 2 Added code to handle boot LUN Greater Than 255 (ER109195).
Version 3.23 Beta 1 * Added support for Helga.
Version 3.22 * Added code to display message when 64 bit address is detected.
Version 3.21 * Removed Beta Banner
Version 3.21 Beta 1 * Added support for Execution Throttle for P3P (ER106372) * Added code to not display connection options for Hilda Trinity adapter. * Checked for invalid LUN in CTRL-Q scan devices.
Version 3.20 * Fixed bug in CTRL_Q utility that could cause some cosmetic display issues. * Added Hilda CLP _hss support. * Configured ISP24xx if on slot 0. * Added "QLogic" to PnP productid (ER104424) * Checked for 4G flag in NVRAM for Hilda FC.(ER104714)
Version 3.19 * Removed Beta Banner
Version 3.19 Beta 1 * Fixed bug with CTRL-Q Loopback Utility (ER100729).
Version 3.18 * Removed Beta Banner
Version 3.18 * Added code to check/program Feature Config checksum. * Fixed bug that could cause buffer overrun in CTRL-Q with Report Lun command (ER100294). * Added check for PCI address change when updating option card data structure.
Version 3.18 Beta 1 * Changed code to use 32 bit pointer to allocate/deallocate EBDA memory. * Added code to check/program Feature Config checksum.
Version 3.17 * Removed Beta Banner
Version 3.17 Beta 1 * Fixed cosmetic issue in displaying data rate in CTRL-Q
Version 3.16 * Changed text for 8300 series adapter External loopback (ER98690). * Fixed display issue with CTRL-Q Diskutility(ER98727) * Fixed Lun select issue with CTRL-Q (ER98675).
Version 3.15 * Removed Beta Banner
Version 3.14 Beta 3 * Fixed bug in displaying selectable boot lun (ER98226) * Removed 4G data rate option for OEM adapter (ER98228) * Limited leading '0's in CTRL-Q menu (ER98389). * Set 'Aggressive Cooling' flag for OCSD. * Enabled Personality Change option.
Version 3.14 Beta 2 * Fixed issue with not restoring defaults on port 1 (ER 97619) * Fixed issue with serdes data saved incorrectly. (ER 97654) * Added code to limit Report Lun List size to 256 luns Version 3.14 Beta 1 * Added check for 0 lun count when selecting device (ER 97385) Version 3.14 * Removed 'Beta' from banner Version 3.13 Beta 17 * Disabled Personality Change option in CTRL-Q. * Fixed bug with WWNN handling for MCTP.(ER 96920) Version 3.13 Beta 16 * Added check for Set MD2 set to 0 (restore defaults) (ER96912) * Added code to reset Port Config after Internal loopback test for 8300 series adapter(FCoE). Version 3.13 Beta 15 * Added support for 16 bit lun (ER96090). Version 3.13 Beta 14 * Added support for Set MD2 CLP string. Version 3.13 Beta 13 * Added code to issue Load Flash FW (3) MB command for 8300 series adapter as part ISP start sequence. (ER 94035). Version 3.13 Beta 12 * Fixed code to prevent async event from causing BIOS to hang when scanning for devices (ER94371). * Added check for Internal Loopback mode when connected to F-Port (ER71773). * Added check for 8300 series adapter FW Auto Load when re-initing ISP. * Version 3.13 Beta 11 * Fixed code to disable ALT+1 Hotkey (ER92844) . * Fixed CTRL-Q code mailbox timeout (ER92957). Version 3.12 Beta 10 * Added warning message in Personality change screen Version 3.12 Beta 9 * Updated BIOS to version 3.12 of non-8300 series adapter BIOS Version 3.12 Beta 8 * Updated 8300 series adapter BIOS code with version 3.11 fixes
Version 3.11 * Removed check for Virtual Address flag on Cold Boot.
Version 3.10 * Changed code to check for signature aaaaaaaah before* updating virtual mac address.
Version 3.09 * Changed code to ignore soft boot signature aaaaaaaah*
Version 3.08 * Added code to save device number in OCSD.
Version 3.07 * Added code to read cold boot register signature to determine when BIOS should update/restore virtual Mac address.
Version 3.06 * Fixed bug where retry count was not always being updated.
Version 3.05 * Added code to support ECHO loopback command.
Version 3.04 * Removed Beta from banner.
Version 3.04 Beta 4 * Fixed bug in clp_hss processing. * Updated some ETOC header data fields.
Version 3.04 Beta 3: * Changed code passing Sensor Data pointer
Version 3.04 Beta 2 * Added support for passing ETOC pointer. * Added support for posting port status for EFI use.
Version 3.04 Beta 1 * Added support for sensor data reporting.
Version 3.03 * Added support NCSI Flex Address.
Version 3.02 * Fixed bug in setting mailbox timeout for TUR.
Version 3.01 * Removed CTRL-Q Loopback test for P3P.
Version 3.00 * Removed Beta banner
Version Beta 14 * Added code to get serial number from VPD data for ISP2532. * Fixed bug in display loopback error status.
Version Beta 13 * Fixed bug in verifying FW for non-P3P HBA's. * Removed QLogic vendor id from BIOS banner. * Added retry for LLIOCB when status subcode is 4.
Version Beta 12 * Fixed bug in not setting up retry count for P3P.
Version Beta 11 * Added support for -LR option * Changed error message when no ISP Functions found.
Version Beta 10 * Added code to check for Wocket card.
Version Beta 9 * Fixed bug with not clearing P3 Async Event.
Version Beta 8 * Added additional check for P3 INIT Complete.
Version Beta 7 * Increased p3_busy_wait delay
1.2 Changes
The following changes have been made to the BIOS for FC-FCoE Adapters between versions 3.02 and 3.24.
* Changed Banner to display 'FCoE' for Schultz (ER110790). * Added additional time to login target when called * after EFI driver unloads. (ER110755.ER110855) * Added support for Helga. * Added code to display message when 64 bit address is detected. * Added support for Execution Throttle for P3P (ER106372) * Added code to not display connection options for Hilda Trinity adapter. * Checked for invalid LUN in CTRL-Q scan devices. * Fixed bug in CTRL_Q utility that could cause some cosmetic display issues. * Added Hilda CLP _hss support. * Configured ISP24xx if on slot 0. * Added "QLogic" to PnP productid (ER104424) * Checked for 4G flag in NVRAM for Hilda FC.(ER104714) * Fixed bug with CTRL-Q Loopback Utility (ER100729). * Added code to check/program Feature Config checksum. * Fixed bug that could cause buffer overrun in CTRL-Q with Report Lun command (ER100294). * Added check for PCI address change when updating option card data structure. * Changed code to use 32 bit pointer to allocate/deallocate EBDA memory. * Added code to check/program Feature Config checksum. * Fixed cosmetic issue in displaying data rate in CTRL-Q * Changed text for Hilda External loopback (ER98690). * Fixed display issue with CTRL-Q Diskutility(ER98727) * Fixed Lun select issue with CTRL-Q (ER98675). * Fixed bug in displaying selectable boot lun (ER98226) * Removed 4G data rate option for OEM adapter (ER98228) * Limited leading '0's in CTRL-Q menu (ER98389). * Set 'Aggressive Cooling' flag for OCSD. * Enabled Personality Change option. * Fixed issue with not restoring defaults on port 1 (ER 97619) * Fixed issue with serdes data saved incorrectly. (ER 97654) * Added code to limit Report Lun List size to 256 luns * Added check for 0 lun count when selecting device (ER 97385) * Disabled Personality Change option in CTRL-Q. * Fixed bug with WWNN handling for MCTP.(ER 96920) * Added check for Set MD2 set to 0 (restore defaults) (ER96912) * Added code to reset Port Config after Internal loopback test for Hilda(FCoE). * Added support for 16 bit lun (er96090). * Add support for Set MD2 CLP string. * Added code to issue Load Flash FW (3) MB command for Hilda as part ISP start sequence. (ER 94035). * Fixed code to prevent async event from causing BIOS to hang when scanning for devices (er94371). * Fixed code to disable ALT+1 Hotkey (er92844) . * Fixed CTRL-Q code mailbox timeout (er92957). * Added warning message in Personality change screen. * Updated BIOS to version 3.12 of non-hilda BIOS * Removed check for Virtual Address on Cold Boot. * Changed code to check for signature aaaaaaaah before updating virtual mac address. * Changed code to ignore soft boot signature aaaaaaaah * Added code to save device number in OCSD. * Added code to read cold boot register signature to determine when BIOS should update/restore virtual Mac address. * Fixed bug where retry count was not always being updated. * Added code to support ECHO loopback command. * Added support NCSI Flex Address.
1.3 Bug Fixes
The following fixes have been made to the BIOS for FC-FCoE Adapters between versions 3.00 Beta 7 and 3.24.
* Changed Banner to display 'FCoE' for Schultz (ER110790). * Added additional time to login target when called * after EFI driver unloads. (ER110755.ER110855) * Added code to handle boot LUN Greater Than 255 (ER109195). * Checked for invalid LUN in CTRL-Q scan devices. * Fixed bug in CTRL_Q utility that could cause some cosmetic display issues. * Added Hilda CLP _hss support. * Configured ISP24xx if on slot 0. * Added "QLogic" to PnP productid (ER104424) * Checked for 4G flag in NVRAM for Hilda FC.(ER104714) * Fixed bug with CTRL-Q Loopback Utility (ER100729). * Added code to check/program Feature Config checksum. * Fixed bug that could cause buffer overrun in CTRL-Q with Report Lun command (ER100294). * Added check for PCI address change when updating option card data structure. * Changed code to use 32 bit pointer to allocate/deallocate EBDA memory. * Added code to check/program Feature Config checksum. * Fixed cosmetic issue in displaying data rate in CTRL-Q * Changed text for Hilda External loopback (ER98690). * Fixed display issue with CTRL-Q Diskutility(ER98727) * Fixed Lun select issue with CTRL-Q (ER98675). * Fixed bug in displaying selectable boot lun (ER98226) * Removed 4G data rate option for OEM adapter (ER98228) * Limitleading '0's in CTRL-Q menu (ER98389). * Set 'Aggressive Cooling' flag for OCSD. * Fixed issue with not restoring defaults on port 1 (ER 97619) * Fixed issue with serdes data saved incorrectly. (ER 97654) * Added code to limit Report Lun List size to 256 luns * Added check for 0 lun count when selecting device (ER 97385) * Disabled Personality Change option in CTRL-Q. * Fixed bug with WWNN handling for MCTP.(ER 96920) * Added check for Set MD2 set to 0 (restore defaults) (ER96912) * Added support for 16 bit lun (er96090). * Add support for Set MD2 CLP string. * Added code to issue Load Flash FW (3) MB command for Hilda as part ISP start sequence. (ER 94035). * Fixed code to prevent async event from causing BIOS to hang when scanning for devices (er94371). * Fixed code to disable ALT+1 Hotkey (er92844) . * Fixed CTRL-Q code mailbox timeout (er92957). * Added warning message in Personality change screen. * Updated BIOS to version 3.12 of non-hilda BIOS * Removed check for Virtual Address on Cold Boot. * Changed code to check for signature aaaaaaaah before updating virtual mac address. * Changed code to ignore soft boot signature aaaaaaaah * Added code to save device number in OCSD. * Added code to read cold boot register signature to determine when BIOS should update/restore virtual Mac address. * Fixed bug where retry count was not always being updated. * Added code to support ECHO loopback command. * Fixed bug in clp_hss processing. * Updated some ETOC header data fields. * Changed code passing Sensor data pointer * Added support for passing ETOC pointer. * Added support for posting port status for EFI use. * Added support for sensor data reporting. * Added support NCSI Flex Address. * Fixed bug in setting mailbox timeout for TUR. * Increased p3_busy_wait delay * Added additional check for P3 INIT Complete. * Fixed bug with not clearing P3 Async Event. * Added code to check for Wocket card. * Added support for -LR option * Changed error message when no ISP Functions found. * Fixed bug in not setting up retry count for P3P. * Fixed bug in verifying FW for non-P3P HBA's. * Removed QLogic vendor id from BIOS banner. * Added retry for LLIOCB when status subcode is 4. * Added code to get serial number from VDP data for ISP2532. * Fixed bug in display loopback error status. * Fixed bug in setting mailbox timeout for TUR.
2. Known Issues
None
3. 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.
4. Contacting Support
For further assistance, contact QLogic Technical Support at: http://support.qlogic.com
Trademarks
Accelera, Accelerating Cluster Performance, InfiniCon Systems, InfiniNIC, InfiniPath, InfiniView, QLA, QLogic, the QLogic logo, ReadyPath, SANdoctor, SANsurfer, and SilverStorm are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.
(c) Copyright 2014. All rights reserved worldwide. QLogic and the QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.
1. Change History 2. Known Issues 3. Notices 4. Contacting Support
1. Changes History
UEFI Driver:
6.11
* AIM Fcode info. is now hidden if the option ROM does not contain Fcode. (ER133730) * Fixed errors in AIM UUID and AIM Serial Number info. (ER133802)
6.10
* Added default UUID support. (ER133286) * Added N/A for undefined vpd fields. (ER133286) * Added v1.28 AIM spec. changes. (ER133286) * Changed a few field sizes to match the AIM spec. (ER133286)
6.09
* Added AIM support for 8G standup cards. (ER132095) * Changes in place to reduce image size. Image binary is now X64. (ER132119)
6.08
* Added fix to hide or list HII elements selectively. (ER116233)
6.07
* Updated to get PN & Card SKU dynamically from I2C VPD for AIM. (ER116141) * Corrected help text string. (ER115814)
6.06
* Updated MTU size and AIM version references as per revised requirement. (ER113361)
6.05
* Updated AIM config strings as per revised requirements. (ER113361)
6.04
* Update AIM support as per revised requirements. (ER113361) * Added fix for boot settings persistency issue in BOFM supported legacy BIOS. (ER112641)
6.03
* Added support for IBM AIM. (ER113428)
6.02
* Added fix to persist user changes made on static forms. (ER112639) * Added feature to dynamically list targets in HII. (ER105725) * EDKII Successor of older tiano/EDKI driver ver 2.51. (07/17/13)
Efiutil:
3.17
* Add fix for 25xx ver_info command. (ER104543)
3.16
* Removed hardcoded subsystem id check. (ER0103883) * Replaced with MBI image traverse for ssid match. (ER0103883)
3.15
* Fixed ambiguity in firmware version display. (ER0103456)
2. Known Issues
* Dynamic target listing in HII requires UEFI 2.3 or later system compliance. * Efiutil does not support the 2.0 Shell. Please load the 1.0 Shell before running Efiutil.
3. 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.
4. Contacting Support
For further assistance, contact QLogic Technical Support at: http://support.qlogic.com
Trademarks
Accelera, Accelerating Cluster Performance, InfiniCon Systems, InfiniNIC, InfiniPath, InfiniView, QLA, QLogic, the QLogic logo, ReadyPath, SANdoctor, SANsurfer, and SilverStorm are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.
(c) Copyright 2014. 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_fc_8g-mb3_11_06_linux_32-64_chg
Version 6.806.08.00 - Moderate Impact/Low Probability of Occurrence ------------------- Fixes: - Incorporated MegaRAID 6.6 x86/x86_64 Linux driver stream - Fixed an issue where performance may drop in sequential read 256kb IO (SCGCQ00677516) - Fixed an issue which may lead to firmware crash and "MonTask: line 1257 in file ../../raid/2108vI2o.c" error in firmware log (SCGCQ00702536)
Features/enhancements: - Added a retry of IO commands as LDIO if raid map sync is failed with MFI_STAT_CONFIG_SEQ_MISMATCH (SCGCQ00651680) - Added support for 1MB IO if the firmware supports it as well (SCGCQ00671670) - Added ability to take a VD offline / bring a VD online, similar to the equivalent actions for PDs (SCGCQ00521610) - Added support for Self-Encrypting Drives in JBOD mode (SCGCQ00399739)
ServeRAID M and MR10 Series SAS Controller Driver for Linux (also supports MegaRAID 8480 SAS Controller)
Adapters Supported: - ServeRAID M1215 SAS/SATA Controller for IBM System x (46C9114) - ServeRAID M5210e SAS/SATA Controller for IBM System x - ServeRAID M5210 SAS/SATA Controller - ServeRAID M5110 SAS/SATA Controller for IBM System x (81Y4481) - ServeRAID M5110e SAS/SATA Controller for IBM System x - IBM Flex System Storage Expansion Node - ServeRAID M5120 SAS/SATA Controller for IBM System x (81Y4478) - ServeRAID M5016 SAS/SATA Controller for IBM System x (90Y4304) - ServeRAID M5115 SAS/SATA Controller for IBM System x (90Y4390) - ServeRAID M5015 SAS/SATA controller (46M0829) - ServeRAID M5014 SAS/SATA controller (46M0916) - ServeRAID M1115 SAS/SATA Controller for IBM System X (81Y4448) - 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 6.704.15.00 - Suggested ------------------- - Fixed an issue where uneven span configuration of RAID 1 will not have proper load balancing for Fast Path Read.
Version 6.602.03.00-2 - Suggested ------------------- Fixes: - Fixed an issue where the system may hang when touching max_sectors. Note: Device driver version number has not changed: 6.602.03.00.
Version 6.602.03.00-1 - Suggested ------------------- Enhancement: - Add support for ServeRAID M1215 SAS/SATA Controller Fixes: - Fixed an issue where Kernel panic occurs due to timeout of MFI/MPT pass-through command, followed by completion through Interrupt context. Note: Device driver version number has not changed: 6.602.03.00.
Version 6.600.20.00-4 - Suggested ------------------- Fixes: - Fixed reboot issue in SLES 11.3 xen. Note: Device driver version number has not changed: 6.600.20.00
Version 6.600.20.00 - Suggested ------------------- Enhancement(s): - Add Support for ServeRAID M5210 and M5210e SAS/SATA Controller
Version 6.506.00.00 - Suggested ------------------- Retain Tip: Tip #28016 Enhancement(s): - Added ability for user to configure the maximum number of MSI-X vectors launched for M51XX and M1XX controllers.
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.01 - Suggested ------------------- Fixes: - Corrected version strings in the iso and rpm files. NOTE: No change to the device driver. Packaging fix only.
Version 00.00.06.15 - Suggested ------------------- Enhancements: - Add support for fpRead/WriteCapable & fpRead/WriteAcrossStripe - Add support for SLES 11 SP2.
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-01 - Suggested ------------------- Fix - Fixed issue where the device driver may fail to install with the following error: "389 SCRIPT INTERNAL INCONISISTENCY! REPORT TO IBM IMMEDIATELY" Note: No change to device driver version.
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 controller. - 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_6_806_08_00_sles11_32-64_chg
========================================================== Change History ========================================================== Document Name: Change History Document Status: IBM General Avalibility Document Version: 3.2.5.1 Latest Driver Version: 3.2.5.1 Document Updated: 01/13/2015 Product: QLogic BR series FC HBA / FCoE CNA
Please visit www.qlogic.com for full documentation, additional drivers, and management applications.
Version 3.2.5.1 New Features and Feature Enhancement: - References to Brocade changed to QLogic - Support for RHEL5.11 and RHEL7.0
Version 3.2.4.0 New Features and Feature Enhancement: - Support for RHEL5.10 and RHEL6.5
Version 3.2.3.0 New Features and Feature Enhancement: - Support for patching firmware via boot image - Support for Linux PTP - Support for UEFI Health Check Protocol - Support for SLES11SP3
Version 3.2.1.0 New Features and Feature Enhancement: - Support for "IBM Flex System FC5024D 4-port 16Gb FC Adapter" PART_NUMBER "95Y2381" - Support for RHEL5.9 and RHEL6.4
Fixes and Enhancements: - Enhanced Linux driver data path to properly handle IPv6 packets. - Enhanced Linux driver to make sure user configured path tov value is persistent and is not changed due to change in dev_loss_tmo.
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_5_1_sles11_32-64_chg
=============================================================================== Emulex FC/FCoE Device Driver for Linux ===============================================================================
Device Driver Version: 10.2.377.27 Supported On: System x and BladeCenter
Problems Fixed: - Error recovery of a "hung" IO to a device is cancelling ALL IOs, not just the culprit one only
Device Driver Version: 10.2.375.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - ELS txcmplq list corruption cause crash during error injection - Cleaned up several issues around ExpressLane feature - Need a HAL workaround for upgrading 10.0 XE102/XE104 f/w to 10.2 - I/O hang on RHEL6.5 for small block (4K) random i/o on POWER8
Device Driver Version: 10.0.800.0 Supported On: IBM System x
Problems Fixed: - Low bi-di throughput seen on 1g ports of HS-23 LOM - Multiple performance improvements - Bonding driver takes approx 20 seconds to be ready
Incremental Interoperability: - RHEL 5.10 - RHEL 6.5 - XE-102 and XE-104 ASIC (OCx14xxx) - Support for set and get channels ethtool operation
Known Issues: - SR-IOV is supported with the following Linux distributions: * RHEL 6.4 and above 64-bit with KVM * SLES11 SP3 and above 64-bit with KVM
NOTE: Guest operating system support is dependent on the Emulex driver version installed in the guest.
Device Driver Version: 8.3.7.27 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Execution of internal loopback causes a crash - Issue which can cause multipath failover to not work properly
Incremental Interoperability: - IBM Flex System FC5052 2-port 16Gb FC Adapter - IBM Flex System FC5054 4-port 16Gb FC Adapter - IBM Tape unit interoperability - see SSIC for more information - SLES 11.3 on IBM System x and BladeCenter
Device Driver Version: 8.3.7.18 Supported On: IBM System x and BladeCenter
Problems Fixed: - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service - OXID Reused before RA_TOV without RRQ to recover - Intermittently storage paths will not recover after switch reboot
Device Driver Version: 8.3.6.4 Supported On: IBM Flex
Problems Fixed: - Fixed debug helper routine failed to dump CQ and EQ entries in non-MSI-X mode - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service - Fixed boot from san failure when SLI4 FC device presented on the same PCI bus - Fix ABTS recovery to be FC spec compliant - Fixed not reporting logical link speed to SCSI midlayer when QoS not enabled - Fix performance problem in pt2pt mode - Fixed SCSI host create showing wrong link speed on SLI3 HBA ports - Update text for misconfigured port messages - Fix discovery bug when swapping cables
Interoperability since previous release: - RHEL6.3 GA Kernel
Device Driver Version: 8.3.5.86 Supported On: IBM System x and BladeCenter
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
Device Driver Version: 8.3.5.74 Supported On: IBM System x, BladeCenter, and Flex
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 compilation errors on some kernels due to debugfs variable definitions - Used PCI configure space read to flush PCI function reset register write - 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
Device Driver Version: 8.3.5.66 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - 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 - Fix driver handling of XRI Aborted CQE response - Fixed port and system failure in handling SLI4 FC port function reset - Fix bug with driver not sending a LOGO with vport delete - Make BA_ACC work on a fully qualified exchange - Fix for SLI4 Port delivery for BLS ABORT ACC - Fix KERNEL allocation while lock held - Incorrect usage of bghm for BlockGuard errors - Fix warning on i386 system - Fix ndlp nodelist not empty wait timeout during driver unloading - Fix mailbox and vpi memory leaks - Support character device to take a reference on the driver - Fix for FDISC failures after firmware reset or link bounce - Support debugfs for injecting T10 DIF errors - Fix SLI4 BlockGuard behavior when protection data is generated by HBA - 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 - Support more driver logs in area of SLI4 port error attention and reset recovery - Fix bug with driver returning the wrong ndlp - Sync up with actual upstream lpfc driver code - Support SLI4 16Gb FC Adapter support for T10 DIF / BlockGuard - Merge from upstream: scsi: Fix up files implicitly depending on module.h inclusion - Fix driver behavior when receiving an ADISC - Fixed unbounded firmware revision string from port caused the system panic - Fix bug with driver processing dump command type 4 using 16Gb FC Adapter - Fix driver does not reset port when reset is needed during fw_dump - Fix ELS FDISC failing with local reject / invalid RPI - Changed SLI4 FC port internal loopback from outer serdes to inner internal - Fix REG_RPI fails on SLI4 HBA putting NPort into NPR state - Fix bug with driver processing an els command using 16Gb FC Adapter - Fix NMI seen due to CQE starvation - Fixed SLI4 FC port obtained 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 SLI4 16Gbit FC port internal and external diagnostic loopback tests - 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 shost lock protection on setting/clearing bit in vport->fc_flag - Fixed missing hbalock protection on setting/clearing bit in phba->link_flag - Fixed illegal state transition during driver unload - Fixed system crash on SLI4 FC port looopback diagnostic test with large buffers - Fixed a potential error path that might try to free DMA memory not allocated - Fixed SLI4 FC port Internal and External loopback diagnostic tests - 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 memory leak when running hba resets to SLI-4 board - Fix driver message 3092 and 3116 to KERN_WARNING - 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 - Support loop for sli4 fc pass-through - No longer read fcoe parameters if board is not fcoe - Fix bug with driver passing a wrong count value - Support restore state and error log when sysfs board_mode attribute access failed - Fixed a typo in two of the log messages just introduced - Support for SLI4_CONFIG non-embedded COMN_GET_CNTL_ADDL_ATTR pass-through - 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 - Return an error if the mbox sysfs is called - Fix firmware upgrade attempt on unsupported adapter - Fix incomplete message number 2889 - Fix system crash when ASIC fails to initialize - Fix virtual fabrics bit set in FLOGI incorrectly - Fix bug with driver not returning extended mailbox data - Fix unsupported link speed accepted by SLI4 port - Incremented minor management version to reflect additional "protocol" sysfs attribute - Modify WQ handling to use entry_repost - Moved link type definitions to apply to all driver streams - Support a sysfs attribute "protocol" to report SLI4 port link protocol type - Support SLI4 INTF_TYPE and SLI_FAMILY as sub-field to the fwrev sysfs attribute - Support structure to support T10 DIF in SLI4 - Fix performance slowed due to too many register accesses - Fixed a warning when converting from simple_strtoul to strict_strtoul - Support Initial code to inject T10 DIF errors - Fixed a possible driver crash when cfg_fcp_eq_count is zero - Fixed non-embedded COMMON_GET_CNTL_ATTR mbox command failed with status 0x4 - Fixed null pointer dereference after clearing FCP policy rules - Changed the way of SLI4 device detecting physical port name - Fixed FCP policy exchange management rule parsing - Support 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 - Fixed driver failed to follow IP reset procedure in SLI4 error attention handler - Fix sysfs lists fabric name for port that has been disconnected from fabric - Support FCP policy exchange management - Changed the timeout to 300 seconds for SLI_CONFIG (0x9B) mailbox command - Fixed fcp underrun reporting - Fixed a driver handling IP reset issue when PCI read return error - Fixed casting problem in calculating tx_words statistics - Support proper error code return for libdfc calling API to make proper decisions - Fix sli4 mailbox status code. Management software has dependencies - Fix compiler warning due to uninitialized local variable - Fix bus reset handler fails with bad failure code - 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 sysfs API mismatch for building against SLES11 SP2 beta kernel - Fixed scsi midlayer queuecommand API mismatch for SLES11 SP2 beta kernel - Fixed ctlreg write bug not checking key string and limiting bytes to write - Fix default adapter name for the OCe15100 - Fixed incomplete scsi messages displayed - Fix cable pull failure on interface type 2 SLI-4 adapters - Fix enable_bg config parameter for SLI4 - Fixed not able to perform firmware reset through sysfs board_mode attribute - 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 request firmware support for little endian systems - Fix driver firmware to match new firmware image format - Fixed SLI4 device firmware reset with SR-IOV virtual functions - Fix SLI4 CT handling for sequences > 4K - Fixed handling of unsolicited frames for vports - Fixed handling of CVL for vports - Fixed crash when aborting els IOs - Fix up CT and oxid/rxid for unsol rcv frames - Fixed mailbox double free panic - Support fcf priority record selection for fcf failover - Fixed compiler warning for putting large amount of memory on stack - Fixed driver build not building in debugfs even if kernel CONFIG_DEBUG_FS=y is set - Fix issue where the FC/FCoE Async Receive CQE did not scale for 16G FC adapters - FLOGI payload has Multiple N_port_ID set when lpfc_enable_npiv clear - Removed unused argument passed to the lpfc_bsg_diag_mode_enter routine - Fixed new ASIC device-mgmt BSG pass-through failed multi-buffer fw download - Support sysfs logging when writeable parameters are changed - Used PCI config space capability for sysfs get PF supported SR-IOV number of VFs - Support wait for SLI port status register for readyness following firmware reset - iDiag added SLI4 device PCI BAR memory mapped reigster access methods - Consolidated duplicating macro definitions - Fixed failure to enable PCIe AER prevent driver initialize and attach to device - Modified log messages for T10-PI processing - iDiag fixed mailbox capture and dump overlapping bitmap macro definition
=============================================================================== Emulex 16GB FC Firmware Package ===============================================================================
Firmware Version: 10.2.377.29 Supported On: System x
Problems Fixed: - None
Incremental Interoperability: - None
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159504)
Firmware Version: 10.2.377.18 Supported On: System x
Problems Fixed: - Link does not recover during IO + Port Cycling with FW 1.1.43.3 - BIOS versions return multiple values - LPe16k point to point (direct attached) connection not bootable in legacy BIOS - LPe16k point to point (direct attached) connection performance issues in legacy BIOS
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159504)
Firmware Version: 10.2.261.36 Supported On: IBM System x and Flex
Problems Fixed: - Server will halt on black screen during rolling reboot of Windows 2012 x64 uEFI SANboot - Server intermittently fails to boot during rolling SANboot (any OS) - Fixed a boot hang associated with server BIOS change - Reported firwmare version in CMM is intermittently incorrect - Unable to set pause Flow control when connected to DCBX switch with PFC off - during cable pull testing a 40 second delay in link up experienced with Brocade switch ports - I/O completion and abort completion WQE are generated out of order - Unexpected WCQE in RQ CQ seen in RXRI mode while performing cable pulls
Incremental Interoperability: - Inventory support for the Flex xHMC (Chassis Hardware Management Console) - Crosslink & Express Lane on LPe16k based solutions
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159504)
Firmware Version: 1.1.43.21 Supported On: IBM System x
Incremental Interoperability: - None
Problems Fixed: - Server will halt on black screen during UEFI rolling reboot reboot cycle test with 16Gb HBA under Windows 2012 x64 - Allows installing and booting from an MSA2040 array configured in PT-PT direct mode at 16G speed. We're now able to enable Autoscan and install/boot from multiple OSes - Added support to bypass configuring pnp Boot Table in a multipath situation. Fixes Microsoft Windows Server 2008 bug. - Fixed the "Read Rev Failure" issue during POST to accept "0" address value as a valid. - Fixed the wrong VPD HBA model number display on the banner and properties, and change the proper VPD data field size. - Fixed the timeout issue on Flogi when try to select a HBA device without connecting to a target or FC switch. - System will halt during reboot cycle test under Windows 2012 x64 UEFI - Fixing PCI Function Number decoding issue in BOFM code - Boot fails during SLES11 SP3 rolling reboot - Enable BFS and update the NVRAM if BOFM target is available - Add Diagnostic support for UEFI 16Gb FC - Reconnect menu item causes a System BIOS exit request only on AMI core system BIOS - Adding port's protocol name and WWPN in browser help menu
Firmware Version: 1.1.43.12 Supported On: IBM System x and Flex
Incremental Interoperability: - IBM Flex System FC5052 2-port 16Gb FC Adapter - IBM Flex System FC5054 4-port 16Gb FC Adapter - FC support for support for ASU/Config Patterns for Flex and ASU for IBM System x & BladeCenter - Direct PT - PT connections - Extended SCSI Pass Thru Protocol - IBM Tape unit interoperability - see SSIC for more information - SLES 11.3 on IBM System x
Problems Fixed: - Windows 2012 OS will not resume from Sleep mode - Boot Device entries can be lost after exiting from BIOS setup
Firmware Version: 1.1.21.9 Supported On: IBM System x
Incremental Interoperability: - IBM Server machine types. Refer to IBM ServerProven for specifics
Problems Fixed: - Fixed FCP_CONF handling bug - No SRR sent after drop write data frame, I/O fails - Adapter does not invoke recovery after dropped read data frame - I/O throughput performance improvements - Link failover when connected to FC Tape - Cosmetic: Cleaned up miscellaneous error handling messages in debug log files - If a new device comes online and attempts to acquire an AL_PA after the link has already come up, the FC link appears to hang until the cable is pulled - Cleaned up link negotiation at 4GB/8GB/16GB speeds with specific switches
Firmware Version: 2.02x11 Boot Code Version: 5.30a3 Supported On: System x, BladeCenter and Flex
Problems Fixed: - None
Incremental Interoperability: - Grantley based ITE
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.02x11 Boot Code Version: 5.30a3 Supported On: System x and BladeCenter
Problems Fixed: - Roll boot code version number to avoid conflict with IBM UXSPi updates
Incremental Interoperability: - Inventory support for the System x xHMC (Chassis Hardware Management Console) for IBM Rack FC HBAs - Grantley Rack Servers
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.02x11 Boot Code Version: 5.13x4 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Server intermittently fails to boot during rolling SANboot (any OS) - Fixed a boot hang associated with server BIOS change
Incremental Interoperability: - Inventory support for the Flex xHMC (Chassis Hardware Management Console)
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159225)
Firmware Version: 2.01a11 Boot Code Version: 5.12a13 Supported On: IBM System x and BladeCenter
Problems Fixed: - Emulex FC Adapter does not auto-enable SAN boot mode when boot target configuration is made via IFM (BOFM) - Emulex FC configuration utility is in the wrong F1 setup screen - IBM CIOv adapter connected to Brocade 8 Gig FC BladeCenter switch intermittently Links up at less than 8 Gig
Firmware Version 2.01a3 Boot Code Version: 5.12a5 Supported On: IBM System x and BladeCenter
Incremental Interoperability: - Enhanced timeout notifications for processing abort failures.
Problems Fixed: - All multi-abort I/Os are returned on the same ring from which the ABORT_MXRI command was received. - Changed the TRCV response in the abort state to CMD RJT to enable the TRSP to be processed. - Corrected an issue with blocked TSEND operations. - Corrected a buffer leak issue with RRQ exchanges. - Corrected an issue where the TRCV IOCB was de-queued improperly causing a XFR_RDY flood. - Corrected an issue where the OXID field was not loaded in the XRI_ABORTED IOCB. - Corrected an issue in recognizing whether an EEPROM is present.
* ISP83xx CNA support * IDC support for three protocols. * Loopback support. * Beacon support.
* Added support for bidirectional commands
* Added support for MCTP dump
* ISP83xx(16G FC) support for Xenserver 6.0 and Oracle UEK.
* SRB Consolidation.
* RSCN handling changes.
* Increase in support of maximum fibre devices.
* Enhancements to support ISP83xx (Limited support). * Driver features supported * 10GB link support only * Port device discovery * LUN discovery * I/O * Perturbations * SG resets of host and SCSI devices.
* Driver features not supported * Beacon support * Loopback * T10 DIX/DIF * SFP read/write * QCC GUI Support * QCC CLI Support * NPIV * Multi-Queue * Boot from SAN * FC-Tape * SLES10.3 driver: * Fix not to MPI reset on ISP83xx is not included.
* Implemeted beacon on/off for ISP82xx.
* Add support for ISP82xx to capture dump (minidump) on failure.
* Provide method for updating I2C attached VPD.
* Resync with latest ISP24xx/25xx firmware (5.08.00).
Industry Standards Compliance ----------------------------- * N/A
3. Bug Fixes
The following fix has been made to the Fibre Channel and FCoE Adapter Inbox Driver Update for Linux Kernel 2.6.x and 3.x:
* 8.04.00.12.xx.y-k * Update the copyright information. * Display the lock owner on lock acquire failure. * Move loopback mode reset after chip reset check. * Extra loopback error handling for ISP83xx. * Do link initialization on get loop id failure. * Do MPI reset only for 81xx.
V2632 (RHEL 6.x, SLES 11.x, Citrix 6.0, UEK): * Revert "qla2xxx: Optimize existing port name server query matching." * Revert "qla2xxx: Avoid losing any fc ports when loop id's are exhausted." * Don't free pool that wasn't allocated. * Unload hangs after issuing BSG commands to vport.
Citrix 6.0: * Create initrd as a part of installation and removal of the driver rpm. * RPM install should install driver under extra instead of driver directory.
RHEL 5.x, SLES 10.x: * MBA_IDC_NOTIFY case should fallthru. * Add fw_dump_size sysfs attribute file. * Add test for validity of virtual host in netlink interface.
SLES 10.x: * Add 8031/2031 cases to request firmware.
* 8.04.00.11.xx.y-k * Move marking fcport online ahead of setting iiDMA speed. * Add 16Gb/s case to get port speed capability. * Get VPD information from common location for CNA. * Dont clear drv active on iospace config failure. * Display that driver is operating in legacy interrupt mode. * Add "16" speed to link speeds array in qla2x00_iidma_fcport() function * Correct race in loop_state assignment during reset handling. * Reject loopback request if one is already in progress. * Update the FTP site references in the driver sources.
V2632 (RHEL 6.x, SLES 11.x Citrix 6.0 and UEK): * Obtain loopback iteration count from bsg request. * Parameterize the link speed string conversion function. * Update ql2xextended_error_logging parameter description with new options. * Fix typo in qla2xxx driver. * Free rsp_data even on error in qla2x00_process_loopback(). * Avoid null pointer dereference in shutdown routine.
RHEL 5.x: * Remove fabric_logout() calls from qla2x00_dev_loss_tmo_callbk() function.
SLES10.x: * Clear local references of rport on device loss timeout notification from FC transport.
* 8.04.00.10.xx.y-k * Honor status value of 2 for report-id acquisition. * Ignore driver ack bit if corresponding presence bit is not set. * Add Gen3 PCIe speed 8GT/s to the log message. * Acquire risc semaphore before resetting ISP.
V2632 (RHEL 6.x, SLES 11.x Citrix 6.0 and UEK): * Ramp down queue depth for attached SCSI devices when driver resources are low. * Determine the number of outstanding commands based on available resources. * Fix for kernel crash when external loopback diagnostic is run through BSG interface. * Fix coccinelle warnings in qla2x00_relogin. * Test and clear FCPORT_UPDATE_NEEDED atomically. * Use correct Request-Q-Out register during bidirectional request processing * Fix typo in qla83xx_fw_dump function. * Move noisy Start scsi failed messages to verbose logging level. * Fix for warnings reported by sparse.
RHEL 5.x: * Inclusion of 4G/8G firmware version 5.08.00. * Log message when qla2xenablemsix module parameter is set to 2( MSI mode) and adpater does not support MSI mode. * Revert "qla2xxx: Use GFF_ID to check FCP-SCSI FC4 type before logging into Nx_Ports" * Revert "qla2xxx: No fcport FC-4 type assignment in GA_NXT response."
Citrix 6.x: * RPM build should hide the directory naming convention from user.
* 8.04.00.09.xx.y-k * No fcport FC-4 type assignment in GA_NXT response. * Fix checkpatch error in qla2xxx_mctp_dump. * Change in setting UNLOADING flag and FC vports logout sequence while unloading qla2xxx driver. * Clear unsupported 'states' during Get-FW-State queries.
V2632 (RHEL 6.x, SLES 11.x Citrix 6.0 and UEK): * Pass correct parameters while creating an initrd. * Remove spurious taking of ha->vport_slock spinlock.
UEK: * Add macro for kernel extended version.
RHEL 5.x: * Use GFF_ID to check FCP-SCSI FC4 type before logging into Nx_Ports. * Pass correct parameters while creating an initrd.
8.04.00.08 Initial release of Qlogic 10Gb FC Driver for RHEL5
qlgc_dd_fc_qla2xxx-8_07_00_083c_sles11_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.5m 03/31/2015 Copyright (c) 2015 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.
Release Notes QLogic bnx2 Linux Driver Version 2.2.5m 01/20/2015 QLogic cnic Linux Driver Version 2.5.20e 01/20/2015
Copyright (c) 2004 - 2014 Broadcom Corporation Copyright (c) 2014 - 2015 QLogic Corporation All rights reserved
bnx2 2.2.5m (January 20, 2015) ================================ Enhancements ----- 1. Change: Merge re-branding changes to the main branch.
Impact: N/A
Fixes -----
1. Problem: Out of memory issue when the adapter is reset. This was reported by a customer.
Cause: kmalloc() failure in bnx2_gunzip_init() during memory fragmentation conditions (~40K contiguous physical memory is not available).
Change: Use vmalloc() instead of kmalloc() for uncompressing the firmware buffer.
2. Problem: UDP packets cannot pass to the upper application, packets are filtered out by our driver or firmware.
Cause: SORT mode was enabled in the code to fix a WOL issue on adapter series 5706/5708.
Change: We have found that disabling SORT mode in chip_init routine fixes the issue reported. We have verified WOL is functioning on 5709/5716 adapters after disabling SORT mode in chip_init.
cnic 2.5.20e (January 20, 2015) ============================ Enhancements ------------ 1. Change: Merge re-branding changes to the main branch.
1. Problem: Fix compilation warnings in newer kernels due to changes introduced in RHEL6.6 support.
Cause: Warnings due to incompatible pointer type initialization because netdev_features_t is 64-bits in newer kernels whereas in RHEL6.6 kernel it is defined to 32-bit.
Change: Change Makefile to look for netdev_features.h to define netdev_features_t as appropriate. Also added check to prevent calling set_netdev_ops_ext() API since kernel expects not to mix ndo_fix_features/ndo_set_features with ethtool_ops.
Cause: Rearrangement of new hw_features flag with the introduction of new structure net_device_ops_ext and APIs and multiple redefinitions.
Change: Added checks to avoid multiple redefinitions of APIs. The features and hw_features are assigned and get_netdev_hw_features() and set_netdev_hw_features() for RHEL6.6 specific checks.
2. Problem: Fix netdev features for newer kernels.
Cause: hw_features in netdev for newer kernels was not getting set.
Change: hw_features field in nedev needs to be set for user selectable features. Added NETIF_F_RXCSUM flag in hw_features and features field of netdev to change rx checksum using ethtool.
Impact: Added support for RHEL6.6 and newer kernel.
bnx2 2.2.5jr (August 21, 2014) =========================== Enhancements ----- 1. Change: As part of re-branding Linux bnx2 driver, removed NetXtreme II/NX2/Nx2 keywords
Impact: N/A
cnic 2.5.20dr (August 21, 2014) ============================ Enhancements ------------ 1. Change: As part of re-branding Linux cnic driver, removed NetXtreme II/NX2/Nx2 keywords
Impact: N/A
bnx2 2.2.5ir (July 30, 2014) =========================== Enhancements ----- 1. Change: Added re-branding changes for Linux bnx2 driver
Impact: N/A
cnic 2.5.20cr (July 30, 2014) ============================ Enhancements ------------ 1. Change: Added re-branding changes for Linux cnic driver
bnx2 2.2.5i (July 22, 2014) =========================== Enhancements ------------ 1. Change: (CQ74921)Revert changes for Broadcom re-branding for Linux bnx2 & cnic OOB drivers
Impact: N/A
cnic 2.5.20b (July 22, 2014) ============================ Enhancements ------------ 1. Change: (CQ74921)Revert changes for Broadcom re-branding for Linux bnx2 & cnic OOB drivers
Impact: N/A
2. Change: Added upstream patch to sync up with upstream driver cnic,bnx2i,bnx2fc: Fix inconsistent use of page size
The bnx2/bnx2x rings are made up of linked pages. However there is an upper limit on the page size as some the page size settings are 16-bit in the hardware/firmware interface. In the current code, Some parts use BNX2_PAGE_SIZE which has a 16K upper limit and some parts use PAGE_SIZE. On archs with >= 64K PAGE_SIZE, it generates some compile warnings. Define a new CNIC_PAGE_SZIE which has an upper limit of 16K and use it consistently in all relevant parts.
Impact: FCoE, iSCSI
Fixes -----
1. Problem: (CQ74840) Compilation Error in cnic driver for RHEL 6.3 and SLES 11.1
Cause: Undefined rcu_access_pointer in RHEL 6.3 and SLES 11.1
Change: cnic need to use rcu_access_pointer to obtain the object reference but this routine is not defined in older RHEL and SLES distros. Added call to rcu_access_pointer using macro for RHEL 6.3 and SLES 11.1
Impact: iSCSI and FCoE
2. Problem: Compilation failure in cnic driver for RHEL 6.5
Cause: Undefined enum _DEFINE_SKB_SET_HASH and skb_set_hash() in RHEL 6.5.
CNIC driver includes bnx2x.h header file. There were some changes made in bnx2x driver using enum _DEFINE_SKB_SET_HASH and skb_set_hash() API. As a result of this change the cnic build failed due to those missing definitions.
Change: Added enum _DEFINE_SKB_SET_HASH and skb_set_hash() in bnx2_compat.h under a new define D_DEFINE_SKB_SET_HASH. In the Makefile, add a rule to check if skb_set_hash() is defined in skbuff.h. If not, then D_DEFINE_SKB_SET_HASH is added to the EXTRA_CFLAGS which would pickup the definitions from bnx2_compat.h.
Impact: bnx2, iSCSI and FCoE
3. Problem: (CQ74942)Kernel panic on CNIC driver load on sles12
Cause: Bug in kernel version code check
Change: Use proper version check macro
Impact: bnx2, iSCSI and FCoE on sles12
bnx2 2.2.5h (June 24, 2014) =========================== Enhancements ----- 1. Change: (CQ74364)Re-branding for Linux bnx2 driver
Impact: N/A
cnic 2.5.19e (June 24, 2014) ============================ Enhancements ------------ 1. Change: (CQ74364)Re-branding for Linux cnic driver
Impact: N/A
package 2.710.52 (June 18, 2014) ============================ Fixes ----- 1. Problem: cnic module does not compile on Xen/REHL5 kernels
Cause: rcu_access_pointer macro is not part of Xen/RHEL5 kernels.
Change: (CQ74100) Define the macro rcu_access_pointer in the driver code if required.
Impact: Xen/REHL5 kernels
2. Problem: (CQ74192) bnx2.c:4387: warning: assignment discards qualifiers from pointer target type
cnic 2.5.19d (June 11, 2014) ============================ Enhancements ------------ 1. Change: (CQ74187) Use proper netdev API for abstracting netdev upon receiving any netdev event
Impact: N/A
Fixes -----
1. Problem: (CQ73766, RHEL BZ1079384) bnx2fc: kernel BUG: sleeping function called from invalid context
Cause: cnic_rcv_netevent() calls ulp_ops->indicate_netevent() under a rcu_read_lock(), that makes the context atomic and bnx2fc_indicate_netevent() takes a mutex. Hence the sleeping-in-atomic causing call trace.
Change: Because the called function, such as bnx2fc_indicate_netevent(), can sleep, we cannot take rcu_lock(). To prevent the rcu protected ulp_ops from going away, we use the cnic_lock mutex and set the ULP_F_CALL_PENDING flag. The code already waits for ULP_F_CALL_PENDING flag to clear in cnic_unregister_device().
Impact: FCoE
2. Problem: (CQ73766, RHEL BZ1094613) ifdown/ifup repeatedly on a fcoe interface causes call trace in cnic_alloc_uio_rings
Cause: We are allocating memory with GFP_KERNEL under spinlock.
Change: Don't take cnic_dev_lock in cnic_alloc_uio_rings(). Since this is the only call manipulating the cnic_udev_list and it is always under rtnl_lock, cnic_dev_lock can be safely removed.
Change: The iSCSI netlink message needs to be sent before the ulp_ops is cleared as it is sent through a function pointer in the ulp_ops. This bug causes iscsid to not get the message when the bnx2i driver is unloaded.
Impact: iSCSI
4. Problem: (CQ74100/BZ1087813) suspicious RCU usage in cnic driver
Cause: Calling rcu_dereference without rcu_read_lock.
Change: cnic need to access the object protected using rcu lock. If rcu_dereference is called without proper read_rcu_lock, RCU debug print stack with suspicious lock issue. If there is a need to access the object without read lock rcu_access_pointer need to be used instead.
Impact: iSCSI and FCoE
cnic 2.5.19c (May 14, 2014) ============================ Enhancements ------------ 1. Change: Added support for UFP FCOE
Impact: FCoE in UFP mode only.
Fixes ----- 1. Problem: (CQ73854)No LUNs discovered in UFP mode, (CQ73853)Kernel stack trace at scsi_eh_2 in UFP mode, (CQ73820)bnx2x driver asserted with driver v7.10.35
Cause: FCP command is going out with VLAN ID 0 (Null VLAN ID). The VLAN tag was missing from the FCP packet as VLAN flag was set to zero in offload_connection and enable_connection ramrods.
Change: vlan_flag in the fcoe_kwqe_conn_offload3 should be set to 1 before sending offload_connection and enable_connection ramrods. Removed code block clearing vlan_flag in fcoe_kwqe_conn_offload3 before calling offload_connection in UFP mode.
Impact: FCoE in UFP mode only.
cnic 2.5.19b (Mar 05, 2014) ============================ Enhancements ------------ 1. Change: Add support for FCoE in UFP mode according to the UFP HSI. The support is transparent to bnx2fc.
Impact: FCoE in UFP mode only.
package 2.710.10 (Feb 25, 2013) =============================== Fixes ----- 1. Problem: Package does not compile on newer kernels
Cause: kernel compatibility issue.
Change: Added new CFLAGS from bnx2x Makefile for bnx2x_compat.h.
Impact: Newer distributions such as RHEL7.
bnx2 2.2.5f (Feb 20, 2014) =========================== Fixes ----- 1. Problem: (CQ72407) "shutdown -h now" causes NMI on 5709 in some scenarios.
Cause: If the function has not been brought up (ifup), system shutdown will cause a WAIT3 and D3 sequence without prior chip reset. This may cause the firmware to power down the PHY which will cause the function to become unresponsive to MMIO reads. The CPU will timeout and NMI as a result.
Change: Added some logic to tell firmware to skip the PHY power down.
Impact: 5709 only. Only ifdown and system shutdown sequences are affected. No run-time impact.
bnx2 2.2.5e (Feb 05, 2014) =========================== Enhancements ------------ 1. Change: Indication if the driver is beta or release in a printk upon firmware dump.
Impact: ESX only.
cnic 2.5.18d (Feb 05, 2014) ============================ Fixes ----- 1. Problem: (CQ72694) Crash in bnx2x_cnic_notify() when getting iSCSI statistics.
Cause: Calling bnx2i_get_stats() after bnx2i has unregistered the device.
Change: cnic should use the per device RCU protected cp->ulp_ops[] when making the upcall to get statistics. It was incorrectly using the global cnic_ulp_tbl which is always valid even if individual devices have been unregistered.
Impact: iSCSI and FCoE
bnx2 2.2.5d (Jan 14, 2014) =========================== Fixes ----- 1. Problem: (CQ71941) Kernel panic when loading bnx2 driver on RHEL6.5 with inbox cnic driver loaded.
Cause: Incompatibility with inbox cnic driver.
Change: Added padding in bnx2 structure so that the inbox cnic driver will always detect NULL in the cnic_probe field.
Impact: RHEL6.5 and newer kernels (SLES11SP3 is not affected)
bnx2 2.2.5c (Jan 06, 2014) =========================== Enhancements ------------ 1. Change: Added ability to read PCI config registers and indirect memory via the ESX private IOCTL.
Impact: bnx2 ESX only.
2. Change: Add reporting of MDI/MDIX status to ethtool.
Impact: Copper devices only.
bnx2 2.2.5b (Nov 18, 2013) =========================== Fixes ----- 1. Problem: (CQ71793) 5709 sometimes does not link up in 100Mbps forced speed.
Cause: PHY advertisement register needs to be set to 0 when speed is forced. The default advertisement register value is 10 Mbps and it will not link up when the speed is 100 Mbps.
Change: Set advertisement register to 0 when speed is forced.
Impact: 5709C forced speed.
bnx2 2.2.4g (Nov 07, 2013) =========================== Fixes ----- 1. Problem: PHY loopback test fails when set to 100Mbps on 5708 Copper.
Cause: Regression caused by enabling auto-MDIX (PHY reg 0x18 shadow 7 bit 9).
Change: Disable it on 5708.
Impact: 5708 only.
bnx2 2.2.4f (Oct 29, 2013) =========================== Fixes ----- 1. Problem: Netqueue didn't get stop and re-initialized properly during reset task, change coalece setting, and self test operations.
Cause: Normal Netqueue stop and re-initialized operations weren't executed while the device went through a full reset.
change: Added proper Netqueue stop/start operations in the above code paths.
Impact: ESX only.
cnic 2.5.18c (Oct 29, 2013) ============================ Enhancements ------------ 1. Change: Add signature to the iSCSI TX doorbell to prevent iscsiuio from getting the wrong value when using older kernel drivers.
Impact: bnx2x iSCSI only.
bnx2 2.2.4e (Oct 23, 2013) ============================ Enhancements ------------ 1. Change: (CQ69514) Enable auto-MDIX when autoneg is disabled by setting copper PHY register 0x18 shadow 7 bit 9.
Impact: All bnx2 copper devices.
2. Change: Display driver version in vmkernel.log during ESX fw dump.
Impact: ESX only.
package 2.78.33 (Sept 23, 2013) =============================== Fixes ----- 1. Problem: Package does not compile on Xen Server 6.2
Cause: kernel compatibility issue.
Change: Added new CFLAGS from bnx2x Makefile for bnx2x_compat.h.
Impact: All distributions. These fixes are only compatible with bnx2x 1.78.56 and newer.
bnx2 2.2.4d (Sept 12, 2013) ============================ Fixes ----- 1. Problem: cnic irq failed to run after esxcli network nic down/up event.
Cause: esxcli network nic down/up event causes bnx2 driver go through bnx2_close and bnx2_open. The sequence of events will re-allocate status block memory and the new status block memory address is not communicated to cnic after bnx2_open.
Impact: bnx2 ESX only.
cnic 2.5.18b (Sept 12, 2013) ============================ Fixes ----- 1. Problem: iSCSI does not work with bnx2x 1.78.52.
Cause: bnx2x doorbell change not compatible with existing iscsiuio.
Change: Pass modified iSCSI CID to iscsiuio for backwards compatibility.
Impact: bnx2x iSCSI.
2. Problem: Panic in cnic after ifdown/ifup bnx2x iSCSI device.
Cause: Accessing uninitialized FCoE EQ. Bug introduced in 2.5.17c which started using bnx2x NO_FCOE macro. cnic did not consistently use NO_FCOE, causing FCoE EQ to be accessed by mistake.
Change: Use NO_FCOE macro consistently in cnic code.
Impact: FCoE.
bnx2 2.2.4c (Aug 30, 2013) ============================ Enhancements ------------ 1. Change: Fix compile errors see on ESX * struct chip_core_dmp definition conflicts with bnx2x, scoped this struct to have a bnx2 prefix * Compiled FW dump for ESX5.5
Impact: bnx2 ESX only.
cnic 2.5.17c (Aug 30, 2013) ============================ Fixes ----- 1. Problem: cnic crash when shutting down 57811 device.
Cause: 57811 Chip ID not reconized by cnic.
Change: Re-structured code to use common bnx2x macros for Chip ID, port ID, pfid.
Impact: iSCSI and FCoE on all bnx2x devices.
bnx2 2.2.4b (Aug 12, 2013) ============================ Fixes ----- 1. Problem: CQ70286 IOVP: PSOD while executing NIC up/down command using esxcli.
Cause: New bnx2_free_irq() also disable MSIX/MSI on the device during bnx2_close. When bnx2_open is called, driver attempt to get INTA interrupt instead of MSIX/MSI interrupt.
Change: Don't disable MSIX/MSI on the device upon close.
Impact: ESX only.
2. Problem: WoL does not work during suspend if device is not up.
Cause: WoL setup skipped in bnx2_suspend() if device is not up.
Change: Always setup WoL in bnx2_suspend().
Impact: bnx2 suspend.
Enhancements ------------ 1. Change: Update 5709 firmware to 6.2.1.c to include mechanism to flush the iscsi OOO ring to silence some error messages about stale hardware index.
Impact: iSCSI on these bnx2x devices where the iSCSI license can only be fully determined after firmware is loaded.
2. Change: Changes to match the new 5709 6.2.1.c firmware to flush the iSCSI OOO ring.
Impact: 5709 iSCSI.
bnx2 2.2.3t (July 23, 2013) ============================ Fixes ----- 1. Problem: CQ70262 IVOP: PSOD HeavyIOChangeMTU test on 5709 card.
Cause: During ring size change, bnx2_free_irq() was called without checking reset_irq flag.
Change: Don't call bnx2_free_irq() if reset_irq flag is false.
Impact: ESX only.
2. Problem: (CQ69619) ethtool NVRAM operations fail when device is down.
Cause: Driver checks and prevents NVRAM operations when device is down.
Change: Remove the check. The driver now stays in D0 power state when the device is down and NVRAM operations are possible.
Impact: ethtool -e|-E
cnic 2.5.16j (July 23, 2013) ============================= Fixes ----- 1. Problem: (RHEL BZ 759217) System hangs when attempting iSCSI connections on 57711E.
Cause: iSCSI license changes from supported to unsupported between bnx2x probe and bnx2x open. bnx2i is unaware that the device does not support iSCSI and attempts to do offload which never completes. The recent change to eliminate symbol_get() to obtain bnx2x_cnic_probe() exposed the problem.
Change: Check iSCSI license again during ->drv_register_cnic(). If there is no iSCSI license, skip ->ulp_start().
Impact: iSCSI on these bnx2x devices where the iSCSI license can only be fully determined after firmware is loaded.
bnx2 2.2.3s (June 27, 2013) ============================ Fixes ----- 1. Problem: PCI shutdown function does not work on ESX.
Cause: system_state and SYSTEM_POWER_OFF not defined.
Change: Added compatibility code.
Impact: ESX only.
bnx2 2.2.3r (June 27, 2013) ============================ Enhancements ------------ 1. Change: (CQ68271, 68277) In order to support ethtool NVRAM operations when the device is down, the following changes were made:
- converted to use new WoL and PM kernel APIs - removed power state changes during open and close - added pci shutdown function to setup WoL during shutdown - converted to new style suspend/resume driver APIs
Impact: Everything related to WoL, shutdown, suspend, resume. Because of the significant changes, the system should be rebooted after running "make install" for the new driver. Without reboot, the new driver may not work as it is not aware that the older driver has put the device into D3hot state.
bnx2 2.2.3q (May 24, 2013) ============================ Enhancements ------------ 1. Change: Simplified compatibility code for driver section macros, __devinit, __devexit, etc.
Impact: None.
bnx2 2.2.3p (May 23, 2013) ============================ Fixes ----- 1. Problem: Bootcode firmware may not detect new message from driver. (VMWare reported issue)
Cause: The initial sequence number may not be unique enough.
Change: Read from the firmware mailbox and add one to it as the initial sequence number.
Impact: All devices.
Enhancements ------------ 1. Change: Made changes to compile on the latest 3.x kernels.
Impact: All.
cnic 2.5.16i (May 23, 2013) ============================= Fixes ----- 1. Problem: (CQ69177) MTU change causes PSOD at bnx2x_drv_ctl
Cause: The OOO handler was falsely triggered to handle OOO tx completions even when bnx2x has failed to allocate resources for the OOO ring. This has caused bnx2x to hit a NULL ptr dereference.
Change: Fixed the cnic OOO handler.
Impact: bnx2x iSCSI only.
cnic 2.5.16h (April 30, 2013) ============================= Enhancements ------------ 1. Change: Added max_fcoe_exchanges parameter so that bnx2fc can support multiple FCoE ports on a device.
Impact: FcoE only.
bnx2 2.2.3o (April 30, 2013) ============================ Fixes ----- 1. Problem: (BDKL225) __napi_schedule assertion when bnx2 switch from MSI to INTx.
Cause: NAPI was not disabled before IRQ is freed when switching from msi mode to INTA mode which prevents VMkernel from updating the stale napi->intr_cookie value.
Change: Disabled NAPI before free IRQ and then re-enable NAPI after chip is re-initialized. In addition, enabling of NAPI should always be done after chip_init().
Impact: All.
bnx2 2.2.3n (Mar 11, 2013) ========================== cnic 2.5.16g (Mar 11, 2013) ========================== Fixes ----- 1. Problem: cnic driver does not compile on XEN server.
Cause: Shared bnx2x_compat.h relies on some CFLAGs to compile properly on XEN server.
Cause: Firmware bug and cnic error handling bug for TCP_CLOSE ramrod.
Change: Added check for iscsi completion error when receiving the TCP_CLOSE ramrod completion.
Impact: bnx2x iSCSI only.
bnx2 2.2.3m (Jan 28, 2013) ========================== cnic 2.5.16e (Jan 28, 2013) =========================== Fixes ----- 1. Problem: (CQ67528) cnic/bnx2 crash when both drivers are loaded on some kernels.
Cause: Shared struct bnx2 compiled differently on bnx2 and cnic, causing cnic to reference the wrong field.
Change: Added bnx2_compat0.h to define the common CFLAGs that affect structure sizes for both drivers to include.
Impact: All (if cnic is loaded)
bnx2 2.2.3k (Jan 25, 2013) ========================== Fixes ----- 1. Problem: CNIC driver didn't get started after bnx2_open().
Cause: CNIC driver is stopped when bnx2_close() is invoked. However, there is no equivalent turn on mechanism when bnx2_open() is called. The issue prevent bnx2i to offload iscsi connections during session recovery.
Change: Added equivalent cnic start procedure in bnx2_open().
Impact: ESX only.
cnic 2.5.16d (Jan 25, 2013) =========================== Fixes ----- 1. Problem: (CQ67375) Unable to turn iSCSI TCP delayed ACK on after it's been turned off.
Cause: tcp_flags in cnic's socket structure not cleared between destroy and create calls.
Change: Clear tcp_flags during socket create call.
Impact: iSCSI only.
2. Problem: (CQ67306) iSCSI TCP delayed ACK not working.
Cause: Firmware HSI change.
Change: Adapted to new firmware HSI which is now defining delayed ACK globally for the HBA.
Impact: iSCSI only.
cnic 2.5.16c (Jan 15, 2013) =========================== Fixes ----- 1. Problem: cnic does not compile on SLES11SP2.
Cause: bnx2x_compat.h conflicts with SLES11SP2 header files.
Change: Modilfed Makefile to detect SLES distribution so that the proper CFLAG can be defined for bnx2x_compat.h
Impact: SLES distributions only.
cnic 2.5.16b (Dec 12, 2012) =========================== bnx2 2.2.3j (Dec 12, 2012) ========================== Enhancements ------------ 1. Change: (CQ60429, 66302) Simplify cnic probing by not using symbol_get(). symbol_get() is unreliable as it fails while the network driver is still initializing.
Impact: iSCSI and FCoE (driver loading and unloading).
Cause: Race condition during simultaneous remote reset and local TCP close/reset. This may be a partial fix and additional fixes in other areas/drivers may be necessary to completely address all symptoms.
Change: If remote reset is detected to be in progress during local close/reset, it will wait for outstanding RAMRODs to complete. Without the wait, bnx2i will proceed to destroy the connection while the SRCH_DELETE/TERM_OFFLOAD RAMRODs are still pending.
Impact: bnx2x iSCSI only.
bnx2 2.2.3i (Nov 05, 2012) ========================== Enhancements ------------ 1. Change: (CQ65960) Make minor compatibility changes to support RHEL6.4
Impact: None.
2. Change: Added support for latest 3.x kernels.
Impact: All supported kernels.
cnic 2.5.14c (Nov 05, 2012) ========================== Fixes ----- 1. Problem: (CQ65178) Panic when loading and unloading cnic with bnx2i and bnx2fc.
Cause: The iSCSI EQ does not get reset during cnic init. When we get the first cnic IRQ, the iSCSI EQ index may be non-zero in the status block, causing the cnic driver to dereference NULL pointer.
Change: Added code to clear the iSCSI EQ index in the STORM memory.
Impact: 10G iSCSI.
bnx2 2.2.3h (Oct 16, 2012) ========================== Fixes ----- 1. Problem: Netdump crash when runing with ESX6.0 OS.
Cause: bnx2 poll controller routine is not compatible with ESX6.0.
Change: For ESX6.0, bnx2 will use ESX poll controller for netdump.
Cause: There is race condition where netdev_watchdog() could erroneouly flag tx timeout in a small window when bnx2_netif_stop() disabled tx queue state while carrier is still on.
Change: Carrier must be turned off before netif_tx_disable() is called.
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.
=============================================================================== Emulex iSCSI Device Driver for Linux ===============================================================================
Device Driver Version: 10.2.377.25 Supported On: System x and BladeCenter
Problems Fixed: - OCl14102 LOM UEFI RHEL7 MPIO not working
Device Driver Version: 10.2.365.0 Supported On: System x and BladeCenter
Problems Fixed: - be2iscsi rpm is failing with dependencies error - Unable to iSCSI SAN install RHEL/SLES/WIN2012R2 with UFP - Server is getting rebooted when we run IPv4+IPv6 bi-di NIC traffic simultaneously on UMC enabled interfaces
Device Driver Version: 10.2.261.1 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - Write error while running traffic - System crashed after running converged IO with driver load unload in a - Possible backlog of eq might happen if _process_cq keep processing for a long time: causes fw UE - Driver memory leak resulting in "DMA: Out of SW-IOMMU space" errors in dmesg file output
Device Driver Version: 10.0.803.21 Supported On: IBM System x
Problems Fixed: - Unable to OEMSEAddTarget or OEMSEDiscoverTaget successfully and get entries in mili2d.log - Emulex drivers are not working on RHEL5 and RHEL6 errata kernel updates - IO Read/Write almost halts with 'DMA: Out of SW IOMMU space' messages while running iSCSI Multipath I/O
Device Driver Version: 4.4.175.0 Supported On: IBM Flex
Problems Fixed: - Cleaned up a cosmetic problem with warning messages during driver compile from source - System crashes when we run simultaneous IO to 6 vNIC’s with iSCSI IO - Linux kdump kernel crashes during shutdown after capturing dump, if be1iscsi driver running
Device Driver Version: 4.1.402.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - 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
Device Driver Version 4.1.334.39 Supported On: IBM System x and BladeCenter
Problems Fixed: - Emulex: Warning messages seen while building Emulex drivers on RHEL platform - Unable to load be1iscsi driver during iSCSI boot OS install - Modprobe be1iscsi hangs when system with max targets login - be1iscsi 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
=============================================================================== Emulex 16GB FC Firmware Package ===============================================================================
Firmware Version: 10.2.377.29 Supported On: System x
Problems Fixed: - None
Incremental Interoperability: - None
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159504)
Firmware Version: 10.2.377.18 Supported On: System x
Problems Fixed: - Link does not recover during IO + Port Cycling with FW 1.1.43.3 - BIOS versions return multiple values - LPe16k point to point (direct attached) connection not bootable in legacy BIOS - LPe16k point to point (direct attached) connection performance issues in legacy BIOS
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159504)
Firmware Version: 10.2.261.36 Supported On: IBM System x and Flex
Problems Fixed: - Server will halt on black screen during rolling reboot of Windows 2012 x64 uEFI SANboot - Server intermittently fails to boot during rolling SANboot (any OS) - Fixed a boot hang associated with server BIOS change - Reported firwmare version in CMM is intermittently incorrect - Unable to set pause Flow control when connected to DCBX switch with PFC off - during cable pull testing a 40 second delay in link up experienced with Brocade switch ports - I/O completion and abort completion WQE are generated out of order - Unexpected WCQE in RQ CQ seen in RXRI mode while performing cable pulls
Incremental Interoperability: - Inventory support for the Flex xHMC (Chassis Hardware Management Console) - Crosslink & Express Lane on LPe16k based solutions
Known Issues: - To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159504)
Firmware Version: 1.1.43.21 Supported On: IBM System x
Incremental Interoperability: - None
Problems Fixed: - Server will halt on black screen during UEFI rolling reboot reboot cycle test with 16Gb HBA under Windows 2012 x64 - Allows installing and booting from an MSA2040 array configured in PT-PT direct mode at 16G speed. We're now able to enable Autoscan and install/boot from multiple OSes - Added support to bypass configuring pnp Boot Table in a multipath situation. Fixes Microsoft Windows Server 2008 bug. - Fixed the "Read Rev Failure" issue during POST to accept "0" address value as a valid. - Fixed the wrong VPD HBA model number display on the banner and properties, and change the proper VPD data field size. - Fixed the timeout issue on Flogi when try to select a HBA device without connecting to a target or FC switch. - System will halt during reboot cycle test under Windows 2012 x64 UEFI - Fixing PCI Function Number decoding issue in BOFM code - Boot fails during SLES11 SP3 rolling reboot - Enable BFS and update the NVRAM if BOFM target is available - Add Diagnostic support for UEFI 16Gb FC - Reconnect menu item causes a System BIOS exit request only on AMI core system BIOS - Adding port's protocol name and WWPN in browser help menu
Firmware Version: 1.1.43.12 Supported On: IBM System x and Flex
Incremental Interoperability: - IBM Flex System FC5052 2-port 16Gb FC Adapter - IBM Flex System FC5054 4-port 16Gb FC Adapter - FC support for support for ASU/Config Patterns for Flex and ASU for IBM System x & BladeCenter - Direct PT - PT connections - Extended SCSI Pass Thru Protocol - IBM Tape unit interoperability - see SSIC for more information - SLES 11.3 on IBM System x
Problems Fixed: - Windows 2012 OS will not resume from Sleep mode - Boot Device entries can be lost after exiting from BIOS setup
Firmware Version: 1.1.21.9 Supported On: IBM System x
Incremental Interoperability: - IBM Server machine types. Refer to IBM ServerProven for specifics
Problems Fixed: - Fixed FCP_CONF handling bug - No SRR sent after drop write data frame, I/O fails - Adapter does not invoke recovery after dropped read data frame - I/O throughput performance improvements - Link failover when connected to FC Tape - Cosmetic: Cleaned up miscellaneous error handling messages in debug log files - If a new device comes online and attempts to acquire an AL_PA after the link has already come up, the FC link appears to hang until the cable is pulled - Cleaned up link negotiation at 4GB/8GB/16GB speeds with specific switches
Firmware Version: 10.2.377.37 Supported On: System x
Problems Fixed: - Ethtool shows “speed=unknown� sometimes for slave interface. (vNIC & UFP) - SVID values are not present under PXE select utility in vNIC1 mode - UMC Mode/Personality change using IBM ASU tool does not reflect in OCM
Incremental Interoperability: - None
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes. ===============================================================================
Firmware Version: 10.2.377.20 and 10.2.377.23
Supported On: System x and BladeCenter
Problems Fixed: - PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug is a cosmetic issue and only impacts PXESelect. The values which are not displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the switch.(151140) - "Configurations have changed" message seen in UEFI setup screen when no changes were made. This pop-up can be ignored and will be fixed in a future code release.(159086) - FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu. This is a cosmetic issue only. The correct VLAN is properly assigned, so there is no functional impact. The actual VLAN ID can be observed elsewhere. (159561) - UE seen while booting the system after a CoreDump - When NIC traffic has run on all the 8 vNICs of an ASIC, the vnics of first port are not honoring the assigned BW - SRIOV performance & Fairness for 16VMs is low on Linux and VMware - ML2 VFA5 device name is show "N/A" under IMM web and CLI of server management>Adapters - BW changes not getting updated with vNIC1 mode - Enable 100M/10M speed in set speed for SGMII interface - UCM/vNIC2, Ports/PCI functions supporting FCoE need to be differentiated to make it easier for the user - UCM/vNIC2 ability to program VirtWWN/WWPN independent of BFS Enable - iSCSI boot not working on higher order PCI functions (PF8 11)on 4 port controllers on ARI enabled systems - Can't install Windows2012 onto the iSCSI LUN whose LUN ID is not 0 - Fixed several issues related to IBM Agentless inventory management - Under heavy bi-di traffic with XE102/XE104 network disconnects can occur during failover/switch side link bounce
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.2.261.41 Supported On: IBM System x
Problems Fixed: - Hit BSOD during VMQ overnight traffic test with cpu affinity change - IBM VFA5 Adapter causing software panic on IBM G8246 Switch in UFP mode - LPVIDs are not getting saved in vNIC2 mode if we change mode from vNIC1 mode to vNIC2 - In MC VINC1, VNIC2, UFP modes, user should see only 4 functions per port for 2 port card
Incremental Interoperability: - Emulex VFA5 2x10 GbE SFP+ Adapter and FCoE/iSCSI SW for IBM System x - Emulex VFA5 2x10 GbE SFP+ PCIe Adapter for IBM System x - Emulex VFA5 2x10 GbE SFP+ Integrated Adapter for IBM System x
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug is a cosmetic issue and only impacts PXESelect. The values which are not displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the switch.(151140)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- "Configurations have changed" message seen in UEFI setup screen when no changes were made. This pop-up can be ignored and will be fixed in a future code release.(159086)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu. This is a cosmetic issue only. The correct VLAN is properly assigned, so there is no functional impact. The actual VLAN ID can be observed elsewhere. (159561)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.2.377.29 Supported On: System x and BladeCenter
Problems Fixed: - iSCSI SAN Boot failed after OS installation completed in UFP and vNIC1 mode with OCe12000 adapter
Incremental Interoperability: - None
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.2.377.18 & 10.2.377.23 Supported On: Flex
Problems Fixed: - PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug is a cosmetic issue and only impacts PXESelect. The values which are not displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the switch.(151140) - "Configurations have changed" message seen in UEFI setup screen when no changes were made. This pop-up can be ignored and will be fixed in a future code release.(159086) - FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu. This is a cosmetic issue only. The correct VLAN is properly assigned, so there is no functional impact. The actual VLAN ID can be observed elsewhere. (159561) - UE seen while booting the system after a CoreDump - When NIC traffic has run on all the 8 vNICs of an ASIC, the vnics of first port are not honoring the assigned BW - SRIOV performance & Fairness for 16VMs is low on Linux and VMware - ML2 VFA5 device name is show "N/A" under IMM web and CLI of server management>Adapters - BW changes not getting updated with vNIC1 mode - Enable 100M/10M speed in set speed for SGMII interface - UCM/vNIC2, Ports/PCI functions supporting FCoE need to be differentiated to make it easier for the user - UCM/vNIC2 ability to program VirtWWN/WWPN independent of BFS Enable - iSCSI boot not working on higher order PCI functions (PF8 11)on 4 port controllers on ARI enabled systems - Can't install Windows2012 onto the iSCSI LUN whose LUN ID is not 0 - Fixed several issues related to IBM Agentless inventory management
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.2.261.41 Supported On: IBM System x
Problems Fixed: - Hit BSOD during VMQ overnight traffic test with cpu affinity change - IBM VFA5 Adapter causing software panic on IBM G8246 Switch in UFP mode - LPVIDs are not getting saved in vNIC2 mode if we change mode from vNIC1 mode to vNIC2 - In MC VINC1, VNIC2, UFP modes, user should see only 4 functions per port for 2 port card
Incremental Interoperability: - Emulex VFA5 2x10 GbE SFP+ Adapter and FCoE/iSCSI SW for IBM System x - Emulex VFA5 2x10 GbE SFP+ PCIe Adapter for IBM System x - Emulex VFA5 2x10 GbE SFP+ Integrated Adapter for IBM System x
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug is a cosmetic issue and only impacts PXESelect. The values which are not displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the switch.(151140)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- "Configurations have changed" message seen in UEFI setup screen when no changes were made. This pop-up can be ignored and will be fixed in a future code release.(159086)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu. This is a cosmetic issue only. The correct VLAN is properly assigned, so there is no functional impact. The actual VLAN ID can be observed elsewhere. (159561)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.2.261.36 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - FRU VPD fields are now properly populated on CN4054 and CN4054R - Fixed UE resulting slow boot at UEFI splash screen and NIC devices removed - When using VMQ with Windows Server 2012 or 2012R2, the user may experience VM connectivity loss, packet drops, system hangs, inability to shutdown VMs and possible system crashes on shutdown. The complete solution also requires 10.2 based Windows NIC driver.
Incremental Interoperability: - Inventory support for the Flex xHMC (Chassis Hardware Management Console)
Known Issues: - Server hangs at "Scan for Fibre Devices", when port disable/enable performed on the Brocade Converged 10 Gb Ethernet Switch Module for IBM BladeCenter. Do not force the link down after POST has completed and then attempt a discovery of the SAN. If you do a reboot is needed.(159125)
- To disable BFS after BOFM or IFM have been enabled, it must be done by setting BFS manually in the EFIBoot config utility or sending a BOFM default command to the port. This is working as expected and we are documenting it here.(159505)
- Intermittently, 255 vPorts can not be created successfully in Windows with the error "ERROR: <127>: Not enough HBA or fabric resources. VPort not created!". There is no known workaround other than to reduce the number of configured vPorts.(155807)
- Target login will fail if you dynamically reconfigure the SAN after POST has executed. If you do, then reboot the system.(159121)
- PXESelect showing incorrect MAC address, bandwidth & SVID values. This bug is a cosmetic issue and only impacts PXESelect. The values which are not displayed correctly in PXESelect can be viewed in UEFI, OCM, and on the switch.(151140)
- IFM Boot target is consumed on a particular port even though the target is not accessible to that port. IFM/BOFM boot target configuration is not supported. This limitation has existed for several code releases and we are now documenting it here.(159226)
- "Configurations have changed" message seen in UEFI setup screen when no changes were made. This pop-up can be ignored and will be fixed in a future code release.(159086)
- The server may hang at "Connecting Boot Devices and Adapters" if both FCoE ports have boot targets configured when using a 10Gb Ethernet Pass-Thru Module for IBM BladeCenter. The server will not hang if only a single port is configured with a boot target.(157137)
- FCoE VLAN ID is being displayed incorrectly as hexadecimal in UEFI menu. This is a cosmetic issue only. The correct VLAN is properly assigned, so there is no functional impact. The actual VLAN ID can be observed elsewhere. (159561)
- In FCoE configurations with BE3 in UFP mode on System x3690 X5 servers, a UEFI rescan is required to boot to the OS. This renders UFP not supportable in UFP/FCoE configurations(158669)
- After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 10.0.803.13 Supported On: IBM System x
Problems Fixed: - IBM Feature on Demand for storage keys now works with Optimized Boot enabled - Link detection time improved from ~70 secs on DAC cable insertion/removal
Incremental Interoperability: - Unified Fabric Protocol on IBM System x Servers
Known Issues: - After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware version: 4.6.281.26 (supported on IBM System x, BladeCenter and Flex)
Problems Fixed: - CN4054 VPD is not valid during/after IMM flash - Links go down after 497 to 498 days in VMWare - Send 'link down' to switch if UE occurs on ASIC
Incremental Interoperability: - Emulex Dual Port 10GbE SFP+ VFA IIIr for IBM System x - Emulex Dual Port 10GbE SFP+ Embedded VFA IIIr for IBM System x
Known Issues: - After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware version: 4.6.281.21 (supported on IBM System x, BladeCenter and Flex)
Problems Fixed: - OCe10 VFA CNAs stuck in "Switch Independent Mode" - Port Identification fails on Port 1 under uEFI menu for PCIe rack VFA
Incremental Interoperability: - IBM Flex System CN4054R 10Gb Virtual Fabric Adapter - IBM Ivy Bridge CPU Based Servers
Known Issues: - After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers.
- Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers.
- When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware version: 4.6.281.8 Supported On: IBM System x, BladeCenter, and Flex
Problems Fixed: - HW iSCSI offload is now supported in UFP Mode (UFP limited to IBM Flex) - Server may hang during boot with multichannel disabled with switch default settings. The IBM 10Gb Virtual Fabric Switch has trunking enabled and the Brocade Converged 10Gbe Switch Module has ports in "Access" mode. If the Brocade Converged 10Gbe Switch Module ports are switched to trunking mode, the hang no longer occurs. - When using Config Patterns with virtual MACs the bandwidth settings are are intermittently reset after some number of server reboots.
Incremental Interoperability: - IBM Flex System Fabric SI4093 System Interconnect Module - IBM Flex System EN6131 40Gb Ethernet Switch - IBM Flex System x222 10Gb Virtual Fabric LOM - SLES 11.3 on IBM System x and BladeCenter - Complete NIC/iSCSI/FCoE support for ASU/Config Patterns for Flex and ASU for IBM System x & BladeCenter
Known Issues: - After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers. - Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers. - When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware version: 4.6.166.7 Supported On: IBM System x and BladeCenter
Problems Fixed: - When connected to Cisco Nexus 4k and 5k switches, the virtual link may not recover on a switch port bounce (shut/no shut) in an ESXi environment. A switch port re-bounce will recover the link. - When connected to Cisco Nexus 4k and 5k switches, OneCommand Manager reports CRC's and there is poor network performance in an ESXi environment
Incremental Interoperability: - ASU/Config Pattern configuration for iSCSI and FCoE (BE3) - UFP for iSCSI (BE3) - Support for using 10Gb ports with legacy 1Gb switches installed in a BladeCenter-S chassis or MSIM/MSIM-T expansion units in a BladeCenter-H or -HT chassis - Update Express System Packs now support Linux errata kernels - ESXi 5.1
Known Issues: - After making changes to any options in the sub-menus under 'controller configuration' in the Emulex UEFI NIC configuration utility and escaping to the prior menu, there is no prompt to save the changes. Be sure to select 'Save' before exiting the configuration menu. Applies to some legacy rack and blade servers. - Intermittently, when changing the multichannel mode, the system will not auto-reboot after exiting F1 UEFI setup and will continue through POST. Manually reboot the server to ensure all changes are applied. Applies to some legacy rack and blade servers. - Server may hang during boot with multichannel disabled with switch default settings. The IBM 10Gb Virtual Fabric Switch has trunking enabled and the Brocade Converged 10Gbe Switch Module has ports in "Access" mode. If the Brocade Converged 10Gbe Switch Module ports are switched to trunking mode, the hang no longer occurs. - When using a Cisco Nexus 4001i Switch Module, intermittently the 10Gb link may come up as 1Gb link speed. An internal switch port bounce will typically establish a 10Gb link. Setting the switch port speed to fixed 10000 will also allow a guaranteed 10Gb connection. More info available in the Cisco Nexus 4001i Switch Module firmware release notes.
Firmware Version: 4.4.180.3 Supported On: IBM Flex
Problems Fixed: - 10Gb ports intermittenly linking at 1Gb speed with the IBM Flex System Fabric EN4093/EN4093R 10Gb Scalable Switch. - Switch Configuration after an erase configuration is not reflected after reboot - '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 - When adding an iSCSI hardware target in UEFI through discovery login, the boot target setting is ignored.
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 - IBM Universal Configuration Manager for Ethernet - IBM Unified Fabric Protocol - Ability to assign Switch Agnostic VLAN IDs without intermediate reboot - Changes to Personality or Multichannel in PXESelect allows further changes to be made w/o reboot - Support for IBM Flex System Fabric CN4093 10Gb Converged Scalable Switch
Known Issues: - HW iSCSI offload is not currently supported in UFP mode
Firmware Version: 4.1.422.8 Supported On: IBM Flex
Problems Fixed: - PHY Loopback fails on 10G ports - RH 6.2 and W2k8 servers crashed after shut/no shut the switch port with FCoE connection and 50 vlans configured - DSA: NIC physical loopback test fails in Command and GUI mode - Firmware update fails to update all VPD Code Level fields - DCBX does not converge with FW 4.1.422 on Cicso 5k.
Interoperability Since Previous Release: - Support for IBM Flex System x440 10Gb Virtual Fabric LOM
Firmware Version: 4.1.422.0 Supported On: IBM Flex
Problems Fixed: - SR IOV: Unable to ping IPV6 from DUT VF to Peer VF - Reading VPD from BE3 timesout making SR IOV fail in newer kernels - 1Gb devices are being suppressed by kernel during the PCI probe in SLES11 SP2 - MAC Loopback fails when Mgmt Adapter Creation fails - Failure of MAC loopback test after firmware update and warm reboot - Suppress efat dump mailbox commands in the efat dump log - Running ethtool with BE3 takes longer than expected after cable pull - Out of Order CQEs - TRACE_LOG function not printing the messages for some of the VF's - esx4/5 issue. svc target cannot be configured properly - RSCN is not generated by switch when a driver restarts - Port Link stays up even after switch removed
Interoperability Since Previous Release: - Support for IBM Flex System EN4054 4-port 10Gb Ethernet Adapter - Support for IBM Flex System CN4054 10Gb Virtual Fabric Adapter - Support for IBM Flex System x240 10Gb Virtual Fabric LOM - Support for IBM Flex System Manager 10Gb Virtual Fabric LOM
Firmware Version: 4.2.433.3 Supported On: IBM System x and BladeCenter
Problems Fixed: - 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
Firmware Version: 4.2.412.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - 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.
Firmware Version: 4.1.455.6 Supported On: IBM System x and BladeCenter
Problems Fixed: - 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
Firmware Version: 4.1.334.47 Supported On: IBM System x and BladeCenter
Problems Fixed: - 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
Firmware Version: 4.0.1062.0 Supported On: IBM System x and BladeCenter
Problems Fixed: - 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.
Dynamic System Analysis (DSA) Preboot Change History
Version 9.54, Build ID DSYTD8G o Enhancement: 1. Embedded DSAp Simplification by removing Low-Value Functionality - Inventory: BIST,PMC - Diags: RSARST Diags, Tape Drive Diags, Optical Drive Diags,Check point (LED) Panel Diags 2. Heartbeat for F2 standalone memory test. 3. IBM High IOPS Adapter Raw Data Collection. 4. pDSA Simplification for FoD Function & GUI Client. 5. Add warning & report in client for nonsupport systems. 6. Change sFTP as the default protocol for transfer log to IBM Service. 7. Get standalone memory test results & SOL support for DSAp(for security efi boot). 8. Update openssl to 1.0.1h from 1.0.1g. o Limitations: 1. After finish run all diagnostics in 25 loop with Emulex 10G options, DSA log will show abnormal, it only record Diags log one time on DSA Diagnostics Completion Log. 2. On GUI, when two ports of the machine want to connect the Extranet at the same time, the machine could not send dsa log to IBM server. you can click test internet connection to solve the problem. 3. System not show event log item in chassis event log & ipmi event log page when trigger SBE in standalone mode. o Special usage: - 2014 IMMV2 2QLFC Product Build
Version 9.43, Build ID DSYTC8E o Enhancement: 1. Preboot GUI redesign and enhancement--refine GUI into more customer friendly style. 2. FoD Support--FoD key re-activation. 3. pDSA proxy auto-config retrieve. o Limitations: 1. DSA Does not support "VMware ESXi" page report for ESXi 5.x key due to "vmvisor-offline-query" limitaion . o Special usage: - 2013 IMMV2 4QLFC
Version 9.33, Build ID DSYTB6E o Limitations: When we want to flash from B5E to B6E, we should level down to AA3 or AA4 first.
Version 9.30, Build ID DSYTB27 o New System Support: Flex System x440 Compute Node (7917, 2584) IBM System x3300 M4 (7382) o Problem(s) Fixed: 1. PMR - 05766,YL2,760 Aenservice appeared after running UpdateXpress & DSA. 2. PMR - 05193,W01,000 7147 - Intermittent random PSOD in vmware. multiple
o Enhancement: None o Limitations: - FIFO test of NIC diagnostics is not supported on the Intel I350 Quad Port GbE. Powerville has shared FIFO and shared FIFO registers making a test impossible if four ports are running at once. - For more limitations please refer to readme. o Special usage: - 2012 ToolsCenter 12D
Version 9.29, Build ID DSYTAB6 o New System Support: Flex System x440 Compute Node (7917, 2584) o Problem(s) Fixed: None o Enhancement: None o Limitations: - DSA implemented signature in product build. Please update IMM to 1AOO34V or later before updating pDSA, or flash failure will occur; - The user can not flash Embedded Preboot on VMware ESX3.5 prior to U4. - When flashing DSA Preboot using wflash/lflash, if you notice a build mismatch error, please make sure IMM firmware level is minimum 29B. Once you upgrade the IMM firmware to 29B or higher, DSA Preboot will continue to flash without error; - For more limitations please refer to readme. o Special usage: - NGP-4Q(12B+ FixPack3)
Version 9.28, Build ID DSYTAA4 o New System Support: x3630 M4 (7519) x3550 M4 (7383) o Problem(s) Fixed: None o Enhancement: None o Limitations: - DSA implemented signature in product build. Please update IMM to 1AOO34V or later before updating pDSA, or flash failure will occur; - The user can not flash Embedded Preboot on VMware ESX3.5 prior to U4. - When flashing DSA Preboot using wflash/lflash, if you notice a build mismatch error, please make sure IMM firmware level is minimum 29B. Once you upgrade the IMM firmware to 29B or higher, DSA Preboot will continue to flash without error; - For more limitations please refer to readme. o Special usage: - IMMV2 system 2012 4Q-LFC
Version 9.27, Build ID DSYTA7F o New System Support: None o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme o Special usage: - IMMv1 system 2012 4Q-LFC
Version 9.26, Build ID DSYTA6G o New System Support: None o Problem(s) Fixed: None o Enhancement: DSA Performance Optimization o Limitations: Refer to readme o Special usage: - 2012 ToolsCenter 12C
Version 9.21, Build ID DSYTA1U o New System Support: None o Problem(s) Fixed: 1.Recovered LSI Rawdata: "MegaCli -FwTermLog -Dsply -aALL" o Enhancement: None o Limitations: Refer to readme 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 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: 1. Add HW remote presence key collection for High volume systems. o Limitations: Refer to readme o Special usage: - 2012 ToolsCenter 12B
Version 9.07, Build ID DSYT9CA o New System Support: x3750 M4 (8722, 8733) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.06, Build ID DSYT9BC o New System Support: Flex System x220 Compute Node (7906) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
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 Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.04, Build ID DSYT99E o New System Support: Flex System x240 Compute Node (8737, 8738, 7863) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.03, Build ID DSYT98I o New System Support: HS23E (8038, 8039) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.02, Build ID DSYT97C o New System Support: iDataPlex dx360 M4 server/2U chassis (7912/7913) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
Version 9.01, Build ID DSYT96D o New System Support: x3500 M4 (7383) x3550 M4 (7914) x3650 M4 (7915) o Problem(s) Fixed: o Enhancement: None o Limitations: None o Special usage: None
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 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: 1. Add GUI and CLI menu for Features on Demand (FoD) Activation Key Management o Limitations: Refer to readme. o Special usage: None
Version 4.02, Build ID DSYT92I o New System Support: iDataPlex Direct Water Cooled dx360 M4 server o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 4.01, Build ID DSYT92H o New System Support: None o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: - 2011 4Q lifecycle
Version 4.00, Build ID DSYT91S o New System Support: None o New server options support: None 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: 1. Added > 1TB memory test support o Limitations: Refer to readme. o Special usage: - 2011 ToolsCenter 11D
Version 3.48, Build ID DSYT89PUS o New System Support: None o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: - 2011 3Q lifecycle
Version 3.47, Build ID DSYT89LUS o New System Support: x3100 M4 (2582) x3250 M4 (2583) o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 3.46, Build ID DSYT89GUS o New System Support: System x iDataPlex dx360 M3 (6391) o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 3.45, Build ID DSYT89EUS o New System Support: None o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. 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 Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 3.43, Build ID DSYT87FUS o New System Support: x3850 X5 / x3950 X5 (7143, 7191) x3690 X5 (7192, 7147) o Problem(s) Fixed: o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 3.40, Build ID DSYT85T o New System Support: BladeCenter HS22 (1911) x3650 M3 (5454) o Problem(s) Fixed: None o Enhancement: None o Limitations: Refer to readme. o Special usage: None
Version 3.30, Build ID DSYT80S o New System Support: None o Problem(s) Fixed: None o Enhancement: 1. Correct a problem with LSI MegaRAID reporting for IBM Service o Limitations: Refer to readme. o Special usage: None
Version 3.20, Build ID DSYT75X o New System Support: x3630 M3 (7377) x3690 X5 (7148, 7149) o Problem(s) Fixed: None o Enhancement: 1. Add LSI Hard Disk Drive (HDD) diagnostic back for both the onboard SAS chip and ServeRAID o Limitations: - 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 - For more limitations please refer to readme o Special usage: None
Verion 3.20, Build ID DSYT75U o New System Support: x3755 M3 (7164) o Problem(s) Fixed: None o Enhancement: None o Limitations: None o Special usage: None
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 Problem(s) Fixed: None o Enhancement: 1. 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 - 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 - For more limitations please refer to readme o Special usage: None
Version 3.02.56, Build ID DSYT56e o New System Support: None o Problem(s) Fixed: None 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. - For more limitations please refer to readme o Special usage: None
Version 3.00, Build ID: DSYT55a o New System Support: None o Problem(s) Fixed: None o Enhancement: - Added support for Machine Types 7327, 7328, 4251, 4252, 4261 o Limitations: - No HDD diagnostics available - For more limitations please refer to readme o Special usage: None
Version 1.16, Y4YT19AUS o New System Support: None o Problem(s) Fixed: None o Enhancement: - Added support for Machine Types 7839, 7836, 7837 o Limitations: None o Special usage: None
Version 1.15, TMYT20AUS o New System Support: None o Problem(s) Fixed: None o Enhancement: - Added support for Machine Types 7321, 6380, 7323 o Limitations: None o Special usage: None
Version 1.14, D6YT37AUS o New System Support: None o Problem(s) Fixed: None o Enhancement: - Added support for Machine Types 7946, 4198, 7947, 4199 o Limitations: None o Special usage: None
Version 1.13, P9YT48AUS o New System Support: None o Problem(s) Fixed: None o Enhancement: - Added support for Machine Types 7870, 1936, 7809 o Limitations: None o Special usage: None
Version 1.00 - Initial release
(C) Copyright International Business Machines Corporation 2008 - 2014. All rights reserved. ibm_fw_dsa_dsytd8g-9_54_anyos_anycpu_chg
IBM HBA/LSI Onboard 12Gb SAS/SATA/SSD Driver for Linux
NOTE TO SERVICE - Reference RETAIN N/A
Supported Controllers: - IBM N2215 SAS/SATA HBA for IBM System x (47C8676) - IBM N2225 SAS/SATA HBA for IBM System x (00AE912) - IBM N2226 SAS/SATA HBA for IBM System x (00AE916)
Version 4.00.01.00 - Non-Critical ------------------ Enchancement: - Add support for SLES 11 SP 3 Fix(es) - Fixed an issue where device driver initialization could fail during loading of the driver in RHEL 5. - Fixed an issue where a kernel panic could be observed after issuing controller diagnostic reset. - Fixed an issue where loading mpt3sas driver could hang in RHEL 5 due to memory allocation failure.
Version 3.00.00.00 - Initial release ------------------ ibm_dd_mpt3sas_4_00_01_00-1_sles11_32-64_chg
Integrated Management Module II (IMM2) Firmware Update Change History
Version 4.97, 1AOO66M, Supported Platforms: HS23, HS23E, x3100 M4, x3250 M4, x3550 M4, x3650 M4, x3500 M4, x3630 M4, x3530 M4, x3300 M4, dx360 M4, x3750 M4, x3100 M5. x3250 M4, xc360 M4, x3650 M4 BD, x3850 X6, x3950 X6 - NOTE: To avoid possible exploits of the vulnerabilities discovered with SSLv3 encryption, support for SSLv3 has been removed from the IMM2 firmware. To access the IMM2 web interface using https, users must make use of client browser versions that support TLS1.2 encryption. Refer to RETAIN Tip H214507 for details. - Critical Fix for x3750M4 -- Fixed issue on missing power supply redundancy lost event - Firmware changes to address security vulnerabilities: CVE-2015-2808, CVE-2015-0204, CVE-2014-3566, CVE-2014-3511, CVE-2014-3509, CVE-2014-3505, CVE-2014-3506, CVE-2014-3508, CVE-2014-5139, CVE-2014-3507, CVE-2014-3510, CVE-2013-4332, CVE-2014-3513, CVE-2014-3567, CVE-2014-3568, CVE-2014-3569, CVE-2014-3570, CVE-2014-3571, CVE-2014-3572, CVE-2014-8275, CVE-2015-0205, CVE-2015-0206. - Fixed a problem that IMM2 unable to detect event from redundant PSU on x3250 M4 - Fixed a problem that PSU 1 and PSU 2 will show changed after hot swap on x3250 M4 - Fixed a problem that FAN will rotate in high speed when booting on 3100 M4 - Fixed a problem that IMM2 LDAP connects to AD server three time simultaneously for each login attempts with wrong password - Fixed a problem that Fan operates abnormally in S5 mode after rebooting system on x3550 M4 - Fixed a problem that "ipmitool chassis status" reporting false drive fault on System x3650 M4 - Fixed a problem that IMM firmware version 4.56 display as 4.55 in DSA log and UEFI data - Fixed a problem that IMM2 cannot log events on x3550 M4 - Fixed a problem that IMM2 may reset due to potential memory leakage - Fixed a problem that failure to send the alert of IMM2 via e-mail - Fixed a problem on IBM NeXtScale nx360 M4 for where the IMM may intermittently report an incorrect DC value to IBM NeXtScale n1200 Fan and Power Control (FPC) - Fixed a problem on NI152 x3650M4 where the IMM may report a power supply configuration mismatch error message in the system event log
Version 4.90, 1AOO66O - Non-critical - Firmware changes to address security vulnerabilities: CVE-2015-2808, CVE-2015-0204, CVE-2014-3566, CVE-2014-3511, CVE-2014-3509, CVE-2014-3505, CVE-2014-3506, CVE-2014-3508, CVE-2014-5139, CVE-2014-3507, CVE-2014-3510, CVE-2013-4332, CVE-2014-3513, CVE-2014-3567, CVE-2014-3568, CVE-2014-3569, CVE-2014-3570, CVE-2014-3571, CVE-2014-3572, CVE-2014-8275, CVE-2015-0205, CVE-2015-0206. - Fixed a problem that IMM firmware version 4.56 displays as 4.55 in DSA log and UEFI data. - Fixed a problem that IMM2 may reset due to a potential memory leakage. - Fixed a cooling issue when the Fusion IO adapter is present - Fixed a problem where the IMM2 LDAP authentication attempts to connect to an AD server three times simultaneously for each login attempt with a wrong password. - Fixed a problem that may cause the IMM2 to fail to send an alert via e-mail. - To support new security requirements the IMM firmware now requires the Java remote presence client to be at version 1.8 or newer
Version 4.80, 1AOO64T - Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839 - Fixed potential problem where Service Advisor not functional when routing through a proxy server
Version 4.61, 1AOO64Y - Fixed a problem on IBM NeXtScale nx360 M4 for intermittent IPMB IO error and ME error. - Fixed a problem on IBM NeXtScale nx360 M4 for unexpected shutdown due to CPU over temperature
Version 4.58, 1AOO64V - Critical - Critical Fix for x3630 M4, x3530 M4, x3300 M4, x3650 M4 BD -- Removed an incorrect error message sometimes displayed when certain RAID adapters are installed in certain PCIe slots
Version 4.56, 1AOO64S - Critical - Critical Fix for x3650 M4, x3650 M4 HD, x3650 M4 BD, x3500 M4, x3630 M4, x3530 M4, x3300 M4 -- Fixed issue on missing power supply redundancy lost event
Version 4.55, 1AOO64N - NonCritical - Firmware changes to address security vulnerabilities: CVE-2014-3508 CVE-2014-3509 CVE-2014-3505 CVE-2014-3506 CVE-2014-3507 CVE-2014-3510 CVE-2014-3511 CVE-2013-2174 CVE-2013-4545 CVE-2014-0015 CVE-2014-0138 CVE-2014-0139 CVE-2014-2653 CVE-2014-2532 - Closed network port 121. - Fixed a problem of I2C error on x3500 M4 systems with use of Fairmont Raid card with FW version 23.22.0-0024 and iMM 1AOO58T - Thermal behavior enhancement on System x iDataPlex dx360 M4 - Fixed a problem that Call Home function was not working with a Proxy server
Version 4.31, 1AOO58T - Critical - Critical Fix for x3650M4, x3550M4, x3500M4, dx360M4, x3100 M4, x3250m4, x3750M4, x3650M4 HD, x3630M4, x3530M4, x3300M4, x3250M5 -- Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198 - Added option to export the certificate signing request in PEM format - Various Remote Presence enhancements including: -- Support for a MAC OS-x client -- Scaled video viewer window -- ASU set up of Remote Presence hot keys -- Virtual media mounting via URL - Removed potentially sensitive information from the service data file - Fixed a problem on x3650 M4, x3550 M4, x3500 M4, x3650 M4 HD where the IMM2 may not detect a loss of power supply redundancy - Fixed a problem where the LDAP group filter does not support a full DN - Fixed a problem where the syslog alert fields "Msg Type" and "Severity" did not follow RFC 5424 - Fixed a problem where the IMM2 only supported the default network port for syslog notifications - Fixed a problem where the SNMP "sysName" query always returns the string "SNMP Service" instead of the system name - Fixed a problem where the Global Login Settings changes were lost after an IMM2 restart
Important: Before you flash the IMM2 firmware back to version 3.82 or older, set the IMM2 Security option to use the Basic Compatibility Mode. This will prevent a possible loss of access to the IMM2.
Version 4.15, 1AOO58K - Suggested - Added support for the BIE (Blade IO Expansion Board) on the HS23, HS23E - Fixed a problem that prevented the AMM from controlling power when local power control is disabled on the HS23, HS23E
Version 3.91, 1AOO56P - Critical - Critical Fix for IBM NeXtScale nx360 M4 -- Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-0224, CVE-2014-0221, CVE-2014-0195, CVE-2014-3470, CVE-2010-5298, CVE-2014-0198
Version 3.90, 1AOO54X - Added support for the IBM NeXtScale PCIe Native Expansion (NeX) Tray for IBM NeXtScale nx360 M4
Version 3.83, 1AOO56I - Critical Fix for x3250 M5, nx360 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.73, 1AOO56D - Critical - Critical Fix for dx360 M4, x3650 M4, x3550 M4, x3500 M4, x3100 M4, x3250 M4, x3750 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.71, 1AOO52W - Critical - Critical Fix for x3550 M4: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882) -- Fixed a problem system may shut down with new Mezz card installed
Version 3.70, 1AOO52Q - Critical - Critical Fix: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882)
Version 3.67, 1AOO50G - Initial Release - Supports System x3650 M4 BD, Machine Type: 5466
Version 3.65, 1AOO50D - Suggested NOTE: If you have a System x3550 M4 with the "Emulex VFA Mezz card" and a ==== single processor, don't update the IMM2 with this firmware - Critical Fix: -- Fixed a problem on the System x3650 M4 server where the system shuts down due to a false temperature event from the ambient temperature sensor - Fixed a problem where the IMM2 may erroneously report a fan fault in the x3630 M4 when the system is powering on. See RETAIN tip H207461 for the description of the original problem - Fixed a screen refresh problem where it occurs after resetting IMM2 - Fixed a firmware problem that may cause the IMM2 to reset unexpectedly - Fixed a problem where the IMM2 SNMP interface may intermittently be unavailable if the system is running VMWARE ESXi 5.x - Fixed a problem where the CPU may potentially throttle in the x3650 M4 system with two 550 watt power supplies and one hard drive backplane
Version 3.60, 1AOO50C - Suggested - Added support for the Intel IvyBridge-EP CPU on the HS23 blade - Fixed a problem where the HS23 hard drive number reported in the AMM event did not match the drive number on the physical blade enclosure - Fixed an intermittent problem where the UXSPI update utility may erroneously report that the firmware image is not meant for the HS23 system - Fixed a problem that causes the AMM web interface to not display properly when drives are removed or inserted - Fixed a problem where the IMM2 may not detect an over temperature condition for a DIMM - Corrected a problem that caused the IMM to report an "Unsupported blade/blower combination" error on HS23
Version 3.56, 1AOO50K - Critical - Fixed a Flex Systems Manager (FSM) Configuration Patterns problem where configuration deployments would fail with an activation job error message: ERROR: LDAP failed with rc=102 ERROR: LDAP failure: SYSPROF_LDAP_BIND_FAIL INFO
Version 3.55, 1AOO50E - Suggested - Fixed an issue so a fully qualified domain name can be used for a syslog collector in addition to an IP address - Fixed an issue to allow a user the ability to specify the port to use for syslog notifications, rather than only supporting the default port
Version 3.50, 1AOO50B - Suggested - Fixed an issue where the default static IPv4 address was assigned to the IMM2 management interface instead of the user configured static IPv4 address in DHCP fallback to static mode, if the DHCP server was not available - Prevent a VLAN from being configured on the IMM2 management interface for Flex nodes - Fixed a problem where the CPU throttling state recovery indication to the FSM might not be properly reported - Corrected an issue with the launch of the IMM2 Remote Console operation that required a restart of the IMM2 - Corrected the firmware to apply the inactivity timeout to web pages that automatically refresh - Updated the web browser support. The following web browsers are supported: Firefox 3.6-20 Chrome 13-26 Internet Explorer 8-10 - Added support for the S3 Sleeping State to the IMM2 user interfaces on those servers that include the S3 feature - Added changes to use the minimum TLS version setting that is provisioned by the CMM in Flex for encrypted communication - Enhanced the content of the service data file to assist in problem determination - Added a option to have the IMM2 automatically copy the firmware from its primary bank into the backup bank after the firmware has been run for a period of time and proven itself to be stable - Enhanced the IMM2 firmware to automatically restore itself without the need for user intervention if the firmware becomes corrupted - Added new commands on the command line interface to stop a serial redirection operation that is currently in progress, and to report the user names that have a serial redirection operation started - Added changes to use the DNS settings that are provisioned by the CMM in Flex to support use of an LDAP hostname for authentication - Updated the firmware to log hardware inventory change informational messages - Added support for the Service Advisor feature on stand alone rack servers to automatically call for service when a repair is needed - Added support to configure the Ethernet-over-USB IP address using ASU - Added changes to support the thermal requirements for new Solid State Drives used with the ServeRAID M5100 Series IBM Flex System Flash Kit v2 - Updated the IMM2 date and time web page on Flex nodes to only display the current date and time - Updated the SSH firmware to address various OpenSSH vulnerabilities that have been identified by security community - Added changes to support the Web Services-Management protocol
Version 3.40, 1AOO48M - Initial Release - Supports System x3250 M5, Machine Type: 5458
Version 3.37, 1AOO48P - Added support for the IBM NeXtScale Storage Native Expansion (NeX) Tray for IBM NeXtScale nx360 M4
Version 3.36, 1AOO48Q - Fixed a problem on System x iDataPlex dx360M4 where a CIM client cannot get needed event information for asserted events
Version 3.30, 1AOO48L - Fixed a problem on System x iDataPlex dx360M4 where nodes shutdown due to a critical temperature event from the Ambient Temp sensor
Version 3.20, 1AOO48K - Supports System NeXtScale nx360 M4, Machine Type: 5455
Version 3.10, 1AOO48H - Added support for System x3650 M4 HD, Machine Type 5460 - Added support for newer CPUs in the System x iDataPlex dx360M4, x3500M4, x3550M4, and x3650M4 servers - Added a feature on the System x3550 M4 and x3650 M4 to fail over from the dedicated systems management network port to the shared port when the dedicated network link is not available - Fixed a problem where an NTP update message is logged every 1440 minutes - Fixed a problem where the IMM2 web interface won't accept an NTP hostname string that starts with a numeric character - Fixed a problem where the LDAP Group Filter authentication does not work as expected - Fixed a problem where the IMM2 reports 0 Watts when the System x iDataPlex dx360M4 is DC cycled or resumes from the S3 sleep state - Fixed an Ethernet problem that may cause an IMM2 failure to establish a link when the Ethernet speed and duplex settings are not configured to use auto-negotiation
Version 2.50, 1AOO40Z - Added support for the Solarflare SFN5162F MR Dual Port 10GbE SFP+ Adapter, and Solarflare SFN6122F LL Dual Port 10GbE SFP+ Adapter for System x3550 M4 and x3650 M4 NOTE: UEFI also needs to be upgraded to D7E128B (v 1.40 or newer, for the x3550 M4) or VVE128B (v1.40 or newer, for the x3650 M4) to support these cards - Added support for the Mellanox ConnectX-3 Dual Port QDR/FDR10 mezzanine card and Mellanox ConnectX-3 VPI Single-port QSFsorry.P FDR14/40GbE HCA on System x3550 M4, and x3650 M4 - Added optional Fan Zone support for single CPU systems (x3550 M4 and x3650 M4) with an installed with Qlogic Dual Port 10GbE SFP+ Embedded VFA - Fixed an intermittent problem where a Gratuitous ARP is not sent successfully - Fixed a problem where after the IMM2 firmware is flashed, there is a slight chance that the IMM2 web server can't be accessed when AC power is reapplied - Disabled the weak cipher suit used in the SSL/TLS firmware with the https protocol to avoid potential security vulnerabilities - Fixed a problem on the System x3750 M4 where the IMM2 shared mode network connection will be lost after upgrading the firmware of the onboard Emulex BE3 controller - Fixed a problem on the HS23 where the OS watchdog timer doesn't work - Fixed a problem on the HS23 where the Fault LED occasionally lights when the chassis is powered on with the BPE4 - Fixed a problem on the HS23 where the server may shut down after resetting the IMM2 - Enhanced the messaging mechanism between the BladeCenter AMM and the IMM2 - Added power management capability in the IMM2 web interface
Version 2.00, 1AOO40E - Critical Fix: -- Improves the reliability of the CPU and/or memory VRDs. This improvement lowers the occurrence of CPU & memory VRD failures on the x3300 M4 and x3750 M4 -- IMM2 improved error reporting for missing/down CPU in invalid CPU configuration for x4440 M4 - Corrected a problem that caused 3.3V and 5V faults to be reported by IMM2 firmware level 1aoo34z(1.85) on the HS23E blade - Eagle Ray SAS controller LED fault support improvements added for all ITE platforms
Version 1.97, 1AOO36R - Critical Fix: -- Improves the reliability of the CPU and/or memory VRDs. This improvement lowers the occurrence of CPU & memory VRD failures on x3650 M4, x3550 M4 and x3500 M4 - Thermal behavior enhancement on System x iDataPlex dx360 M4
Version 1.95, 1AOO36P (for System x iDataPlex servers) - Added support for NVIDIA K1,K2,K20,K20x GPUs on System x iDataPlex dx360 M4
Version 1.88, 1AOO40A (for PureFlex System Compute Nodes) - Critical Fix: -- Fixed a potential security vulnerability with node management user accounts (Reference to Security Bulletin CVE-2012-4838) - Fixed a problem on Flex Systems where the SNMP get and set authority levels did not work - Fixed a problem on Flex Systems where mounting of remote media in a Linux environment showed a USB error - Fixed a problem on Flex Systems that caused the Remote Control Video Viewer window on a RHEL5.8 client to move when the arrow key is pressed - Fixed a problem on Flex Systems where the SMTP "Test Connection" button did not work when the SMTP port is changed - Fixed a problem on Flex Systems where the SNMP get and set authority levels did not work - Fixed a problem on Flex Systems where mounting of remote media in a Linux environment showed a USB error - Fixed a problem on Flex Systems that caused the Remote Control Video Viewer window on a RHEL5.8 client to move when the arrow key is pressed - Fixed a problem on Flex Systems where the SMTP "Test Connection" button did not work when the SMTP port is changed - Corrected the Mezzanine card power fault monitoring on the Flex System x440 Compute Node - Corrected a problem with IBM Fabric Manager configuration from the Flex Chassis Management Module - Added support to retrieve configuration settings from an LDAP server - Added support for the Flex Storage Expansion Node - Added support for CIM indications over https - Added fingerprint checking for SFTP transfers - Added automatic recovery of corrupted UEFI firmware - Added support for authenticated SMTP alerts - Added a display of the users who have a Remote Control session in progress - Provided a request to a Remote Control client to disconnect the session - Added support for the server S3 (sleep) state - Changed the default NTP sync interval from 3 minutes to 24 hours - Fixed a problem where the ambient temperature is only displayed in degrees Fahrenheit - Fixed a problem on the web interface where 'local' is not accepted as a top level domain name in the email format when configuring event recipients - Corrected an IMM2 SNMP trap OID to match the prior IMM format - Fixed a problem that prevented an external USB device from being remotely mounted as a floppy drive in Windows Server 2003 - Changed the blue Location led behavior to not blink when a firmware update is in progress
Version 1.85, 1AOO34Z (for BladeCenter blades and System x Servers) - Critical Fix: -- Fixed a potential security vulnerability with node management user accounts (Reference to Security Bulletin CVE-2012-4838) - Fixed a problem where a Blade Open Fabric Manager uncorrectable error can occur when booting the HS23 - Fixed a problem that IMM IPMI command periodically timed out when using HS23 in Chassis with the management network being disabled in some special configurations - Added support for the HS23 to recognize NEBS/Enterprise Mode for Telco chassis (this feature needs Advanced Management Module Firmware BPET62U or later) - Fixed a problem where the ambient temperature is only displayed in degrees Fahrenheit - Fixed a problem where on rack systems that have 2 power supplies installed, the 'Redundancy Power unit has been restored' event is logged every time that the IMM2 is reset - Fixed a problem where a Fan Tach going low (lower critical) event is intermittently asserted when configuring the IMM2 to use an NTP server - Fixed a problem on the web interface where 'local' is not accepted as a top level domain name in the email format when configuring event recipients - Corrected an IMM2 SNMP trap OID to match the prior IMM format - Fixed a problem that prevented an external USB device from being remotely mounted as a floppy drive in Windows Server 2003 - Changed the blue Location led behavior to not blink when a firmware update is in progress - Fixed a problem on the HS23E that causes Preboot DSA to hang in CLI mode when a user accesses it using Serial over LAN - Fixed a problem on rack servers where ASU cannot set IMM.GRP_GroupName.1 and IMM.GRP_GroupName.2 if the string length is 16 characters or longer. The firmware was corrected to allow a maximum length of 64 characters - Added support for CIM indications over https - Added fingerprint checking for SFTP transfers - Added automatic recovery of corrupted UEFI firmware - Added support for authenticated SMTP alerts - Added a display of the users who have a Remote Control session in progress - Provided a request to a Remote Control client to disconnect the session - Added support for the server S3 (sleep) state
Version 1.85, 1AOO34Y (for PureFlex System V7000 Storage Node) - Added support for Flex System V7000 Storage Node
Version 1.79, 1AOO36F - Thermal behavior enhancement on System x iDataPlex dx360 M4
Version 1.78, 1AOO36E - Thermal behavior enhancement for 115W & 95W CPU on System x iDataPlex dx360 M4 - Added support for the Intel KNC 5110p card
Version 1.77, 1AOO32X - Thermal behavior enhancement for 115W CPU on System x iDataPlex dx360 M4
Version 1.75, 1AOO32S - Fixed a problem that a PCI uncorrectable error occurs when using HS23 with CFFh card (44W4479) in the BCS chassis - Fixed a problem where an "Unsupported blade/blower combination" error is reported when using the HS23 in the BCHT chassis configured in Enterprise mode - Fixed a problem in System x3530 M4, where the reported Active Energy Manager input/output power readings are inaccurate - Fixed a problem in System x3530 M4, x3630 M4, where an LDAP account can not login using the AD_CrossDomain tree - Fixed a problem in System x3530 M4, x3630 M4, where a user cannot use the "DNS to Find LDAP server/Extract search domain from login ID" setting from the IMM2 web to access an eDirectory server - Added support for Common Form Factor power supplies Oversubscription in System x3750 M4, Machine Types: 8722, 8733
Version 1.65, 1AOO32O - Support the power supply Over-Subscription feature - Support the 750 Watt DC power supply for System x3650 M4,x3550 M4 - Support IBM 1.2TB High IOPS MLC Mono Adapter, IBM 2.4TB High IOPS MLC Duo Adapter for System x3650 M4, x3550 M4 - Support IBM LLM-SM Dual Port 10GbE SFP+ Adapter for System x3650 M4 - Fixed an abnormal Fan Zone recovery problem - Fixed a problem that IMM2 Email notification doesn't support an e-mail address with the underscore '_' character - Fixed a power policy "Restore" problem - Fixed a problem where the LDAP hostname can't be changed by ASU - Fixed a problem that the length of email address (for SNMP notification) is limited to 32 characters
Version 1.60, 1AOO32P - Fixed a problem where the Chassis Management Module cannot correctly get the Mezzanine card information for the Flex System x220 Compute Node - Fixed a problem where the PreBoot DSA firmware could not be updated under VMWare ESXi 5 through the Flex System Manager's Update Manager - Fixed a problem where an IMM2 communications error can occur if an unexpected response causes VMware to spawn multiple processes when it does not receive the data it expects from the IMM2
Version 1.59, 1AOO32K - Supports System x3300 M4, Machine Types: 7382
Version 1.53, 1AOO30Z - Included an update to the FPGA that fixes an intermittent issue where the CPUs do not show up in a system with a RAID card installed, when the AC is removed and reapplied from the server without allowing sufficient time for the system hardware to completely discharge
Version 1.52, 1AOO34A - Added redundant power supply and hot swap hard drive support in System x3100 M4
Version 1.51, 1AOO30Y - Support for NVIDIA Tesla K10, M2070Q, M2090 GPU cards on System x iDataPlex dx360 M4 - Fixed a problem in System x iDataPlex dx360 M4 where the password expires after creating a new user in the IMM2 web interface - Fixed a problem in System x iDataPlex dx360 M4, when the memory sensor changes from 'critical' to 'warning,' but the severity is not updated in the syslog or the email notification
Version 1.50, 1AOO30W - Supports System HS23, Machine Types: 7875,1929 - Supports System x3650 M4, Machine Types: 7915 - Supports System x3550 M4, Machine Types: 7914 - Supports System x3500 M4, Machine Types: 7383 - Added support for the Intel Xeon E5-2643 processor on the HS23 in BCH-R3, BCS and BCHT chassis - Fixed a problem where the IMM2 incorrectly logged an "Unsupported blade/blower combination" on the HS23 in the BC-E 8677 chassis - Fixed a power restore problem on systems that have 2 Delta power supplies installed - Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where OpenLDAP Group Authentication filtering function doesn't work - Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where LDAP account can not login using the AD_CrossDomain tree
Version 1.45, 1AOO28S - Fixed a problem in Flex System x220 where the Chassis Management Module (CMM) Command Line Interface can't display the Mezzanine card information - Fixed a problem in Flex System x220 and x240 where the prebootDSA firmware cannot be updated through Flex System Manager's Update Manager
Version 1.40, 1AOO30T - Supports System x3750 M4, Machine Types: 8722, 8733
Version 1.38, 1AOO30D - Supports System x3630 M4, Machine Type: 7158 - Supports System x3530 M4, Machine Type: 7160
Version 1.36, 1AOO30P - Fixed an intermittent remote media failure in system HS23E - Fixed a problem in system HS23E where remote media does not work when two or more users have concurrent remote control sessions
Version 1.34, 1AOO28Q - Supports Flex System Manager Node, Machine Type: 8731 - Supports Flex System x240 Compute Node, Machine Types: 7863, 8737, 8738 - Supports Flex System x220 Compute Node, Machine Types: 2585, 7906
Version 1.32, 1AOO28N - Supports System x3630 M4, Machine Type: 7158 - Supports System x3530 M4, Machine Type: 7160 - Fixed a problem that may see unexpected fan events after power on in x3100 M4 and x3250 M4 systems - Enhanced robustness on I2C bus test
Version 1.30, 1AOO28M - Supports System HS23E, Machine Types: 8038,8039
Version 1.26, 1AOO26N - Supports System x3650 M4, Machine Types: 7915
Version 1.25, 1AOO26K - Supports System x3550 M4, Machine Types: 7914 - Supports System x3500 M4, Machine Types: 7383 - Supports System x iDataPlex dx360 M4, Machine Types: 7912,7913
Version 1.22, 1AOO26O - Supports System HS23, Machine Types: 7875,1929 Problems Fixed: - Fixed a problem where the BOFM configuration may be lost after a blade power cycle - Fixed an LED error indication that occurs on the BPE4 - Fixed a problem where the Info LED lights during the discovery stage - Fixed a problem where an ABR event is not logged - Fixed an intermittent communication problem between the AMM and IMM2 - Fixed a problem that causes the remote media function to hang when a second user attempts to mount remote media - Fixed a problem where the 'break' keyboard function doesn't work with Serial Over LAN
Version 1.21, 1AOO26L - Supports System HS23, Machine Types: 7875,1929
Version 1.10, 1AOO24B - Supports System dx360 M4, Machine Types: 7918,7919
Version 1.05, 1AOO10K - Fixed the false alert issue in redundant PSU model
Version 1.00, 1AOO10I - Initial Release - Supports System x3250 M4, Machine Types: 2583,2587 - Supports System x3100 M4, Machine Types: 2582,2586
(C) Copyright International Business Machines Corporation 2008 - 2015. All rights reserved.