BIOS/FW/UEFI Update for IBM N2200 Series SAS/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)
NOTE TO SERVICE - Reference RETAIN #N/A
Version 1.11.01 - Moderate Impact/Low Probability of Occurrence --------------- Contains: BIOS Firmware UEFI Driver 08.27.00.00 11.125.00.00 13.00.00.00
Firmware Fixes: - Fixed issue where invalid or unsupported signature FIS was not validated for expander attached SATA drives (SCGCQ00852290) - Fixed issue where BUSY TIMEOUT PERIOD Field was incorrectly populated in UCM Control Mode Page for SATA Drive (SCGCQ00871463) - Fixed issue where during SATA FORMAT Operation, REQUEST SENSE command is not failed with expected response where DESC bit is set (SCGCQ00872727) - Fixed slot assignment to direct attach SEP Device Handle that previously resulted in slot number out of bounds condition (SCGCQ00894230) - Fixed issue where locate was not working for a particular slot in the external enclosure due to firmware not picking up the correct phy index (SCGCQ00932707) - Fixed issue where 19th entry of Self-Test Results Log Page was not showing during SAT translation. (SCGCQ00847941) - Fixed issue where SATA hinting feature causes IO timeouts with slow spin up drives under Linux (SCGCQ00867345) - Fixed issue where SCSI ATA passthrough code did not check for correct CDB length (SCGCQ00915201) - Fixed issue where SES command locate fails for first time after discovery when slot number information source bit is set (SCGCQ00923283) - Fixed fault 0x4300 during discovery error recovery testing (SCGCQ00860398) - Fixed issue where SES locate was not working for external enclosure (SCGCQ00915737) - Fixed fault d060 observed when running IOs with link_reset Task management command in a loop (SCGCQ00865100, Port of SCGCQ00840603) - Fixed issue where after cable pull, SAS device page 0 entry device present for missing expander after discovery complete (SCGCQ00910603, Port of SCGCQ00904470) - Fixed PL Fault 0x6002 When Sending SCSI Security Protocol Out Commands to SATA SSDs (SCGCQ00910188, Port of SCGCQ00888033) - Fixed PL Fault 0x5833 When Performing Controller Reboots (SCGCQ00895602, Port of SCGCQ00888103) - Fixed issue where IOs completed with good status when EEDP Check enabled and EEDP error injected with 4096 block size(SCGCQ00856981, Port of SCGCQ00855669) - Fixed issue where system hangs after adapter reset with heavy IO load (SCGCQ00877119, Port of SCGCQ00646625) - Fixed issue where when using a large number of SATA drives, out of resource condition may cause IOs to be pended indefinately (SCGCQ00887685, Port of SCGCQ00885544) - Fixed issue where SATA SSDs in locked state not showing up after manually loading driver. (SCGCQ00859102, Port of SCGCQ00843668) - Fixed issue where SSD Marked Failed After Encountering 03/1100 Sense (Medium Error) (SCGCQ00945560, Port of SCGCQ00933048) - Fixed long I/O latency with large burst of non-auto I/Os generated while other read/write I/Os are running (SCGCQ00884667, Port of SCGCQ00884179) - Fixed issue where fast back-to-back or parallel PCIe configuration requests after certain addresses can generate bad Config Read data (SCGCQ01070088, Port of SCGCQ01047773) - Fixed PL Fault 0x5814 while handling Task Management during IO Timeout (SCGCQ00860153, Port of SCGCQ00842366)
UEFI Fixes: - Fixed issue where UEFI/HII offered RAID10 & RAID1E creation even when these RAID levels are disabled (SCGCQ00855519) - Fixed issue where following a system BIOS update, system hangs in HII 'Change Controller Properties'. (SCGCQ00907731) - Fixed issue where the SEP devices are not exposed in Extended SCSI Passthru protocol (SCGCQ00907013, Port of SCGCQ00905547)
UEFI Enhancements: - Use PCI IO Protocol Write function as alternate to Serial IO write function to route debug messages to serial port of host system. (SCGCQ00898744) - Add Logical Block Size of disk to device properties screen in HII. (SCGCQ00886820) - Eliminate Maximum transfer size limitation of BlockI/O calls in SAS3 IT UEFI (SCGCQ00850298) - Modify Port and Phy Configuration in UEFI HII to accomodate multiple SAS cores and disabled core. (SCGCQ00834025, Port of SCGCQ00802753) - Added relevant help message for Phy settings. (SCGCQ00869976)
BIOS Fixes: - Fixed long response delays with config utility navigation response. (SCGCQ00884882) - Fixed issue where BIOS CU displays "page read error" messages when connected to large topology. (SCGCQ00886786) - Fixed help text of format tab for 4K SAS drives. (SCGCQ00860653, Port of SCGCQ00834444)
BIOS Enhancements: - Add Logical Block Size of disk to device properties screen. (SCGCQ00898447, Port of SCGCQ00887338) - Change Auto-Refresh Interval for BIOS Configuration Utility (CU) Topology Screen (SCGCQ00898423, Port of SCGCQ00887368)
- Fixed issue where rapid successive controller resets would cause HBA to stop responding on the PCIe bus (SCGCQ00556766) - Fixed issue where when phy power management is enabled, TARGET RESET function fails yet command is reported a success. (SCGCQ00570820) - Fixed issue where PCIe Link Down can cause transmit margin field to not reset resulting in PCIe validation tests failing (SCGCQ00663185) - Fixed issue where SCSI command is not failed with expected response when SATA drive undergoing a format operation and reserved fields are set as Non-Zero value (SCGCQ00679566) - Fixed issue where read log ext command wasn't issued by PL FW to recover from error during the failure of write verify command (SCGCQ00675166) - Fixed IOC fault state 0x1609 caused by Message Unit Reset (SCGCQ00582515) - Fixed issue where SAS Phy page 1 and 2 error counters wrap around when maximum values are reached. (SCGCQ00651231) - Fixed fault 0x265D when running large block IO with higher Qdepth (SCGCQ00600832) - Fixed issue in Transport Layer Retries Code causing 0x265D and 0x0501 faults (SCGCQ00609576) - Fixed issue where Bad TLB entry causes 0x26B5 fault in IT/IR firmware (SCGCQ00629210) - Fixed 0x6828 fault when using large CDB (SCGCQ00614498) - Fixed fault 0x1901 seen when running Unmap IO’s during task aborts for a SATA drive (SCGCQ00711858) - Fixed issue where system gets hung & reboot while running IO's along with diag reset on the Controller which has Active and Inactive volumes. (SCGCQ00714125) - Fixed issue where cards would fault with 58B4 on power up due to incorrect SERDES setting (SCGCQ00728903) - Fixed WRITE SAME(10) and WRITE SAME(16) SCSI commands fail on last LBA of SATA Drive, incorrectly reporting logical block out of range. (SCGCQ00703433) - Fixed fault 0x4203 when WRITE AND VERIFY (16) command us executed to SATA Drive for LBA Out of Range (SCGCQ00705320) - Fixed issue where ATA Translation of sector count in sense data is inconsistent for READ DMA pass-through cmd (SCGCQ00712688) - Fixed issue where CLI command to dump L1 data cache causes 0x265D fault (SCGCQ00715317) - Fixed SATA Init problem causing 0x6230 controller fault (SCGCQ00683795) - Fixed fault 0x265D hit when booting controller with attached enclosure (SCGCQ00709712) - Fixed issue where Negotiated Physical Link Rate in SAS IO Unit Page 0 may not be correct after pulling a cable (SCGCQ00696408) - Fixed issue in NVDATA where SGPIO PHYs reversed (SCGCQ00750746) - Fixed I2C slave status interrupt not always cleared with I2C Write operation (SCGCQ00731646)
Firmware Enhancements: - Improved implementation of SCSI transport layer (SATL) handling while the SATA drive is in security 'frozen' state (SCGCQ00549302) - SCSI Transport Layer: Indicate support for the ATA Device Server Password security protocol (SCGCQ00625580) - IO Processor Target Mode performance improvements (SCGCQ00685827)
UEFI Fixes: - Fixed issue where the navigation of HII screens was very slow when no drives are connected to an expander (SCGCQ00569123) - Reduce the boot time for UEFI driver for large configurations. Fixes a falsely reported Backup GPT corruption. (SCGCQ00498101) (RETAIN Tip H212119) - Fixed issue where HII configuration utility did not print the complete SAS address (SCGCQ00709781) - Fixed issue where View Physical Disk Properties screen on HII was not showing correct disk details (connector:encl:slot) when more than 8 disks are directly attached. (SCGCQ00691104)
UEFI Enhancements: - Obtain the Physical Slot number from the PCI Bridge first and use fall back to SMBIOS table if unable retrieve slot number from PCI Bridge. (SCGCQ00498095) - Retry Test Unit Ready command if drive foes not respond on first try. (SCGCQ00518198) - Adding a small delay (2 seconds) to get proper operation status after starting an operation (like consistency check) in HII (SCGCQ00621480) - Enhanced HII configuration utility to display tape drive information (SCGCQ00700835)
BIOS Fixes: - Fixed issue where the system boot hangs when Legacy BIOS is disabled (using HII) on certain UEFI systems. (SCGCQ00637088) - Fixed issue where the Legacy BIOS failed to detect certain large capacity SAS drives (SCGCQ00696486)
BIOS Enhancements: - Support configurable timeout for Start Stop Unit Command. (SCGCQ00694336)
Version 1.09.04 - Moderate Impact/Low Probability of Occurrence --------------- Contains: BIOS Firmware UEFI Driver 08.21.06.00 09.00.02.00 10.00.00.00
Fixes: - Fixed issue where HDD removal not properly reported as Target Device missing when attached to adapter through an expander. (SCGCQ00777858) - Fixed issue where Fault State (0x265d) is observed in driver logs while connecting an enclosure with fully populated SATA drives (SCGCQ00856085) - Fixed issue where 0x7C54 fault seen during I/T switching (SCGCQ00847013) - Fixed issue where certain drive pull scenarios result in longer time to discovery running (~3+ seconds) (SCGCQ00843759) - Improved PCIe Config operation handling to avoid 0x0D03 faults (SCGCQ00836878) - Fixed issue where controller could fault with 0x4A00 during link break (SCGCQ00793956) - Fixed the occurrence of fault 0x1708, when a free MID is attempted to be failed to the host. (SCGCQ00826420) - Fixed occurrence of fault 0x5814/0x5813 while handling Task Management during IO Timeout (SCGCQ00865024) - Fixed issue where SATA drive with slow spin up can cause IO timeout in Linux. (SCGCQ00869554) - Fixed system hang after adapter reset with heavy IO load (SCGCQ00877099) - Fixed issue with slow BIOS interface response with certain hardware e nvironments (SCGCQ00888867) - Fixed UEFI issue where in an environment with multi-lun devices where lun size varies, backup GPT corruption can occur (SCGCQ00907441)
Enhancements: - In BIOS added a new field to Device Properties called "Logical Sector Size". The possible values are 512B, 4K and Unknown. (SCGCQ00887338) - Improved the response time in UEFI HII utility for SAS3 IT/IR Controllers (SCGCQ00821793)
Version 1.07 - Moderate Impact/Low Probability of Occurrence --------------- Contains: BIOS Firmware UEFI Driver 08.15.01.00 07.00.01.00 08.00.00.00 Firmware:
Fixes: - Fixed issue where 0xD025 fault appeared while running non-FastPath I/O to SATA disk with outstanding FastPath I/Os to SAS disk (SCGCQ00604668) - Fixed fault 0xD071 while running stress and glitching all 4 phys as part of a cable break test. (SCGCQ00590502) - Fixed MPI Power Management Global Request Change to Reduced or Standby state results in "Operation State Not Supported" or "IOC Busy" (SCGCQ00584284) - Fixed issue where when transitioning MPI Power Management speed from lower to higher rate the command falsely reported as successful (SCGCQ00584288) - Fixed issue with mixture of FastPath IO's and standard firmware path IO's timing out on SATA disks (SCGCQ00576190) - Fixed SATA only issue where Multiple 'Write Verify' SCSI commands with zero data length leads to f/w fault (0x4203 or 0x4C31). (SCGCQ00549293) - Fixed fault 0x6230 while disabling expander phys and running stress in multi-path failover environment (SCGCQ00692652) (SCGCQ00699059) - Fixed various conditions causing 0x6230 fault when cable breaking (SCGCQ00669775) (SCGCQ00699057) (SCGCQ00643835) - Fixed issue where rapid successive controller resets would cause HBA to stop responding on the PCIe bus (SCGCQ00556766) - Fixed issue where when phy power management is enabled, TARGET RESET function fails yet command is reported a success. (SCGCQ00570820) - Fixed issue where PCIe Link Down can cause transmit margin field to not reset resulting in PCIe validation tests failing (SCGCQ00663185) - Fixed issue where SCSI command is not failed with expected response when SATA drive undergoing a format operation and reserved fields are set as Non-Zero value (SCGCQ00679566) - Fixed issue where read log ext command wasn't issued by PL FW to recover from error during the failure of write verify command (SCGCQ00675166) - Fixed IOC fault state 0x1609 caused by Message Unit Reset (SCGCQ00582515) - Fixed issue where SAS Phy page 1 and 2 error counters wrap around when maximum values are reached. (SCGCQ00651231) - Fixed fault 0x265D when running large block IO with higher Qdepth (SCGCQ00600832) - Fixed issue in Transport Layer Retries Code causing 0x265D and 0x0501 faults (SCGCQ00609576) - Fixed issue where Bad TLB entry causes 0x26B5 fault in IT/IR firmware (SCGCQ00629210) - Fixed 0x6828 fault when using large CDB (SCGCQ00614498) - Fixed fault 0x1901 seen when running Unmap IO’s during task aborts for a SATA drive (SCGCQ00711858) - Fixed issue where system gets hung & reboot while running IO's along with diag reset on the Controller which has Active and Inactive volumes. (SCGCQ00714125) - Fixed issue where cards would fault with 58B4 on power up due to incorrect SERDES setting (SCGCQ00728903) - Fixed WRITE SAME(10) and WRITE SAME(16) SCSI commands fail on last LBA of SATA Drive, incorrectly reporting logical block out of range. (SCGCQ00703433) - Fixed fault 0x4203 when WRITE AND VERIFY (16) command us executed to SATA Drive for LBA Out of Range (SCGCQ00705320) - Fixed issue where ATA Translation of sector count in sense data is inconsistent for READ DMA pass-through cmd (SCGCQ00712688) - Fixed issue where CLI command to dump L1 data cache causes 0x265D fault (SCGCQ00715317) - Fixed SATA Init problem causing 0x6230 controller fault (SCGCQ00683795) - Fixed fault 0x265D hit when booting controller with attached enclosure (SCGCQ00709712) - Fixed issue where Negotiated Physical Link Rate in SAS IO Unit Page 0 may not be correct after pulling a cable (SCGCQ00696408) - Fixed issue in NVDATA where SGPIO PHYs reversed (SCGCQ00750746) - Fixed I2C slave status interrupt not always cleared with I2C Write operation (SCGCQ00731646)
Enhancements: - Improved implementation of SCSI transport layer (SATL) handling while the SATA drive is in security 'frozen' state (SCGCQ00549302) - SCSI Transport Layer: Indicate support for the ATA Device Server Password security protocol (SCGCQ00625580) - IO Processor Target Mode performance improvements (SCGCQ00685827)
UEFI:
Fixes: - Fixed issue where the navigation of HII screens was very slow when no drives are connected to an expander (SCGCQ00569123) - Reduce the boot time for UEFI driver for large configurations (SCGCQ00498101) (RETAIN Tip H212119) - Fixed issue where HII configuration utility did not print the complete SAS address (SCGCQ00709781) - Fixed issue where View Physical Disk Properties screen on HII was not showing correct disk details (connector:encl:slot) when more than 8 disks are directly attached. (SCGCQ00691104)
Enhancements: - Obtain the Physical Slot number from the PCI Bridge first and use fall back to SMBIOS table if unable retrieve slot number from PCI Bridge. (SCGCQ00498095) - Retry Test Unit Ready command if drive foes not respond on first try. (SCGCQ00518198) - Adding a small delay (2 seconds) to get proper operation status after starting an operation (like consistency check) in HII (SCGCQ00621480) - Enhanced HII configuration utility to display tape drive information (SCGCQ00700835)
BIOS:
Fixes: - Fixed issue where the system boot hangs when Legacy BIOS is disabled (using HII) on certain UEFI systems. (SCGCQ00637088) - Fixed issue where the Legacy BIOS failed to detect certain large capacity SAS drives (SCGCQ00696486)
Enhancements: - Support configurable timeout for Start Stop Unit Command. (SCGCQ00694336)
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)
BIOS/FW/UEFI Update for IBM N2115 SAS/SATA Controller
Controller Supported: IBM N2115 SAS/SATA Controller (46C8989)
NOTE TO SERVICE - Reference RETAIN #N/A
Version 1.20 - Non-Critical ------------- Contains: BIOS Firmware UEFI Driver 7.39.00.00 20.00.02.00 7.27.04.00 Enhancements: - Added System X agentless support - Indicate support for the ATA Device Server Password security protocol - Allow UEFI and BIOS to be Enabled/Disabled individually - Added ConnectorName and EnclosureLevel fields to SAS Device Page 0 to help identify physical location of a target device - Set SATA HOLD threshold to be configurable in NVDATA - If HW can gets into a stuck state, clear that state upon break received.
Fixes: - Set SAS drives to track bad blocks using a bad block table rather than using a SCSI Write Long. - Fixed DMAGroup performance issue. - Fixed issue with Phase 18 IR FW boot a RAID volume (such as raid 10), 2308 bootup hangs at OROM "Initializing.." and fault 8803 seen. - Fixed report Luns command to a SATA drive fails with CheckCondition/Invalid Field in CDB when Allocation length set to Zero. - Fixed issue where Raid Accelerator IOs can hang if the stream of IOs suddenly stops. - Fixed issue where an invalid frame sent during a PIO-mode SATA passthrough command results in resetting the drive. - Fixed issue where lots of NCQ I/O error messages were reported. - Fixed issue where certain PCIe timeouts occur in the presence of link unavailable, and a hang condition or data corruption can occur. - Fixed issue where system hangs after adapter reset with heavy IO load. - Fixed issue where access to Last Logical Block Address (LBA) of SATA Drive is Prevented and LBA out Of range by one block is missed. - Made change to deal with link getting stuck and causing missing drives. - Fixed IR issue where page header information is not filled in when RAID PHYS DISK PAGE 0 is returned for a non-RAID Disk drive. - Fixed issue where controller hits 0x265d fault while creating volume when there is an inactive volume. - DID_SOFT_ERRORs are seen when hot plug is performed on the RAID1 volume along with IOs. - Fixed issue where system gets hung and reboots while running IO's along with diag reset on the Controller which has active and inactive volumes. - Fixed latency spikes seen during performance testing on OEM system - MPI 2.5: distribute target command buffers received across multiple reply queues. - Fixed issue where command sas2flash -dflash results in a non-functional system. - Fixed issue where internal device reset storm after controller reset using long CDB. - Fixed 0x6003 Fault Due to Task Management of Lost IO - Fixed 0x58A1 fault occurs on partner controller while issuing MUR to a target mode controller with outstanding IOs. - Fixed issue where IO error and stop when hot plug a HDD from RAID1 - Fixed issue where fault 8901 is seen once the volume is roamed.
Fixes: - 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/FW/UEFI Update for IBM N2125 SAS/SATA Controller
Controller Supported: IBM N2125 SAS/SATA Controller (46C9011)
NOTE TO SERVICE - Reference RETAIN #N/A
Version 1.20 - Non-Critical ------------- Contains: BIOS Firmware UEFI Driver 7.39.00.00 20.00.02.00 7.27.04.00 Enhancements: - Added System X agentless support - Indicate support for the ATA Device Server Password security protocol - Allow UEFI and BIOS to be Enabled/Disabled individually - Added ConnectorName and EnclosureLevel fields to SAS Device Page 0 to help identify physical location of a target device - Set SATA HOLD threshold to be configurable in NVDATA - If HW can gets into a stuck state, clear that state upon break received.
Fixes: - Set SAS drives to track bad blocks using a bad block table rather than using a SCSI Write Long. - Fixed DMAGroup performance issue. - Fixed issue with Phase 18 IR FW boot a RAID volume (such as raid 10), 2308 bootup hangs at OROM "Initializing.." and fault 8803 seen. - Fixed report Luns command to a SATA drive fails with CheckCondition/Invalid Field in CDB when Allocation length set to Zero. - Fixed issue where Raid Accelerator IOs can hang if the stream of IOs suddenly stops. - Fixed issue where an invalid frame sent during a PIO-mode SATA passthrough command results in resetting the drive. - Fixed issue where lots of NCQ I/O error messages were reported. - Fixed issue where certain PCIe timeouts occur in the presence of link unavailable, and a hang condition or data corruption can occur. - Fixed issue where system hangs after adapter reset with heavy IO load. - Fixed issue where access to Last Logical Block Address (LBA) of SATA Drive is Prevented and LBA out Of range by one block is missed. - Made change to deal with link getting stuck and causing missing drives. - Fixed IR issue where page header information is not filled in when RAID PHYS DISK PAGE 0 is returned for a non-RAID Disk drive. - Fixed issue where controller hits 0x265d fault while creating volume when there is an inactive volume. - DID_SOFT_ERRORs are seen when hot plug is performed on the RAID1 volume along with IOs. - Fixed issue where system gets hung and reboots while running IO's along with diag reset on the Controller which has active and inactive volumes. - Fixed latency spikes seen during performance testing on OEM system - MPI 2.5: distribute target command buffers received across multiple reply queues. - Fixed issue where command sas2flash -dflash results in a non-functional system. - Fixed issue where internal device reset storm after controller reset using long CDB. - Fixed 0x6003 Fault Due to Task Management of Lost IO - Fixed 0x58A1 fault occurs on partner controller while issuing MUR to a target mode controller with outstanding IOs. - Fixed issue where IO error and stop when hot plug a HDD from RAID1 - Fixed issue where fault 8901 is seen once the volume is roamed.
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 SMP passthrough command failure due to smp back off interrupt. Appears in system log as 0x311c0030. (SCGCQ00889925) - Fixed issue where host boot fails in the presence of blank flash/corrupt firmware in flash (SCGCQ00894439) - Fixed issue where SATA drive errors, bad performance, or boot failure may appear after update to 20.00.02.00 firmware (SCGCQ00859226)(Retain Tip# H015210)
Version 1.20.01 - Moderate Impact/Low Probablility of Occurrence ------------- Contains: BIOS Firmware UEFI Driver 7.39.00.00 20.00.03.00 7.27.04.00
- Fixed an issue seen with RAID 10 array where during a warm OS boot, certain drive models with a long spin up delay may get marked as failed for being unresponsive. This delay ultimately triggers a rebuild of the array.
Fixes: - 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.
- Fixed SMP passthrough command failure due to smp back off interrupt. Appears in system log as 0x311c0030. (SCGCQ00889925) - Fixed issue where host boot fails in the presence of blank flash/corrupt firmware in flash (SCGCQ00894439) - Fixed issue where SATA drive errors, bad performance, or boot failure may appear after update to 20.00.02.00 firmware (SCGCQ00859226)(Retain Tip# H015210)
Version 1.20.01 - Moderate Impact/Low Probablility of Occurrence ------------- Contains: BIOS Firmware UEFI Driver 7.39.00.00 20.00.03.00 7.27.04.00
- Fixed an issue seen with RAID 10 array where during a warm OS boot, certain drive models with a long spin up delay may get marked as failed for being unresponsive. This delay ultimately triggers a rebuild of the array.
Fixes: - 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.
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-0252 --------------------
Version 20.13.1-0245 - Moderate Impact/Low Probability of Occurrence --------------------- - Fixed an issue where virtual drivers become inconsistent after the system an AC failure. (SCGCQ00897229) - Fixed an issue where Illegal request sense messages are seen repeatedly in FW logs due to attempts to collect temperaure for pds which does not support page (0x2F) at every smart poll interval. (SCGCQ00898459) - Fixed an issue where command "cli set securitykey=Lsi@12345" fails with error code "1001" and error message "invalid key". - Added a warning message when preboot configuration utility is Disabled but the user tries to launch it. (SCGCQ00662761) - Fixed an issue where WebBIOS Advance software option menu from main page could hang the system. (SCGCQ00683327) - Updated the drive speed display string to support 12Gb/s (SCGCQ00751036) - Corrected inconsistency in size showing in for total capacity property between webBIOS and MSM (SCGCQ00752176)
Version 20.13.1-0200 - Critical ------------------- Enhancement: - Display drive speed for 12 GB Seagate hard drives in MSM. - List battery status in BIOS as N/A for iMR controllers 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 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-0252_linux_32-64_chg
ServeRAID 6GB SAS/SATA Controller Firmware Update
Adapters Supported: ServeRAID M5110 SAS/SATA Controller for IBM System x (81Y4481) ServeRAID M5110e SAS/SATA Controller for IBM System x ServeRAID M5120 SAS/SATA Controller for IBM System x (81Y4478) ServeRAID M5016 SAS/SATA Controller for IBM System x (90Y4304) ServeRAID M5115 SAS/SATA Controller for IBM Flex System (90Y4390) ServeRAID M5016 SAS/SATA Controller for IBM System x (90Y4304)
NOTE TO SERVICE - Reference RETAIN #N/A
Version 23.34.0-0009 - High Impact/High Probability of Occurrence -------------------- FW Package: 23.24.0-0009
HII: 03.17.14.02
UEFI Driver: 0x06110200
BIOS: 5.50.03.0
MR FW: 3.460.35-6104
iMR FW: 3.460.34-6103
Fixes:
- Fixed the potential of a data miscompare that was observed only at a vendor test facility under very heavy IO and abnormal practices (SCGCQ00995594, Port of SCGCQ00976904)
- Fixed an issue where error "Controller encountered fatal error and was reset" may occur under heavy IO and background operations (SCGCQ00894643)
- Fixed an issue where VMWare may crash when a Guest Operating System is powered off (SCGCQ00872121, Port of SCGCQ00854914)
- Fixed an issue where write-verify performance was lower than expected (SCGCQ00858151, SCGCQ00874193)
- Fixed an issue where "I2C 4 PID 10 SCL STUCK Low! while I2C Rx receiving data intStatus 00008000" may appear in firmware log (SCGCQ01007592)
- Fixed an issue where the Measured Voltage instead of Charging Voltage was displayed in event log (SCGCQ00876489)
- Fixed an issue where Supercap "Battery Not Present" error may occur after shutdown or reboot during a learn cycle (SCGCQ00917115)
- Fixed an issue where Write-through and Write-back cache policies can be changed via Windows Logical Disk Properties. (SCGCQ00856979)
- Fixed an issue where enclosures may go missing when connected in daisy-chain after multiple expander reset cycles (SCGCQ00840725, Port of SCGCQ00818569)
- Fixed an issue where MegaRAID Storage Mananger may display an error message if 'Schedule Consistency Check' is selected. (SCGCQ00852649, Port of SCGCQ00832908)
- Fixed an issue where Patrol Read Properties window does not pop up on MegaRAID Storage Manager (SCGCQ00862478, Port of SCGCQ00797676)
- Fixed an issue where MegaRAID Storage Manager shows messages with Error code 240 and no description (SCGCQ00970948, Port of SCGCQ00904466)
- Fixed an issue where Amber LED may turn on erroneously when an enclosure's slot numbers start with 0 but bay numbers start with 1 (SCGCQ01019622, Port of SCGCQ00903181)
- Fixed an issue where the Generic RAID1 profile option in HII is not greyed-out after creating 64 Virtual Drives (SCGCQ00826822, Port of SCGCQ00816137)
- Fixed an issue where firmware may hang until system is reset (SCGCQ00928869, Port of SCGCQ00923286)
- Fixed an issue where a Virtual Drive may disappear on reboot if it was created with drives from a previously-erased Virtual Drive (SCGCQ00937912, Port of SCGCQ00900237)
- Fixed an issue where Functional Level Reset was not supported (SCGCQ00854343, Port of SCGCQ00840253)
- Fixed an issue where an "L2 unrecoverable cache error" may occur when modifying Patrol read properties (SCGCQ00854668, Port of SCGCQ00847162)
- Fixed an issue where a Hot Spare disk may become Unconfigured Good on reboot (SCGCQ00862477, Port of SCGCQ00803341)
- Fixed an issue where SafeID may change on repeated queries using StorCLI (SCGCQ00949550, Port of SCGCQ00941577)
- Fixed an issue where error "MonTask: line 1272 in file ../../raid/1078dma.c" may occur while running IO in Virtual Machines (SCGCQ01016071, Port of SCGCQ00822403)
- Fixed an issue where incorrect connector information "connector: null x0" shows in MegaRAID Storage Manager (SCGCQ01016040, Port of SCGCQ00996578)
- Fixed an issue where a concurrent Consistency Check cannot be started after resetting adapter to factory defaults (SCGCQ00839437, Port of SCGCQ00838830)
- Fixed an issue where JBOD mode may be disabled if a Virtual Drives is offline (SCGCQ00871662, Port of SCGCQ00827731)
Enhancements:
- Added protection for clearing Foreign Configuration if preserved cache exists (SCGCQ00880783, Port of SCGCQ00842327)
- Enhanced cache restore operation for when restore data size is different than cache size (SCGCQ00860303, Port of SCGCQ00855038)
Version 23.34.0-0006 --------------------
Version 23.33.0-0044 --------------------
Version 23.33.0-0043 - High Impact/High Probability of Occurrence ----------- Fixes: - Fixed an issue where hard drive slot amber LED not functioning correctly. - Fixed an issue in iMR mode where "Controller encountered fatal error and was reset" errors can occur under heavy IOs and background operations (SCGCQ00894643) (RETAIN Tip H001154) - Fixed an issue where BBU status says optimal but firmware logs indicate that the BBU has failed (SCGCQ00838052) (RETAIN Tip H214857) - Fixed an issue where importing a foreign configuration may fail after reconstruction on 4k sector drives (SCGCQ00830109) - Fixed an issue where the firmware may allow the OS to change VD cache settings (SCGCQ00842350) - Fixed an issue where MR firmware reports "no SMART" error when attaching a PFA drive (SCGCQ00839455) - Fixed an issue where the firmware may hang (enter MonTask) when a guest OS is powered on or off in VMWare (SCGCQ00854914) - Fixed an issue where setting the learn cycle property of iBBU09 gives an I2C error (SCGCQ00831315) - Fixed an issue where "Prepare for Removal" does not work on a PD when drive erase is in progress (SCGCQ00811219) - Fixed an issue where MSM displays "The requested command has invalid arguments" error message if 'Schedule Consistency Check' is selected (SCGCQ00852649) - Fixed an issue where cache memory size in iMR is not showing 0 (SCGCQ00838893) - Fixed an issue where an incorrect MFI_STAT_PD_TYPE_WRONG error is returned by the firmware when PDs with different block size are mixed (SCGCQ00840251) - Fixed an issue where the controller reports cache memory size as 0 when no logical drives are present (SCGCQ00837600) - Fixed an issue where concurrent consistency check cannot be started after issuing "setfactorydefaults" command (SCGCQ00839437) - Fixed an issue where uEFI may report LSI EFI driver "Unhealthy" or "Failed" when more than 64VDs are configured (SCGCQ00831006) - Fixed an issue where functional level reset was not properly showing as unsupported (SCGCQ00854343) - Fixed an issue where the legacy CTRL-H utility may report the wrong PCIe slot number (SCGCQ00799339) - Fixed an issue where the legacy OpROM may show an expander as a JBOD drive in POST (SCGCQ00809682) - Fixed an issue where an encrypted JBOD may be presented to the system in encrypted form even though password was entered incorrectly (SCGCQ00808086)
Enhancements: - Added ability to determine SuperCap revision ID when VPD is not programmed (SCGCQ00828990) - Added support for SES RQST_OK deassertion for customer proprietary JBOD SEP (SCGCQ00834321) - Added feature to enable support for detecting CPLD code version (SCGCQ00840631) - Added feature to enable drive fault LED to be lit when a known-bad drive is connected to the controller (SCGCQ00858142) - Added feature to turn on drive Fault LED when the controller detects a drive that was previously marked Bad (SCGCQ00858140)
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_6gb-23_34_0-0009_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
Integrated Management Module II (IMM2) Firmware Update Change History
Version 5.60, 1AOO72H - NonCritical - Supports systems: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4, x220, x222, x240, x440, x280, x480, x880 - Firmware changes to address security vulnerabilities: CVE-2015-5219, CVE-2015-5300, CVE-2016-0778, CVE-2015-3194, CVE-2015-3195, CVE-2015-3196, CVE-2015-7981, CVE-2015-8126, CVE-2016-0705, CVE-2016-0797, CVE-2016-0799, CVE-2015-8472, CVE-2015-8126, CVE-2015-8710, CVE-2016-0755 - Added support to filter out invalid drive information from the RAID controller - Fixed a problem on the x3750 M4 that causes the IMM to report a power supply mismatch fault - Fixed a problem that causes the IMM to unexpectedly reset on the x3850 X6 and x3950 X6 - Fixed a problem with the power capping settings that causes the x3850 x6 to power off - Fixed a problem that causes the configuration restore operation to fail when the system has 12 network ports. - Fixed a problem where the IMM reports a system volume fault and the x3550 M4 cannot be powered on - Added changes to make the firmware more robust and avoid hang conditions. - Added changes to enhance DSA/OneCLI IPMI-LAN access.
Version 5.41, 1AOO70I - Critical - Supports systems: x3550 M4 - Firmware improvement to address a potential reliability issue for a voltage regulator. Not updating to this level could lead to a failed system board. Please refer to tip HT 118532.
Version 5.40, 1AOO70H - Critical - Supports systems: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4, x220, x222, x240, x440, x280, x480, x880 - Firmware changes to address security vulnerabilities: CVE-2015-7575, CVE-2016-0777, CVE-2016-0778 - Corrected a problem that prevented Lenovo XClarity Administrator from authenticating with the IMM2 - Fixed a problem on the x3850 X6 where the server unexpectedly reboots after an IMM2 reset - Fixed a problem on the x480 X6 that causes the CMM to report an 'unknown' IO connectivity status - Fixed a problem on the x3650 M4 that causes fan3 and fan4 to run at incorrect speeds - Fixed a problem that prevented the IMM2 gateway setting from being changed on the IMM2 web and in the UEFI menu. - Fixed a problem on the x3650 M4 where LDAP authentication does not work
Version 5.20, 1AOO68L - Critical - Supports systems: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4, x240, x440, x280, x480, x880 - Firmware changes to address security vulnerabilities: CVE-2013-2207, CVE-2013-4508, CVE-2013-4559, CVE-2013-4560, CVE-2014-5352, CVE-2014-5353, CVE-2014-5355, CVE-2014-8121, CVE-2014-8176, CVE-2014-9421, CVE-2014-9422, CVE-2015-1349, CVE-2015-1781, CVE-2015-1788, CVE-2015-1789, CVE-2015-1790, CVE-2015-1791, CVE-2015-1792, CVE-2015-1799, CVE-2015-3216, CVE-2015-3405, CVE-2015-4000, CVE-2015-4171, CVE-2015-4620, CVE-2015-5477, CVE-2015-5600, CVE-2015-5722 - Re-enabled the EDH cipher for the LDAP client - Fixed a problem on x3550 M4 where MSM connectivity issue on X3650 M4 and X3550 M4 with ESXi 5.5 u2 on IMM v4.97 - Fixed a problem where setting NIST800-131A mode on the web, CLI, and SNMP is inconsistent - Fixed a problem where the signed certificate status on the web and the CLI does not match - Fixed a problem on x3650 M4 where the "NvDIMM Status & Cables" sensor does not de-assert - Fixed a problem where the DIMM's Manufacturer ID information is not displayed - Fixed a problem where the password is not changed after setting the password via OneCLI - Fixed a problem where a user cannot log using LDAP Active Directory Application Mode - Fixed a problem on x3850 X6 where the IMM2 does not detect power supply faults and over-temperature conditions - Fixed a problem on x3500 M4/x3550 M4/x3650 M4/x3650 M4 HD where the IMM2 reports power supply configuration mismatch assertion and deassertion events within seconds - Re-enabled TLS1.0/TSL1.1 support for the web and WS-MAN interfaces when the IMM2 is in NIST mode - Fixed a problem on x3100 M4/x3250 M4 where there is no alert message logged when AC power is lost
Version 4.97, 1AOO66M - NonCritical - Supported Platforms: HS23, HS23E, x3100 M4, x3100 M5, x3250 M4, x3250 M5, x3300 M4, x3500 M4, x3530 M4, x3550 M4, x3630 M4, x3650 M4, x3650 M4 BD, x3650 M4 HD, x3750 M4, x3850 X6, x3950 X6, dx360 M4, nx360 M4 - 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. - After applying this firmware update all subsequent self-signed certificates are generated using SHA-2 cryptographic hashes. Certificate signing requests are also generated using SHA-2 cryptographic hashes if the IMM2 is configured to run in NIST SP 800-131A Compliance mode. - Critical Fix for x3750 M4 -- Fixed issue on missing power supply redundancy lost event - Firmware changes to address security vulnerabilities: CVE-2013-2566, CVE-2013-2877, CVE-2013-4332, CVE-2013-4854, CVE-2013-6435, CVE-2014-0191, CVE-2014-3505, CVE-2014-3506, CVE-2014-3507, CVE-2014-3508, CVE-2014-3509, CVE-2014-3510, CVE-2014-3511, CVE-2014-3513, CVE-2014-3566, CVE-2014-3567, CVE-2014-3568, CVE-2014-3569, CVE-2014-3570, CVE-2014-3571, CVE-2014-3572, CVE-2014-3634, CVE-2014-3660, CVE-2014-3683, CVE-2014-8118, CVE-2014-8275, CVE-2014-8500, CVE-2014-9293, CVE-2014-9294, CVE-2014-9295, CVE-2014-9297, CVE-2014-9298, CVE-2015-0204, CVE-2015-0205, CVE-2015-0206, CVE-2015-0235, CVE-2015-2808, CVE-2013-7423, CVE-2014-5352, CVE-2014-7817, CVE-2014-9402, CVE-2014-9421, CVE-2014-9422, CVE-2014-9423, CVE-2015-0209, CVE-2015-0286, CVE-2015-0287, CVE-2015-0288, CVE-2015-0289, CVE-2015-0292, CVE-2015-0293, CVE-2015-1472 - 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 - NonCritical - Firmware changes to address security vulnerabilities: CVE-2013-2566, CVE-2013-2877, CVE-2013-4332, CVE-2013-4854, CVE-2013-6435, CVE-2014-0191, CVE-2014-3505, CVE-2014-3506, CVE-2014-3507, CVE-2014-3508, CVE-2014-3509, CVE-2014-3510, CVE-2014-3511, CVE-2014-3513, CVE-2014-3566, CVE-2014-3567, CVE-2014-3568, CVE-2014-3569, CVE-2014-3570, CVE-2014-3571, CVE-2014-3572, CVE-2014-3634, CVE-2014-3660, CVE-2014-3683, CVE-2014-8118, CVE-2014-8275, CVE-2014-8500, CVE-2014-9293, CVE-2014-9294, CVE-2014-9295, CVE-2014-9297, CVE-2014-9298, CVE-2015-0204, CVE-2015-0205, CVE-2015-0206, CVE-2015-0235, CVE-2015-2808 - 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 - NonCritical - 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 - NonCritical - 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.50, 1AOO64L - NonCritical - Updated the firmware with patches to address the OpenSSL vulnerabilities listed in CVE-2014-3509, CVE-2014-3506, CVE-2014-3507, CVE-2014-3505, CVE-2014-3508, 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 - Fixed a problem where an erroneous event could be logged for an expansion card that would be followed by a recovery message several seconds later. - Fixed an issue with the web interface that could show a firmware update has failed if the user leaves the web interface inactive for over 20 minutes after downloading the update file. - Corrected an issue that might cause erroneous faults to be reported for the ServeRAID M5115 SAS/SATA when the server power is off. - Fixed an issue for multinode partition capable systems where when switching between partition and stand-alone modes repeatedly while also powering the nodes on and off, the IMM2 mode information could get out of sync with the server.
Version 4.35, 1AOO62W - Refresh Release - Support for refresh of the System x3650 M4 BD, Machine Type: 5466
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.23, 1AOO62Z - Initial Release - Adds support for System x880 X6, Machine Type: 4259, 7903
Version 4.21, 1AOO58U - NonCritical - 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 4.20, 1AOO58R - NonCritical - Fixed an issue in I2C communications that could cause CMM to report, "FPGA Host 2 Communication is offline" - Fixed a problem that required the browser cache to be cleared before accessing IMM2 web page. - Corrected a problem that caused the CMM to reporting an I/O connectivity problem with the FSM - Enhanced the IMM2 service and support data to better aid in the diagnosis of VPD issues - Added support for the S3 system sleep state - Added support for agentless monitoring of PCIe devices - Enabled a Flex compute node to be powered on sooner after installation in the chassis - Added RFC compliance checking for user input - Ensured consistency in Daylight Savings Time setting between the CMM and IMM2 - Added support for enhanced hard drive monitoring and status - Corrected an issue that caused false reports of incorrect / missing / corrupt VPD events.
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 4.10, 1AOO58F - Initial Release - Supports System x3100 M5, Machine Type: 5457
Version 4.04, 1AOO64E - NonCritical - Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839 - Fixed potential problem where Memory Details on Critical DIMM points to a different location - Fixed potential problem for power state mismatching when one node transitions from AC disconnected to AC connected while the other node is powered up
Version 4.02, 1AOO58S - NonCritical - Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839 - Fixed a potential problem where a single CPU and single Power Supply model may show a configuration error - Fixed a potential problem where fans running at high speed under normal operation may erroneously log a fan failure - 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 - Fixed a power state change problem when removing a Compute book with an I/O book attached - Fixed a problem where PCIE adapters in I/O books may not show up after an OS reboot
Version 4.00, 1AOO58I - NonCritical - Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839 - Add Scalable support. - x3950 X6 initial GA support level - Add support for enhanced hard drive monitoring and status - Fixed a potential problem that may cause the IMM to reboot in a configuration with multiple single port network cards.
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.90, 1AOO54X - NonCritical - Added support for the IBM NeXtScale PCIe Native Expansion (NeX) Tray for IBM NeXtScale nx360 M4
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.85, 1AOO56U - Critical - Critical Fix for x220, x222, x240, x440, Flex System Manager Node -- 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.84, 1AOO56J - Critical - Critical Fix for x3300 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.83, 1AOO56I - Critical - Critical Fix for x3250 M5, nx360 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.82, 1AOO56E - Critical - Critical Fix for x3850 X6 / x3950 X6 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.81, 1AOO52Z - Critical - Critical fix: -- Corrected the x3850/x3950 x6 server to turn off power from the power supplies when a power fault occurs
Version 3.80, 1AOO52U - Initial Release - Supports IBM System x3850/x3950 X6, Machine Type: 3837, 3839 - up to 4 CPU in one system - x3850 X6 initial GA support level
Version 3.79, 1AOO56G - Critical - Critical Fix for x240, x222, x440, x220, Flex System Manager Node -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.78, 1AOO52Y - Critical - Critical Fixes: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882) -- Fixed a potential security vulnerability with Trusted Platform Module (TPM) initialization settings (refer to security bulletin CVE-2014-0881)
Version 3.77, 1AOO56H - Critical - Critical Fix for x3630 M4, x3530 M4 -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.76, 1AOO56Q - Critical - Critical Fix for x3650 M4 BD -- 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.75, 1AOO56F - Critical - Critical Fix for x3650 M4 BD -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
Version 3.74, 1AOO52R - Critical - Critical Fix: -- Fixed a potential security vulnerability with information contained in service data (refer to security bulletin CVE-2014-0882) - Supports System x3650 M4 BD, Machine Type: 5466
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.62, 1AOO56T - Critical - Critical Fix for x220, x222, x240, x440, Flex System Manager Node -- 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 2.61, 1AOO44V - Critical - Critical Fix for x240, x220, x440, x222, Flex System Manager Node -- Updated the firmware with patches to address the 'Heartbleed' OpenSSL bug (CVE-2014-0160)
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: | DHE-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-SHA256 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
IMPORTANT NOTICE: For X3300 M4, it is required to upgrade both the primary and backup IMM2 firmware to Version 1.86, 1AOO40D or later. After the IMM2 is successfully updated, it is highly recommended to run the following IPMI command: Get device id (ipmitool raw 6 1) If the last two bytes returned show 0x2A 0x41 even after a reset of the IMM2, please refer to TDR-H207183 or MIGR-5092140 for more information.
Version 1.86, 1AOO40D - Critical - Critical Fix: -- Fixed a problem where the X3300 M4 system configured with a M5110/M5120 RAID card plus the "IBM ServeRAID M5100 Series 512MB/1 gigabytes (GB) Flash/RAID 5 Upgrade for IBM System x" option might have problem if AC power is removed while the system is running
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) - Initial Release - 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.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.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 - 2016. All rights reserved.
ibm_fw_imm2_1aoo72h-5_60_anyos_noarch_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)
Version 8.00.00.00 - Moderate Impact/Low Probability of Occurrence ------------------ Fixes: - Driver initialization fails after some random iterations of load/unload of mpt3sas driver module (SCGCQ00589083) - Kernel Panic seen while booting the system with blank card. (SCGCQ00574258) - Driver initialization fails while performing HBA device hotplug/unplugs operations (SCGCQ00526796) - During driver load with a flaky disk in the setup, discovery related I/O times out which results in SCSI error recovery initiating host reset and then the controller won't see any disk (SCGCQ00571398) - During hot-plugging of a disk (having a flaky link) the disk addition stops and any further disk addition or removal doesn't happen on that controller. (SCGCQ00571402) - Drives attached to the expander are not discovered (SCGCQ00571418) - The driver message logs contain an entry "mpt2sas0: _base_get_ioc_facts: failed going to ready state (SCGCQ00571424) - device_unblock messages are not seen in the logs regarding device unblock (SCGCQ00664470) - Kernel panic while issuing LUN reset or target reset during running IOs (SCGCQ00655811) - Kernel Panic is seen when issued Diag reset from task management (SCGCQ00654562) - When IOC goes bad, while flushing the IOs, protection info SGLs are not released for DIF IOs. (SCGCQ00664893) - Synchronization between PF and VF host drivers is missing while performing diag reset operation and it leads to firmware faults such as 0x1500 (SCGCQ00682671) - When LUN 0 is offline, the other LUNs were not visible to the system. (SCGCQ00703194)
Enhancements: - Added code to display Location of End Device. (SCGCQ00452326) - On detecting that the IOC is over heated and entered fault state, the driver flush all running commands, and forces a panic with message ‘TEMPERATURE FAULT: STOPPING' (SCGCQ00654911) - Added new module parameter to allow /disallow host driver to issue SCSI commands to bring up drive. (SCGCQ00609923)
Version 4.00.01.00 - Non-Critical ------------------ Enchancement: - Add support for SLES 11 SP 3
Version 3.00.00.00 - Initial release ------------------ ibm_dd_mpt3sas_12_00_00_00_sles11_32-64_chg
 Broadcom NetXtreme TG3 Linux Driver
Version 3.137n
Copyright (c) 2015 Broadcom Corporation All rights reserved
tg3: Modify tg3_tso_bug() to handle multiple TX rings
tg3_tso_bug() was originally designed to handle only HW TX ring 0, Commit d3f6f3a1d818410c17445bce4f4caab52eb102f1 ("tg3: Prevent page allocation failure during TSO workaround") changed the driver logic to use tg3_tso_bug() for all HW TX rings that are enabled. This patch fixes the regression by modifying tg3_tso_bug() to handle multiple HW TX rings.
Signed-off-by: Prashant Sreedharan Signed-off-by: Michael Chan Signed-off-by: David S. Miller
Commit 506724c463fcd63477a5e404728a980b71f80bb7 "tg3: Override clock, link aware and link idle mode during NVRAM dump" changed the timeout value for nvram command execution from 100ms to 1ms. But the 1ms timeout value was only sufficient for nvram read operations but not write operations for most of the devices supported by tg3 driver. This patch sets the MAX to 50ms. Also it uses usleep_range instead of udelay.
Signed-off-by: Prashant Sreedharan Signed-off-by: Michael Chan Suggested-by: David Miller Signed-off-by: David S. Miller
tg3: Clear NETIF_F_TSO6 flag before doing software GSO
Commit d3f6f3a1d818410c17445bce4f4caab52eb102f1 ("tg3: Prevent page allocation failure during TSO workaround") modified driver logic to use tg3_tso_bug() for any TSO fragment that hits hardware bug conditions thus the patch increased the scope of work for tg3_tso_bug() to cover devices that support NETIF_F_TSO6 as well. Prior to the patch, tg3_tso_bug() would only be used on devices supporting NETIF_F_TSO.
A regression was introduced for IPv6 packets requiring the workaround. To properly perform GSO on SKBs with TCPV6 gso_type, we need to call skb_gso_segment() with NETIF_F_TSO6 feature flag cleared, or the function will return NULL and cause a kernel oops as tg3 is not handling a NULL return value. This patch fixes the problem.
Signed-off-by: Prashant Sreedharan Signed-off-by: Michael Chan Signed-off-by: David S. Miller
commit 014b20133bcd442db554c2d2d86181b34cd15b66 commit 506724c463fcd63477a5e404728a980b71f80bb7 Author: Prashant Sreedharan Date: Sat May 24 01:32:09 2014 -0700
tg3: Override clock, link aware and link idle mode during NVRAM dump
When cable is not present the clock speed of some of the devices is reduced based upon power saving mode setting in NVRAM. Due to this NVRAM reads take long time to complete as a result CPU soft lockup message is seen. Fix is to override clock, disable link aware and link idle modes before NVRAM reads and restore them back after the reads are complete. During this period also check if the thread needs to be rescheduled and if there are any signals to handle.
Also decrease the NVRAM command execution timeout value to 1ms.
Signed-off-by: Prashant Sreedharan Signed-off-by: Michael Chan Signed-off-by: David S. Miller
commit de750e4c4bf36b8a14401527e6541e8620ea6267 Author: Michael Chan Date: Sun May 11 20:22:55 2014 -0700
tg3: Update copyright and version to 3.137
Signed-off-by: Michael Chan Signed-off-by: David S. Miller
commit d3f6f3a1d818410c17445bce4f4caab52eb102f1 Author: Michael Chan Date: Sun May 11 20:22:54 2014 -0700
tg3: Prevent page allocation failure during TSO workaround
If any TSO fragment hits hardware bug conditions (e.g. 4G boundary), the driver will workaround by calling skb_copy() to copy to a linear SKB. Users have reported page allocation failures as the TSO packet can be up to 64K. Copying such a large packet is also very inefficient. We fix this by using existing tg3_tso_bug() to transmit the packet using GSO.
Signed-off-by: Prashant Sreedharan Signed-off-by: Michael Chan Signed-off-by: David S. Miller
commit d71c0dc4e961e74143a644f248fc1a39cabf6586 Author: Michael Chan Date: Sun May 11 20:22:53 2014 -0700
tg3: Don't modify ip header fields when doing GSO
tg3 uses GSO as workaround if the hardware cannot perform TSO on certain packets. We should not modify the ip header fields if we do GSO on the packet. It happens to work by accident because GSO recalculates the IP checksum and IP total length.
Also fix the tg3_start_xmit comment to reflect that this is the only xmit function for all devices.
Signed-off-by: Prashant Sreedharan Signed-off-by: Michael Chan Signed-off-by: David S. Miller
tg3: Do not include vlan acceleration features in vlan_features
Including hardware acceleration features in vlan_features breaks stacked vlans (Q-in-Q) by marking the bottom vlan interface as capable of acceleration. This causes one of the tags to be lost and the packets are sent with a sing vlan header.
CC: Nithin Nayak Sujir CC: Michael Chan Signed-off-by: Vlad Yasevich Signed-off-by: David S. Miller
commit d7b95315cc7f441418845a165ee56df723941487 Author: Michael Chan Date: Fri Feb 28 15:05:10 2014 -0800
tg3: Don't check undefined error bits in RXBD
Redefine the RXD_ERR_MASK to include only relevant error bits. This fixes a customer reported issue of randomly dropping packets on the 5719.
Signed-off-by: Michael Chan Signed-off-by: David S. Miller
tg3: Poll cpmu link state on APE + ASF enabled devices
On ASF enabled devices where the mgmt firmware runs on the application processing engine, there is a race between the tg3 driver processing a link change event and the ASF firmware clearing the link changed bit in the EMAC status register. This leads to link notifications to the driver sometimes getting lost.
Poll the CPMU link state as a backup for the normal interrupt path update if ASF is enabled.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
tg3: Set the MAC clock to the fastest speed during boot code load
On the 5717, 5718 and 5719 devices, the bootcode runs slower when any port doesn't have a link due to clock speed slowing down as part of the link-aware feature. This leads to the driver timing out waiting for the bootcode signature.
This patch overrides the clock policy to the highest frequency just before reset and restores it after the bootcode is up.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
commit e565eec31d9d5b1024311564f6536162df951de4 Author: Michael Chan Date: Fri Jan 3 10:09:12 2014 -0800
tg3: Add unicast filtering support.
Up to 3 additional unicast addresses can be added to the perfect match filter table.
Signed-off-by: Michael Chan Signed-off-by: Nithin Nayak Sujir Signed-off-by: David S. Miller
commit f022ae62dd84425192b27100dcf907019f654d02 Author: Michael Chan Date: Fri Jan 3 10:09:11 2014 -0800
tg3: Refactor __tg3_set_mac_addr()
so that individual MAC address filter entries can be set.
Signed-off-by: Michael Chan Signed-off-by: Nithin Nayak Sujir Signed-off-by: David S. Miller
tg3: Expand 4g_overflow_test workaround to skb fragments of any size.
The current driver assumes that an skb fragment can only be upto jumbo size. Presumably this was a fast-path optimization. This assumption is no longer true as fragments can be upto 32k.
v2: Remove unnecessary parantheses per Eric Dumazet.
Cc: stable@vger.kernel.org Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
tg3: Initialize REG_BASE_ADDR at PCI config offset 120 to 0
The new tg3 driver leaves REG_BASE_ADDR (PCI config offset 120) uninitialized. From power on reset this register may have garbage in it. The Register Base Address register defines the device local address of a register. The data pointed to by this location is read or written using the Register Data register (PCI config offset 128). When REG_BASE_ADDR has garbage any read or write of Register Data Register (PCI 128) will cause the PCI bus to lock up. The TCO watchdog will fire and bring down the system.
Signed-off-by: Nat Gurumoorthy Acked-by: Michael Chan Signed-off-by: David S. Miller
tg3: Expand multicast drop counter miscounting fix to 5762
commit 4d95847381228639844c7197deb8b2211274ef22 - "tg3: Workaround rx_discards stat bug", added a workaround for miscounted statistics for multicast packets. This fix needs to be applied to the 5762.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
tg3: Add flag to disable 1G Half Duplex advertisement
Some link partners have issues if the non-standard 1G half duplex is advertised. This patch adds support for an nvram setting to disable the advertisement.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
rxbds_empty is an informational statistic signifying that a ring full condition was observed. It does not mean an overflow has occurred.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
commit 8496e85c20e7836b3dec97780e40f420a3ae2801 Author: Rafael J. Wysocki Date: Sun Dec 1 02:34:37 2013 +0100
PCI / tg3: Give up chip reset and carrier loss handling if PCI device is not present
Modify tg3_chip_reset() and tg3_close() to check if the PCI network adapter device is accessible at all in order to skip poking it or trying to handle a carrier loss in vain when that's not the case. Introduce a special PCI helper function pci_device_is_present() for this purpose.
Of course, this uncovers the lack of the appropriate RTNL locking in tg3_suspend() and tg3_resume(), so add that locking in there too.
These changes prevent tg3 from burning a CPU at 100% load level for solid several seconds after the Thunderbolt link is disconnected from a Matrox DS1 docking station.
Signed-off-by: Rafael J. Wysocki Acked-by: Michael Chan Signed-off-by: David S. Miller
commit 7260899bde50cbe84bdf0a15b5642e2c3b03db32 Author: Ben Hutchings Date: Mon Nov 18 22:59:43 2013 +0000
tg3: Implement the SIOCGHWTSTAMP ioctl
While we're doing this, fix the error code for SIOCSHWTSTAMP ioctl on non-timestamping hardware.
Compile-tested only.
Signed-off-by: Ben Hutchings
commit 58b187c68d91b54b82f6fd267ee3346ed8770655 Author: Ben Hutchings Date: Thu Nov 14 00:40:56 2013 +0000
tg3: Validate hwtstamp_config completely before applying it
tg3_hwtstamp_ioctl() should validate all fields of hwtstamp_config before making any changes. Currently it sets the TX configuration before validating the rx_filter field.
Compile-tested only.
Signed-off-by: Ben Hutchings Acked-by: Nithin Nayak Sujir Signed-off-by: David S. Miller
commit 85aec73d595b8847f9c4ea571deb127913f0d508 Author: Ivan Vecera Date: Wed Nov 6 14:02:36 2013 +0100
tg3: avoid double-freeing of rx data memory
If build_skb fails the memory associated with the ring buffer is freed but the ri->data member is not zeroed in this case. This causes a double-free of this memory in tg3_free_rings->... path. The patch moves this block after setting ri->data to NULL. It would be nice to fix this bug also in stable >= v3.4 trees.
Cc: Nithin Nayak Sujir Cc: Michael Chan Signed-off-by: Ivan Vecera Acked-by: Michael Chan Signed-off-by: David S. Miller
commit d458cdf712e0c671e8e819abb16ecd6e44f9daec Author: Joe Perches Date: Tue Oct 1 19:04:40 2013 -0700
net:drivers/net: Miscellaneous conversions to ETH_ALEN
Convert the memset/memcpy uses of 6 to ETH_ALEN where appropriate.
Also convert some struct definitions and u8 array declarations of [6] to ETH_ALEN.
Signed-off-by: Joe Perches Acked-by: Arend van Spriel Signed-off-by: David S. Miller
tg3: add support a phy at an address different than 01
When phylib was in use tg3 only searched at address 01 on the mdio bus and did not work with any other address. On the BCM4705 SoCs the switch is connected as a PHY behind the MAC driven by tg3 and it is at PHY address 30 in most cases. This is a preparation patch to allow support for such switches.
phy_addr is set to TG3_PHY_MII_ADDR for all devices, which are using phylib, so this should not change any behavior.
Signed-off-by: Hauke Mehrtens Acked-by: Nithin Nayak Sujir Signed-off-by: David S. Miller
Commit 989038e217e94161862a959e82f9a1ecf8dda152 ("tg3: Don't turn off led on 5719 serdes port 0") added code to skip turning led off on port 0 of the 5719 since it powered down other ports. This workaround needs to be enabled on the 5720 as well.
Cc: stable@vger.kernel.org Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
commit ede23fa8161c1a04aa1b3bf5447812ca14b3fef1 Author: Joe Perches Date: Mon Aug 26 22:45:23 2013 -0700
drivers:net: Convert dma_alloc_coherent(...__GFP_ZERO) to dma_zalloc_coherent
__GFP_ZERO is an uncommon flag and perhaps is better not used. static inline dma_zalloc_coherent exists so convert the uses of dma_alloc_coherent with __GFP_ZERO to the more common kernel style with zalloc.
Remove memset from the static inline dma_zalloc_coherent and add just one use of __GFP_ZERO instead.
Trivially reduces the size of the existing uses of dma_zalloc_coherent.
Realign arguments as appropriate.
Signed-off-by: Joe Perches Acked-by: Neil Horman Acked-by: Jesse Brandeburg Acked-by: Jeff Kirsher Signed-off-by: David S. Miller
While EEH error happens, we might not have network device instance (struct net_device) yet. So we can't access the instance safely and check its link state, which causes kernel crash. The patch fixes it.
EEH: Frozen PE#2 on PHB#3 detected EEH: This PCI device has failed 1 times in the last hour EEH: Notify device drivers to shutdown (NULL net_device): PCI I/O error detected Unable to handle kernel paging request for data at address 0x00000048 Faulting instruction address: 0xd00000001c9387a8 Oops: Kernel access of bad area, sig: 11 [#1] SMP NR_CPUS=1024 NUMA PowerNV : NIP [d00000001c9387a8] .tg3_io_error_detected+0x78/0x2a0 [tg3] LR [d00000001c9387a4] .tg3_io_error_detected+0x74/0x2a0 [tg3] Call Trace: [c000003f93a0f960] [d00000001c9387a4] .tg3_io_error_detected+0x74/0x2a0 [tg3] [c000003f93a0fa30] [c00000000003844c] .eeh_report_error+0xac/0x120 [c000003f93a0fac0] [c0000000000371bc] .eeh_pe_dev_traverse+0x8c/0x150 [c000003f93a0fb60] [c000000000038858] .eeh_handle_normal_event+0x128/0x3d0 [c000003f93a0fbf0] [c000000000038db8] .eeh_handle_event+0x2b8/0x2c0 [c000003f93a0fc90] [c000000000038e80] .eeh_event_handler+0xc0/0x170 [c000003f93a0fd30] [c0000000000cc000] .kthread+0xf0/0x100 [c000003f93a0fe30] [c00000000000a0dc] .ret_from_kernel_thread+0x5c/0x80
Reported-by: Wei Yang Signed-off-by: Gavin Shan Acked-by: Nithin Nayak Sujir Signed-off-by: David S. Miller
Turning off led on port 0 of the 5719 serdes causes all other ports to lose power and stop functioning. Add tg3_phy_led_bug() function to check for this condition. We use a switch() in tg3_phy_led_bug() for consistency with the tg3_phy_power_bug() function.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
commit 6829309926b90c4c32d1f4cafeb600cd34a721e3 Author: Daniel Borkmann Date: Tue Aug 13 11:45:13 2013 -0700
net: tg3: fix NULL pointer dereference in tg3_io_error_detected and tg3_io_slot_reset
Commit d8af4dfd8 ("net/tg3: Fix kernel crash") introduced a possible NULL pointer dereference in tg3 driver when !netdev || !netif_running(netdev) condition is met and netdev is NULL. Then, the jump to the 'done' label calls dev_close() with a netdevice that is NULL. Therefore, only call dev_close() when we have a netdevice, but one that is not running.
[ Add the same checks in tg3_io_slot_reset() per Gavin Shan - by Nithin Nayak Sujir ]
Reported-by: Dave Jones Signed-off-by: Daniel Borkmann Cc: Gavin Shan Cc: Michael Chan Signed-off-by: Nithin Nayak Sujir Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
The 5762 devices sometimes incorrectly treat udp fragments as RMCP packets and route to the APE. This patch sets the RX_MODE_IPV4_FRAG_FIX bit for these devices which enables the proper behaviour.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
The PTP_CAPABLE tg3 devices have a gpio output that is toggled when the free running counter matches a watchdog value. This patch adds support to set the watchdog and enable this feature.
Since the output is controlled via bits in the EAV_REF_CLCK_CTL register, we have to read-modify-write it when we stop/resume.
Cc: Richard Cochran Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
tg3: Allow NVRAM programming when interface is down
Previously, when the interface was brought down, the driver would set the power state to D3hot. In D3hot, we don't have access to the NVRAM. This patch removes the call to set the power state to PCI_D3hot in close. A following patch will implement the shutdown handler to properly set the D3hot state when the system is going down.
Doing the above means that the TG3_PHYFLG_IS_LOW_POWER should not be checked to validate access to the NVRAM.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
During probe, the driver is incorrectly switching the power to Vaux on the 5717 and later devices. At this point, we are in D0 state and drawing maximum power. We also definitely have Vmain available. It doesn't make sense to switch to Vaux since it has a lesser maximum power draw and we might go over the limit. On a new system, we observe that not all ports are recognized in some of the slots with this call in place.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
When the EEH error is the result of a fenced host bridge, MMIO accesses can be very slow (milliseconds) to timeout and return all 1's, thus causing the driver various timeout loops to take way too long and trigger soft-lockup warnings (in addition to taking minutes to recover).
It might be worthwhile to check if for any of these cases, ffffffff is a valid possible value, and if not, bail early since that means the HW is either gone or isolated. In the meantime, checking that the PCI channel is offline would be workaround of the problem.
Cc: # v3.0+ Signed-off-by: Gavin Shan Signed-off-by: David S. Miller
commit 72bb72b0d98847d22c6fae4e170121f3640f0f60 Author: Michael Chan Date: Mon Jun 17 13:47:25 2013 -0700
tg3: Prevent system hang during repeated EEH errors.
The current tg3 code assumes the pci_error_handlers to be always called in sequence. In particular, during ->error_detected(), NAPI is disabled and the device is shutdown. The device is later reset and NAPI re-enabled in ->slot_reset() and ->resume().
In EEH, if more than 6 errors are detected in a hour, only ->error_detected() will be called. This will leave the driver in an inconsistent state as NAPI is disabled but netif_running state is still true. When the device is later closed, we'll try to disable NAPI again and it will loop forever.
We fix this by closing the device if we encounter any error conditions during the normal sequence of the pci_error_handlers.
v2: Remove the changes in tg3_io_resume() based on Benjamin Poirier's feedback.
Signed-off-by: Michael Chan Signed-off-by: Nithin Nayak Sujir Signed-off-by: David S. Miller
Some systems that don't need wake-on-lan may choose to power down the chip on system standby. Upon resume, the power on causes the boot code to startup and initialize the hardware. On one new platform, this is causing the device to go into a bad state due to a race between the driver and boot code, once every several hundred resumes. The same race exists on open since we come up from a power on.
This patch adds a wait for boot code signature at the beginning of tg3_init_hw() which is common to both cases. If there has not been a power-off or the boot code has already completed, the signature will be present and poll_fw() returns immediately. Also return immediately if the device does not have firmware.
Cc: stable@vger.kernel.org Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
Commit 091f0ea30074bc43f9250961b3247af713024bc6 "tg3: Add New 5719 Read DMA workaround" added a workaround for TX DMA stall on the 5719. This workaround needs to be applied to the 5720 as well.
Cc: stable@vger.kernel.org Reported-by: Roland Dreier Tested-by: Roland Dreier Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
The current code calls tg3_set_bdinfo() separately on napi0, followed by a loop that does napi1+. Simplify it by setting bdinfo in the loop for all napi contexts.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
tg3: Split APE driver state change out of boot reset signature update
Unlike the boot signature that needs to be set before every reset, the ape state only needs to be updated to tell the firmware that the driver is now taking/releasing control of the hardware. Move the calls to tg3_ape_driver_state_change() to better, more appropriate places.
Also, the firmware does not distinguish between SUSPEND and START states anymore. Remove the SUSPEND case in the switch.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
tg3: Ensure boot code has completed initialization before accessing hardware
After resetting the device, the driver waits for a signature to be updated to know that firmware has completed initialization. However, the call to tg3_poll_fw() is being done too late and we're writing to the GRC_MODE register before it has completely initialized, causing contention with firmware. This logic has existed since day one but is causing PCIE link to go down randomly at startup on one platform once every few hundred reboots.
Move the tg3_poll_fw() up to before we write to the GRC_MODE register after reset.
Signed-off-by: Nithin Nayak Sujir Signed-off-by: Michael Chan Signed-off-by: David S. Miller
commit 1cbf9eb85a6601b58f01a71ff10299d2bf5d3365 Author: Nithin Sujir Date: Sat May 18 06:26:55 2013 +0000
tg3: Implement set/get_eee handlers
Reviewed-by: Ben Li Signed-off-by: Michael Chan Signed-off-by: Nithin Nayak Sujir Signed-off-by: David S. Miller