===============================================================================
Emulex FC Device Driver for Linux
===============================================================================

Device Driver Version: 11.2.209.49
Supported On: System x Rack, BladeCenter, and Flex

Problems Fixed:
- None

Incremental Interoperability:
- RHEL7 Update 3 Support
- SLES12 SP2 Support

Known Issues:
- None

===============================================================================

Device Driver Version: 10.3.135.0
Supported On: System x Flex

Problems Fixed:
- Error recovery of a "hung" IO to a device is cancelling ALL IOs,
not just the culprit one only

Incremental Interoperability:
- Grantley based ITE

Known Issues:
- None

===============================================================================

Device Driver Version: 10.2.375.0
Supported On: IBM System x and BladeCenter

Problems Fixed:
- ELS txcmplq list corruption cause crash during error injection
- Cleaned up several issues around ExpressLane feature
- Need a HAL workaround for upgrading 10.0 XE102/XE104 f/w to 10.2
- I/O hang on RHEL6.5 for small block (4K) random i/o on POWER8

Incremental Interoperability:
- Grantley Rack Servers

Known Issues:
- None

===============================================================================

Device Driver Version: 10.2.261.0
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- lpfc message number 0127 is not reporting the correct information
- Replace CRC16 used in T10-PI related driver code

Incremental Interoperability:
- Crosslink & Express Lane on LPe16k based solutions

Known Issues:
- None

===============================================================================

Device Driver Version: 10.0.800.0
Supported On: IBM System x

Problems Fixed:
- Low bi-di throughput seen on 1g ports of HS-23 LOM
- Multiple performance improvements
- Bonding driver takes approx 20 seconds to be ready

Incremental Interoperability:
- RHEL 5.10
- RHEL 6.5
- XE-102 and XE-104 ASIC (OCx14xxx)
- Support for set and get channels ethtool operation

Known Issues:
- SR-IOV is supported with the following Linux distributions:
* RHEL 6.4 and above 64-bit with KVM
* SLES11 SP3 and above 64-bit with KVM

NOTE: Guest operating system support is dependent on the Emulex driver
version installed in the guest.

===============================================================================

Device Driver Version: 8.3.7.27
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Execution of internal loopback causes a crash
- Issue which can cause multipath failover to not work properly

Incremental Interoperability:
- IBM Flex System FC5052 2-port 16Gb FC Adapter
- IBM Flex System FC5054 4-port 16Gb FC Adapter
- IBM Tape unit interoperability - see SSIC for more information
- SLES 11.3 on IBM System x and BladeCenter

Known Issues:
- None

===============================================================================

Device Driver Version: 8.3.7.18
Supported On: IBM System x and BladeCenter

Problems Fixed:
- FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported
class of service
- OXID Reused before RA_TOV without RRQ to recover
- Intermittently storage paths will not recover after switch reboot

Incremental Interoperability:
- RHEL 5.9
- RHEL 6.4

Known Issues:
- No known issues

===============================================================================

Device Driver Version: 8.3.6.4
Supported On: IBM Flex

Problems Fixed:
- Fixed debug helper routine failed to dump CQ and EQ entries in non-MSI-X mode
- FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported
class of service
- Fixed boot from san failure when SLI4 FC device presented on the same PCI bus
- Fix ABTS recovery to be FC spec compliant
- Fixed not reporting logical link speed to SCSI midlayer when QoS not enabled
- Fix performance problem in pt2pt mode
- Fixed SCSI host create showing wrong link speed on SLI3 HBA ports
- Update text for misconfigured port messages
- Fix discovery bug when swapping cables

Interoperability since previous release:
- RHEL6.3 GA Kernel

Known Issues:
- No known issues

===============================================================================

Device Driver Version: 8.3.5.86
Supported On: IBM System x and BladeCenter

Problems Fixed:
- Kernel panics with FCoE on HS23 in SLES 11.2 x86_64. Also requires a SLES11.2
kernel update
- FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported
class of service

Interoperability since previous release:
- RHEL6.3 GA Kernel

Known Issues:
- No known issues

===============================================================================

Device Driver Version: 8.3.5.74.1p
Supported On: IBM System x and BladeCenter

Problems Fixed:
- Fixed kernel panic after scsi_eh escalation by checking the proper return
status

===============================================================================

Device Driver Version: 8.3.5.74
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Fixed system crash due to not providing SCSI error-handling host reset
handler
- Debug helper utility routines for dumping various SLI4 queues
- Fix unsol abts xri lookup
- Fixed issues with LPe16000 to LPe16000 discovery
- Fix driver crash during back-to-back ramp events
- Reregister VPI for SLI3 after cable moved to new Saturn port
- Fix log message 2597 displayed when no error is detected
- Fixed FCP LOG for easier Finisar trace correlation
- Fix kernel panic when going into to sleep state
- Fix error message displayed even when not an error
- Fix Read Link status data
- Fix unable to create vports on FCoE SLI4 adapter
- Fix initiator sending flogi after acking flogi from target
- Fix the case where an array controller does not apply FCP priority rules
- Added support for handling SLI4-port XRI resource-provisioning profile
change
- Change default DA_ID support from disabled to enabled
- Fix bug with driver unload leaving a scsi host for a vport around
- Update copyright date for files modified in 2012
- Fix compilation errors on some kernels due to debugfs variable definitions
- Used PCI configure space read to flush PCI function reset register write
- Fixed system panic when extents enabled with large number of small blocks
- Fixed system panic during EEH recovery
- Fix resource leak when acc fails for received plogi
- Fix SLI4 driver module load and unload test in a loop crashes the system
- Fix missing CVL event causing round-robin FCF failover process to stop
- Fix deadlock during adapter offline request
- Fix same RPI registered multiple times after HBA reset

===============================================================================

Device Driver Version: 8.3.5.66
Supported On: IBM System x, BladeCenter, and Flex

Problems Fixed:
- Fix SLI4 driver module load and unload test in a loop crashes the system
- Fix missing CVL event causing round-robin FCF failover process to stop
- Fix deadlock during adapter offline request
- Fix same RPI registered multiple times after HBA reset
- Fix driver handling of XRI Aborted CQE response
- Fixed port and system failure in handling SLI4 FC port function reset
- Fix bug with driver not sending a LOGO with vport delete
- Make BA_ACC work on a fully qualified exchange
- Fix for SLI4 Port delivery for BLS ABORT ACC
- Fix KERNEL allocation while lock held
- Incorrect usage of bghm for BlockGuard errors
- Fix warning on i386 system
- Fix ndlp nodelist not empty wait timeout during driver unloading
- Fix mailbox and vpi memory leaks
- Support character device to take a reference on the driver
- Fix for FDISC failures after firmware reset or link bounce
- Support debugfs for injecting T10 DIF errors
- Fix SLI4 BlockGuard behavior when protection data is generated by HBA
- Fix for driver using duplicate RPIs after 16Gb/s adapter port reset
- Fix discovery problem when in pt2pt
- Fixed failure in handling large CQ/EQ identifiers in an IOV environment
- Fix Locking code raises IRQ twice
- Fix driver not returning when bad ndlp found in abts error event handling
- Support more driver logs in area of SLI4 port error attention and reset
recovery
- Fix bug with driver returning the wrong ndlp
- Sync up with actual upstream lpfc driver code
- Support SLI4 16Gb FC Adapter support for T10 DIF / BlockGuard
- Merge from upstream: scsi: Fix up files implicitly depending on module.h
inclusion
- Fix driver behavior when receiving an ADISC
- Fixed unbounded firmware revision string from port caused the system panic
- Fix bug with driver processing dump command type 4 using 16Gb FC Adapter
- Fix driver does not reset port when reset is needed during fw_dump
- Fix ELS FDISC failing with local reject / invalid RPI
- Changed SLI4 FC port internal loopback from outer serdes to inner internal
- Fix REG_RPI fails on SLI4 HBA putting NPort into NPR state
- Fix bug with driver processing an els command using 16Gb FC Adapter
- Fix NMI seen due to CQE starvation
- Fixed SLI4 FC port obtained link type and number dependent on link connection
- Fixed SLI4 FC port internal loopback without SFP and external
link/loopback plug
- Fix driver incorrectly building fcpCdb during scsi command prep
- Fixed FCP EQ memory check prevent initialize to single interrupt vector case
- Fixed SLI4 16Gbit FC port internal and external diagnostic loopback tests
- Fixed system panic during EEH recovery on SLI4 FC port
- Fix FLOGI fails with invalid RPI (0x04) after connecting to a arbitrated loop
- Fix ELS SCR failing with local reject / invalid RPI
- Fix SLI4 port failures after firmware reset or dump
- Fix port reset log messages indicate error when no error is seen
- Fixed an issue where HBQ buffers are uninitialized in the base driver
- Fixed missing shost lock protection on setting/clearing bit in vport->fc_flag
- Fixed missing hbalock protection on setting/clearing bit in phba->link_flag
- Fixed illegal state transition during driver unload
- Fixed system crash on SLI4 FC port looopback diagnostic test with large
buffers
- Fixed a potential error path that might try to free DMA memory not allocated
- Fixed SLI4 FC port Internal and External loopback diagnostic tests
- Fix a crash while deleting 256 vports
- Fix vport never finished discovery if switch runs out of resources
- Fix kernel build warnings
- Fix kernel panic when putting board in offline state twice
- Fix memory leak when running hba resets to SLI-4 board
- Fix driver message 3092 and 3116 to KERN_WARNING
- Fix PCI read failure looks like a over temperature event
- Fixed driver event reporting to mgmt on error attention due to forced dump
- Fix not displaying firmware rev for BE UCNA boards
- Fixed ABTS failure logic not rediscovering targets
- Fix bug with driver not byte swapping extended mailbox data
- Fix premature ndlp cleanup after second target LOGO
- Fix Link pull causes I/O failures
- Support loop for sli4 fc pass-through
- No longer read fcoe parameters if board is not fcoe
- Fix bug with driver passing a wrong count value
- Support restore state and error log when sysfs board_mode attribute access
failed
- Fixed a typo in two of the log messages just introduced
- Support for SLI4_CONFIG non-embedded COMN_GET_CNTL_ADDL_ATTR pass-through
- Support for SLI4 FC port persistent linkdown through config region 23
- Fix for ABTS. Do not free original IOCB whenever ABTS fails
- Fixed Linux driver inconsistency in reporting FC host port-state through OCM
- Return an error if the mbox sysfs is called
- Fix firmware upgrade attempt on unsupported adapter
- Fix incomplete message number 2889
- Fix system crash when ASIC fails to initialize
- Fix virtual fabrics bit set in FLOGI incorrectly
- Fix bug with driver not returning extended mailbox data
- Fix unsupported link speed accepted by SLI4 port
- Incremented minor management version to reflect additional "protocol"
sysfs attribute
- Modify WQ handling to use entry_repost
- Moved link type definitions to apply to all driver streams
- Support a sysfs attribute "protocol" to report SLI4 port link protocol type
- Support SLI4 INTF_TYPE and SLI_FAMILY as sub-field to the fwrev sysfs
attribute
- Support structure to support T10 DIF in SLI4
- Fix performance slowed due to too many register accesses
- Fixed a warning when converting from simple_strtoul to strict_strtoul
- Support Initial code to inject T10 DIF errors
- Fixed a possible driver crash when cfg_fcp_eq_count is zero
- Fixed non-embedded COMMON_GET_CNTL_ATTR mbox command failed with status 0x4
- Fixed null pointer dereference after clearing FCP policy rules
- Changed the way of SLI4 device detecting physical port name
- Fixed FCP policy exchange management rule parsing
- Support check to lpfc_decode_firmware_rev to handle releases that have an 'X'
- Fixed RPI leaks in ELS protocol handling
- Fix kernel crash during boot with SLI4 card installed
- Fixed NPIV FDISC failure on SLI4 if-type 2 ports
- Fixed driver failed to follow IP reset procedure in SLI4 error attention
handler
- Fix sysfs lists fabric name for port that has been disconnected from fabric
- Support FCP policy exchange management
- Changed the timeout to 300 seconds for SLI_CONFIG (0x9B) mailbox command
- Fixed fcp underrun reporting
- Fixed a driver handling IP reset issue when PCI read return error
- Fixed casting problem in calculating tx_words statistics
- Support proper error code return for libdfc calling API to make proper
decisions
- Fix sli4 mailbox status code. Management software has dependencies
- Fix compiler warning due to uninitialized local variable
- Fix bus reset handler fails with bad failure code
- Made proper error code return for libdfc calling API to make proper decisions
- Made error log include PCI BAR bitmap from kernel when enable PCI device
failed
- Fixed sysfs API mismatch for building against SLES11 SP2 beta kernel
- Fixed scsi midlayer queuecommand API mismatch for SLES11 SP2 beta kernel
- Fixed ctlreg write bug not checking key string and limiting bytes to write
- Fix default adapter name for the OCe15100
- Fixed incomplete scsi messages displayed
- Fix cable pull failure on interface type 2 SLI-4 adapters
- Fix enable_bg config parameter for SLI4
- Fixed not able to perform firmware reset through sysfs board_mode attribute
- Fixed not recovering SLI port in handling error attention with RN bit set
- Fixed two crash cases when unsolicted ELS ECHO_CMD is received
- Fix direct connect does not come up for SLI4 FC ports
- Fixed long wait when firmware reset to a SLI port without required privilege
- Fix request firmware support for little endian systems
- Fix driver firmware to match new firmware image format
- Fixed SLI4 device firmware reset with SR-IOV virtual functions
- Fix SLI4 CT handling for sequences > 4K
- Fixed handling of unsolicited frames for vports
- Fixed handling of CVL for vports
- Fixed crash when aborting els IOs
- Fix up CT and oxid/rxid for unsol rcv frames
- Fixed mailbox double free panic
- Support fcf priority record selection for fcf failover
- Fixed compiler warning for putting large amount of memory on stack
- Fixed driver build not building in debugfs even if kernel
CONFIG_DEBUG_FS=y is set
- Fix issue where the FC/FCoE Async Receive CQE did not scale for 16G FC
adapters
- FLOGI payload has Multiple N_port_ID set when lpfc_enable_npiv clear
- Removed unused argument passed to the lpfc_bsg_diag_mode_enter routine
- Fixed new ASIC device-mgmt BSG pass-through failed multi-buffer fw download
- Support sysfs logging when writeable parameters are changed
- Used PCI config space capability for sysfs get PF supported SR-IOV number of
VFs
- Support wait for SLI port status register for readyness following firmware
reset
- iDiag added SLI4 device PCI BAR memory mapped reigster access methods
- Consolidated duplicating macro definitions
- Fixed failure to enable PCIe AER prevent driver initialize and attach to
device
- Modified log messages for T10-PI processing
- iDiag fixed mailbox capture and dump overlapping bitmap macro definition

===============================================================================

Device Driver Version: 8.3.5.35
Supported On: IBM System x and BladeCenter

- Initial Release

===============================================================================
elx_dd_fc_17a-11_2_209_49-2_sles11_32-64_chg

ServeRAID M and MR10 Series SAS Controller Driver for SLES11
(also supports MegaRAID 8480 SAS Controller)

Adapters Supported:
ServeRAID M1215 SAS/SATA Controller for (46C9114)
LSI SAS3004 RAID for NA-Newport RAID
ServeRAID M5210 SAS/SATA Controller for (46C9110)
ServeRAID M5225-2GB SAS/SATA Controller for (00AE938)
ServeRAID M5210e SAS/SATA Controller for (46C9117CTO)
ServeRAID M5110 SAS/SATA Controller for (81Y4481)
ServeRAID M5110 SAS/SATA Controller (CTO only) for (81Y4483CTO)
ServeRAID M5110e SAS/SATA Controller for (90Y4343CTO)
ServeRAID M5120 SAS/SATA Controller for (81Y4478)
IBM Flex System Storage Expansion Node for (68Y8588)
ServeRAID M5115 SAS/SATA Controller for Flex System for (90Y4390)
ServeRAID M5100 Series IBM Flex System Flash Kit for X6 for(44T1178)
ServeRAID M5016 SAS/SATA Controller for (90Y4304)
ServeRAID M5110e SAS/SATA Controller for (90Y4343CTO)
ServeRAID M5025 SAS/SATA Controller for (46M0830)
ServeRAID M5015 SAS/SATA Controller for (46M0829)
ServeRAID M5014 SAS/SATA Controller for (46M0916)
ServeRAID M1115 SAS/SATA Controller for (81Y4448)
ServeRAID M1015 SAS/SATA Controller for (46M0831)

Supported Kernels:
SLES 11.2,11.3,11.4,


NOTE TO SERVICE - Reference RETAIN #N/A

07.707.04.00 - Moderate Impact/Low Probability of Occurrence
---------------------
MR 7.7 (new)

Defects:
- Driver will use 64 bit request descriptor for sending IO to Ventura firmware.(SCGCQ01514452)
- FW flash is not needed for driver.(SCGCQ01593539)
- Modified driver prints to dump relevant FW provided values(part of controller info structure) in syslog.(SCGCQ01626839)
- Merge upstream patch "Convert timers to use timer_setup" to in-house and support timer_setup API in 4.15 kernels.(SCGCQ01586787)
- MR7.7: scsi_dma_map() is called twice in IO path.(SCGCQ01619432)
- Driver is incorrectly deciding combined reply queue mode for SAS3.0 controller(SCGCQ01633318)
- Updated driver's file- "OS_Support_list_mr7.7.txt" with CMA support enablement and retpoline compliant driver binaries.(SCGCQ01760521)
- Renamed scratchpad registers from scratchpad0 , scratchpad1 etc ... in order to align with firmware naming convention.(SCGCQ01440031)
-(SCGCQ01664978)
- Use IOC_INIT frame once driver has verified IOC_INIT frame allocation was successful.(SCGCQ01440720 port of SCGCQ01430747)
- Driver should go through stream detection logic after it's finalized which path(fastpath vs non fastpath) IO will go through.(SCGCQ01483730 port of SCGCQ01468189)
- XenServer 7.3 OS support- MR 7.6.(SCGCQ01594134 port of SCGCQ01554012)
- Divert FastPath IO with Chain frame to Firmware path.(SCGCQ01598186 port of SCGCQ01593175)
- expose fw_outstanding and drv_outstanding variables to the OS level sys interface.(SCGCQ01475068 port of SCGCQ01019663)
- Driver should go through stream detection logic after it's finalized which path(fastpath vs non fastpath) IO will go through.(SCGCQ01542421 port of SCGCQ01468189)
- expose fw_outstanding and drv_outstanding variables to the OS level sys interface.(SCGCQ01542422 port of SCGCQ01019663)
- After a kill adpater, megasas_wait_for_adapter_operational waits for almost 360seconds before bailing out.(SCGCQ01619441 port of SCGCQ01615239)
- Setup IRQs only after Reply descriptors are allocated.(SCGCQ01542423 port of SCGCQ01506133)
- MR: Remove trace kernel RPMs from SUSE SLES11 SP4 driver iso images.(SCGCQ01594109 port of SCGCQ01563428)
- megasas_get_target_prop failing after OCR completed.(SCGCQ01619439 port of SCGCQ01607430)
- NVMe Task Management - Controller Reset Support (MegaRAID).(SCGCQ01592015 port of SCGCQ01545040)
- Updated OEL6_UEK and OEL7_UEK buildkit.(SCGCQ01443432 port of SCGCQ01439776)
- Use IOC_INIT frame once driver has verified IOC_INIT frame allocation was successful.(SCGCQ01449786 port of SCGCQ01430747)
- Use pci_{alloc/free}_irq_vectors for >=4.12 kernels.(SCGCQ01449816 port of SCGCQ01442784)
- Setup IRQs only after Reply descriptors are allocated.(SCGCQ01514459 port of SCGCQ01506133)
- Driver will use 64 bit request descriptor for sending IO to Ventura firmware.(SCGCQ01523087 port of SCGCQ01514452)
- Increased JBOD FPIO timeout by 1 sec to workaround hardware bug which causes timeout 1 sec earlier than provided timeout value.(SCGCQ01542419 port of SCGCQ01449957)

EnhancementRequests (23)
- Use pci_{alloc/free}_irq_vectors for >=4.12 kernels.(SCGCQ01442784)
- Few officially unsupported PCI IDs are removed from MR7.7 driver code.(SCGCQ01598587)
- XenServer 7.4 OS support - MR 7.7.(SCGCQ01628129)
- Increased JBOD FPIO timeout by 1 sec to workaround hardware bug which causes timeout 1 sec earlier than provided timeout value.(SCGCQ01449957)
- Rebase inbox megaraid_sas driver to inhouse to reduce two different code base for maintenance.(SCGCQ01578030)
- MR_Aero: Create timer based thread in MR drivers to detect firmware FAULT.(SCGCQ01157766)
- Remove UpdateIoMetric and hence adapter level spinlock from IO path(SCGCQ01522127)
- Create cpu to msix table for kernel provided PCI_IRQ_AFFINITY (>=4.12 kernel).(SCGCQ01598134)
- OS driver support for Oracle Linux 7.5 - MR 7.7.(SCGCQ01586106)
- OS Driver Support for Ubuntu 18.04- MR 7.7.(SCGCQ01586128)
- Support RHEL7.5 GCA (3.10.0-862.el7.x86_64).(SCGCQ01586135)
- Early detection of faulty controller.(SCGCQ01599562)
- Change attribution language from Avago to Broadcom and update copyright end year.(SCGCQ01753095)
- Offload R5/R6 division to driver.(SCGCQ01513544)
- Update Linux Driver BST scripts and wrapper.(SCGCQ01529349)
- Marlin support is added to drivers.(SCGCQ01440724)
- Remove support for RHEL7.1, OEL7.2 and SLES12.(SCGCQ01449982)
- Optimize code around (raid context) in IO path.(SCGCQ01598187)
- Removed support of RHEL7.1, SLES12 and OEL7.2.(SCGCQ01600475)
- FW OCR Debug Mechanism - triggerSnapDump.(SCGCQ01520447)
- Set SLD bit in RAID map when "enableSLDOnAllRWIOs" is enabled.(SCGCQ01715619)
- Revert code changes related to iMR performance throttling.(SCGCQ01749962)
- Revert changes added in driver to divert FastPath IO with Chain frame.(SCGCQ01752939)

Version 07.705.05.00 - Moderate Impact/Low Probability of Occurrence
---------------------
Defects:
- Driver fires a DCMD to incorrect Target ID¡¯s to obtain Maximum Data transfer size (MDTS) of NVME devices.(SCGCQ01760644)

EnhancementRequests:
- Compiled megaraid_sas driver binaries with retpoline support to workaround Spectre v2 vulnerabilities.(SCGCQ01790176)

Version 07.705.04.00 - Moderate Impact/Low Probability of Occurrence
----------------------
Defects (7)
- Provided driver workaround to reset __GFP_WAIT flag while allocating IO request frames.(SCGCQ01394892)
- Driver will use 64 bit request descriptor for sending IO to Ventura firmware.(SCGCQ01514452)
- Set DMA mask after FW is in READY state in PCI resume path of megaraid_sas driver(SCGCQ01389431)
- Fixed few dev found and coverity reported defects(SCGCQ01392652)
- Selective stream detection logic in driver(SCGCQ01392643)
- During PCI remove, set unload flag after scsi_remove_host is called.(SCGCQ01392656)
- update LD map after populate drv_map, increase wait in IOCTL, fix index in error handling, rework in refiring DCMDs.(SCGCQ01415439)

EnhancementRequests (10)
- MR7.4: Add SLES12 SP3 OS support.(SCGCQ01396756)
- Added support for RHEL7.4.(SCGCQ01455156)
- Added driver support for OEL7.4.(SCGCQ01396747)
- Increased JBOD FPIO timeout by 1 sec to workaround hardware bug which causes timeout 1 sec earlier than provided timeout value.(SCGCQ01449957)
- Added support for threaded interrupts.(SCGCQ01498747)
- MR7.4: OS driver support for RHEL 7.4.(SCGCQ01396738)
- Added support for SLES12 SP3.(SCGCQ01455167)
- Added driver binary support for Xenserver7.2.(SCGCQ01393249)
- Remove support for RHEL7.1, OEL7.2 and SLES12.(SCGCQ01449982)
- Removed support for few OS to align with OS support matrix policy.(SCGCQ01393194)

CSETActivities (14)
- Added support for threaded interrupts.(SCGCQ01615015 port of SCGCQ01498747)
- Driver should go through stream detection logic after it's finalized which path(fastpath vs non fastpath) IO will go through(SCGCQ01483730 port of SCGCQ01468189)
- Use IOC_INIT frame once driver has verified IOC_INIT frame allocation was successful.(SCGCQ01455132 port of SCGCQ01430747)
- MR: OEL 7.4 and 6.x x86_64 RPMs do not have the correct kernel versions.(SCGCQ01611888 port of SCGCQ01607445)
- expose fw_outstanding and drv_outstanding variables to the OS level sys interface.(SCGCQ01475068 port of SCGCQ01019663)
- Updated correct supported kernel version of Ubuntu16.04 in driver's document- OS_support_list_mr7.5.txt.(SCGCQ01564604 port of SCGCQ01454090)
- Added NVME passthru support in MR linux driver.(SCGCQ01424605 port of SCGCQ01407028)
- Updated correct supported kernel version of Ubuntu16.04 in driver's document- OS_support_list_mr7.5.txt.(SCGCQ01455206 port of SCGCQ01454090)
- Added NVME passthru support in MR linux driver.(SCGCQ01455135 port of SCGCQ01407028)
- Updated OEL6_UEK and OEL7_UEK buildkit.(SCGCQ01443433 port of SCGCQ01439776)
- Setup IRQs only after Reply descriptors are allocated.(SCGCQ01514459 port of SCGCQ01506133)
- Use pci_{alloc/free}_irq_vectors for >=4.12 kernels.(SCGCQ01449816 port of SCGCQ01449816)
- Use IOC_INIT frame once driver has verified IOC_INIT frame allocation was successful.(SCGCQ01449786 port of SCGCQ01430747)
- Set DMA mask after FW is in READY state in PCI resume path of megaraid_sas driver.(SCGCQ01392672 port of SCGCQ01389431)




Version 7.703.07.00- Moderate Impact/Low Probability of Occurrence
---------------------
fixes:
- Send sense buffer upper 32bits inside IOC INIT frame.(SCGCQ01315987)
- MR: On OEL 6.x/7.x with UEK kernels - megaraid_sas.conf file from the kmod rpm does not match kernel version.(SCGCQ01319368)
- pass upper 32 bits of version buffer and system information buffer to FW inside IOC INIT frame.(SCGCQ01326366)
- Workaround changes for FW MFA frame pull issue.(SCGCQ01338087)
- Log dmesg if IOC INIT fails in IOMMU and RDPQ enabled enviornment for user information only.(SCGCQ01338097)
- Validated if any of DMA buffers pool which should be in same 4GB region does not cross 4GB boundary.(SCGCQ01338372)
- Memset to zero for MFI command frame for IOC INIT and use lower_32_bits() macro to get lower 32bits of DMA address passed to FW.(SCGCQ01341287)
- Removed Crusader ID(device ID- 0x0015) from supported PCI IDs of MR7.2 linux driver.(SCGCQ01350963)
- MR7.3: Code review defect - ioc_init_frame not freed during kernel module unload.(SCGCQ01384694)
- MR7.2: In megasas_issue_tm() SMID needs to be used for Task abort case only.(SCGCQ01315252)
- Incorrect processing of IOCTL frames for SMP/STP commands.(SCGCQ01383823)
- Set cmd_status inside DCMD/IO/header frame to MFI_STAT_OK to wake up all pended IOCTLs.(SCGCQ01298582)
- Removed print "Failed from megasas_complete_cmd" from PD CFQ sequence DCMD completion path.(SCGCQ01321565)
- Do not switch DMA mask to meet same 4gb requirement. IOMMU does not work well with such DMA mask switch.(SCGCQ01342578)
- Allocated MFI frame size and the size of MPT chain frame(Where MFI frame resides for MFI MPT passthru commands) should match.(SCGCQ01342650)
- Minimum possible value for module parameter- resetwaittime should be 1 secs instead of 0 secs.(SCGCQ01344137)
- Set DMA mask after FW is in READY state in PCI resume path of megaraid_sas driver.(SCGCQ01389431)
- MR7.3: Data miscompare found with WB secure VD RAID 1 with LSA sending IOCTLs in parallel.(SCGCQ01378684)

EnhancementRequests:
- Added support for 64bit DMA mask for invader.(SCGCQ01294199)
- MR7.3: add support for Citrix XenServer 7.1 OS.(SCGCQ01257971)
- Send current time to FW during IOC init.(SCGCQ01307072)
- Added support for RHEL7.4.(SCGCQ01455156)
- MR7.3: add support for OEL 6.9.(SCGCQ01289005)
- Added support for threaded interrupts.(SCGCQ01498747)
- Added support for 64bit DMA.(SCGCQ01301940)
- Added support for SLES12 SP3.(SCGCQ01455167)

CSETActivities:
- Set cmd_status inside DCMD/IO/header frame to MFI_STAT_OK to wake up all pended IOCTLs.(SCGCQ01381770 port of SCGCQ01298582)
- MR: On OEL 6.x/7.x with UEK kernels - megaraid_sas.conf file from the kmod rpm does not match kernel version.(SCGCQ01320324 port of SCGCQ01319368)
- Use IOC_INIT frame once driver has verified IOC_INIT frame allocation was successful.(SCGCQ01455132 port of SCGCQ01430747)
- Updated correct supported kernel version of Ubuntu16.04 in driver's document- OS_support_list_mr7.5.txt.(SCGCQ01455206 port of SCGCQ01454090)
- Added NVME passthru support in MR linux driver.(SCGCQ01455135 port of SCGCQ01407028)
- Updated OEL6_UEK and OEL7_UEK buildkit.(SCGCQ01443433 port of SCGCQ01439776)
- Minimum possible value for module parameter- resetwaittime should be 1 secs instead of 0 secs.(SCGCQ01344142 port of SCGCQ01344137)


Version 7.702.06.00- Moderate Impact/Low Probability of Occurrence
---------------------
Defects (47)
- Reset MPT frame field cmd_completed while retrurning it back to free pool.(SCGCQ01176530)
- Optimized R1 FP write code.(SCGCQ01191077)
- Before populating driver RAID map copy memset drv_map to zero and ldTgtIdtoLd array to 0xff(SCGCQ01204087)
- Initialize stream detection array properly.(SCGCQ01204096)
- On SPARC/Big endian host, need to convert peerSMID to little endian to CPU before accessing(SCGCQ01216698)
- Fixed coverity reported issues and changed name of few functions.(SCGCQ01219231)
- Don't set tm_capable for JBDO when PD CFG SEQ map is not available(SCGCQ01226222)
- Remove local defination FALSE/TRUE and use OS provided false/true.(SCGCQ01256130)
- Used vmalloc for crash dump buffers and driver's local RAID maps(SCGCQ01270059)
- Reduce size of fusion_context allocation during driver load by moving load_balance_info array out, and try vmalloc if kmalloc fails.(SCGCQ01183280)
- Flooding of messages- "BRCM: IO does not end on page boundary; sge_len" while running RAW IOs.(SCGCQ01189815)
- Fixed data corruption by asking OS not to do merging of IOs to avoid SGE holes(SCGCQ01231229)
- Code review defect: create separate function for allocating RAID maps(SCGCQ01282924)
- Removed Crusader ID(device ID- 0x0015) from supported PCI IDs of MR7.2 linux driver(SCGCQ01350963)
- Updated OS to send page aligned SGEs by calling blk_queue_virt_boundary(SCGCQ01206279)
- Use vmalloc followed by memset to zero instead of vzalloc in driver code.(SCGCQ01206316)
- MR_ValidateMapInfo issue on bigendian platform (In some case Detect Ghost VDs)(SCGCQ01213952)
- Fixed code review defects(SCGCQ01254323)
- Removed code inside macros VD_EXT_DEBUG, SPAN_DEBUG and enahnce prints in OCR path(SCGCQ01270056)
- FW fault happens as driver wrongly fill numSGE=0.(SCGCQ01274103)
- Code optimization and enhanced prints for debugging(SCGCQ01224881)
- Remove unsupported PCI Device IDs from the driver code(SCGCQ01234256)

- Resolved conflict of PCI device ID-0x0015(SCGCQ01254317)
- MR7.2: In megasas_issue_tm() SMID needs to be used for Task abort case only(SCGCQ01315252)
- Save interfaceType for each sysPDs inside SCSI device's private data field which will persists until sysPD is removed/deleted.(SCGCQ01216464)
- Code Optimization and enhanced prints(SCGCQ01223300)

- MR 7.1: Linux OS crash when powering off enclosure during I/O(SCGCQ01229442)
- Return pending IOs with status DID_REQUEUE instead of DID_RESET to SCSU layer before doing OCR(SCGCQ01231846)
- MR7.2: Port changes from upstream to make in-house MR 7.2 code to be consistent with upstream code(SCGCQ01282321)
- Add print for partially copied SCSI IO and fix few endianness issues(SCGCQ01224305)
- Linux Driver 07.700.23.00/Getting megaraid_sas prints during startup of OS(SCGCQ01255074)
- aen class range check to avoid kernel panic(SCGCQ01256126)
- Corrected bitmap macros inside struct RAID_CONTEXT35(SCGCQ01269453)
- Set cmd_status inside DCMD/IO/header frame to MFI_STAT_OK to wake up all pended IOCTLs.(SCGCQ01298582)
- Fix few dev found issues(SCGCQ01226224)
- On OEL SPARC (Big Endian), Linux MR 7.1 driver loading fails to initialize Ventura which has RDPQ support enabled(SCGCQ01229897)
- Fixed few code collab defects/comments(SCGCQ01202237)
- Remove throttle IOs prints in IO path and add sysfs parameter to reflect number of R1 FP writes(SCGCQ01204099)
- Ventura MR-7.0.1 RHEL 7.2 driver: ERR messages when installing driver 7.700.20.00(SCGCQ01222990)
- Use do_div() kernel API to do modulo operation of 64 bit dividend and 32bit divisor .(SCGCQ01243263)
- megasas_complete_cmd_dpc_fusion() will be called with 1 sec delay inside function megasas_wait_for_outstanding_fusion(SCGCQ01256116)
- Allocated MFI frame size and the size of MPT chain frame(Where MFI frame resides for MFI MPT passthru commands) should match(SCGCQ01342650)
EnhancementRequests (17)
- Big endian architecture is now support for Ventura generation of MR HBA.(SCGCQ01256016)
- Fixed the problem of sync_irq not being called when MSI-x are disabled.(SCGCQ01206307)
- Port changes from MR7.0 and MR6.13 critical fixes to MR7.1(SCGCQ01167939)
- In megasas_build_ldio_fusion, code to set controller CPU affinity can be optimized(SCGCQ01216486)
- Set device queue depth same as controller's can_queue for SCSI MQ mode(SCGCQ01271569)
- Add SLES 11 32-bit build kit support to Ventura MR.(SCGCQ01214721)
- Ported fixes from MR 6.13 to MR 7.1(SCGCQ01222522)
- Added support for RHEL7.3(SCGCQ01224300)
- Support SPARC/PPC/ARM (Big/Little Endian). Fix Endianess issue in MR Ventura driver.(SCGCQ01183275)
- Added DCMD interface to read target properties for SCSI device(VDs and JBODs both)(SCGCQ01220142)
- Added KMOD RPM support for OEL7.3 UEK.(SCGCQ01227476)
- R1 Write IOPs improvement(SCGCQ01213232)
- Extra code for bug in A0 ventura is removed. Optimized Descriptor write as Ventura required 32 bit in major IO Path operation.(SCGCQ01215347)
- Remove Crusader device support from driver(SCGCQ01259175)
- Don't re-issue Reset on the way back OCR(SCGCQ01215089)
- Rework start_vm_build script used for VBAS build and new build infrastructure for DKMS RPMs(SCGCQ01261800)
-

Version 7.700.26.00- Moderate Impact/Low Probability of Occurrence
---------------------
Enhancement:
- Added support for ThinkSystem HBA and RAID.

Version 6.812.08.00
-------------------


Version 6.810.09.00 - Moderate Impact/Low Probability of Occurrence
---------------------
Fixes:

- Fixed an issue where deadlock may occur when the Automatic Event Notification thread runs in parallel with error handler thread (SCGCQ00911332, Port of SCGCQ00868731)

- Fixed an issue where driver will operated in RDPQ mode regardless of whether firmware has advertised support or not (SCGCQ00872542)

- Fixed an issue where system may reset with error "BUG: unable to handle kernel NULL pointer dereference at 00000000000000d0" preceded by error "megasas: target reset FAILED!!" (SCGCQ00875223)

- Fixed an issue where driver MFI frames could be freed twice (SCGCQ00879190)

- Fixed an issue where some out-of-band commands had different timeouts than others (SCGCQ00884247)

- Fixed an issue where performance was lower on async IO submissions from the SCSI mid layer (SCGCQ00884242)

- Fixed an issue where a kernel panic may occur if the system is reset or fail to reboot (SCGCQ00859634, Port of SCGCQ00857740)

- Fixed an issue where Task Management frames were not being dumped after the Tast Management Reply frame data (SCGCQ00860038)

- Fixed an issue where a fatal error may occur when an out-of-band command times out during an Online Controller Reset (SCGCQ00882011, Port of SCGCQ00868661)

- Fixed an issue where kernel may hang when many commands are timing out or many Automatic Event Notifications are being processed (SCGCQ00857245)

- Fixed an issue where megaraid_sas module was not being included inside initrd/initramfs (SCGCQ00880965)

- Fixed an issue where kernel may panic if driver does not setup IRQs for non-MSI-x interrupt mode (SCGCQ00870263, Port of SCGCQ00867873)

- Fixed an issue where driver return code is based on command completion rather than command return code (SCGCQ00856103, Port of SCGCQ00856089)

- Fixed an issue where Tape drives may not be detected by the Operating System (SCGCQ00914385, Port of SCGCQ00911702)

- Fixed an issue where max_sectors per IO request may be set to more than firmware can handle (SCGCQ00917992, Port of SCGCQ00917399)

- Fixed an issue where an IERR may occurr on heavy IO with Failover (SCGCQ00864111, Port of SCGCQ00736612)


Enhancements:

- Enhanced queue depths in driver for physical disks based on interface type (SCGCQ00879700)

- Improved naming of internal functions (SCGCQ00866064)

- Updated module parameter "rdpq_enable" default to "1" (enable RQPQ mode) (SCGCQ00871565)

- Enhanced reply queue to support queue depth greater than 1K (SCGCQ00853521)

- Added feature for driver to support Task Management for JBOD and Virtual Drives (SCGCQ00854635)

- Added module parameter to disable 1M IO support and set default to enable 1M IO support (SCGCQ00911362)

- Enhanced tasklet initialization so it would occur before setting up IRQs (SCGCQ00914393, Port of SCGCQ00911709)

- Simplified HB handling for SR-IOV (SCGCQ00864113, Port of SCGCQ00700580)

- Enhanced driver to update Online Controller Reset capability when it changes (SCGCQ00914389, Port of SCGCQ00908352)

- Added feature to print Critical, Fatal and Dead firmware events into system logs (SCGCQ00868723, SCGCQ00882010, Port of SCGCQ00866176)

- Enhanced HB handling to align with behavior on other Operating Systems (SCGCQ00864117, Port of SCGCQ00707323)

- Removed excess dead code (SCGCQ00850012)

Version 6.808.16.00-3 - Moderate Impact/Low Probability of Occurrence
---------------------
Enhancements:
- Add support for 32 bit systems

Version 6.808.16.00-1 - Moderate Impact/Low Probability of Occurrence
---------------------
Fixes:
- Fixed an issue where a deadlock may occur around reset_mutex when Automatic Event Notification threads run in parallel with error handlers - (SCGCQ00911332, Port of SCGCQ00868731)
- Fixed an issue where scanning of Tape drives does not occur depending on whether the drive state is set to systemPD or not - (SCGCQ00914385, Port of SCGCQ00911702)
- Fixed an issue where max_sectors may be set larger than what firmware can support - (SCGCQ00917992, Port of SCGCQ00917399)
- Fixed an issue where kernel may panic due to driver not setting up IRQs for non MSI-x interrupt mode - (SCGCQ00870263, Port of SCGCQ00867873)
- Fixed an issue where driver may halt firmware due to improper error handling for DCMD failure cases - (SCGCQ00882011, Port of SCGCQ00868661)
- Fixed an issue where driver may hang kernel due to deadlock - (SCGCQ00857245)
- Fixed an issue where system may crash due to timeout for flushing cache and shutting down controller DCMDs was not long enough - (SCGCQ00841491)
- Fixed an issue where deadlock may occur between Online Controller Reset and Automatic Event Notification processing function - (SCGCQ00846933)
- Fixed an issue where PCI writes from Automatic Event Notification thread were occurring during Online Controller Reset - (SCGCQ00836410)
- Fixed an issue where MFI frames linked list may corrupt due to double-freeing of frame in the case of an MFI IO timeout - (SCGCQ00837932)
- Fixed an issue where kernel may panic inside PCI subsystem due to IRQs not freed before disabling MSI-X interrupts - (SCGCQ00827403)
- Fixed an issue where ldcount was not validated for non-240VD firmware - (SCGCQ00820349)
- Fixed an issue where a command block would occur for JBODs with FastPath IOs after a drive is replaced - (SCGCQ00806534)
- Fixed an issue where 1MB IO support was not supported controller-wide - (SCGCQ00816313)

Enhancements:
- Set DMA alignment to 8 bytes for PI-enabled VDs - (SCGCQ00928796, Port of SCGCQ00928176)
- Added a parameter to support disabling 1MB IO support - (SCGCQ00911362)
- Added support for printing Critical, Fatal and Dead Firmware events into system logs - SCGCQ00882010, Port of SCGCQ00866176)
- Added support for driver to perform an Online Controller Reset at driver load time if the controller is not responding - (SCGCQ00820389)

Note: Install version is 6.808.16.00.

Version 6.808.14.00 - Moderate Impact/Low Probability of Occurrence
---------------------
Fixes
- Fixed an issue where controller may reset or "MonTask: line 1276" error will occur with JBOD present (SCGCQ00837088)
- Fixed a performance issue on RAID1 with 256k IO size (SCGCQ00674872)
- Fixed a performance issue on RAID1 reads with FastPath enabled (SCGCQ00646224)
- Fixed an issue where an Online Controller Reset may take an unusually lon time (SCGCQ00420374)
- Fixed an issue where a controller firmware crash may not be recognized by driver (SCGCQ00249742)
- Fixed an issue where an MFI frame may be freed twice on MFI command timeout (SCGCQ00837932)
- Fixed an issue where the firmware may fault in an Automatic Event Notification fires during an Online Controller Reset before the chip is in READY state (SCGCQ00836410)
- Fixed an issue where there was no IO timeout value for SCSI management commands for Secure JBOD (SCGCQ00750452)
- Fixed a performance issue on SSDs in JBOD mode (SCGCQ00619694)
- Fixed an issue where file system on a VD can go to read-only on ECC error detection (SCGCQ00608705)
- Fixed an issue where disks may not be found during installation after loading the driver (SCGCQ00299643)
- Fixed an issue where a kernel panic may occur when cable pulled during system reboot (SCGCQ00841491)
- Fixed an issue where 240VD support was not fully implemented (SCGCQ00652795)
- Fixed an issue where the driver may crash if msix_disable=1 is passed to kernel as boot parameter (SCGCQ00383508)
- Fixed an issue where IO errors may occur when connected to a Tape drive (SCGCQ00399947)
- Fixed an issue where kernel may hang due to megaraid_sas driver deadlock (SCGCQ00857245)
- Fixed an issue where kernel may panic when deleting VD and background IO is occurring (SCGCQ00803468)
- Fixed an issue where crash dump may be disabled after an Online Controller Reset (SCGCQ00601138)
- Fixed an issue in 32bit OSs where driver may not load on boot (SCGCQ00362423)
- Fixed an issue where deadlock may occur (SCGCQ00846933)
- Fixed an issue where a kernel panic may occur because IRQs are not freed before disabling MSI-X interrupts (SCGCQ00827403)
- Fixed an issue where multiple Online Controller Resets can trigger a Core Exception (SCGCQ00707592)
- Fixed an issue where crash dump may not be performed properly (SCGCQ00593374)
- Fixed an issue where firmware may fault with CacheCade (SCGCQ00796461)
- Fixed an issue where adapter may hang (SCGCQ00709216)
- Fixed an issue where an offline VD may cause boot hangs (SCGCQ00284564)
- Fixed an issue where kernel may panic (SCGCQ00820349)
- Fixed an issue where kernel may crash in megaraid_sas driver with CacheCade if there are many Automatic Event Notifications and LD sync operations occurring (SCGCQ00712031)
- Fixed an issue where system may hang with CacheCade (SCGCQ00687881)
- Fixed an issue where the same disk may show multiple times in OS (SCGCQ00568992)
- Fixed an issue where kernel may panic on Linux kernels version 3.0 or greater (SCGCQ00561505)
- Fixed an issue where invalid IO statistics may be provided if driver supports more than just 512b sector drives (SCGCQ00282615)
- Fixed an issue where driver fails to reboot system due to outstanding IOs in SCSI mid-layer when controller is in error state (SCGCQ00362023)

Enhancements
- Added ability for JBOD IOs going via firmware path to use timeout value provided by OS (SCGCQ00764795)
- Added a retry of IO commands as LDIO if raid map sync is failed with MFI_STAT_CONFIG_SEQ_MISMATCH (SCGCQ00712510)
- Added support for 4k sector drives if the system supports it (SCGCQ00259244)
- Added support for driver to perform an Online Controller Reset if the controller is not responding (SCGCQ00820389)
- Fixed an issue where system may hang on S3 resume (SCGCQ00758933)
- Added a feature to prevent command block with FastPath after JBOD drive replacement (SCGCQ00806534)
- Enhanced 1MB IO support (SCGCQ00816313)
- Added support for "megaraid_sas.disable_ext_io=1" boot parameter to disable 1M IO support (SCGCQ00911362)
- Added support for Secure JBOD (SCGCQ00711555, SCGCQ00753765)
- Fixed an issue where user space applications may hang if IOCtl is sent prior a kill adapter issued (SCGCQ00759916)
- Fixed an issue where OS may crash on a SCSI IO timeout (SCGCQ00631210)
- Fixed an issue where system may fail to reboot or will kernel panic on init 6 if controller has faulted (SCGCQ00859634)
- Fixed an issue where firmware may fault (SCGCQ00702536)
- Fixed an issue where controller may crash during system power cycle (SCGCQ00647390)
- Fixed an issue where kernel may crash when megaraid_sas driver is loaded but no MegaRAID controllers are present (SCGCQ00282968)


Version 6.806.08.00 - Moderate Impact/Low Probability of Occurrence
-------------------
Fixes:
- Incorporated MegaRAID 6.6 x86/x86_64 Linux driver stream
- Fixed an issue where performance may drop in sequential read 256kb IO (SCGCQ00677516)
- Fixed an issue which may lead to firmware crash and "MonTask: line 1257 in file ../../raid/2108vI2o.c" error in firmware log (SCGCQ00702536)

Features/enhancements:
- Added a retry of IO commands as LDIO if raid map sync is failed with MFI_STAT_CONFIG_SEQ_MISMATCH (SCGCQ00651680)
- Added support for 1MB IO if the firmware supports it as well (SCGCQ00671670)
- Added ability to take a VD offline / bring a VD online, similar to the equivalent actions for PDs (SCGCQ00521610)
- Added support for Self-Encrypting Drives in JBOD mode (SCGCQ00399739)

Version 6.704.15.00 - Suggested
-------------------
- Fixed an issue where uneven span configuration of RAID 1 will
not have proper load balancing for Fast Path Read.

Version 6.602.03.00-2 - Suggested
-------------------
Fixes:
- Fixed an issue where the system may hang when touching max_sectors.
Note: Device driver version number has not changed: 6.602.03.00.

Version 6.602.03.00-1 - Suggested
-------------------
Enhancement:
- Add support for ServeRAID M1215 SAS/SATA Controller
Fixes:
- Fixed an issue where Kernel panic occurs due to timeout of
MFI/MPT pass-through command, followed by completion through
Interrupt context.
Note: Device driver version number has not changed: 6.602.03.00.

Version 6.600.20.00-4 - Suggested
-------------------
Fixes:
- Fixed reboot issue in SLES 11.3 xen.
Note: Device driver version number has not changed: 6.600.20.00

Version 6.600.20.00 - Suggested
-------------------
Enhancement(s):
- Add Support for ServeRAID M5210 and M5210e SAS/SATA Controller

Version 6.506.00.00 - Suggested
-------------------
Retain Tip: Tip #28016
Enhancement(s):
- Added ability for user to configure the maximum number of MSI-X
vectors launched for M51XX and M1XX controllers.


Version 00.00.06.19 - Suggested
-------------------
Fixes:
- Fixed an issue where a kernel crash may occur in some cases,
when megaraid_sas driver is loaded but controller is not present.

Version 00.00.06.15.01 - Suggested
-------------------
Fixes:
- Corrected version strings in the iso and rpm files.
NOTE: No change to the device driver. Packaging fix only.

Version 00.00.06.15 - Suggested
-------------------
Enhancements:
- Add support for fpRead/WriteCapable & fpRead/WriteAcrossStripe
- Add support for SLES 11 SP2.

Fixes:
- Mask off MFI_FRAME_IEEE, MFI_FRAME_SGL64, MFI_FRAME_SENSE64 in
megasas_mgmt_fw_ioctl() to prevent memory scribble issues from
incorrectly built MegaCli frames.
- Fixed reglockFlags for degraded RAID 5/6.

Version 00.00.06.12-01 - Suggested
-------------------
Fix
- Fixed issue where the device driver may fail to install with the
following error: "389 SCRIPT INTERNAL INCONISISTENCY! REPORT TO IBM
IMMEDIATELY"
Note: No change to device driver version.

Version 00.00.06.12 - Suggested
-------------------
Enhancement
- Add support for ServeRAID M5016

Fixes
- LSI Channel fixes

Version 00.00.04.38 - Non-critical
-------------------
- Fixed issue where device driver could print message "kernel megasas:
Command pool empty!" when the controller and megaraid driver are idle.

Version 00.00.04.37 - Suggested
-------------------
- Fixed issue where the ServeRAID M1015 controller will halt during a OCR.
- Fixed issue where OCR will not execute when the physical drives are in a
power transition mode.
- Fix issue where the ServeRAID M1015 controller will halt with a degraded
RAID 5 array during IO.

Version 00.00.04.30 - Non-critical
-------------------
- Added support for the ServeRAID M5025 SAS/SATA Controller

Fixes:
- Fixed issue where during IO firmware faults at line : MonTask: line 1193
in file ../../raid/1078dma.c
- Fixed issue where After 64 VD's are created using MSM the 'fdisk -l'
command does not work.
- Fixed issue where the firmware faults at line 739 in file
../../raid/1078main.c when rebooting after a recon.
- Fixed issue where the drive partition is no longer present on the OS after
importing a foreign configuration.
- Fixed issue where Linux does not show the correct size of VD the second
time if the 'fdisk -l' command is executed.

Version 00.00.04.17 - Non-critical
-------------------
- Added support for the ServeRAID M1015 SAS/SATA controller.
- Added support for the ServeRAID M5000 Series Advanced Feature Key.


Version 00.00.04.10 - Non-critical
-------------------
- Added logic to support next-gen SAS2 controllers.
- Added support for the ServeRAID M5015 and M5014 SAS/SATA controllers.


Version 00.00.03.23 - Non-critical
-------------------
- Added support for the IBM ServeRAID MR10ie (CIOv) SAS controller.
- Fixed an issue where, on a Xen kernel with guest OSs running, invoking
kdump causes a system reboot.
- Fixed an issue that results in a kernel panic when kdump is run on a system
with heavy drive I/O.


Version 00.00.03.21 - Suggested
-------------------
- Added support for the IBM ServeRAID MR10is SAS controller.
- Fixed an issue where a command timeout would occur on a particular SAS
hard drive, and would not recover.
- Added a shutdown DCMD call to the shutdown routine to ensure a graceful
shutdown.
- Updated the list of required pre-built binaries.
- Fixed an issue the could cause unexpected interrupts.
- Fixed an issue where a memory sanity check would sometimes fail for a
certain pointer on a 64-bit system, causing some enclosure components to
not be seen.


Version 00.00.03.18 - Suggested
-------------------
- Added support for the IBM ServeRAID MR10il SAS controller.
- Fixed an issue where the OS would not reboot when a rebuild was in
progress.


Version 00.00.03.13 - Non-critical
-------------------
- Added support the IBM ServeRAID MR10i, MR10k, and MR10M SAS controllers.
- Fixed an issue where, on boot to Xen kernel on Red Hat Enterprise Linux
(RHEL) 5 64-bit, the user would encounter an “Error 13: Invalid or
unsupported executable format” error.


Version 00.00.03.06 - Suggested
-------------------
- Added diskdump support for Red Hat Enterprise Linux (RHEL) 3 and RHEL 4.
- Set the reply_q_sz value to the maximum number of commands supported by the
firmware.
- On 2.4 kernels: fixed an issue where, when the system was rebooted, the
shutdown routine did not get called; added a notifier for the reboot event
and initiated a flush command from the reboot event handler.
- Fixed issue where, on RHEL 3 Update 6, the driver would not install on
AMD64 systems.


Version 00.00.03.01-1
---------------------
- Initial release
ibm_dd_sraidmr_7_707_04_00_sles11_x86-64_chg

===============================================================================
Emulex 16GB Fibre Channel Firmware Package
===============================================================================

Firmware Version: 11.2.209.51
Supported On: System x Rack and Flex

Problems Fixed:
- None

Incremental Interoperability:
- RHEL7 Update 3 Support
- SLES12 SP2 Support
- Windows 2016 Support
- VMware ESXi 6.5 Support

Known Issues:
- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159504)

===============================================================================

Firmware Version: 10.3.145.0
Supported On: System x Flex

Problems Fixed:
- None

Incremental Interoperability:
- Grantley based ITE

Known Issues:
- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159504)

===============================================================================

Firmware Version: 10.2.377.18
Supported On: System x

Problems Fixed:
- Link does not recover during IO + Port Cycling with FW 1.1.43.3
- BIOS versions return multiple values
- LPe16k point to point (direct attached) connection not bootable in legacy
BIOS
- LPe16k point to point (direct attached) connection performance issues in
legacy BIOS

Incremental Interoperability:
- Grantley Rack Servers

Known Issues:
- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159504)

===============================================================================

Firmware Version: 10.2.261.36
Supported On: IBM System x and Flex

Problems Fixed:
- Server will halt on black screen during rolling reboot of Windows 2012 x64
uEFI SANboot
- Server intermittently fails to boot during rolling SANboot (any OS)
- Fixed a boot hang associated with server BIOS change
- Reported firwmare version in CMM is intermittently incorrect
- Unable to set pause Flow control when connected to DCBX switch with PFC off
- during cable pull testing a 40 second delay in link up experienced with
Brocade switch ports
- I/O completion and abort completion WQE are generated out of order
- Unexpected WCQE in RQ CQ seen in RXRI mode while performing cable pulls

Incremental Interoperability:
- Inventory support for the Flex xHMC (Chassis Hardware Management Console)
- Crosslink & Express Lane on LPe16k based solutions

Known Issues:
- To disable BFS after BOFM or IFM have been enabled, it must be done by
setting BFS manually in the EFIBoot config utility or sending a BOFM default
command to the port. This is working as expected and we are documenting it
here.(159504)

===============================================================================

Firmware Version: 10.0.803.8
Supported On: IBM System x

Problems Fixed:
- EFI BOOT fail during SLES11 SP3 rolling reboot

Incremental Interoperability:
- None

Known Issues:
- None

===============================================================================

Firmware Version: 1.1.43.21
Supported On: IBM System x

Incremental Interoperability:
- None

Problems Fixed:
- Server will halt on black screen during UEFI rolling reboot reboot cycle
test with 16Gb HBA under Windows 2012 x64
- Allows installing and booting from an MSA2040 array configured in PT-PT
direct mode at 16G speed. We're now able to enable Autoscan and install/boot
from multiple OSes
- Added support to bypass configuring pnp Boot Table in a multipath situation.
Fixes Microsoft Windows Server 2008 bug.
- Fixed the "Read Rev Failure" issue during POST to accept "0" address value
as a valid.
- Fixed the wrong VPD HBA model number display on the banner and properties,
and change the proper VPD data field size.
- Fixed the timeout issue on Flogi when try to select a HBA device without
connecting to a target or FC switch.
- System will halt during reboot cycle test under Windows 2012 x64 UEFI
- Fixing PCI Function Number decoding issue in BOFM code
- Boot fails during SLES11 SP3 rolling reboot
- Enable BFS and update the NVRAM if BOFM target is available
- Add Diagnostic support for UEFI 16Gb FC
- Reconnect menu item causes a System BIOS exit request only on AMI core
system BIOS
- Adding port's protocol name and WWPN in browser help menu

Known Issues:
- None

===============================================================================

Firmware Version: 1.1.43.12
Supported On: IBM System x and Flex

Incremental Interoperability:
- IBM Flex System FC5052 2-port 16Gb FC Adapter
- IBM Flex System FC5054 4-port 16Gb FC Adapter
- FC support for support for ASU/Config Patterns for Flex and ASU for IBM
System x & BladeCenter
- Direct PT - PT connections
- Extended SCSI Pass Thru Protocol
- IBM Tape unit interoperability - see SSIC for more information
- SLES 11.3 on IBM System x

Problems Fixed:
- Windows 2012 OS will not resume from Sleep mode
- Boot Device entries can be lost after exiting from BIOS setup

Known Issues:
- None

===============================================================================

Firmware Version: 1.1.43.3
Supported On: IBM System x

Incremental Interoperability:
- VPD-W for Lancer

Problems Fixed:
- Emulex FC Adapter does not auto-enable SAN boot mode when boot target
configuration is made via IFM

Known Issues:
- None

===============================================================================

Firmware Version: 1.1.21.9
Supported On: IBM System x

Incremental Interoperability:
- IBM Server machine types. Refer to IBM ServerProven for specifics

Problems Fixed:
- Fixed FCP_CONF handling bug
- No SRR sent after drop write data frame, I/O fails
- Adapter does not invoke recovery after dropped read data frame
- I/O throughput performance improvements
- Link failover when connected to FC Tape
- Cosmetic: Cleaned up miscellaneous error handling messages in debug log
files
- If a new device comes online and attempts to acquire an AL_PA after the link
has already come up, the FC link appears to hang until the cable is pulled
- Cleaned up link negotiation at 4GB/8GB/16GB speeds with specific switches

Known Issues:
- None

===============================================================================

Firmware Version: 1.0.11.108
Supported On: IBM System x

- Initial Release

===============================================================================
elx_fw_fc_17a-lp16-11_2_209_51-1_linux_32-64_chg

ÿþServeRAID M1200 SAS\SATA Controller Firmware Update



Adapters Supported: ServeRAID M1215 SAS/SATA Controller Andros-8 for (46C9114)

LSI SAS3004 RAID Andros-e for (NA-Newport RAID)



Support OS:

RHEL 6.8,6.9,6.10, RHEL 7.5,7.6,7.7,

SLES 11.2,11.3,11.4, SLES 12.2,12.3,12.4,



NOTE TO SERVICE - Reference RETAIN #N/A



Version 24.21.0-0112 - Moderate Impact/Low Probability of Occurrence

--------------------

PACKAGE: 24.21.0-0112

BIOS: 6.36.00.3

UEFI Driver: 0x06180203

HII: 03.25.05.12

MR NVDATA: 3.1705.00-0020

iMR NVDATA - 3.1705.01-0012

MR Firmware - 4.680.00-8489

iMR Firmware - 4.680.01-8488

MR 6.14



Defects (15)

- LD Inquiry still show as AVAGO_B for VD even when JBOD drive is set as boot PD.(SCGCQ02052706)

- Fatal FW error observed on connecting enclosure in a multipath or cascading another enclosure when slot based device ID feature is enabled.(SCGCQ02141291)

- Fix API changes done for NVMe readiness(SCGCQ02142981)

- Add NVMe width comments to mr.h(SCGCQ02146846)

- During SpinUpRecoveySM 2/4/1C sense data is not handled(SCGCQ02149370)

- Non boot VD gets vendor identification as "AVAGO_B" for a specific OEM(SCGCQ02160670)

- Boot VD Inquiry String is not retained, after foreign importing the Boot VD configuration(SCGCQ02057908)

- montask observed inline 1704 in ../../raid/bootMsg.c during enclosure cable pull/push.(SCGCQ02136344)

- Flaky link drive connection causing a fatal error.(SCGCQ02141740)

- SED drive moved to fail state during device missing delay (DMD)(SCGCQ02144016)

- IOUNITPAGE 11 parameters are not updated in the next boot.(SCGCQ02154597)

- TUR timeout increased from 64 sec to 120sec.(SCGCQ02118063)

- When slot based device ID feature is enabled, Drive Slot id and device ids are not matching after hot plug of direct attached drives(SCGCQ02144003)

- 6.14_FW : Fatal FW error observed on iMR controller after flashing latest FW pkg 24.21.0-0111 and rebooting the system.(SCGCQ02171024)

-(SCGCQ02102580)

- Initialize cache after diagnostics testing(SCGCQ02157830 port of SCGCQ02134286)

- CSCuv03959 DPMR6 - System hung after abort running CC continuously overnight.(SCGCQ02169538 port of SCGCQ00883695)

- IO Error observed on few VD's, after setting the boot drive in NVMe Mix Mode Configuration(SCGCQ02099404 port of SCGCQ02058292)

- Kill Adapter if PD FW download is run in continous loop(SCGCQ02139082 port of SCGCQ02059825)



EnhancementRequests (32)

- Add New Generic OOB API To Read ROC Temp, Drive Temp, Drive Type, Drive Protocol and status through OOB BMC(SCGCQ01940661)

- Add a new log event used whenever the snap dump properties are modified.(SCGCQ01963328)

- Add a bit for atomic descriptor capable(SCGCQ01965047)

- Add CTRL_SB_SOFT_SECURE_MODE event to indicate soft secure mode(SCGCQ01965721)

- Introduced new controller bit(SCGCQ01985474)

- Customer needs to generate and extract the On-demand based debug data both for MR and iMR.(SCGCQ02000566)

- Driver parameter bit for support of tool box cmd(SCGCQ02002119)

- Add new MFI Fault sub code for Secure Boot Preboot Auth failure(SCGCQ02006657)

- Reword event log messages as it creates unnecessary panic.(SCGCQ02013675)

- Modification in MR_SNAPDUMP_TRIGGER_TYPE enum value(SCGCQ02030653)

- Additional details about spare(SCGCQ02033538)

- API change to support NVMe Passthrough over OOB(SCGCQ02035295)

- API change to support new DCMD for consolidated device list(SCGCQ02037158)

- API changes for NVMe speed and width changes(SCGCQ02053667)

- API changes for linkconfig interface(SCGCQ02053671)

- Increase in MR_PD_INFO.name length to 32 characters(SCGCQ02079068)

- MR Windows IOCTL Error codes to Application added to MR API(SCGCQ02103183)

- Add MFI STAT and MR Event for Secure Boot indicating fw dl was not allowed due to an existing pending key change(SCGCQ02103973)

- Better error message for certain unmap operations(SCGCQ02111563)

- OEM request to implement slot based device ID for direct attached or enclosure connected drives(SCGCQ02111943)

- As per OEM request bypassing the cache for particular workload on 512E drives.(SCGCQ02123808)

- Add disableOffloadNum field in MR_SNAPDUMP_PROPERTIES struct(SCGCQ02125252)

- API changes for a better presentation of Atlas to tools(SCGCQ02149380)

- API changes for Lane Margining(SCGCQ01921241)

- Standard SCSI Inquiry vendor identification should be  AVAGO_B for VD that is set as boot device(SCGCQ02030668)

- Unlocking FDE disk after a power-on-reset (POR(SCGCQ02050712)

- MR API: Add support bits for currentSpeed and clkMode(SCGCQ02132334)

- Adding NVACHE messages indicate when SLC format has started and completed(SCGCQ02137048)

- FW prints SASIOUnitPage 11 during boot up.(SCGCQ02144058)

- Change the order of DDF header updates when there are errors existing in DDF headers currently on the drive(SCGCQ02124249)

- Enhance data collection when a MU error is seen(SCGCQ02134251)

- Unblock and allow the SCSI pass-through commands to bad/failed/offline PDs(SCGCQ02136394)



Version 24.21.0-0097 - Moderate Impact/Low Probability of Occurrence

--------------------



PACKAGE: 24.21.0-0097

BIOS: 6.36.00.3

UEFI Driver: 0x06180203

HII: 03.25.05.12

MR NVDATA: 3.1705.00-0018

iMR NVDATA - 3.1705.01-0012

MR Firmware - 4.680.00-8458

iMR Firmware - 4.680.01-845

MR 6.14

SATA PD does not change to failed state after read medium error detected(SCGCQ01624704)

- Repetitive OOB and LED prints observed in FW logs(SCGCQ01727104)

- FW Crashes when user tries to fetch SMP PassThru Info using Host SLT(SCGCQ01937319)

- Do not allow RAID config in JBOD-WB mode and prevent change of personality if WB mode is set(SCGCQ01685447)

- dev defect - Setting defaults for JBOD-WB mode and code cleanup(SCGCQ01681100)

- Cannot create or mount xfs filesystem using xfsprogs 4.19.x kernel 4.20(SCGCQ02027889)

- xfs_info command run on an XFS file system created on a VD of strip size 1M shows sunit and swidth as 0(SCGCQ02056038)

- CV going into WT mode during learn after upgrading to versions later than 24.18.0-0021 - FW fault after factory defaults(SCGCQ02060813)

- After using hdparm to lock a SATA SSD JBOD drive the drive fails to be unlocked by the MR FW on reboot(SCGCQ02083536)

- Kill adapter observed while running target reset on JBOD WB(SCGCQ01789188)

- SMp command failure in OOB Path(SCGCQ01927021)

- HDET_MR 6.14: OOB - SCSI PassThru Command fails with error code 0x2E (SCGCQ01936541)

- Once pinnedcache is set to off not able to toggle field value in JBOD WB mode(SCGCQ01671213)

- PL Fault observed while running target reset on JBOD WB(SCGCQ01676164)

- MR 6.14: FW reported incorrect value for max data transfer request size as 4 MB in Storcli app.(SCGCQ02023160)

- Kill Adapter observed while running task management on JBOD-WB with IO's (SCGCQ02009801)

- Max number of PDs for PatrolRead to run concurrently should be in range from 1 to MR controller's max configurable PDs(SCGCQ02008420)

- Some Configured drives may change to JBOD and Unconfigure Good after Set JBOD=on and reboot(SCGCQ02080101)

- MR controller was missing in UEFI after reboot when the bootable JBOD drive was removed(SCGCQ02112533)

- MR API - Incorrect value used for MR_DCMD_CTRL_SNAPDUMP_ONDEMAND (SCGCQ01882581)

- MR 6.14 - PD show all StorCLI command fails for UBAD SAS & SATA drives (SCGCQ01915285)

- With ESXi 6.7 OS or latter, a SATA SSD drive that is configured as EPD will be dropped by OS when driver reload is done(SCGCQ01969605)

- Dev defect: Incorporate the new changes done in MR API(SCGCQ01760667)

- Amber LED not seen for UBAD PD's (SCGCQ01770256)

- Continuous SRAM correctable error prints followed by controller reset(SCGCQ02023839)

- Able to create RAID configuration even after it has been disabled(SCGCQ01670086)

- With a pending personality change, Global hot spares are allowed to be created and should be blocked.(SCGCQ01750315 port of SCGCQ01742187)

- SMP pass through not working when the  PD 0 is BAD drive(SCGCQ01945674 port of SCGCQ01945602)

- (CSETActivity) - MCTP over PCIe discovery(SCGCQ01904092 port of SCGCQ01184923)

- CIT: Same EID assigned to 2 930-8i controllers(SCGCQ01886616 port ofSCGCQ01830180 )

- Controller OCR seen when DM multipathing issues read CDB with zero blocks(SCGCQ01822167 port of SCGCQ01808882)

- Unable to recover config when changing security password before re-inserting drives(SCGCQ01874302 port of SCGCQ01715058)

- 23=Flash programming error while upgrading the Controller FW causes the APP image corruption(SCGCQ02085501 port of SCGCQ02074630)



EnhancementRequest:

- RTTrace Enable/Disable API changes(SCGCQ01830211)

- MR API changes to support EKMS over OOB(SCGCQ01874035)

- API Changes for Driver/FW DCMD HandShake(SCGCQ01841266)

- Added new events for unmap policy change(SCGCQ01871912)

- Add secure boot key update complete event(SCGCQ01928254)

- Including The Time Stamp for every Snap Dump created in the firmware.(SCGCQ01797424)

- Unmap: Define new events for enhanced UNMAP support [MR7.8](SCGCQ01803319)

- Deprecate the snap dump fields that are no longer needed for MR_SNAP_DUMP_PROPERTIES structure(SCGCQ01816724)

- [MR 7.8] API change to return apt failure status for a personality change request(SCGCQ01853480)

- Interrupt coalsecing setting per group of 8 replies queues (h/w VF registers (SCGCQ01886424)

- HDET: Support smp passthrough storeliboob (API changes requirement(SCGCQ01916035)

- Add secure boot support(SCGCQ01792416)

- API change to provide learn complete timestamp(SCGCQ01845269)

- POC in 6.14: WB support and Pinned Cache changes(SCGCQ01581022)

- Aero FW - Reporting SSD wear gauge values for OEM specific customers(SCGCQ01798686)

- Support SC_INQUIRY and SC_LOG_SENSE SCSI Passthrough commands on drives in bad state for a particular OEM(SCGCQ01888257)

- FW changes for the configurable parameters(SCGCQ01609320)

- Add the API to clear all the snap-dumps from firmware.(SCGCQ01824135)

- API Changes - After Vision PSOC FW update, applications should ask the user for power cycle instead of reboot(SCGCQ01765150)

- Add new MFI Status - MFI_STAT_PD_NOT_ELIGIBLE_FOR_LD (SCGCQ01818580)

- HDET: Support smp passthrough in storlib and storeliboob (SCGCQ01799154)

- Fail the drive and do not pin the cache(SCGCQ01584411)

- Integrated Invader PL RO - SCGCQ02000507 phase 14, Version 14.00.11.00 to MR 6.14(SCGCQ02000920)

- [MR 7.8] API change to export "disable least latency mode"(SCGCQ01887495)

- Fix MR_CTRL_INFO to support backward compatibility(SCGCQ01946548)

- Added customer serial number field to MFC Manufacturing 2 structure(SCGCQ01873417)

- Added Support for Triggering SnapDump(SCGCQ01848759)

- Add Board Support Package Image Type to MR_IMAGE_TYPE(SCGCQ01931637)







Version 24.21.0-0084 - Moderate Impact/Low Probability of Occurrence

--------------------

MR/iMR 6.14



PACKAGE: 24.21.0-0084

BIOS: 6.36.00.3

UEFI Driver: 0x06180203

HII: 03.25.05.11

NVDATA: 3.1705.00-0018

iMR NVDATA - 3.1705.01-0012

Firmware - 4.680.00-8434

iMR Firmware - 4.680.01-8435



Defects:

- SATA SSD not discovered by OS during hibernate test.(SCGCQ01949781)

- Intruder and Invader controllers returnning vpd86 error.(SCGCQ01929277)

- FW reports that the board passed BBU Retention test on boards that have a non operational ONFI NAND memory.(SCGCQ01891177 Port Of Defect SCGCQ01934351)

- Invader IMR : PD fails to get marked as foreign on insertion.(SCGCQ01950845 Port Of Defect SCGCQ01955263)

- Preserved Cache doesn't flush back during Foreign Import.(SCGCQ01466831 Port Of Defect SCGCQ01904085)



Version 24.21.0-0067 - Moderate Impact/Low Probability of Occurrence

--------------------

PACKAGE: 24.21.0-0067

BIOS: 6.36.00.3

UEFI Driver: 0x06180203

HII: 03.25.05.10

NVDATA: 3.1705.00-0016

iMR NVDATA - 3.1705.01-0011

Firmware - 4.680.00-8392

iMR Firmware - 4.680.01-8393



Defects (8)

- 'CacheVault Flash Size' is showing as 3.0 GB after upgrading FW when it should show 4.0 GB.(SCGCQ01615779)

- criteo: Storcli shows R0 VD as WB in JBOD personality where as FW shows in WT mode.(SCGCQ01714445)

- Revert code changes from CSET SCGCQ01569257.(SCGCQ01717743)

- Customer specific 3108 PCIe add-on card fails to come back while resuming from sleep state S.(SCGCQ01718911)

- FW returns success for enabling encryption when it is failed on the drives.(SCGCQ01830718)

- Line 535 in ../../raid/cachePreserve.c for trying to create Pinned Cache by Cable Pull..(SCGCQ01839662)

- memset the deviceStateLedBitmap properly.(SCGCQ01844264)

- OOB SCSI passthru command (READ DEFECT 12) return without response data.(SCGCQ01793262)

- FW is observing Kill Adapter while CCVD disassociate in progress.(SCGCQ01186806 port of SCGCQ01172369)

- Update the MAXTransferLength properly for Driver enabled 1MB support feature.(SCGCQ01238543 port of SCGCQ01232275)

- FW crashes when FW update(OFU) is done with faluty onfi.(SCGCQ01249569 port of SCGCQ01227115)

- irq handler flooding taskqueue and persistent ID removal corrupting memory.(SCGCQ01399132 port of SCGCQ01299784)

- Firmware allows to add bad blcoks beyond actual number of blocks..(SCGCQ01430024 port of SCGCQ01403292)

- MCTP: Addressing PCIe credirt free issue..(SCGCQ01447186 port of SCGCQ01446811)

- Firmware discovery is not listing all the drives after removal/insert Enclosure Cable with IO.(SCGCQ01579250 port of SCGCQ01555943)

- MR FW memory Leak across driver load/unload.( SCGCQ01579251port of SCGCQ01573393)

- With controller operating in least latency mode, FW hits montask upon running IOs.(SCGCQ01587048 port of SCGCQ01116419)

- Increase the recon BB list entries to align with BBM MAX BAD entries.(SCGCQ01635416 port of SCGCQ01623254)

- Issue: JBOD devices were dropped after unloading driver and reloading driver in linux.(SCGCQ01639846 port of SCGCQ01566087)

- : FW asserts when invalid parameters to set excluded ld for CC is sent to firmware..(SCGCQ01670394 port of SCGCQ01635729)

- Colusa SAS expander reset results in unpredictable performance.(SCGCQ01697517 port of SCGCQ01455811)

- MR 7.6 - "NVCache has gone bad" during POST after flashing the latest package 1226 and rebooted.(SCGCQ01714326 port of SCGCQ01635062)

- When NVRAM value is read from cached address ,primary core reads stale value and skips writing to NVRAM..(SCGCQ01715349 port of SCGCQ01676080)

- F/W Hangs during reboot.(SCGCQ01716602 port of SCGCQ01616551)

- MR7.6: Firmware hit montask running task management reset in loops.(SCGCQ01727364 port of SCGCQ01675742)

- When NVRAM value is read from cached address ,primary core reads stale value and skips writing to NVRAM.(SCGCQ01729680 port of SCGCQ01676080)

- LAS does not show proper state of secured locked drives..(SCGCQ01732045 port of SCGCQ01615781)

- F/W Hangs during reboot.(SCGCQ01758976 port of SCGCQ01616551)

- Pd firmware download timer is calculated accordingly.(SCGCQ01758988 port of SCGCQ01669508)

-.(SCGCQ01763953 port of SCGCQ01749090)

- Smart Return Status passthru command failed on SATA drives.(SCGCQ01806402 port of SCGCQ01555033)

- LAS does not show proper state of secured locked drives..(SCGCQ01807819 port of SCGCQ01615781)

-.(SCGCQ01838484 port of SCGCQ01807938)

- 9460-8i is reporting Chip Temperature of 255 when the ambient temp is about 0 C.(SCGCQ01850339 port of SCGCQ01565568)

- Found invalid event.(SCGCQ01375915 port of SCGCQ01347858)

- 9460-16i disappears from F1 setup after encrypting SED.(SCGCQ01565312 port of SCGCQ01326871)

- Sanitize Support.(SCGCQ01577753 port of SCGCQ01526323)

- Increase the recon BB list entries to align with BBM MAX BAD entries.(SCGCQ01633668 port of SCGCQ01623254)

- Sanitize progress in TTY log showing incorrect elapsed time.(SCGCQ01681594 port of SCGCQ01630577)

- Pd firmware download timer is calculated accordingly.(SCGCQ01682987 port of SCGCQ01669508)



EnhancementRequests (11)

- Integrate phase 12 PL (12.00.13.00) with MR 6.12.(SCGCQ01580766)

- FW change: Request to add NVDATA and PNP IDs for new card introduction.(SCGCQ01826466)

- Integrate Intruder Phase 14 PL - 14.00.10.00 Firmware MR PL Release.(SCGCQ01764776)

- Criteo: API changes reversal.(SCGCQ01760512)

- PL Integration: Integrate Intruder PL phase 13.00.10.00 with MR 6.13 Intruder.(SCGCQ01698033)

- PL Integration : Integrate Invader phase 12.00.14.00 PL with MR 6.12.(SCGCQ01716598)

- RTTrace API Changes.(SCGCQ01745568)

- Mixing Rules for SED and non-SED drives to create non-secure array with controller security enabled..(SCGCQ01757538)

- Unmap: Define new API for enhanced UNMAP support.(SCGCQ01758062)

- Adding API bit to indicate whether forced personality change is supported or not..(SCGCQ01762153)

- PL Integration: Integrate Invader Phase 13.00.10.00 PL with MR 6.13 Invader.(SCGCQ01698045)





Version 24.21.0-0052 - Moderate Impact/Low Probability of Occurrence

--------------------

PACKAGE: 24.21.0-0052

BIOS: 6.36.00.2

UEFI Driver: 0x06180202

HII: 03.25.05.04

NVDATA: 3.1705.00-0014

iMR NVDATA - 3.1705.01-0011

Firmware - 4.680.00-8353

iMR Firmware - 4.680.01-8354



Defects (42)

- Intruder Controller Disappear during clean shutdown on OEM server.(SCGCQ01375977)

-.(SCGCQ01753405)

-.(SCGCQ01749090)

- When NVRAM value is read from cached address ,primary core reads stale value and skips writing to NVRAM..(SCGCQ01676080)

- Pd firmware download timer is calculated accordingly.(SCGCQ01669508)

- IO path function accessed by both core is not synchonized..(SCGCQ01640234)

- False alarm of "cache Discarded" when the System, with Invader controller + WT R5 volume, is shutdown normally..(SCGCQ01627751)

-.(SCGCQ01623408)

- Increase the recon BB list entries to align with BBM MAX BAD entries.(SCGCQ01623254)

- MR FW memory Leak across driver load/unload.(SCGCQ01573393)

- Incorrect Micron NAND Model Number read from flash.(SCGCQ01531136)

- MR_6.14 PACK 23 - On performing a cable pull/push operation during drive is in failed state, result to MonTask.(SCGCQ01529830)

- [Factory issue] MR 3108 controller BIOS stop at 3 different initialization screen.(SCGCQ01497858)

- IO access to iMR FW will fail after sveral powercycle.(SCGCQ01494761)

- iMR Compilation fails even with RELEASE option in 6.12 after taking errata MR workaround SCGCQ01323607 and its child defects.(SCGCQ01494566)

- SED Drive become UBad during secure erase on MegaRAID 9361-8i controller.(SCGCQ01473188)

- 6.14 : Reverting the sysDma changes.(SCGCQ01465727)

- On iMR Invader & for 2 enclosures connected in cascaded multi path , power off and then power on the 1st enclosure, PDs not getting detected.(SCGCQ01455949)

- Firmware upgrade/downgrade operation failing on SKINNY controller.(SCGCQ01455133)

- MCTP: Addressing PCIe credirt free issue..(SCGCQ01446811)

- Parameter Page Invalid, Setting channel count based on DDR Size..(SCGCQ01440768)

- FW breaks into montaks with pinned cache and foreign configuration.(SCGCQ01378970)

- FW reported tmm Date of Manufacture 15/25/6.(SCGCQ01395084)

- Interrupting Offload will Lead to Next offload cycle to fail.(SCGCQ01399701)

- Enable WB support via API.(SCGCQ01405242)

- F/W Hangs during reboot.(SCGCQ01616551)

- iMR compilation breaks, exceeding 1MB flash region allocated.(SCGCQ01520940)

- Extend iMR change of trap related data should be in same module as trap ISR..(SCGCQ01514867)

- Workaround for IO access to iMR FW will fail after sveral powercycle on 3004 controller..(SCGCQ01507504)

- linker error resolved.(SCGCQ01472217)

- Problem with I2C Slave communication with external Masters that don t support slave clock stretching..(SCGCQ01443277)

- MR : Cache data Lost when Term Log is set to "on" and grown bad blocks are there in the controller.(SCGCQ01394288)

-.(SCGCQ01400707)

- Learn cycle shown as active when Learn cycle fails.(SCGCQ01400807)

- Firmware allows to add bad blcoks beyond actual number of blocks..(SCGCQ01403292)

- OCR getting disabled after NVRAM delete.(SCGCQ01719006)

- MCTP : Porting of firmware download fixes from Ventura.(SCGCQ01439651)

- NVCache state not transitioning from 'Faulty' to 'Ok' until after reboot.(SCGCQ01395724)

- Intermittent: On iMR_Invader & cascaded Enclosures, after power off the enclosure, FW holds the PD info and apps display PDs.(SCGCQ01483727)

- controller VPD info is hidden as per OEM request.(SCGCQ01454973)

- SSD SATA JBOD discovered as 0.0MB after re-loading the same driver..(SCGCQ01446965)

- Firmware discovery is not listing all the drives after removal/insert Enclosure Cable with IO.(SCGCQ01555943)



EnhancementRequests (47)

- New events for PR/CC conflicts and sector size mismatch.(SCGCQ01227051)

- Provide customized default smartpollinterval to 30 for iMR3004 product.(SCGCQ01748252)

- RTTrace API Changes.(SCGCQ01745568)

- API changes needed to support eHBA product series.(SCGCQ01727346)

- Create sanitize events.(SCGCQ01713708)

- Memset the PinnedDataStructure when DRAM dirty signature is zero.(SCGCQ01713149)

- Integrate latest phase 14.0 - 14.00.08.00 PL with MR 6.14.(SCGCQ01682170)

- as per customer request enabled FBU02 and 4G TFM support.(SCGCQ01681106)

- Modify event string APIs for MISSING and OFFLINE LDs.(SCGCQ01628177)

- New configuration params added for EPD-PT devices.(SCGCQ01599607)

- MR API change request to Enable/disable the parallel PD FW update feature based on PNP ID s.(SCGCQ01595347)

- Integrate latest phase 14 PL with MR 6.14.(SCGCQ01593998)

- Integrate Invader Phase 14 PL - 14.00.06.00 Firmware MR PL Release.(SCGCQ01589431)

- Add support to defeature Cached I/O policy.(SCGCQ01581032)

- Implement Snapdump debugging capability.(SCGCQ01567770)

- Integrate Intruder phase 14 PL - 14.00.08.00 with MR 6.14 Intruder.(SCGCQ01459161)

- customer request for GPIO support..(SCGCQ01452102)

- Enable DO_REAL_TIME_ISP and DO_DISABLE_ISP_CLAMP flags while flashing CPLD for Intruder cards.(SCGCQ01452026)

- Fail to Set SSDSmartErEnabled to TRUE when copyback is disabled.(SCGCQ01403999)

- PL 14.00.07.00 intgration to MR 6.14 intruder..(SCGCQ01401110)

- Integrate phase 14 Intruder PL - 14.00.06.00 with MR 6.14.(SCGCQ01386225)

- Add "Incompatible with Profile" event.(SCGCQ01289924)

- Add MR API bit to indicate the profile is NVMe Only profile.(SCGCQ01216848)

-.(SCGCQ01389581)

- Add Test Link Diagnostic API.(SCGCQ01436268)

- Add a new structure to provide OEMs ability to switch to select either I2C or PCIe as an out of band transport.(SCGCQ01445048)

- Provide OEMs ability to select either I2C or PCIe as an out of band transport.(SCGCQ01450245)

- Update description of MR_DCMD_CTRL_PERSONALITY_SET Dcmd.(SCGCQ01467149)

- Add support for API fields to report SED type of PD.(SCGCQ01587230)

- Add OnOff parameter in Properties2 of Structure MR_CTRL_PROP to enable/disable mix of Enterprise & Opal SED drives.(SCGCQ01593520)

- NVDATA parameter to OPAL SED.(SCGCQ01614689)

- Added a new interface between driver-aops to indicate if 64 bit SGL support is enabled.(SCGCQ01620350)

- Add new MFI Status to block requested operation due to existing controller configuration.(SCGCQ01670135)

- Change the mr.h API comment showing the new return status for the - MR_DCMD_PD_GET_INFO.(SCGCQ01670234)

- API change for Switch attached NVMe HW RAID support for Supermicro backplanes.(SCGCQ01697667)

- Request to enable JBOD for Rambler PNP ID.(SCGCQ01727448)

- Reverted the DDR tuning values.(SCGCQ01625968)

- Porting the changes of NVRAM_Struct from MesaVerde stream to 6.14.(SCGCQ01563144)

- Enhance Messaging Unit error ISR to dump debug information of virtual functions having error.(SCGCQ01553249)

- CacheCade: IO performance need to be improved for WB SVD and WB CCVD combination for specific PnP ID.(SCGCQ01472061)

- FW breaks into montaks with pinned cache and foreign configuration.(SCGCQ01403814)

- Boot message string change for BOOT_MSG_CACHE_DISCARD.(SCGCQ01394348)

- Block OCR after Clearing NVRAM.(SCGCQ01386919)

- PL 14.00.05.00 Integration with Invader MR 6.14.(SCGCQ01384265)

- Added MR_MFC_DEFAULTS.NVMeAbortTO and MR_MFC_DEFAULTS.NVMeMaxControllerResetTO.(SCGCQ01532045)

FW to fail back host command for the wrong value.(SCGCQ01575960)

- Setting DDR flag for ROMB design having new DDR for an OEM.(SCGCQ01466802)



CSETActivities (71)

- Infinite loop in onfiSyncModeEnter.(SCGCQ01259314 port of SCGCQ00329024)

- HW workaround implementation for SCGCQ00830272 and SCGCQ01048567.(SCGCQ01326393 port of SCGCQ01323607)

- MR_6.14: Intruder PCI Trapping ISR incorrect logic for config trap address.(SCGCQ01334364 port of SCGCQ01332947)

- Firmware crashes during medium error recovery and Rebuild.(SCGCQ01348660 port of SCGCQ01304521)

- Resulting R0 VD is showing as not consistent after reconstruction..(SCGCQ01348998 port of SCGCQ01288897)

- Imr Invader FW crashes while upgrading from Pkg 24.18.0-0021 to Pkg 24.21.0-0007..(SCGCQ01351814 port of SCGCQ01342601)

- Intruder 4G DDR tuning value has to be changed in MR FW..(SCGCQ01369344 port of SCGCQ01368845)

- Found invalid event.(SCGCQ01375914 port of SCGCQ01347858)

- Placement of an image checkword at data area of NOR flash leads to controller crash.(SCGCQ01375943 port of SCGCQ01375071)

- Block OCR after Clearing NVRAM.(SCGCQ01392471 port of SCGCQ01386919)

- Block OCR after Clearing NVRAM.(SCGCQ01394920 port of SCGCQ01386919)

- SCS/PL debug logs for "rb", "tb", or "dmdiag pl dbg" are sometimes mangled due to multiple mprintf's overlapping.(SCGCQ01399457 port of SCGCQ01283702)

- RedBrick controller hang at DCR Err Logg Address 29e02..(SCGCQ01412795 port of SCGCQ01375159)

- RedBrick controller hang at DCR Err Logg Address 29e02..(SCGCQ01412827 port of SCGCQ01375159)

- LSA hangs when user try to change drive security key..(SCGCQ01412848 port of SCGCQ01342655)

- B200M4 (Carmel/ 3108 iMR): driver crashed after FW update via UCSM (UCSM bundle 2.2(8fS2)A/B to 3.1(2.163)A/B).(SCGCQ01412896 port of SCGCQ01271186)

- Parameter Page Reads fail during ONFI bringup..(SCGCQ01415428 port of SCGCQ01413557)

- heck Consistency doesn't identify double media errors once aborting and starting CC again.(SCGCQ01421932 port of SCGCQ01411591)

- heck Consistency doesn't identify double media errors once aborting and starting CC again.(SCGCQ01421933 port of SCGCQ01411591)

- heck Consistency doesn't identify double media errors once aborting and starting CC again.(SCGCQ01421934 port of SCGCQ01411591)

- Revert the DDR tuning values back to default value.(SCGCQ01446963 port of SCGCQ01444640)

- PL considers Timer Handle=0 and invalid, MR FW did not..(SCGCQ01446983 port of SCGCQ01399026)

- MCTP: Addressing PCIe credirt free issue..(SCGCQ01447187 port of SCGCQ01446811)

- Parameter Page Invalid, Setting channel count based on DDR Size..(SCGCQ01447901 port of SCGCQ01440768)

- Drives in Enclosure spin up values for OEM board is not initialized correctly.(SCGCQ01466081 port of SCGCQ01450221)

- IOMMU fault at address 0x80360000.(SCGCQ01473355 port of SCGCQ01279547)

- Enable DO_REAL_TIME_ISP and DO_DISABLE_ISP_CLAMP flags while flashing CPLD for Intruder cards.(SCGCQ01503730 port of SCGCQ01452026)

- SED Drive become UBad during secure erase on MegaRAID 9361-8i controller.(SCGCQ01503736 port of SCGCQ01473188)

- [Factory issue] MR 3108 controller BIOS stop at 3 different initialization screen.(SCGCQ01519905 port of SCGCQ01497858)

- MR_6.14 PACK 23 - On performing a cable pull/push operation during drive is in failed state, result to MonTask.(SCGCQ01532358 port of SCGCQ01529830)

- OCR is disabled by default is RC build, even NVDATA if it is enabled..(SCGCQ01540279 port of SCGCQ01503204)

- MR7.1/7.3 Termlog/UARTlog - messages sometimes missed in Termlog.(SCGCQ01540361 port of SCGCQ01498188)

-.(SCGCQ01569257 port of SCGCQ01097035)

- If an INVALID applicationMsgTag id received, then failed the command with MFI_OOB_STATUS_INVALID_CMD using command id MAX_OOB_COMMANDS..(SCGCQ01575976 port of SCGCQ01337332)

- Sanitize Support.(SCGCQ01577752 port of SCGCQ01526323)

- SATA PassTrough commands with check condition taking long time to complete..(SCGCQ01582512 port of SCGCQ01561887)

- VMware Passthrough Adapter does not sync time on VM power on.(SCGCQ01595865 port of SCGCQ01592800)

- Jbod become Ugood sometimes after reboot.(SCGCQ01616609 port of SCGCQ01508978)

- Colusa SAS expander reset results in unpredictable performance.(SCGCQ01618030 port of SCGCQ01455811)

- 'CacheVault Flash Size' is showing as 3.0 GB after upgrading FW when it should show 4.0 GB.(SCGCQ01640816 port of SCGCQ01615779)

- Drives are reverted back to JBOD after perfoming instant secure erase.(SCGCQ01683366 port of SCGCQ01615777)

- MR7.1/7.3 Termlog/UARTlog - messages sometimes missed in Termlog.(SCGCQ01714377 port of SCGCQ01498188)

- In HII whether entering the correct pass phrase or the wrong pass phrase a secured SED becomes unsecured.(SCGCQ01715297 port of SCGCQ01301947)

- B200 M5 / Carmel (3108 iMR) - VSAN failure during controller reset test.(SCGCQ01760837 port of SCGCQ01397566)

- MR 6.14 Beta: MonTask: line 245 in file ../../raid/1078int.c while running reboot test with background operations.(SCGCQ01339329 port of SCGCQ01332706)

- MR : Cache data Lost when Term Log is set to "on" and grown bad blocks are there in the controller.(SCGCQ01403930 port of SCGCQ01394288)

- Interrupting Offload will Lead to Next offload cycle to fail.(SCGCQ01403958 port of SCGCQ01399701)

- SSD SATA JBOD discovered as 0.0MB after re-loading the same driver..(SCGCQ01447007 port of SCGCQ01446965)

- MCTP : Porting of firmware download fixes from Ventura.(SCGCQ01447173 port of SCGCQ01439651)

- Controller crash observed while running OLTP workload (4K and 16K 16QD).(SCGCQ01447780 port of SCGCQ01438216)

- PL considers Timer Handle=0 and invalid, MR FW did not..(SCGCQ01467708 port of SCGCQ01399026)

- [Factory issue] MR 3108 controller BIOS stop at 3 different initialization screen.(SCGCQ01519906 port of SCGCQ01497858)

- Extend iMR change of trap related data should be in same module as trap ISR..(SCGCQ01521684 port of SCGCQ01514867)

- Event Log Corruption..(SCGCQ01532399 port of SCGCQ01451417)

- Rebuild Rate %100 takes much longer time than %30 while running IO. It should take much shorter time..(SCGCQ01540424 port of SCGCQ01336908)

- Controller crash observed while running OLTP workload.(SCGCQ01565253 port of SCGCQ01447773)

- OEM iMR 8i controller fails to complete an OCR.(SCGCQ01565318 port of SCGCQ01330611)

- Snap3 : Drives drops while running transformation operation on R1 to R5 with 900 Medium errors.(SCGCQ01598538 port of SCGCQ01581661)

- LSA shows Stop Erase option for VDs on which Erase operation is not in progress.(SCGCQ01605097 port of SCGCQ01600267)

- Memset the PinnedDataStructure when DRAM dirty signature is zero.(SCGCQ01724925 port of SCGCQ01713149)

- Firmware crashes during medium error recovery and Rebuild.(SCGCQ01348657 port of SCGCQ01304521)

- Firmware crashes during medium error recovery and Rebuild.(SCGCQ01348658 port of SCGCQ01304521)

- FW is not correctly reporting Hide VD operation as not supported.(SCGCQ01348841 port of SCGCQ01274084)

- MR7.3: 4k PD Configuration can't be imported from iMR to MR Controller. However, it can be imported from MR to iMR.(SCGCQ01402828 port of SCGCQ01395842)

- PL considers Timer Handle=0 and invalid, MR FW did not..(SCGCQ01467725 port of SCGCQ01399026)

- Extend iMR change of trap related data should be in same module as trap ISR..(SCGCQ01520788 port of SCGCQ01514867)

- MR 7.6 - "NVCache has gone bad" during POST after flashing the latest package 1226 and rebooted.(SCGCQ01683358 port of SCGCQ01635062)

- Controller hang with FDE Drive (Micron 510DC).(SCGCQ01328038 port of SCGCQ01304133)

- Assertion failure in ../../mros/mem.c : mb->tag==tag.(SCGCQ01539460 port of SCGCQ01515324)

- Parameter Page Reads fail during ONFI bringup..(SCGCQ01415424 port of SCGCQ01413557)

- If an INVALID applicationMsgTag id received, then failed the command with MFI_OOB_STATUS_INVALID_CMD using command id MAX_OOB_COMMANDS..(SCGCQ01512549 port of SCGCQ01337332)





Version 24.21.0-0016-1

----------------------

HII: 03.25.05.03

UEFI Driver: 0x06180202

BIOS: 6.36.00.1_4.19.08.00_0x06180202

iMR FW: 4.680.01-8257

PACKAGE=24.21.0-0016



fixes:

-- Try to flash HBA cards' firmware when there are HBA cards installed



Version 24.21.0-0016 - Moderate Impact/Low Probability of Occurrence

-------------------

HII: 03.25.05.03

UEFI Driver: 0x06180202

BIOS: 6.36.00.1_4.19.08.00_0x06180202

iMR FW: 4.680.01-8257

PACKAGE=24.21.0-0016



Defects:

-  MR 6.13: Blocked Spin down Pass thru command for configured drives.(SCGCQ01201958)

-  In RAID personality, MR_DCMD_CFG_AUTOCFG DCMD is disabled in non(SCGCQ01213915)

-  Setting all the ldtoTgtId with 0xff beyond 240 entries.(SCGCQ01215003)

- (SCGCQ01219438)

-  MR_EVT_PD_ERROR_STATS events are logged when drive is moved to REBUILD/UNCONFIGURED BAD/ONLINE/OFFLINE. Also correct DCMD(SCGCQ01223284)

-  FW crashes when FW update(OFU) is done with faluty onfi(SCGCQ01227115)

-  Coverity issues:fixed the coverity defects.(SCGCQ01230560)

-  Update the MAXTransferLength properly for Driver enabled 1MB support feature(SCGCQ01232275)

-  Assertion failure in ../../dm/mpt2/mptrec.c at line 3139, while performing cable pull/push operation.(SCGCQ01235505)

-  corrected the span index(SCGCQ01236287)

-  Coverity issue 15748 and 17765(SCGCQ01241568)

-  Drive Strength values are incorrect for last 8 phys of Red Brick Controller(SCGCQ01241680)

-  Change Slew Rate on dual rank RedBrick Boards to fix ECC Errors.(SCGCQ01242817)

-  Cache Data lost if power loss happens during descriptor preparation.(SCGCQ01253076)

-  'C0:mr_wakeup: mem 45569e20, cache line ffffffff' observed while running BGI on RAID 5 Volume with media errors.(SCGCQ01256120)

-  Assertion failure in ../../raid/2108vI2o.c at line 2398 on flashing firmware(SCGCQ01258563)

-  Dev defect to address action items identified during Ventura(SCGCQ01260609)

-  Dev defect to handle HW action items identified during Intruder(SCGCQ01261213)

-  Cache data Lost when Term Log is set to "on"(SCGCQ01261426)

-  6.13 ONFI_PORT: If power loss occurs after OCR, FW might lose tty log.(SCGCQ01262834)

-  6.13_ONFI_PORT: Program the erase and wait count values during ONFI Initialization.(SCGCQ01262883)

-  6.13 ONFI PORT :Set bit 0 in global Interrupt Register so that host will receive an interrupt.(SCGCQ01262884)

-  Flash File System Reads fail after system reset.(SCGCQ01267220)

-  FW does not remember user induced bad blocks across boots.(SCGCQ01267700)

-  MR 6.13(SCGCQ01268066)

-  Unable to access device PD (SSD)(SCGCQ01268412)

-  MR_6.13:FW flash pack (SCGCQ01273216)

-  Cache Restore fails if supercap is removed while cache offload is in Progress.(SCGCQ01274494)

-  Unable to set termlog on/off from storcli intermittently on Intruder Armstrong board.(SCGCQ01278512)

-  Storcli Failed to create single PD R0 from UGood drive which has replaced a UBAD foreign drive(SCGCQ01282181)

-  Intruder : After Termlog Toggling with power cycle, result to ERROR: Dirty disk cache data has been lost(SCGCQ01282319)

-  Modify Read Eye Training Algorithm to make it spec compliant.(SCGCQ01283719)

-  High DB and Log write(SCGCQ01285311)

-  Coverity reported an uninitialized variable(SCGCQ01285595)

-  OS hung and iMR FW reset when do delete and create VD from previous powersave PD (Spindowned)(SCGCQ01287286)

-  Reboot the system with 240 R0 Volumes and changing the mode(SCGCQ01288297)

-  PL Fault 0000601e observed while running multipath on/off script in JBOD mode.(SCGCQ01288781)

-  erase types and startSecureEraseNonSED is set accordingly(SCGCQ01289147)

-  Modify NVDATA boot message to rename 'NVDATA image' to 'firmware image'(SCGCQ01290201)

-  Cache data lost event seen for WT vds(SCGCQ01313607)

-  Kill adapater observed while running IO's on 240 Volumes(SCGCQ01313950)

-  Coverity: Fixing Coverity defect 16148(SCGCQ01316152)

-  Fixing the coverity raised issue(SCGCQ01318465)

-  Coverity issue 19341(SCGCQ01319291)

-  HW workaround implementation for SCGCQ00830272 and SCGCQ01048567(SCGCQ01323607)

-  auto config is not happening in some cases after issuing storcli /cx set autopdcache=r0(SCGCQ01323848)

-  MR 6.14 Beta: MonTask: line 245 in file ../../raid/1078int.c while running reboot test with background operations(SCGCQ01332706)

-  MR_6.14: Intruder PCI Trapping ISR incorrect logic for config trap address(SCGCQ01332947)

-  ntruder: Fix the Intruder Boot Block compilation and warning issue.(SCGCQ01334292)

-  Imr Invader FW crashes while upgrading from Pkg 24.18.0(SCGCQ01342601)

-  No amber LED when a configured disk is removed(SCGCQ01343017)

-  Controller fails to boot up when migrated from 6.13 to 6.14 FW for Specific OEM(SCGCQ01348114)

-  Value defined for the DDR turning parameter DP_IO_VREF_1_2 is wrong for invader boards(SCGCQ01350295)

-  MR_INVADER_WORKAROUND_PCIE_IGNORE_REPLY_PARITY_ERROR macro definition missing(SCGCQ01351483)

-  Intruder 4G DDR tuning value has to be changed in MR FW.(SCGCQ01368845)

-  Lenovo Sebastian Fatal Firmware error when connecting to straight without Group ID support.(SCGCQ01204592)

-  FW does not fail unsupported erase type for a PD(SCGCQ01221549)

-  Allow Cyrpto erase on non(SCGCQ01222318)

-  Fix coverity reported issue(SCGCQ01227079)

-  FW is not updating EPDs list exposed to host after drives removal event is posted which is causing dev nodes are not getting deleted on drive removal(SCGCQ01230441)

-  Diagnostics report of iMR Invader contains information about R6 and R60 is set to 0(SCGCQ01235661)

-  Enable MR_DCMD_PD_ERROR_STATS and the event MR_EVT_PD_ERROR_STATS only for direct attached drives(SCGCQ01237252)

-  DATA TLB ERROR, While connecting controller each Port to Back(SCGCQ01252111)

-  MR 6.13.1Alpha:Probable Drive/cable issue Event not printed in firmwarelogs on triggering drive/cable error when connected BP(SCGCQ01256005)

-  Handling of DCR errors in MSS core(SCGCQ01263110)

-  Controller does not boot up while performing cache offload .(SCGCQ01278480)

-  Controller cache discarded due to memory/battery problem(SCGCQ01280181)

-  Perf(SCGCQ01283507)

-  Code review: turn off the onfi when bbu is bad(SCGCQ01297565)

-  Coverity issues 19244, 19245, 19246 and 19248(SCGCQ01299214)

-  MR 6.14 Intruder(Vail): Intruder Controller hangs in primary core on reboot in Dell Power Edge T620 server.(SCGCQ01299482)

-  Fix coverity issue 19253 Structurally dead code in checkCacheOffloadStatus, raid/1078init.c(SCGCQ01300678)

-  coverity defects fixed(SCGCQ01300689)

-  To fix coverity issue 17759(SCGCQ01317039)

-  Found invalid event(SCGCQ01347858)

-  Placement of an image checkword at data area of NOR flash leads to controller crash(SCGCQ01375071)

- (SCGCQ01227044)

-  FC: 0 CS: 0 offload meta signature not valid, ffffffff observed in FW logs on a system restart.(SCGCQ01299424)

-  MR 6.14 (SCGCQ01300667)

-  Coverity issue 15356(SCGCQ01301658)

-  update the boundary values in UpdateFeatureSetValues()(SCGCQ01209605)

-  FW hang finaly leading to kill adatper with inBox driver(SCGCQ01250342)

-  MR7.1_NVMe: After foreign import of 64 R0 VDs, operating system unable to discover the VDs(SCGCQ01229929 Port Of SCGCQ01209394)

-  FW crashes when FW update(OFU) is done with faluty onfi(SCGCQ01235056 Port Of SCGCQ01227115)

-  Server (Purley): Controller (16i) (SCGCQ01235753 Port Of SCGCQ01200311)

-  In RAID personality, MR_DCMD_CFG_AUTOCFG DCMD is disabled in non(SCGCQ01237142 Port Of SCGCQ01213915)

-  Storcli failed to stop drives LED locating with a range(SCGCQ01241870 Port Of SCGCQ01051728)

-  MR7.1_NVMe: After foreign import of 64 R0 VDs, operating system unable to discover the VDs(SCGCQ01242766 Port Of SCGCQ01209394)

-  unable to encrypt disk when using no pass(SCGCQ01245596 Port Of SCGCQ01144752)

-  Offline Marked DG (RAID0) appearing in RHEL 7 install(SCGCQ01245782 Port Of SCGCQ00995384)

-  SAS2208 card reset in DataCenter due to unknown reason(SCGCQ01247264 Port Of SCGCQ01240574)

-  RDM in Use(SCGCQ01255837)

-  ONFI: To properly handle the OCR case with RESET Status Register.(SCGCQ01259337 Port Of SCGCQ00665475)

-  ONFI BBLIST:ONFI BadBlocks: COL disarmed, VDs remain in WB mode, no Administrative Messages to bad flash part.(SCGCQ01260470 Port Of SCGCQ01235856)

-  Firmware halts upon changing controller personality to JBOD mode with MCTP enabled(SCGCQ01260889 Port Of SCGCQ01252243)

-  Infinite loop in onfiSyncModeEnter(SCGCQ01260995 Port Of SCGCQ00329024)

-  FW crashes when setting fwtermlog bbu=on to a card with bad NAND flash(SCGCQ01261425 Port Of SCGCQ01129530)

-  Insertion of the boot messages and the evets for montoring the ONFI backup capacity.(SCGCQ01263212 Port Of SCGCQ00433463)

-  'C0:mr_wakeup: mem 45569e20, cache line ffffffff' observed while running BGI on RAID 5 Volume with media errors.(SCGCQ01263800 Port Of SCGCQ01256120)

-  Handling of DCR errors in MSS core(SCGCQ01263859 Port Of SCGCQ01263110)

-  Invalid date for next learn cycle is set due to invalid date from OEM server (STF: Next learn time is 1970(SCGCQ01264476 Port Of SCGCQ01152321)

-  GetAllLDAllowedOperation call in Storelib is not returning Allowed operations when some LDs are deleted(SCGCQ01265445 Port Of SCGCQ01250559)

-  FD33xD issues in VMWare(SCGCQ01266300 Port Of SCGCQ01203008)

-  In RAID personality, MR_DCMD_CFG_AUTOCFG DCMD is disabled in non(SCGCQ01274496 Port Of SCGCQ01213915)

-  MR_6.13:FW flash pack (SCGCQ01280567 Port Of SCGCQ01273216)

-  unable to encrypt disk when using no pass(SCGCQ01287082 Port Of SCGCQ01144752)

-  Controller cache discarded due to memory/battery problem(SCGCQ01288848 Port Of SCGCQ01280181)

-  RAID10 VD goes to failed state after performing RLM(SCGCQ01289123 Port Of SCGCQ01277951)

-  IN FAILED ARRAY bit is not being set when a VD is cleared(SCGCQ01289194 Port Of SCGCQ01137359)

-  Storcli Failed to create single PD R0 from UGood drive which has replaced a UBAD foreign drive(SCGCQ01290418 Port Of SCGCQ01282181)

-  RAID10 VD goes to failed state after performing RLM(SCGCQ01291340 Port Of SCGCQ01277951)

-  Controller cache discarded due to memory/battery problem(SCGCQ01291492 Port Of SCGCQ01280181)

-  Cannot stop patrol read on PD with medium errors by the stop cmd(SCGCQ01294884 Port Of SCGCQ01063103)

-  Perf(SCGCQ01297497 Port Of SCGCQ01283507)

-  Code review: turn off the onfi when bbu is bad(SCGCQ01297666 Port Of SCGCQ01297565)

-  Code review: turn off the onfi when bbu is bad(SCGCQ01299260 Port Of SCGCQ01297565)

-  Perf(SCGCQ01300759 Port Of SCGCQ01283507)

-  PL Fault 0000601e observed while running multipath on/off script in JBOD mode.(SCGCQ01304919 Port Of SCGCQ01288781)

-  Firmware:(SCGCQ01306491 Port Of SCGCQ01258853)

-  6.14 : To fix IOPATH overflow during linking(SCGCQ01311731 Port Of SCGCQ01311464)

-  Unable to access device PD (SSD)(SCGCQ01321307 Port Of SCGCQ01268412)

-  OS hung and iMR FW reset when do delete and create VD from previous powersave PD (Spindowned)(SCGCQ01326069 Port Of SCGCQ01287286)

-  HW workaround implementation for SCGCQ00830272 and SCGCQ01048567(SCGCQ01326394 Port Of SCGCQ01323607)

-  B200M4 (Carmel/ 3108 iMR): driver crashed after FW update via UCSM (UCSM bundle 2.2(8fS2)A/B to 3.1(2.163)A/B)(SCGCQ01331892 Port Of SCGCQ01271186)

-  B200M4 (Carmel/ 3108 iMR): driver crashed after FW update via UCSM (UCSM bundle 2.2(8fS2)A/B to 3.1(2.163)A/B)(SCGCQ01332726 Port Of SCGCQ01271186)

-  MR 6.14 Intruder(Vail): Intruder Controller hangs in primary core on reboot in Dell Power Edge T620 server.(SCGCQ01334334 Port Of SCGCQ01299482)

-  MR_6.14: Intruder PCI Trapping ISR incorrect logic for config trap address(SCGCQ01334365 Port Of SCGCQ01332947)

-  MR 6.14 Beta: MonTask: line 245 in file ../../raid/1078int.c while running reboot test with background operations(SCGCQ01339330 Port Of SCGCQ01332706)

-  Cache data lost event seen for WT vds(SCGCQ01349420 Port Of SCGCQ01313607)

-  Kill adapater observed while running IO's on 240 Volumes(SCGCQ01350347 Port Of SCGCQ01313950)

-  No amber LED when a configured disk is removed(SCGCQ01350771 Port Of SCGCQ01343017)

-  Firmware hits montask while reconstruction when drive is pulled out(SCGCQ01351442 Port Of SCGCQ01260340)

-  MR 6.13: Blocked Spin down Pass thru command for configured drives.(SCGCQ01351559 Port Of SCGCQ01201958)

-  IOMMU fault at address 0x80360000(SCGCQ01356192 Port Of SCGCQ01279547)

-  LSA hangs when user try to change drive security key.(SCGCQ01367331 Port Of SCGCQ01342655)

-  Invalid date for next learn cycle is set due to invalid date from OEM server (STF: Next learn time is 1970(SCGCQ01241869 Port Of SCGCQ01152321)

-  MR6.12 NVRAM Overflow (SCGCQ01248969 Port Of SCGCQ01230749)

-  FD33xD issues in VMWare(SCGCQ01261095 Port Of SCGCQ01203008)

-  FD33xD issues in VMWare(SCGCQ01263759 Port Of SCGCQ01203008)

-  Configuration lost and system crashed on having a stale configuration connected(SCGCQ01273187 Port Of SCGCQ01170701)

-  PL Fault 0000601e observed while running multipath on/off script in JBOD mode.(SCGCQ01304921 Port Of SCGCQ01288781)

-  FC: 0 CS: 0 offload meta signature not valid, ffffffff observed in FW logs on a system restart.(SCGCQ01351052 Port Of SCGCQ01299424)

-  Controller fails to boot up when migrated from 6.13 to 6.14 FW for Specific OEM(SCGCQ01351614)

-  SAS2208 card reset in DataCenter due to unknown reason(SCGCQ01311439 Port Of SCGCQ01240574)

-  Drive Strength values are incorrect for last 8 phys of Red Brick Controller(SCGCQ01247082 Port Of SCGCQ01241680)

-  Firmware hits montask while reconstruction when drive is pulled out(SCGCQ01282285 Port Of SCGCQ01260340)

-  Code review: turn off the onfi when bbu is bad(SCGCQ01299219 Port Of SCGCQ01297565)

-  Controller does not boot up while performing cache offload .(SCGCQ01288845 Port Of SCGCQ01278480)



EnhancementRequests:

-  New fault code for routine synchronous reset(SCGCQ01264142)

-  Vail FW not responding to PWR_REQ in time. Request to up the number of TURs sent before timing out drive.(SCGCQ01373161)

-  Disable OOB communication via I2C(SCGCQ01369359)

-  Integrate Intruder PL 14.00.04.00 with MR 6.14(SCGCQ01341925)

-  PL phase 13.0007.00 integration with MR 6.13(SCGCQ01334112)

-  PL integration(SCGCQ01330898)

-  Integrate PL phase 14.00.02.00 with MR 6.14(SCGCQ01307233)

-  Integrate 13.00.06.00 PL to MR 6.13(SCGCQ01304141)

-  PL integration 12.00.10.00 with MR 6.12(SCGCQ01276465)

-  Integrated PL 12.0.9.0 with MR 6.12(SCGCQ01268897)

-  Shift IOPATH code by 4 cache lines to workaround intruder performance issue.(SCGCQ01262698)

-  PR State Machine Clean up during Patrol Read/Check Consistency Conflicts(SCGCQ01260431)

-  Integrate intruder PL 13.00.04.00 (SCGCQ01237533)(SCGCQ01238286)

-  Integrate PL 13.00.04.00 to MR_FW_SAS3_6.13_4G_DDR(SCGCQ01238126)

-  Open up MR_DCMD_CFG_AUTOCFG for iMR for GET operation(SCGCQ01228949)

-  Customer requesting digitally signed FW packages on their Intruder controller(SCGCQ01215397)

-  MPI 2.5 and 2.6: Need IT FW to send new event for expander failing SMP(SCGCQ01180886)

-  MPI 2.5: Add two new reason codes to Active Cable Exception Event Data(SCGCQ01208954)

-  MPI 2.5 : Add support for reporting Chassis Slot to Enclosure Page 0(SCGCQ01213028)

-  MPI 2.6: Add new firmware download type (CBB BACKUP)(SCGCQ01258005)

-  MPI 2.6: Device side PCIe SRNS flag(SCGCQ01276256)

-  MPI 2.6: Add new firmware download type (CPLD IMAGE)(SCGCQ01305760)

-  IN FAILED ARRAY bit is not being set when a VD is cleared(SCGCQ01137359)

-  Integrate Intruder PL 13.00.05.00 (RO SCGCQ01263844)(SCGCQ01265401)

-  Add additional sense data to firmware tracker list(SCGCQ01254954)

- Method for determining bad ONFI flash via Storcli & SNMP trap upon NAND flash failure for Aspen and Vail (Invader and Intrude(SCGCQ01219862)

-  MPI2.6: Mfg7 support for arbitrary starting slot number(SCGCQ01213267)

-  MPI 2.6: Add Aero PCI Device IDs(SCGCQ01373008)

-  Isolating faulty cable issue from bad drive issue(SCGCQ01215270)

-  PL integration(SCGCQ01268896)



-



Version 24.16.0-0101 - High Impact/High Probability of Occurrence

-------------------

FW Package: 24.16.0-0101

HII: E3.21.14.03

UEFI Driver: 0x06150501

BIOS: 6.32.02.1

MR FW: 4.660.00-8214

iMR FW: 4.660.01-8215



Fixes:

- Fixed an issue where some log context in UART was missing in TTY dump. (SCGCQ01230749)

- Fixed an issuer kill adapter command was executed in line 1272 in file ../../raid/1078dma.c after pulling enclosure cable with IOs running on 240VD, JBOD SCGCQ00857533

- Fixed an issue where cache data could be lost when term log is set to "on." (SCGCQ01267851 Port of - SCGCQ01261426)

- Fixed an issue where CRC mismatch and invalid log event found while querying for Controller properties and learn cycle in parallel. (SCGCQ01219985 Port of Defect - SCGCQ00919945)

- Fixed an issue where rebuild error on PD with iMR 9341-8i SAS3008. (SCGCQ01220128 Port of - SCGCQ00915417)

- Fixed an issue where drives were not marked as Foreign upon OCR when controller already has max configured PD's (SCGCQ01219897 Port of Defect - SCGCQ01163849)

- Fixed an issue where drives with configuration were getting converted to JBOD if system already has maximum configurable drives. (SCGCQ01149764 Port of Defect SCGCQ01136693)

- Fixed an issue where StorCLI failed to create single PD R0 from unconfigured good drive which has replaced a UBAD foreign drive. (SCGCQ01290418 Port of Defect SCGCQ01282181)

- Fixed an issue where RAID personality, MR_DCMD_CFG_AUTOCFG DCMD is disabled in non-240 VD environment. (SCGCQ01267801 Port of Defect SCGCQ01213915)

- Fixed an issue where StorCLI was not showing virtual drives after personality switch from SDS to RAID. (SCGCQ01238639 Port of Defect - SCGCQ01081305)

- Fixed an issue where the controller became unresponsive after hitting OCM error. (SCGCQ01219901 Port of Defect - SCGCQ00924986)

- Fixed an issue where the firmware halts upon changing controller personality to JBOD mode with MCTP enabled. (SCGCQ01260889 Port of Defect SCGCQ01252243)

- Fixed an issue where firmware logs printed in UART were missing in tty dump. (SCGCQ01230749)

- Fixed an issue where OS hung and iMR FW reset when delete and create VD commands using previous powersave physical drive spindowned. (SCGCQ01287286)

- Fixed an issue where StorCLI was not showing virtual drives after personality switch from SDS to RAID. (SCGCQ01093890 PORT OF Defect - SCGCQ01081305)

- Fixed PCI device page enclosure level/connector name to match SAS device page. (SCGCQ01071374)

- Fixed an issue where mem 45569e20, cache line ffffffff' observed while running BGI on RAID 5 Volume with media errors. (SCGCQ01266169, SCGCQ01256120)

- Fixed an issue where local storage admin config FSM failure on setting TR on 64 VDs, when there were a large number of events transferred over OOB, one event could be missing in some cases. (SCGCQ01243832, SCGCQ01243833, SCGCQ01243834, SCGCQ01243836 PORT OF Defect SCGCQ01128180)

- Fixed an issue where some logs printed in UART were missing in TTY dump. (SCGCQ01242651, SCGCQ01242650, SCGCQ01242649 PORT OF Defect SCGCQ01230749)

- Fixed an issue where firmware breaks MonTask: line 245 in file ../../raid/1078int.c with IOs on max VD configured and BGOps. (SCGCQ00895481, SCGCQ00895482, SCGCQ00895474 Defect SCGCQ00890133)

- Fixed an issue where as part of R1 undergoing RLM to a R0 volume, the medium errors that were injected, were discovered but not reported as corrected. (SCGCQ00893669 PORT OF Defect -SCGCQ00846621)

- Fixed an issue where iEEESGL flag was not getting set for IO request in SES DCDB handler. (SCGCQ01186523, SCGCQ01238262, SCGCQ01242590, SCGCQ01242592, SCGCQ01242597 PORT OF Defect - SCGCQ01157072)



Enhancements:

- Added defines for SAS 4 and PCIe 4 speeds. (SCGCQ00948955)

- Modified PCIe Link config pages to include a link field. (SCGCQ00954619)

- MR API bit to indicate if the profile is NVMe Only profile. (SCGCQ01213092)

- Fixed an issue where the foreign configuration that has been imported went off-line within few seconds, as all the drives are getting transitioned to Unconfigured-Good with PD_InsertionPostProcess() getting kicked-in. (SCGCQ01198744 Port of Defect SCGCQ00800589)

- Added two new MFI_STAT values to better describe RAID 10 volume creation errors: MFI_STAT_INVALID_DRIVE_COUNT and MFI_STAT_UNEVEN_SPAN_NOT_SUPPORTED. (SCGCQ01222698)

- Isolated faulty cable issue from bad drive issue. (SCGCQ01203751)

- Removed all defines and structure fields related to SOP support. (SCGCQ00925839)

- Removed all defines and structure fields related to AHCI support. (SCGCQ00948258)

- Added EclosureLevel and ConnectorName fields to PCIe Device Page 0 with the same meaning as SAS Device Page 0. (SCGCQ00949638)

- Added IOCException bit 10 to indicate that backend PCIe device support has been disabled due to an initialization failure and

added InitStatus field to PCIe IO Unit Page 1 t provide more detail.(SCGCQ01009104)

- Added flag to force completion queue entry return for NVMe Encapsulated request. (SCGCQ01013930)

- Added Negotiated Link Rate and Negotiated Port Width to PCIe Device page 0. (SCGCQ01017027)

- Added bit to LinkFlag field of PCIe IO Unit Page 1 PhyData to specify SRIS mode. (SCGCQ01018687)

- Updated header file to include SATADeviceWait time to IO Unit page 11. (SCGCQ01092340)

- Added new definitions for the ImageType field of FwDownload and FwUpload messages. Also, added new flash region definitions for the Flash Layout Extended Image Data. (SCGCQ01136127)

- Added reason codes MPI26_EVENT_ACTIVE_CABLE_PRESENT and MPI26_EVENT_ACTIVE_CABLE_DEGRADED to Active Cable Exception Event Data. (SCGCQ01146583)

- Defined interface to support firmware assisted VD/JBOD properties: max IO size, device queue depth. (SCGCQ01188711)

- Fixed an issue where L2/L3 Cache error was detected on the RAID controller during boot (24 hours after shutdown hang. (SCGCQ01219839 Enhancement Request SCGCQ01018958)





Version 24.16.0-0092 - High Impact/High Probability of Occurrence

-------------------

FW PACKAGE: 24.16.0-0092



MR FW: 4.660.00-8156



iMR FW: 4.660.01-8157



BIOS: 6.32.02.1



UEFI: 0x06150501



HII: 03.21.14.01







Fixes:



- Fixed an issue where MR_RAID_CTX_G35 reserved field has one bit too many, resulting in 17 bits in a U16 - (SCGCQ00886417)



- Fixed an issue where controller may hang when an OCR is triggered on a RAID5 LD with no supercap - (SCGCQ00926628)



- Fixed an issue where PDs are getting swapped and rebuild starts on incorrect PD after an enclosure power cycle - (SCGCQ00927155)



- Worked around an issue where a false ReplyParityError may occur - (SCGCQ00927504)



- Fixed an issue where numSGEExt field was removed from MPI25_SCSI_VENDOR_REGION, affecting support for 1MB IO - (SCGCQ00927738)



- Fixed an issue where CacheVault size reports as 0KB for some controllers - (SCGCQ00929077)



- Fixed an issue where controller firmware may halt with error "MonTask: line 1281 in file ../../raid/1078dma.c" - (SCGCQ00931397)



- Fixed an issue where ONFI hardware was disarmed on OCR - (SCGCQ00933096)



- Fixed an issue where MSM does not show "hide" option after "unhide" on RAID0 - (SCGCQ00933123)

-

Fixed an issue where rebuild doesn't complete with cmd_block_flush on RAID6 with SAS SSD - (SCGCQ00933841)

- Fixed an issue where storcli is unable to create logical drives via auto-configuration, such as with command "storcli /cx set autopdcache=r0" - (SCGCQ00935727)



- Fixed an issue where a new field in RAID_MAP_EXT causes backward compatibility issues - (SCGCQ00940224)



- Fixed an issue where online firmware update may fail in Windows due to language attribute - (SCGCQ00941886)



- Fixed an issue where performance was lower than expected due to DataCacheInvalidateSnoop was not being used for sense buffer- (SCGCQ00944526)



- Fixed an issue where makefile is missing changes required for enabling PLDEBUG - (SCGCQ00945858)



- Fixed an issue where performance was lower than expected due to stale calls to processdevicewaitQ - (SCGCQ00947221)



- Fixed an issue where code events had repetitive IDs - (SCGCQ00948535)



- Fixed an issue where a value assigned to a variable is never used - (SCGCQ00948781)



- Fixed an issue where error "MonTask: line 245 ..1078int.c" may occur on reboot with foreign import - (SCGCQ00948931)



- Fixed an issue where two enclosure IDs are displayed in MSM Physical tab when connected via multipath to some enclosures - (SCGCQ00950425)



- Fixed an issue where firmware fails to copyback from hotspares - (SCGCQ00952836)



- Fixed an issue where inquiry string is not updated during drive firmware upgrade through offline mode update - (SCGCQ00953396)



- Fixed an issue where code analysis tool reported issues - (SCGCQ00954107)



- Fixed an issue where firmware may hang on enclosure power cycle - (SCGCQ00976597)



- Fixed an issue where error "MonTask: line 1281 in file ../../raid/1078dma.c" may occur on enclosure power cycle - (SCGCQ00976780)



- Fixed an issue where CacheCade firmware may not get enough time to flush windows when no free window is available - (SCGCQ00976904)



- Fixed an issue where ring buffer print was occurring even when PLDEBUG is not enabled - (SCGCQ00979831)



- Fixed an issue where controller firmware may halt at "MonTask:" when running IO to CacheCade Virtual Drives - (SCGCQ00980216)



- Fixed an issue where controller firmware may halt at "MonTask:" during enclosure power cycle - (SCGCQ00981645)



- Fixed an issue where DATATLB error may occur on hotplug of some enclosures - (SCGCQ00983232)



- Fixed an issue where controller firmware may halt when running SAS adapter diagnostic command from storcli - (SCGCQ00987879)



- Fixed an issue with some unused values in code - (SCGCQ00987940)



- Fixed some issues discovered in code review - (SCGCQ00987966)



- Fixed an issue where error "MonTask: line 909 in file ../../raid/raidscsi.c" may occur during heavy IO and power cycles - (SCGCQ00988674)



- Fixed an issue where data length may not be set appropriately based on CBD size - (SCGCQ00988813)



- Fixed an issue where storclio may fail to read some VPD information from SBR - (SCGCQ01065177, Port of SCGCQ00990939)



- Fixed an issue where OCR is not enabled by default in release candidate builds - (SCGCQ00991489)



- Fixed an issue where a performance issue may occur - 9% drops for 6Gig 512BSATASSDs with 24PD R5 in RW 32KB IOSz for 256QD - (SCGCQ00991492)



- Fixed an issue where kill adapter may occur when restoring multipath with SATA drives - (SCGCQ00992114)



- Fixed an issue where an uninitialized byte transfer variable may cause unaligned DMA lengths - (SCGCQ00994097)



- Fixed an issue where controller firmware may fault when importing a configuration with only Global Hotspare PDs on an iMR controller - (SCGCQ00994846)



- Fixed an issue where controller firmware may hang on abort of Background Initialization of a VD expansion - (SCGCQ00996532)



- Fixed an issue where pinned cache data structure members may need to be reinitialized between firmwares with different cache header versions - (SCGCQ00996607)



- Fixed an issue where enclosure discovery may fail when enclosure with spun-down drives is disconnected and reconnected - (SCGCQ00996692)



- Fixed an issue where error "IO error 9 in CheckFwIoDescList" may occur on cable pull/push - (SCGCQ00997291)



- Fixed an issue where CPU affinity define values may not be updated properly to align with CPU affinity structure changes - (SCGCQ01000077)



- Fixed an issue where DCMD processing may return before setting the JBOD as a boot device in NVRAM - (SCGCQ01000230)



- Fixed an issue where OCR may not be blocked after firmware downgrade - (SCGCQ01000359)



- Fixed an issue where SAS SSD RAID5 performance may be lower than expected - (SCGCQ01001861)



- Fixed an issue where CtrlInfo.adapterOperations3.supportProfileChange is missing in API- (SCGCQ01001936, SCGCQ01014835)



- Fixed an issue where number of LDs may not be checked before calling RM_SataBBMUpdateDivertNodesFromSBBMTable - (SCGCQ01002055)



- Fixed an issue where CacheCade Virtual Drive deletion path refers to the wrong Virtual Drive - (SCGCQ01002268)



- Fixed an issue where controller firmware may hang after connecting some enclosures with SATA drives - (SCGCQ01002798)



- Fixed an issue where error "MonTask: line 1281 in file ../../raid/1078dma.c" may occur when cables are removed/reinserted in a multipath environment with IO - (SCGCQ01002921)



- Fixed an issue where some changes were not ported - (SCGCQ01003552)



- Fixed an issue where controller may experience assertion failure when drives are being removed/reinserted with background IO - (SCGCQ01004144)



- Fixed an issue where DRAM signature may receive a stale copy on ONFI restore - (SCGCQ01004279)



- Fixed an issue where firmware switches descriptors and prepares for an offload even when SuperCap is absent - (SCGCQ01004385)



- Fixed an issue where performance may be lower than expected for Sequential Reads in RAID mode - (SCGCQ01012499)



- Fixed an issue where error "MonTask@line 179 in file ../../dm/src/chipmgr.c" may occur on repeated system reboots - (SCGCQ01015019)



- Fixed an issue where CacheCade parameters are populated in controller info even when 240VD feature is enabled - (SCGCQ01015026)



- Fixed an issue where SAS Port PAge 0 and SAS IO UNIT Page 1 did not function correctly resulting in MonTask error - (SCGCQ01015470)



- Fixed an issue where controller firmware may throw invalid arguments when setting debug variable for some commands - (SCGCQ01015761)



- Fixed an issue where controller firmware may exhibit MonTask error when setting up debug variables with levels from storcli - (SCGCQ01016534)



- Fixed an issue where controller firmware perform cache offload and restore operation even on a clean shutdown - (SCGCQ01018477)



- Fixed an issue where SDS personality was not supporting 1MB IO - (SCGCQ01020626)



- Fixed an issue where SDS personality did not have SAS drive queue depth of 128- (SCGCQ01020631)



- Fixed an issue where divert locks were not being used for Write-Back volumes on Sequential Read - (SCGCQ01020634)



- Fixed an issue where error "Core 0 in 245 in file ../../raid/1078int.c" may occur on cable remove/reinsert on JBODs with IO - (SCGCQ01020979)



- Fixed an issue where firmware may incorrectly disable the cache offload engine after an OCR when pinned cache is present and a clean shutdown occurs - (SCGCQ01021488)



- Fixed an issue where a DATATLB error may occur after flashing controller firmware and rebooting - (SCGCQ01023585)



- Fixed an issue where controller firmware may halt when controller firmware update occurs immediately after a drive microcode update - (SCGCQ01024661)



- Fixed an issue where error "Line 245 in ../../raid/1078int.c" may occur when rebooting server after inserting Virtual Drives when pinned cache is present - (SCGCQ01028404)



- Fixed an issue where write policy may not be retained after unblocking the SDVs and making the CacheCade Virtual Drive / SVD Optimal - (SCGCQ01028464)



- Fixed an issue where a MonTask error may occur when an SVD is associated with CacheCade and one of the SVD member drives is removed - (SCGCQ01030089)



- Fixed an issue where unsupported message types in MCTP path were not handled correctly - (SCGCQ01030166)



- Fixed an issue where an L2 Cache Error may occur when performing cable remove/reinsert on an enclosure - (SCGCQ01030408)



- Fixed an issue where TweakIO was not supported on iMR - (SCGCQ01032429)



- Fixed an issue where a cache restore operation may take more than 90 seconds when power cycles occur with pinned cache present - (SCGCQ01033348)



- Fixed an issue where error "line 1279 in file ../../raid/1078dma.c" with PL fault - (SCGCQ01033740)



- Fixed an issue where a Pinned Cache critical message may occur when booting from S3 sleep mode - (SCGCQ01033930)



- Fixed an issue where error "line 4839 in file ../../raid/cache.c" may occur with cache offload - (SCGCQ01034706)



- Fixed an issue where more than one special task could run on a CacheCade Virtual Drive - (SCGCQ01034955)



- Fixed an issue where recheck for presence of pinned cache may not occur after command block grant - (SCGCQ01034977)



- Fixed a timing issue by removing previous change SCGCQ01023287 - (SCGCQ01035343)



- Fixed an issue where Virtual Drive creation may fail in RAID mode on personality change - (SCGCQ01036091)



- Fixed an issue where controller firmware may fault with error "line 1279 in file 1078dma.c" - (SCGCQ01036154)



- Fixed an issue where a kill adapter may be issued when a TUR is sent to a device after IO timeouts - (SCGCQ01037095)



- Fixed an issue where controller firmware may fault when multipath is broken during IO - (SCGCQ01037747)



- Fixed an issue where EPDs may not be created after system reboot - (SCGCQ01038702)



- Fixed an issue where IO to JBOD may fail on some drives when a path is broken in a multipath scenario - (SCGCQ01038719)



- Fixed an issue where controller firmware may hang during an OCR when a reconstruction from RAID0 to RAID1 is in progress - (SCGCQ01039732)



- Fixed an issue where a read from an uninitialized pointer may occur - (SCGCQ01040543)



- Fixed some issues discovered as part of code review - (SCGCQ01040575)



- Fixed an issue where controller firmware may fault with error "MonTask: line 605 in file ../../raid/routines.c" when controller firmware update and drive firmware updates are performed simultaneously - (SCGCQ01040587)



- Fixed an issue where error "Assertion failure in ../../raid/cmd.c line 3089" may occur if host task management completes before pending commands are aborted or completed - (SCGCQ01040595)



- Fixed an issue where pinned cache may result in an assertion failure - (SCGCQ01041463)



- Fixed an issue where some error cases may not be handled properly - (SCGCQ01041729)



- Fixed an issue where abort task management function failes to abort firmware commands split into multiple internal commands - (SCGCQ01042128)



- Fixed an issue where a kill adapter may occur when disableErrorRecovery=1 and a DCMD is sent - (SCGCQ01042237)



- Fixed a compilation issue - (SCGCQ01042829)



- Fixed an issue where HII menu may not allow mode change - (SCGCQ01046130)



- Fixed issues discovered as part of code review - (SCGCQ01047319)



- Fixed an issue where error "MonTask: line 1280 in file ../../raid/1078dma.c" may occur when toggling SSD caching on/off during IO - (SCGCQ01048675)



- Fixed an issue where random performance may drop from 1.1M to 0.8M with SAS SSD - (SCGCQ01049230)



- Fixed an issue where supportBit functionality was not present for MR_CFG_USER_CONFIGURABLE - (SCGCQ01049236)



- Fixed an issue where cache bypass may not work with 4k drives and a random workload - (SCGCQ01049253)



- Fixed an issue where PLDEBUG was not disabled - (SCGCQ01049262)



- Fixed an issue where code may try to access 255th Logical Drive when only 240 are supported - (SCGCQ01049335)



- Fixed an issue where makeSystem bit in MR_PD_ALLOWED_OPS was not disabled - (SCGCQ01050314)



- Fixed an issue where alternate path cleanup on device removal may not occur correctly - (SCGCQ01052105)



- Fixed an issue where JBOD behavior may automatically change to EPD - (SCGCQ01053601)



- Fixed an issue where EPD may be deleted after a controller OCR - (SCGCQ01054436)



- Fixed an issue where CacheCade Virtual Drive performance was lower than expected - (SCGCQ01055907)



- Fixed an issue where MonTask error may occur on firmware upgrade - (SCGCQ01056349)



- Fixed an issue where error "DATA TLB ERROR(SRR0/1,ESR) exception: sf=c0137f50" may occur under IO to VDs and EPDs in EPD mode - (SCGCQ01057471)



- Fixed an issue where error handling may not occur for direct attached devices during targetID allocation - (SCGCQ01058026)



- Fixed an issue where SAS Address for paths may not be shown in firmware events when true multipath is enabled - (SCGCQ01058118)



- Fixed an issue where firmware flash with OCR may result in "Host memory not available" - (SCGCQ01059104)



- Fixed an issue where OCR was allowed in Safe Mode - (SCGCQ01059795)



- Fixed an issue where MonTask error may occur when IO is underway during SVD CacheCade association process - (SCGCQ01060661)



- Fixed an issue where MonTask DATATLB error may occur on IO timeout with immediate IO - (SCGCQ01061150)



- Fixed an issue where Virtual Drives may be displayed as 0.000TB after doing a factory reset - (SCGCQ01061594)



- Fixed an issue where rebuild may not recover properly on medium errors - (SCGCQ01063920)



- Fixed an issue where an EPD may become Foreign on EPD removal/reinsertion - (SCGCQ01064307)



- Fixed an issue where an incorrect message may be displayed in EPD mode when no Virtual Drives are present - (SCGCQ01064584)



- Fixed an issue where firmware may report failure when initiating an Instant Secure Erase against Foreign drives that are Locked - (SCGCQ01064725)



- Fixed an issue where enclosure topology may change after deleting EPD/JBOD - (SCGCQ01066150)



- Fixed an issue where drive slot information may not be shown properly, or always shows as 0-3:1:0 - (SCGCQ01066199)



- Fixed an issue where firmware may allow a reconstruction from RAID0 to RAID6 on iMR - (SCGCQ01066211)



- Fixed an issue where enclosure topology information may not be cleared from NVRAM - (SCGCQ01069328)



- Fixed an issue where firmware may throw an event with "Pass-through EPD" instead of "JBOD" - (SCGCQ01070146)



- Fixed an issue where error "DATA TLB ERROR(SRR0/1,ESR) exception: sf=c0137f50" may occur - (SCGCQ01070174)



- Fixed an issue where controller firmware may fail to discover a directly-attached SSD - (SCGCQ01073684)



- Fixed an issue where DDF may be read when the drive is locked by a third-party application - (SCGCQ01074264)



- Fixed an issue where IO stalls may be seen when Foreign Drives are imported while Pinned Cache is present - (SCGCQ01074390)



- Fixed an issue where controller firmware may fault with no cache metadata while running heavy IO - (SCGCQ01075043)



- Fixed an issue where debug routines were not as robust as possible - (SCGCQ01075835)



- Fixed an issue where a DATATLB error may occur on import of a Foreign Configuration - (SCGCQ01077584)



- Fixed an issue where JBOD may show up as a RAID0 in 240VD configuration - (SCGCQ01077659)



- Fixed compiling issues for iMR - (SCGCQ01077981)



- Fixed an issue where controller firmware may issue kill adapter when power cycling a secondary enclosure repeatedly - (SCGCQ01078220)



- Fixed an issue where error "FW Crash at line 2001 in file /bbu/onfi.c" may occur when running IO on Virtual Drives when a CacheCade Virtual Drive is present - (SCGCQ01080073)



- Fixed an issue where controller cannot set personality behavior after flashing firmware - (SCGCQ01080529)



- Fixed an issue where storcli not showing Virtual Drive after controller personality switch - (SCGCQ01081305)



- Fixed an issue where controller was not properly determining if a drive needs to be locked - (SCGCQ01083145)



- Fixed an issue where activity LED is always on even when no drives are present - (SCGCQ01083581)



- Fixed an issue where L2 Cache Error occurs when IO is run with cable remove/reinsert - (SCGCQ01087818)



- Fixed an issue where error "MonTask: line 3169 in file mptrec.c" may occur on cable remove/reinsert- (SCGCQ01089223)



- Fixed an issue where Phase 12 physical layer was not - Integrated - (SCGCQ01089372)



- Fixed an issue where EPDs auto configuration fails during OCR on 240VD setup when Pinned Cache is present - (SCGCQ01096547)



- Fixed an issue where a Physical Layer fault may occur when running IO on SVD when a CacheCade Virtual Drive is present a target resets are issued to Secure JBOD - (SCGCQ01117179)



- Fixed an issue where controller firmware did not have enough descriptors for 2-die chips - (SCGCQ01118693)



- Fixed an issue where an ECC error spike may be observed during a Cache Restore operation when read eye training has failed - (SCGCQ01124194)



- Fixed an issue where compilation broke due to increase in iopath size by 1120 bytes - (SCGCQ01126393)



- Fixed an issue where a DATATLB error may be observed when IO, target resets, OCR and a rebuild occur concurrently - (SCGCQ01130939)



- Fixed an issue where controller firmware event logs show EPD creation when booted in JBOD mode - (SCGCQ01130979)



- Fixed an issue where a kill adapter may occur when moving a PI-enabled RAID5 Virtual Drive to degraded state - (SCGCQ01131151)



- Fixed an issue where retry mechanism for Cache Offload may run when ECC errors is less than 40 - (SCGCQ01131808)



- Fixed an issue where Write Back volumes may not be imported when changing controller personality - (SCGCQ01135382)



- Fixed an issue where controller firmware may disable Fast Path for SED/FDE JBOD - (SCGCQ01135893)



- Fixed an issue where SES topology information may not be updated as expected - (SCGCQ01137834)



- Fixed an issue where UEFI driver may not load - (SCGCQ01138961)



- Fixed an issue where MR_DCMD_CFG_AUTOCFG DCMD is not allowed when ignore64ldRestriction is not set - (SCGCQ01139912)



- Fixed an issue where some messages in VDM queue may not be initialized with proper values - (SCGCQ01149312)



- Fixed an issue where a MonTask error may occur when Cache Offload does not complete successfully - (SCGCQ01149971)



- Fixed an issue where debug code added for testing was not removed - (SCGCQ01152456)



- Fixed a performance issue where normal IOs were being impacted by inline DMA for double-buffered IO - (SCGCQ01154297)



- Fixed an issue where controller firmware may use a bad block for Cache Offload operation - (SCGCQ01159064)



- Fixed an issue where coalescing was enabled for Write-Through EPDs in JBOD personality - (SCGCQ01161309)



- Fixed an issue where performance may drop 15% SR IO Sizes-4K QD(256),12G SAS HDD,x16 - (SCGCQ01166024)



- Fixed an issue where performance may drop 12% to 22% SW IO Sizes-16K QD(2) ,12GSAS HDD,x8,x16x,24,x40PD - (SCGCQ01166028)



- Fixed an issue where a Fatal Firmware error may occur during power cycle - (SCGCQ01167011)



- Fixed an issue where performance may drop 20% SR, 8K-IO Size,QD(256) RAID-10 6G SATA-HDD x16DC - (SCGCQ01171907)



- Fixed an issue where very high write latency may occur - (SCGCQ01176422)



- Fixed an issue where activity LED may be lit and never turn off - (SCGCQ01191412)



- Fixed an issue where performance may drop 6% to 15% Perf drop in all IO size with Higher QD in 12G SAS HDD [x16EC,x24EC,x40EC] - (SCGCQ01193231)



- Fixed an issue where error "MonTask: line 4789 in file ../../raid/cache.c" may occur when importing a RAID0 CacheCade Virtual Drive - (SCGCQ00942270)



- Fixed some code review defects - (SCGCQ00980759)



- Fixed an issue where writes may fail on JBODs after an OCR - (SCGCQ00981721)



- Fixed an issue where host DDF memory is not reserved after OCR followed by firmware flash - (SCGCQ00992541)



- Fixed an issue where a kill adapter may occur on heavy IO with background operations on CacheCade Virtual Drives and SVD - (SCGCQ00995919)



- Fixed an issue where controller firmware may asser when JBOD is removed during an OCR - (SCGCQ00996138)



- Fixed an issue where a suspended rebuild does not start on a RAID1 CacheCade physical drive even after SSCD flush has completed - (SCGCQ00999971)



- Fixed an issue where error "Montask in line 164 in file ../../raid/2108vDma.c" may occur when scanning for Virtual Drives on directly-attached PI drives - (SCGCQ01000488)



- Fixed an issue where storcli command "storcli /cx show preservedcache" will report success on an iMR controller - (SCGCQ01002022)



- Fixed an issue where kill adapter may occur when running 64K IOs on Virtual Drives and JBODs with a mix of 6Gbps and 12Gbps drives - (SCGCQ01023587)



- Fixed an issue where a drive microcode update start event is not logged when offline method used - (SCGCQ01024062)



- Fixed an issue where insertion/removal of a secondary SEP or expander device would affect firmware internally maintained enumerated topology order - (SCGCQ01024970)



- Fixed an issue where controller firmware may hang on power cycle of an enclosure - (SCGCQ01043365, Port of SCGCQ01025024)



- Fixed an issue where all EPD errors may not return MFI_STAT_SCSI_DONE_WITH_ERROR - (SCGCQ01025697)



- Fixed an issue where EPDs may be created in DDF_ForeignScan() - (SCGCQ01028289)



- Fixed a code merge issue - (SCGCQ01029522)



- Fixed an issue where a DATATLB error "restore_cache_line_buffer +1b0" may occur on enclosure removal while updating drive firmware - (SCGCQ01029529)



- Fixed an issue where Unavailable flag may not be cleared for VDs even after spin-up recovery - (SCGCQ01030591)



- Fixed an issue where storcli drive inquiry command may fail when true multipath is enabled - (SCGCQ01033041)



- Fixed an issue where a DATATLB "DM_PL_ProcessCompletion+334" error may occur while running IO - (SCGCQ01033082)



- Fixed an issue where controller firmware did not allocate targetID based on the port and slot the JBOD is direct attached to - (SCGCQ01033957)



- Fixed some code review issues - (SCGCQ01036929)



- Fixed an issue where backend Physical Layer frames for Core0 were not 4k - (SCGCQ01037133)



- Fixed an issue where kill adapter may occur when power cycling enclosures - (SCGCQ01037718)



- Fixed an issue where enclosure enumeration order should remain consistent across OCRs and reboots - (SCGCQ01038595)



- Fixed an issue where incorrect values may occur in CacheCade Virtual Drive counters - (SCGCQ01039080)



- Fixed an issue where unsupported message type handling does not occur according to MCTP spec - (SCGCQ01039363)



- Fixed an issue where controller firmware allows switch from EPD to EPD-passthrough even with more than 128 devices - (SCGCQ01039421)



- Fixed an issue where a diagnostics test failure moves a Secure JBOD drive to Foreign Unconfigured Good - (SCGCQ01039512)



- Fixed an issue where controller firmware may crash during hibernation - (SCGCQ01042005)



- Fixed an issue where ldlimit may not be able to reset to default when Virtual Drives exist with targetID greater than 64 - (SCGCQ01042131)



- Fixed an issue where storcli may show an incorrect number of Physical Drives - (SCGCQ01042249)



- Fixed an issue where controller may show port number as "null" or the same even with different types of port connectivity - (SCGCQ01045937)



- Fixed an issue where an out of bound read and uninitialized scalar variable may occur - (SCGCQ01046119)



- Fixed an issue where controller cannot create the 240th Virtual Drive even though 240 are supported - (SCGCQ01046644)



- Fixed some code review issues - (SCGCQ01047222)



- Fixed an issue where "OOB_slaveOnly" variable may not be set to 0 for PCIe path - (SCGCQ01049035)



- Fixed an issue where debug prints were not removed in Host Task Management and EPD creation path - (SCGCQ01049304)



- Fixed some code review issues - (SCGCQ01050889)



- Fixed an issue where flags indicating SSC flush status may not be cleared even after completion of the SSC flush - (SCGCQ01053360)



- Fixed an issue where iMR controller restart may fail after firmware flash even though OCR is enabled - (SCGCQ01053769)



- Fixed some code review issues - (SCGCQ01054547)



- Fixed an issue where error "Exception in core 0" may occur when running target resets with IO - (SCGCQ01058187)



- Fixed an issue where controller firmware hangs after destaging preserved cache - (SCGCQ01059184)



- Fixed an issue where a kill adapter may occur when aborting a Full Initialization on 240 Virtual Drives - (SCGCQ01059439)



- Fixed an issue where a target reset may be issued on an incorrect device handle in true multipath Write-Back configuration - (SCGCQ01059769)



- Fixed an issue where error "MonTask: line 2379 in file ../../raid/2108vI2o.c" may occur - (SCGCQ01060599)



- Fixed an issue where error "FW crash at line 1155 in file ../../dm/src/dm.c" may occur - (SCGCQ01061211)



- Fixed an issue where error "Controller crash observed at line 1280 in file ../../raid/1078dma.c" when rebuilding a RAID1 - (SCGCQ01062346)



- Fixed an issue where SSC flush flags may be cleared in a non-command-block context - (SCGCQ01062386)



- Fixed an issue where storcli may display "Max SGE Count 60" even after largeIOsupport is enabled - (SCGCQ01064082)



- Fixed an issue where a DATATLB error "firmware break at Line 245 in ../../raid/1078int.c" may occur - (SCGCQ01064652)



- Fixed an issue where firmware logs may show an incorrect print for Background Initialization start on a RAID0 Virtual Drive after completing a Reconfiguration - (SCGCQ01065567)



- Fixed an issue where a kill adapter may occur when hotplugging 240 EPDs with IO in progress - (SCGCQ01066104)



- Fixed an issue where L2 Cache Error may be seen during ref tag error recovery on a PI Virtual Drive - (SCGCQ01066219)



- Fixed a performance issue where up to ~18% Perf Drop, SW for 4K/8k/16K @ 4&16QD, RW for 8K @ 4 QD, 12G SAS SSD,24PD,R5 - (SCGCQ01067709)



- Fixed an issue where controller may fail a drive for a SMART error even when MRIE mode is 2 or 3 - (SCGCQ01070758)



- Fixed an issue where not enough information was included in dump memory to debug memory alloc/free related issues - (SCGCQ01073663)



- Fixed an issue where controller firmware may halt on Pinned Cache generaion with multiple RAID0 Virtual Drives - (SCGCQ01075170)



- Fixed an issue where failed FastPath / immediate IO may report as success leading to SCSI-3 PRR failure - (SCGCQ01076183)



- Fixed an issue where a DATATLB error may occur when running IO on a max-PD Virtual Drive with Daisy-chained enclosures - (SCGCQ01076235)



- Fixed an issue where command queue depth only scaling to 64 for SAS HDDs - (SCGCQ01076289)



- Fixed an issue where multiInitSupport was not in the EepromMfcDisplay debug function - (SCGCQ01079664)



- Fixed an issue where controller firmware crash may occur when running IO in JBOD mode and multipath is enabled - (SCGCQ01080258)



- Fixed an issue causing iMR compilation problems - (SCGCQ01081326)

- Fixed an issue where error "Montask line 121 in file ../../raid/taskman.c" with "No more tasks available!" - (SCGCQ01082101)

- Fixed an issue where security key may be deleted when switching controller personality - (SCGCQ01085646)



- Fixed an issue where cache thresholds may not be adjusted appropriately on Pinned Cache generation - (SCGCQ01099559)



- Fixed an issue where error "Input parameters are invalid" may occur when creating a Virtual Drive in Advanced configuration - (SCGCQ01125119)



- Fixed an issue where double buffering code was not under an #ifdef for easy switch - (SCGCQ01131004)



- Fixed a performance issue where 5.5% drop in R10,R0 with 16K IO size SR-4QD with 40PD-12G-4K-SAS-HDD-SS-256K-WB-mode-Win2012-R2 - (SCGCQ01134731)



- Fixed a performance issue where 15% to 20% drops SW IO Sizes-256K QD(1,2),12G SAS HDD,x16,x24,x40- (SCGCQ01166023)



- Fixed a performance issue that may occur with Virtual Drives with 4Kn members - (SCGCQ01180459)



- Fixed a performance issue where RAID10 reads intermittently provide very poor performance - (SCGCQ00930527)



- Fixed an issue where controllers with 2GB of DRAM may fail to discover drives - (SCGCQ00987952)



- Fixed an issue where MSM provides "Make EPD" option for Unconfigured Good drives - (SCGCQ00995279)



- Fixed an issue where a kill adapter may occur under heavy IO in a multipath environment - (SCGCQ01016542)



- Fixed an issue where error "Assertion failure at line 807 in /raid/cache.c" may occur when running CacheCade Virtual Drive association/deassociation and SVD background operations are in progress - (SCGCQ01018367)



- Fixed an issue where DMA context switching settings are non-optimal for less than 24 disk expander configurations - (SCGCQ01020635)



- Fixed an issue where error "Firmware crash@line 108 in file ../../raid/taskman.c" may occur when performing creation/deletion of EPDs - (SCGCQ01023898)



- Fixed an issue where Unconfigured drives may be marked as Foreign even when no DDF is present - (SCGCQ01023963)



- Fixed an issue where error "Assertion failure in ../../dm/src/dm.c at line 1054" may occur on enclosure power cycle - (SCGCQ01025328)



- Fixed an issue where true multipath was not enabled - (SCGCQ01028614)



- Fixed an issue where enclosure devices at sasLevels greater than 1 were determined as direct attached devices - (SCGCQ01029470)



- Fixed an issue where exposeMultipath EPD param during behaviour mode change was not handled properly - (SCGCQ01029550)



- Fixed an issue where controller firmware fails to import Foreign configuration with Pinned Cache - (SCGCQ01029579)



- Fixed an issue where error "MonTask: line 2357 in file ../../raid/2108vI2o.c" may occur when running IO on 64 Virtual Drives and an Online Controller Reset is performed - (SCGCQ01030234)



- Fixed an issue where Operating System fails to boot due to continuous Logical Drive write map sync prints - (SCGCQ01030470)



- Fixed an issue where DDF PdDataInfo structure may be overwritten while a DDF update is in progress - (SCGCQ01030749)



- Fixed an issue where AutoConfig options set 0 after flashing firmware - (SCGCQ01033250)



- Fixed an issue where system may hang on boot when a reconstruction is in progress - (SCGCQ01034677)



- Fixed an issue where more than one reconstruction at a time may be allowed - (SCGCQ01036076)



- Fixed an issue where JBOD or EPD-passthrough may not be able to be created from Unconfigured drives when behavior mode is JBOD - (SCGCQ01039737)



- Fixed an issue where applications may fail CacheCade Virtual Drive creation when controller booted in 240VD mode is switched to 64VD mode - (SCGCQ01040017)



- Fixed an issue where Virtual Drive policies may not revert back on downgrade failure due to error "MFI_STAT_FLASH_NOT_ALLOWED" - (SCGCQ01041187)



- Fixed an issue where error "Montask line 1279 in file ../../raid/1078dma.c" may occur on performing target resets while running IO to Virtual Drives and JBODs - (SCGCQ01041735)



- Fixed an issue where Clear Foreign Configuration and Clear Configuration may report success even on failure - (SCGCQ01042004)



- Fixed some compilation issues - (SCGCQ01042472)



- Fixed an issue where defaults may be set on reboot after changing MFC settings - (SCGCQ01045951)



- Fixed an issue where boot drive setting may change to the first Virtual Drive by default on every reboot - (SCGCQ01045976)



- Fixed some code review issues - (SCGCQ01046172)



- Fixed an issue where controller firmware may fault during a firmware upgrade - (SCGCQ01051069)



- Fixed an issue where controller may incorrectly process the device wait queue during host task management - (SCGCQ01053010)



- Fixed an issue where Mode E offline flashing may display failure even after the image transfer is successful - (SCGCQ01054885)



- Fixed an issue where a kill adapter may occur when running Background Operations with OCR while CacheCade Virtual Drive association/dissociation in progress - (SCGCQ01058771)



- Fixed an issue where controller firmware may fault when downgrading - (SCGCQ01058792)



- Fixed an issue where an L2 Cache Error may be reported during OFC on iMR controllers - (SCGCQ01059873)



- Fixed an issue where error "Assertion failure in ssd_cache_fw.c" may occur during CacheCade Virtual Drive association/dissociation and Background Operation start/top and secondary enclosure cable insert/remove - (SCGCQ01059919)



- Fixed an issue where DATATLB error "Fatal firmware error: Line 245 in ../../raid/1078int.c" may occur - (SCGCQ01061565)



- Fixed an issue where error "MonTask at line 245 in file /raid/1078int.c" may occur when importing a Foreign SED/FDE configuration - (SCGCQ01065547)



- Fixed an issue where commands may not fail bakc to host if Command Block is not granted for more than 20 seconds - (SCGCQ01066198)



- Fixed an issue where "C0:MFI_STAT_NOT_FOUND" may be shown in firmware log when running IO against EPD/JBOD and system reboot/shutdown occurs - (SCGCQ01068464)



- Worked around an issue where spurious interrupts may cause a Physical Layer fault D230 - (SCGCQ01068609)



- Fixed an issue where a DATATLB error may occur when CacheCade support is not enabled on the system - (SCGCQ01069431)



- Fixed an issue where controller personality mode remains the same even when it has been changed to single-drive RAID0 - (SCGCQ01074396)



- Fixed an issue where stale enclosure entries may remain in topology array even after removing an enclosure - (SCGCQ01076184)



- Fixed an issue where only 30 Physical Drives may be able to be converted to Unconfigured Good on iMR controllers - (SCGCQ01077558)



- Fixed an issue where controller RAID layer may not handle RDM_STATUS_FAILED error - (SCGCQ01082528)



- Fixed an issue where cache may not be initialized after the deletion of the last targetID - (SCGCQ01156911)



- Fixed an issue where controller firmware may fault under heavy IO and target resets in progress with more than 32 EPDs - (SCGCQ01010222)



- Fixed an issue where controller firmware may fault when marking a Physical Drive of a CacheCade Virtual Drive as missing followed by a Replace Missing operation - (SCGCQ01021539)



- Fixed an issue where persistent reservation may not occur for true multipath configurations - (SCGCQ01022350)



- Fixed an issue where an improper offload of MEM_ - Fixed region in DDR may occur on reboot of host with Pinned Cache - (SCGCQ01029481)



- Fixed an issue where cache windows may not be properly allotted after making a RAID0 CacheCade Virtual Drive offline and then online - (SCGCQ01030735)



- Fixed an issue where controller firmware may hang on target reset to multiple drives - (SCGCQ01030891)



- Fixed an issue where the Virtual Drive ID may not be properly allocated when creating 240 Virtual Drives - (SCGCQ01035495)



- Fixed an issue where pldebug was not enabled - (SCGCQ01037904)



- Fixed an issue where if and else case were both returning FALSE - (SCGCQ01040437)



- Fixed an issue where controller firmware may crash when running IO to a dual-core capable Virtual Drive with Pinned Cache present - (SCGCQ01041766)



- Fixed an issue where an Assertion failure error may occur when Task Management is issued to EPDs with background IO - (SCGCQ01047185)



- Fixed some code review issues - (SCGCQ01047193)



- Fixed an issue where load balance may not occur on boot due to outstanding IO in disk - (SCGCQ01050467)



- Fixed an issue where only 26 drives can be converted as Unconfigured Good - (SCGCQ01059916)



- Fixed an issue where JBODs may go to Failed state when running Full Initialization with multipath cable push/pull - (SCGCQ01060295)



- Fixed an issue where incorrect Physical Drive details may be shown in an EPD deletion event - (SCGCQ01061128)



- Fixed an issue where a "VD missing" message may be displayed at POST after deleting an EPD and rebooting the system - (SCGCQ01061827)



- Fixed a compilation issue - (SCGCQ01063479)



- Fixed an issue where an error "kill adapter at line 1280" may occur under IO and multipath cable push/pull under RHEL7 - (SCGCQ01065343)



- Fixed an issue where controlelr name may not be displayed in any applications - (SCGCQ01069489)



- Fixed an issue where a DATATLB error may occur on iMR controllers when attempting to enable TTY to see discovery logs - (SCGCQ01078092)



- Fixed an issue where some controllers may fault with Uncorrectable ECC error detected - (SCGCQ01080061)



- Fixed an issue where an incorrect offset to devstateTAble pointers may occur - (SCGCQ01081352)



- Fixed an issue where an EPD may move to Shield state on SCSI/Immediate IO respose of BUSY - (SCGCQ01095557)



- Fixed an issue where an error "FW crash at line 8003 in file ../../raid/pd.c" may occur when performing target resets and Background IO - (SCGCQ01100216)



- Fixed an issue where AutoConfig DCMD may not report the correct stsatus for non-240VD mode - (SCGCQ01156132)



- Fixed an issue where text4 section may not load during firmware initialization - (SCGCQ01027455)



- Fixed some code review defects - (SCGCQ01031313)



- Fixed an issue where DATATLB error may occur when updating controller firmware when offline Disk Groups are present, followed by a server reboot - (SCGCQ01034958)



- Fixed an issue where error "Assertion failure at line 2359 in file ../../raid/2108vI2o.c" may occur when switching personalities - (SCGCQ01035492)



- Fixed an issue where error "Exception in Core 0" may occur during reconstruction of SVD when a CacheCade is present - (SCGCQ01037857)



- Fixed an issue where controller firmware may hang when creating a RAID1 and RAID0 Virtual Drive - (SCGCQ01042209)



- Fixed an issue where EPDs may be converted to Unconfigured Good when performing enclosure power cycles - (SCGCQ01046038)



- Fixed an issue where buffer overruns may occur - (SCGCQ01047035)



- Fixed an issue where values provided for MRIE mode may not be validated properly - (SCGCQ01048239)



- Fixed an issue where IO failures during path removal in true multipatch may not be handled correctly - (SCGCQ01054654)



- Fixed an issue where Auto Import of Foreign Configurations may fail for RAID1 Virtual Drive when Pinned Cache is present - (SCGCQ01060671)



- Fixed an issue where storcli may allow to set link speed to 1.5Gbps even though that is not supported - (SCGCQ01061902)



- Fixed an issue where a personality switch from EPD to single-drive RAID0 may fail even when there is no configuration - (SCGCQ01065596)



- Fixed a typo - (SCGCQ01070821)



- Fixed an issue where controller may hang when flashing a 4MB image - (SCGCQ01157158)



- Fixed an issue where controller firmware returns success to applications even though a Secure JBOD conversion as failed - (SCGCQ01038757)



- Fixed an issue where a timer list issue may occur when creating/deleting EPDs on a large config - (SCGCQ01043654)



- Fixed an issue where error "Failed to get VD VF mapping list" may occur on query "show VF map" - (SCGCQ01064037)



- Fixed an issue where MonTask error "No More Task available!!" may occur when a task management is issued from the Operating System - (SCGCQ01085194)



- Fixed an issue where L2/L3 Cache Error may be detected on controller during boot after shutdown - (SCGCQ01018958)



- Fixed an issue where device discovery may infinite loop when firmware gets a timeout for READ CAPACITY command - (SCGCQ01015624)



- Fixed an issue where a BSOD may occur on firmware upgrade from non-240VD firmware to 240VD-firmware when OS is behind the controller - (SCGCQ00829978, SCGCQ00829979, SCGCQ00829980, Port of SCGCQ00825725)



- Fixed an issue where firmware may return incorrect values for Logical Drive Physical Sector Size when Force Emulation is set on a 4Kn drive - (SCGCQ00918755, Port of SCGCQ00905002)



- Fixed an issue where an exception may occur on import of a Foreign Configuration whe number of Virtual Drives is greater than the supported 31 - (SCGCQ00935533, Port of SCGCQ00927528)



- Fixed an issue where storcli show all command triggers a datastore disconnect in VMWare ESXi - (SCGCQ00935551, Port of SCGCQ00928506)



- Fixed an issue where MonTask error may occur on boot after creating 240 Virtual Drives and rebooting the system - (SCGCQ00945341, Port of SCGCQ00905416)



- Fixed an issue where a kernel panic and/or MonTask error may occur due to host command count being incorrectly updated - (SCGCQ00976812, Port of SCGCQ00948256)



- Fixed an issue where dirty cache was not being ignored when firmware is updated with cache version change - (SCGCQ00988757, Port of SCGCQ00944012)



- Fixed an issue where security-related commands run even if a lock key is not assigned to controller - (SCGCQ00988906, Port of SCGCQ00940921)



- Fixed an issue where controller firmware may crash when running IO if the FastPath engine tries to add the timer for a new IO - (SCGCQ00988908, SCGCQ01017522, Port of SCGCQ00917821)



Worked around an issue where a firmware fault may occur due to a false ReplyParityError - (SCGCQ00988988, SCGCQ00988989, Port of SCGCQ00927504)



- Fixed an issue where locate LED may remain on for a reinserted drive - (SCGCQ01014122, Port of SCGCQ00998112)



- Fixed an issue where a DATATLB error may occur when hotplugging some enclosures - (SCGCQ01015796, Port of SCGCQ00983232)



- Fixed an issue where firmware may hang when trying to complete a FW_RAID_MAP command - (SCGCQ01022257, Port of SCGCQ01015745)



- Fixed an issue where Abort Task may fail to abort outstanding FastPath command - (SCGCQ01023239, Port of SCGCQ01020088)



- Fixed an issue where controller may be unable to import Foreign, locked Secured Drives - (SCGCQ01023287, Port of SCGCQ00994721)



- Fixed an issue where IOs may be terminated on EPDs when doing target resets while disks go Offline - (SCGCQ01028573, Port of SCGCQ00953540)



- Fixed an issue where initial boot prints may be missing during firmware initialization and restore operations - (SCGCQ01041470, Port of SCGCQ01012327)



- Fixed an issue where ECC bit count may not be programmed to 24 correctly - (SCGCQ01069986, Port of SCGCQ01051207)



- Fixed an issue where CTRL-R may not automatically refresh the screen after some operations - (SCGCQ01070182, Port of SCGCQ01068368)



- Fixed an issue where Spare Pool start address may be set incorrectly after some cache offload and restore operations - (SCGCQ01070258, Port of SCGCQ01069753)



- Fixed an issue where performance degradation may occur due to MultiCpuAtomicDec()/MultiCpuAtomicInc() functions modifying scsi_pending_cmds - (SCGCQ01073190, Port of SCGCQ01044217)



- Fixed an issue where Data Protection bit may not be cleared during Secure Erase and reboots - (SCGCQ01078532, SCGCQ01078533, SCGCQ01078536, SCGCQ01069761, Port of SCGCQ01065119)



- Fixed an issue where a read retry is needed when ECC errors in excess of 24bits per 1100 bytes occur - (SCGCQ01081899, SCGCQ01081900, SCGCQ01089927, Port of SCGCQ01078237)



- Fixed an issue where LUID may be changed during import of Foreign configuration from non-240VD firmware to 240VD firmware - (SCGCQ01084595, SCGCQ01087947, SCGCQ01163258, SCGCQ01163768, Port of SCGCQ00907658)



- Fixed an issue where error "15=Fatal firmware error: Line 1972 in ../../raid/flex.c" or "MonTask: line 1972 in file ../../raid/flex.c" may occur on boot when running a rebuild and a reconstruction - (SCGCQ00996655, SCGCQ01088182, SCGCQ00907979, Port of SCGCQ00902755)



- Fixed an issue where IO failures may be observed on 4Kn Virtual Drives with PI enabled - (SCGCQ01117016, SCGCQ01118907, SCGCQ01129839, SCGCQ01130945, SCGCQ01130999, SCGCQ01131000, SCGCQ01131001, SCGCQ01131002, SCGCQ01131003, Port of SCGCQ01081912)



Disable support for PI and do not allow PI to be re-enabled - (SCGCQ01128064, Port of SCGCQ01105478)



- Fixed an issue where import of a max Foreign Configuration may fail - (SCGCQ01129847, Port of SCGCQ00679180)



- Fixed an issue where error "bladeErrorIsrTask ChanNum 0 intStatus" may occur when enabling security on controller - (SCGCQ01130922, SCGCQ01130938, Port of SCGCQ01077578)



- Fixed an issue where presence of pinned cache may not result in a move of all unpinned windows of a degraded CacheCade Virtual Drive to read-only - (SCGCQ01136063, Port of SCGCQ01118285)



- Fixed an issue where controller firmware may fault when running command "storcli /c0 set termlog=on" - (SCGCQ01139844, Port of SCGCQ01129530)



- Fixed an issue where CTRL-H was allowing user to enable PI when PI is disabled - (SCGCQ01141456, Port of SCGCQ01139294)



- Fixed an issue where EPDs may not be created after system reboot when Physical Drive erase is in progress on one or more drives - (SCGCQ01146473, Port of SCGCQ01144014)

- Fixed an issue where a kill adapter may occur during a simultaneous rebuild, reconstruction and drive pull - (SCGCQ01149315, Port of SCGCQ01143971)



- Fixed an issue where configured drives may be converted to JBOD if system already has maximum number of configurable drives - (SCGCQ01149763, Port of SCGCQ01136693)



- Fixed an issue where controller may report 1MB as IO size regardless of the IO type or mode - (SCGCQ01180170, SCGCQ01180171, Port of SCGCQ01137690)



- Fixed an issue where iEEESGL flag may not be set for IO requests in SES DCDB handler - (SCGCQ01186523, SCGCQ01205429, Port of SCGCQ01157072)



- Fixed an issue where Logical Drive to Physical Drive LDA conversion happens using PRL11 for LBAs that have not yet been migrated - (SCGCQ01201996, Port of SCGCQ01186096)



- Fixed an issue where flash block read timeouts may be observe when flash file system read failures and read eye training failures occur simultaneously - (SCGCQ01229234, Port of SCGCQ01208490)



- Fixed an issue where MR_DCMD_CFG_AUTOCFG DCMD may be disabled in non-240 VD environment - (SCGCQ01232073, Port of SCGCQ01213915)



- Fixed an issue where controller firmware may assert when booting with 4K drives - (SCGCQ00935534, Port of SCGCQ00927547)



- Fixed an issue where Auto RAID0 may fail with 8 enclosures connected - (SCGCQ00938868, Port of SCGCQ00934300)

- Fixed an issue where code was not detecting crossage of 1 MB page boundary through proper Assert - (SCGCQ00947988, Port of SCGCQ00931010)



- Fixed an issue where rebuild fails to start on CacheCade virtual drives after successful import - (SCGCQ00954124, Port of SCGCQ00950030)



- Fixed an issue where am rebuild error "Error f0" may occur on iMR controllers - (SCGCQ00979952, Port of SCGCQ00915417)



- Fixed an issue where Locate LED may remain on for reinserted drive - (SCGCQ00999675, Port of SCGCQ00997675)



- Fixed an issue where a MonTask or DATATLB error may occur when there is Pinned Cache involving degraded, sliced Virtual Drives - (SCGCQ01023909, SCGCQ01023910, Port of SCGCQ00997180)



- Fixed an issue where LED may not turn off when a drive is removed - (SCGCQ01026815, Port of SCGCQ01003387)



- Fixed an issue where SEP devices at sasLevels greater than 1 may be determined as Direct Attached Devices - (SCGCQ01027840, Port of SCGCQ01004946)



- Fixed an issue where a MonTask error may occur when IO, target resets and cable insert/remove are occurring simultaneously - (SCGCQ01028575, Port of SCGCQ00979797)



- Fixed an issue where correct slot number may not be collected for SES enclosures - (SCGCQ00925533, SCGCQ01180864, Port of SCGCQ00903181)



- Fixed an issue where drive may not be marked as Foreign on OCR when controller already has max configured drives - (SCGCQ01202208, Port of SCGCQ01163849)



- Fixed an issue where controller configuration may be lost when connecting a stale configuration - (SCGCQ01205397, Port of SCGCQ01170701)



- Fixed an issue where error "MonTask: line 3386 in file ../../dm/src/devmgr.c" may occur when running IO to JBOD SAS SSD and cables removed/reinserted - (SCGCQ01232131, Port of SCGCQ01213918)



- Fixed an issue where error "adapter at base port not responding" may appear on boot when firmware issues mode sense command to faulty drives - (SCGCQ01001353, Port of SCGCQ00999966)



- Fixed an issue where error "Firmware crash @line 245 in file ../../raid/1078int.c" may occur on enclosure power cycles - (SCGCQ01022262, Port of SCGCQ01015293)



- Fixed an issue where message "I2C 4 PID 10 SCL STUCK Low! while I2C Rx receiving data intStatus 00008000" may still be printed in firmware log - (SCGCQ01026304, Port of SCGCQ01007592)



- Fixed an issue where firmware returns an error when flashing individual components through storcli such as NVDATA, BTBL etc - (SCGCQ01030747, Port of SCGCQ01015302)



- Fixed an issue where totalLines required to carry IO/Flush operation may not be restricted to primary core - (SCGCQ01033265, Port of SCGCQ01019324)









Enhancements:



- Added Physical Layer library version 12.0.5.0 - (SCGCQ01231972)



- Reverted DDR tuning changes for some controllers - (SCGCQ01224232)



- Added Physical Layer 10.00.11.00 - (SCGCQ01194361)



- Added AutoConfig feature support for 64VD mode - (SCGCQ01170212)



- Added a feature for firmware to turn on fault LED for drives less than 512MB - (SCGCQ01156969)



- Renamed HBA mode to JBOD mode - (SCGCQ01146813)



- Added JBOD personality to MR_CTRL_PERSONALITY - (SCGCQ01146597)



- Added supportPdMapTargetId flag in MR_CTRL_INFO and MFI_CAPABILITIES - (SCGCQ01141251)



- Added interfaceType to MR_DEV_HANDLE_INFO - (SCGCQ01141229)



- Added API support for TFM/SCAP _MR_BBU_VPD_INFO_ - Fixed parameters - (SCGCQ01139344)



- Added new fields to MPI2_MR_PARAMS_PAGE_0 - (SCGCQ01137628)



- Added a new control command to fetch ROC temperature data over I2C - (SCGCQ01137627)



- Added a targetID interface to the API for system PD/JBOD drives - (SCGCQ01128348)



- Added page-level retries for cache offload read commands with unrecoverable ECC errors - (SCGCQ01118692)



- Implemented flash-level data scrambler support - (SCGCQ01118685)



- Integrated Physical Layer 11.00.07.00 - (SCGCQ01117938)



- Added 40-bit correction support for some controller's ONFI flash - (SCGCQ01093426)



- Integrated Physical Layer 12.00.01.00 - (SCGCQ01070254)



- Added feature to not use cache lines for FastPath failed IO - (SCGCQ01048213)



- Added support to persist the MR_CFG_USER_CONFIGURABLE - (SCGCQ01046154)



- Added ability to initiate a learn every 24 hours - (SCGCQ01043205)



- Added support for new preboot tool HIIA - (SCGCQ01036145)



- Added support for AutoConfiguration for EPDs - (SCGCQ01024552)



- Added parallel drive microcode update support - (SCGCQ01023507)



- Added additional EEDP error reporting capability so SCSI IO Reply - (SCGCQ01002367)



- Modified "SAS IO Unit Page 4" to add a new field "SATAHintingTimeout" - (SCGCQ00996127)



- Integrated Physical Layer version 09.00.100.00 - (SCGCQ00995100)



- Added some changes to CtrlDiag.c - (SCGCQ00993617)



- Integrated Physical Layer version 09.00.59.00 - (SCGCQ00993610)



- Improved performance of Write-through CacheCade Virtual Drives with respect to Write-back CacheCade Virtual Drives - (SCGCQ00991600)



- Added additional EEDP Error Reporting capability to SCSI IO Reply - (SCGCQ00988360)



- Integrated Physical Layer from Phase 11 - (SCGCQ00988065)



- Integrated Physical Layer 10.250.07.00 - (SCGCQ00950469)



- Implemented recovery logic to recover good blocks that are falsely marked as bad - (SCGCQ00939352)



- Addressed regression with POC 4 - (SCGCQ00928870)



- Implemented profile management API for drivers and other external to application entities - (SCGCQ00867953)



- Added MegaAPI modifications for FastPath ReadModifyWrite and Cache Bypass features - (SCGCQ00875328)



- Added Private API modifications for FastPath ReadModifyWrite and Cache Bypass features - (SCGCQ00875330)



- Merged api_overrides mega_api files with the files in the Mega_API development stream - (SCGCQ00883262)



- Merged api_overrides pvt_api files with the files in the Pvt_API development stream - (SCGCQ00883315)



- Updated NVDATA EEPROM tag for evaluation boards - (SCGCQ00898133)



- De-featured AHCI support - (SCGCQ00941620)



- Added Read-Ahead capable bit to communicate to driver that Read-Ahead is capable in firmware - (SCGCQ00987841)



- Expanded MR_CTRL_INFO from 2K to 4K - (SCGCQ01023741)



- Added support bit in controller info to inform storcli whether firmware is running in iButton or iButtonless mode - (SCGCQ01059740)



- Added Private API changes for iButtonless operation - (SCGCQ01059744)



- Added profile management changes to support requestedProfileID and optimisedProfile - (SCGCQ01075821)



- Added Mega API changes to incorporate new IO subtype to support redirect cached IO - (SCGCQ01094549)



- Added MR_RAID_FLAGS_IO_SUB_TYPE_LDIO_BW_LIMIT = 7 to mfi.h file - (SCGCQ01133839)



- Added handling of parameters during behavior mode switch for OCR and reboot cases - (SCGCQ01060770)



- Integrated Physical Layer library 09.00.102.00 - (SCGCQ01045607)



- Updated CFGI and Physical Layer to SAS3.5 Phase 12 - (SCGCQ01041442)



- Integrated Physical Layer 11.250.07.00 - (SCGCQ01038935)



- Integrated Physical Layer 11.25.00.00 - (SCGCQ01037066)



- Added feature to allocate alias targetID for EPDs when true multipath is enabled - (SCGCQ01024648)



- Added true multipath host task management - (SCGCQ01024444)



- Improved performance of Write-through CacheCade Virtual Drives with respect to Write-back CacheCade Virtual Drives - (SCGCQ01015822)



- Added logging of SuperCap Fault Assertion along with associated status bits during runtime - (SCGCQ01011381)



- Integrated Physical Layer 11.00.02.00 - (SCGCQ01010302)



- Improved IO performance by disabling or enabling driver coalescing based on configuration - (SCGCQ00992516)



- Added single-image offload for CacheVault single write mode - (SCGCQ01199671)



- Integrated Physical Layer 12.00.03.00 - (SCGCQ01091093)



- Changed DDR phy termination settings for some controllers - (SCGCQ01066266)



- Integrated Physical Layer 12.00.01.00 - (SCGCQ01063510)



- Added handling for 128 drives per enclosure - (SCGCQ00920037)

- Integrated Physical Layer 12.00.05.00 - (SCGCQ01162534)



- Added feature for firmware to complete SYNC_CACHE command for VDs even if mode page bit is disabled - (SCGCQ01125303)



- Added feature to support exporting RAID geometry - (SCGCQ00936726)



- Added "supported bits" mbox value to MR_DCMD_CFG_AUTOCFG - (SCGCQ01025967, Port of SCGCQ01020092)



- Unblocked MCTP over PCIe levels - (SCGCQ01145325, Port of SCGCQ01134167)



- Added MR_DCMD_CFG_AUTOCFG for iMR for GET operation - (SCGCQ01232103, Port of SCGCQ01228949)



- Added capability to expose each SAS expander-attached SEP as a separate Enclosure PD - (SCGCQ01150206, Port of SCGCQ01093800)

Converted some unrecoverable errors to recoverable errors - (SCGCQ00943806, Port of SCGCQ00890049)



- Added feature to handle the presence and absences of randomizer - (SCGCQ01156575, Port of SCGCQ01133554)



- Added support for SCSI SANITIZE/Crypto commands on JBOD drives - (SCGCQ01144707, Port of SCGCQ01129378)



- Removed reset of Idle Timers - (SCGCQ01223113, Port of SCGCQ01145782)



- Added ability to allow security commands to drives which are not managed by SafeStore - (SCGCQ01026630, Port of SCGCQ01007634)



- Added changes for Profile management API support - (SCGCQ00883008, SCGCQ00883045)



Version 24.12.0-0039 - High Impact/High Probability of Occurrence

-------------------

FW Package: 24.12.0-0039

HII: E3.19.07.06

UEFI Driver: 0x06130201

BIOS: 6.30.03.2

MR FW: 4.620.00-8080

iMR FW: 4.620.01-8081



Fixes:

- Disabled further usage of PI due to a potential data issue (SCGCQ01128078)

- Fixed an issue where In CTRL-R the controller is giving the option to enable the drive protection under controller operations (F2) with firmware which does not support the data protection. (SCGCQ01139294, SCGCQ01074426, SCGCQ01131138)

- Fixed an issue where a configured drive is inserted, rebuild started on wrong virtual drive after the enclosure power cycle. (SCGCQ00988970 Port of SCGCQ00927155)

- Fixed an issue where the screen is not refreshing after operations in CTLR-R. (SCGCQ01088160)

- Fixed an issue where controller broke into montask upon reboot after running a rebuild and reconstruction. (SCGCQ01088178 Port of SCGCQ00902755)

- Fixed an issue where /O failures observed on 4k virtual drive with data Protection Enabled, when virtual drive goes offline due to source drive error when Rebuild is progressing on a degraded virtual drive (SCGCQ01130941 Port of SCGCQ01081912)

- Fixed an issue for iMR where the supported configurable physical drive count is already filled and more configured drives are added and get converted to JBOD and their configuration was cleared. (SCGCQ01149762)

- Fixed an issue where data compare error found during recovery of CacheCade pinned windows across OCR/Reboot or discard of CacheCade pinned windows while CacheCade degrade flush in progress. (SCGCQ01136062)

- Fixed an issue where iEEESGL flag was not getting set for IO request in SES DCDB handler. (SCGCQ01186523 Port of SCGCQ01157072)

- Fixed an issue where L2/L3 Cache error was detected on the RAID controller during boot. (SCGCQ01155454 Port of SCGCQ01018958)



Enhancement(s):

- Revert the DDR tuning changes for specific PCI IDs. (SCGCQ01224232)

- SCSI SANITIZE/Crypto on JBOD Drives under MR. (SCGCQ01155380 Port of SCGCQ01129378)



Version 24.12.0-0033 - High Impact/High Probability of Occurrence

-------------------



FW Package: 24.12.0-0033

HII: E3.19.07.06

UEFI Driver: 0x06130201

BIOS: 6.30.03.2

MR FW: 4.620.00-7178

iMR FW: 4.620.01-7179



Fixes:

- Fixed an issue where changing RAID FoD key (Add/Remove) through customer application will make the original VD change to foreign. (SCGCQ01111615)

- Fixed an issue where security is disabled on a ServRAID M5210 controller after a FOD key is added or removed until next reboot. (SCGCQ01132432)



Enhancement:

- Added the capability for users to save the FoD key to TMM through the MSM pop-up advanced software options. (SCGCQ01085797)





Version 24.12.0-0024 - High Impact/High Probability of Occurrence

--------------------



FW Package: 24.12.0-0024

HII: E3.19.07.03

UEFI Driver: 0x06130200

BIOS: 6.30.03.0

MR FW: 4.620.00.6070

iMR FW: 4.620.01.6071



Fixes:

- Fixed the potential of a data miscompare that was observed only at a vendor test facility under very heavy I/O and abnormal practices (SCGCQ00990093, Port of SCGCQ00976904)

- Fixed an issue where performing back-to-back target resets on the same JBOD may results in an Controller Reset (SCGCQ00857181)

- Fixed an issue where firmware may allow a Reconstruction to be performed when Pinned Cache is present (SCGCQ00857692)

- Fixed an issue where "MonTask" error may occur when importing a Foreign Configuration (SCGCQ00860066)

- Fixed an issue where controller does not Stop on Error and boots into Operating System when Pinned Cache is present(SCGCQ00860503)

- Fixed an issue where firmware allows CacheCade Virtual Drive deletion when Pinned Cache is present (SCGCQ00871973)

- Fixed an issue where a firmware downgrade FW downgrade may fail when IO and Background Operations are being performed (SCGCQ00873239)

- Fixed an issue where error "Core 0 exception in line 245 in ../../raid/1078int.c" may occur when Target Reset sent to Physical Disks in parallele with Background Operations (SCGCQ00878554)

- Fixed an issue where error "Assertion failure in ../../dm/src/dmDrvPrep.c at line 836" may occur (SCGCQ00879198)

- Fixed an issue where firmware may hang on Task Abort (SCGCQ00881901)

- Fixed an issue where iPtr and rPtr values may be greater than the size of the buffer (SCGCQ00886685)

- Fixed an issue where more IOs were allowed than the available buffer could support (SCGCQ00894472)

- Fixed an issue where the Operating System may become unresponsive after creating multiple sliced Virtual Disks (SCGCQ00894608)

- Fixed an issue where adapter may reset under certain conditions (SCGCQ00895554)

- Fixed an issue where error "line 1271 in file ../../raid/1078dma.c" may occur when running FastPath with CacheCade (SCGCQ00898799)

- Fixed an issue where forceCacheFlush was occurring in an iMR context where it doesn't apply (SCGCQ00899762)

- Fixed an issue where importing 240 Virtual Drives may cause a firmware fault (SCGCQ00900601)

- Fixed an issue where error "line 229 in file ../../raid/mtask.c" may occur when Hibernating Windows 10 (SCGCQ00905864)

- Fixed an issue where importing a Foreign Configuration may fail (SCGCQ00908325)

- Fixed an issue where FastPath IO may not time out properly (SCGCQ00910124)

- Fixed an issue where StorCLI may report an incorrect ScapBatVersionNO when using command "/c0/cv show all" (SCGCQ00914343)

- Fixed an issue where some default values may not be picked up for unchanged controller properties sharing the same byte (SCGCQ00914740)

- Fixed an issue where chain mid allocation for JBOD may fail (SCGCQ00915081)

- Fixed an issue where configuration creation may fail after creation of a CacheCade Virtual Drive followed by JBOD creation (SCGCQ00917307)

- Fixed an issue where a cable pull during a Target Reset on JBOD may result in a data TLB error (SCGCQ00923289)

- Fixed an issue where controller may become unresponsive after hitting an OCM error(SCGCQ00924986)

- Fixed an issue where the Physical Device map was being updated unnecessarily (SCGCQ00927173)

- Fixed an issue where some drives could not be discovered successfully (SCGCQ00927792)

- Fixed an issue where attempting to stop a Drive Erase operation from application may cause firmware to hang (SCGCQ00928150)

- Fixed an issue where controller disappears when performing a cable pull (SCGCQ00928333)

- Fixed an issue where CacheCade Virtual Drive creation may fail with false error (SCGCQ00930044)

- Fixed an issue where controller may hang when importing a drive into a RAID0 CacheCade Virtual Drive (SCGCQ00934196)

- Fixed an issue where firmware would not allow an Online Firmware Update (SCGCQ00936693)

- Fixed an issue where error "line 219 in file ../../raid/mficmd.c" may occur when powering system on from S3 sleep (SCGCQ00937487)

- Fixed an issue where error "MonTask: line 1281 in file /raid/1078dma.c" may occur when running enclosure cable pulls with CacheCade Virtual Drive (SCGCQ00941531)

- Fixed an issue where firmware recovers invalid cache after firmware update (SCGCQ00944012)

- Fixed an issue where LdInitPdDone did not include flush command block (SCGCQ00945033)

- Fixed an issue where driver may panic and controller may reset on medium errors with Pinned Cache (SCGCQ00948257)

- Fixed an issue where Virtual Drives don't revert back to Write-Back once the controller Pinned Cache is destaged (SCGCQ00948466)

- Fixed an issue where firmware may fault when running full initialization on Virtual Drives with LDBBM entries created during Consistency Check (SCGCQ00952627)

- Fixed an issue where a SES Discovery Error may occur on repeated retries for some expanders (SCGCQ00976741)

- Fixed an issue where the drive bay LED may not turn off when the drive is removed (SCGCQ01003387)

- Fixed an issue where error "MonTask: line 4946 in file ../../raid/ld.c" may occur when multipath cable pull occurs Patrol Read (SCGCQ00857528)

- Fixed an issue where Locate LED turns off when cable failover performed (SCGCQ00869681)

- Fixed an issue where "Watchdog Timer Exception" error followed by firmware fault after initiating Physical Drive erase operation (SCGCQ00872140)

- Fixed an issue where a firmware fault occurs when issuing Task Management commands on 240 JBODs while running IO (SCGCQ00872889)

- Fixed an issue where Virtual Drive deletion could cause IO freeze time to increase (SCGCQ00873201)

- Fixed an issue where a data TLB error would occur after issuing task abort (SCGCQ00873991)

- Fixed an issue where "MonTask" error may occur due to a Full-Disk Encryption / Self-Encrypting Disk that fails to spinup (SCGCQ00874332)

- Fixed an issue where error "adapter at baseport not responding" may occur (SCGCQ00880919)

- Fixed an issue where cache is not flushed immediately upon firmware recieving the cache-flush out-of-band command (SCGCQ00882125)

- Fixed an issue where IO may slow while deleting Virtual Drives (SCGCQ00891924)

- Fixed an issue where IO halts on JBODs with "read/write error" when the target drives are reset in Linux (SCGCQ00893588)

- Fixed an issue where "MonTask: line 1413 in file ../../raid/config.c" may occur when creating a CacheCade Virtual Drive (SCGCQ00894610)

- Fixed an issue where firmware does not log controller property change event for enabling/disabling 240VD feature (SCGCQ00895577)

- Fixed an issue where event length may come up as 0 (SCGCQ00897406)

- Fixed an issue where firmware was not seding the proper status for aborted commands (SCGCQ00900250)

- Fixed an issue where controller firmware may fault during Hibernation or when the driver loads twice (SCGCQ00902938)

- Fixed an issue where firmware may fault after creating 240 Virtual Drives and rebooting the server (SCGCQ00905416)

- Fixed an issue where progress for CacheCade disassociation activity is not displayed for all source Virtual Drives (SCGCQ00906846)

- Fixed an issue where error "Assert at line 1181 mpthostcmd.c" may occur when FastPath has been disabled or for a timeout IO (SCGCQ00910006)

- Fixed an issue where error "LMID HS-FIFO Error 0x8" may occur when removing a redundant path to a JBOD with IO (SCGCQ00914274)

- Fixed an issue where applications may show incorrect value for Max Parallel Commands field of Controller Information in iMR(SCGCQ00914751)

- Fixed an issue where firmware was failing ABORT TASK and ABORT TASK SET commands on SATA JBOD (SCGCQ00915088)

- Fixed an issue where exception may occur on Online Controller Reset (SCGCQ00917523)

- Fixed an issue where "MonTask" error may occur in a drive removal or multipath removal scenario (SCGCQ00919229)

- Fixed an issue where the wrong MFI_STAT is returned from PdDcmdSysPdMapAbort (SCGCQ00930593)

- Fixed an issue where an Online Firmware Update may fail when downgrading from firmware that supports 240 Virtual Drives to firmware that does not (SCGCQ00930917)

- Fixed an issue where "DM_EnableFastPathOnDevice :: FP enabled on devhandle" may be printed in logs even though FastPath is enabled (SCGCQ00936617)

- Fixed an issue where "C0:Index 0098 allocated from pool 3" prints continuously in log with 12Gbps Enclosures and SATA drives (SCGCQ00937572)

- Fixed an issue where firmware prematurely rejects ONFI flash module (SCGCQ00937617)

- Fixed an issue where SafeID may change on repeated queries using StorCLI (SCGCQ00941577)

- Fixed an issue where firmware may fault when importing Virtual Drives with Pinned Cache (SCGCQ00949440)

- Fixed an issue where Write-Back Virtual Drives are converted to Write-Through on system reboot or Online Controller Reset(SCGCQ00859720)

- Fixed an issue where a Data TLB error may occur when firmware is upgraded or downgraded (SCGCQ00867065)

- Fixed an issue where a Data TLB error may occur when aborting a host command (SCGCQ00874357)

- Fixed an issue where firmware may fault when running IO with Task Resets on JBODs (SCGCQ00877673)

- Fixed an issue where error "MonTask: line 245 in file ../../raid/1078int.c" may occur while running IO with 64 Virtual Drives and removing drives belonging to CacheCade (SCGCQ00878587)

- Fixed an issue where cache flush was occurring during Virtual Drive deletion (SCGCQ00878923)

- Fixed an issue where IO dip is seen when deleting Virtual Drives (SCGCQ00879193)

- Fixed an issue where a Data TLB error may occur when sending Target Reset on JBOD via out-of-band commands (SCGCQ00881919)

- Fixed an issue where perTunerMode is not set correctly after a controller reset (SCGCQ00882897)

- Fixed an issue where error "MonTask: line 2735 in file ../../ssd/ssd_cache_fw.c" may occur when error are injected repeatedly (SCGCQ00887019)

- Fixed an issue where a rebuild cannot be started for a degraded CacheCade Virtual Drive after heavy IO (SCGCQ00887428)

- Fixed an issue where error "MonTask: line 245 in file ../../raid/1078int.c" may occur with IOs on maximum Virtual Drives configured and Background Opertations are occurring (SCGCQ00890133)

- Fixed an issue where Patrol Read doesn't resume after Consistency Check completes after a system reboot (SCGCQ00894344)

- Fixed an issue where StorCLI throws an error when performing "/c0/vx show all" after a Full Initialization on RAID1 Virtual Drive with SSDs (SCGCQ00904899)

- Fixed an issue where a firmware fault occurs when a copyback operation fails to start (SCGCQ00904905)

- Fixed an issue where LUID is changed when importing a non-240VD configuration to a 240VD firmware (SCGCQ00907658)

- Fixed an issue where a "MonTask" error may occur when under heavy JBOD IO and the JBOD IOs begin failing (SCGCQ00915078)

- Fixed an issue where error "line 1279 in file ../../raid/1078dma.c" may occur on iMR firmware during boot (SCGCQ00915092)

- Fixed an issue where controller reset occurs under stress with 240 Virtual Drives configured (SCGCQ00915398)

- Fixed an issue where Online Firmware Update would fail due to driver reload issues (SCGCQ00915454)

- Fixed an issue where a Data TLB error may occur during reconstrution operation when Target Resets are issued to JBODs (SCGCQ00921993)

- Fixed an issue where "Core 0 exception" is seen when trying to import Foreign Configurations with Pinned Cache (SCGCQ00863880)

- Fixed an issue where CTRL-R interface does not show correct port information when hotplugging enclosure paths (SCGCQ00866487)

- Fixed an issue where firmware may fault when an enclosure with an especially slow drive is present (SCGCQ00867120)

- Fixed an issue where error "MonTask: line 1280 in file ../../raid/1078dma.c" may occur on out-of-band command timeout (SCGCQ00872875)

- Fixed an issue where error "Assertion failure in ../../raid/cache.c at line 774" may occur after pulling out an enclosure cable (SCGCQ00878097)

- Fixed an issue where write performance drops in RAID5, Write-Through, No Read-Ahead, Stripe Size 64, 1MB IO at queue depth 128/256 (SCGCQ00878414)

- Fixed an issue where an imported 4K-drive RAID0 becomes Unconfigured Good on reboot (SCGCQ00895689)

- Fixed an issue where Online Firmware Update fails with "not supported" message (SCGCQ00915073)

- Fixed an issue where Logical Drive IO for FastPath-capable RAID0/RAID1 were not handled properly in the presence of a RAID5/RAID6 Write-Through volume running sequential write streams (SCGCQ00915409)

- Fixed an issue where a CRC mistmatch and Invalid Log Event are surfaced when checking Controller Properties in parallel with a Learn Cycle (SCGCQ00919945)

- Fixed an issue where performance drops are seen on writes to RAID1 FastPath volumes (SCGCQ00931895)

- Fixed an issue where event messages reporting CacheCade Virtual Disk target ID and remaining CacheCade size are incorrect (SCGCQ00864019)

- Fixed an issue where firmware faults when using an Online Controller Reset from StorCLI after having issued "supportResetNow" (SCGCQ00878150)

- Fixed an issue where an "Exception in Core -0" error may occur on iMR firmware under VMWare (SCGCQ00904103)

- Fixed an issue where "MsgAlloc: No free messages, poolIndex=4" may appear in logs while running IO on JBODs (SCGCQ00908982)

- Fixed an issue where the TTY log dump is not persistent across multiple boots (SCGCQ00877100)

- Fixed an issue where drives that return errors for all protocol commands may be retried indefinitely (SCGCQ00805369)

- Fixed an issue where setting the Learn Cycle property of iBBU09 gives an i2C error (SCGCQ00837206)

- Fixed an issue where driver may hang with LSI2008-based adapters (SCGCQ00843390)

- Fixed an issue where device wait queue is not cleared when drive is no longer online (SCGCQ00878401)

- Fixed an issue where Windows may BSOD on firmware upgrade when running driver 6.707.08.00 (SCGCQ00886272)

- Fixed an issue where disableImmediateIO NVDATA value is not honored by firmware (SCGCQ00886666)

- Fixed an issue where Foreign Configuration could be cleared even when Pinned Cache is present (SCGCQ00889209)

- Fixed an issue where a Virtual Drive under Reconstruction may go Degraded if the drive being reconstructed is removed before the operation completes (SCGCQ00891282)

- Fixed an issue where a "MonTask" error may occur after initiating a RAID Level Migration (SCGCQ00891288)

- Fixed an issue where system hang may occur after aborting running Consistency Checks repeatedly (SCGCQ00895265)

- Fixed an issue where a "MonTask" error may occur after creating 240 Virtual Drives and rebooting the server (SCGCQ00908121)

- Fixed an issue where LUID is changed when importing a non-240VD configuration to 240VD-enabled controller (SCGCQ00908153)

- Fixed an issue where a Virtual Drive may disappear on reboot if created with drives from a previously-deleted Virtual Drive (SCGCQ00914823)

- Fixed an issue where device wait queue is not cleared if a drive is no longer online (SCGCQ00923279)

- Fixed an issue where message "Found invalid event at fc4966ec" is printed in firmware log every 5 seconds (SCGCQ00931370, SCGCQ00979910)

- Fixed an issue where firmware is unable to detect all Virtual Drive's "Degraded" status for partial Virtual Drives created on the same Physical Drives (SCGCQ00942380)

- Fixed an issue where driver may panic and firmware may hang when medium errors are present (SCGCQ00954118)

- Fixed an issue where firmware does not discard dirty cache after firmware update (SCGCQ00992657)

- Fixed an issue where some Recoverable Errors were marked as Unrecoverable (SCGCQ01015699)

- Fixed an issue where HII and Ctrl-R show an incorrect message when trying to import a 65th Virtual Drive (SCGCQ00803718)

- Fixed an issue where Functional Level Reset (FLR) was not supported (SCGCQ00843936)

- Fixed an issue where Write-through and Write-back cache policies can be changed via Windows Logical Disk Properties. (SCGCQ00883311)

- Fixed an issue where many "LdDcmd ***** return pinned list 0" messages may be printed in firmware log (SCGCQ00895459)

- Fixed an issue where an alert is repeated twice for Cancel Consistency Check on Virtual Drives (SCGCQ00900027)

- Fixed an issue where error "Controller encountered fatal error and was reset" may occur under heavy IO and background operations (SCGCQ00905603)

- Fixed an issue where CacheCade-related 240 Virtual Drive checks were not checking controller properties (SCGCQ00905809)

- Fixed an issue where out-of-band applications may not display Show Configuration Summary when 240 Virtual Drives are created (SCGCQ00908237)

- Fixed an issue where a RAID0 using 4k drives may not be visible after reboot (SCGCQ00999181)

- Fixed an issue where firmware may not poll all temperature sensor channels every 5 seconds (SCGCQ00844152)

- Fixed an issue where Hard Drive RAID0 and RAID10 performance at 1M stripe size is suboptimal between queue depths of 16 to 256 (SCGCQ00876154)

- Fixed an issue where StorCLI will report Success when flashing an MR-only package on an iMR-only controller (SCGCQ00882149)

- Fixed an issue where 'Fw initializing devices' may hang with specific failed drives (SCGCQ00884719)

- Fixed an issue where controller may report cache size as "0" when no logical drives are present (SCGCQ00891273)

- Fixed an issue where a Physical Disk may not go to Online state even after creating a Virtual Drive on it (SCGCQ00910741)

- Fixed an issue where error "SAS core detected EEDP error in application tag" may occur (SCGCQ00936647)

- Fixed an issue where "storcli /c0 show all" shows many Bad Block messages in the log (SCGCQ00892136)

- Fixed an issue where firmware may log Controller Properties Changed events twice (SCGCQ00908238)

- Fixed an issue where a Virtual Drive under Reconstruction may be set Degraded if the drive under reconstruction is removed (SCGCQ00922677)

- Fixed an issue where firmware may enter fault state after system power cycle with an SSD drive (SCGCQ00835227)

- Fixed an issue where firmware may fault and RSOD may occur when a Virtual Drive is deleted when a Reconstruction is in progress on a PI-enabled VD combined with a slow initialization on another Virtual Drive (SCGCQ00872263)

- Fixed an issue where firmware doesn't report no SMART error when a Predictive-Failure Analysis (PFA) drive is present (SCGCQ00841772)

- Fixed an issue where firmware may not detect inserted drives (SCGCQ00876142)



Enhancements:

- Added support for restarting Patrol Reads after they are interrupted by a Consistency Check (SCGCQ00883176)

- Added ability to enable and disable 1M IO support via controller property (SCGCQ00893029)

- Added support for Task Management for JBOD/sysPDs (SCGCQ00855457)

- Reduced Command Block latency during Background Operations (SCGCQ00865372)

- Added ability to not moe Write-back Virtual Drives to Write-through when Pinned Cache is less than 50% of available buffers (SCGCQ00852502)

- Updated iMR queue depth to 928 (SCGCQ00888862, SCGCQ00930846, SCGCQ00896497)

- Disabled SATA HOQ support for iMR controllers (SCGCQ00942547)

- Added Task Management support for JBOD/sysPD (SCGCQ00861819, SCGCQ00855457)

- Re-enabled 1M IO support (SCGCQ00874200)

- Added support for Event Reporting for SuperCap Health after Learn Cycles (SCGCQ00894455)








ibm_fw_sraidmr_1200-24_21_0-0112_linux_32-64_chg

============================
R E L E A S E N O T E S
============================

Broadcom Linux bnx2 and 10GigE Virtual Bus Drivers(VBD)

Version 2.2.5r
04/20/2016
Copyright (c) 2016 Lenovo Corporation
All rights reserved


NOTE:
These driver release information is the original from the vendor. They include multiple driver
change histories for multiple Linux Operating Systems. Some drivers may or may not
pertain to all Linux Operating Systems but are part of this file for references.

====================================================================================================

**********************************************************************************************
**********************************************************************************************



Original file from Vendor... BNX2



**********************************************************************************************
**********************************************************************************************


Release Notes
QLogic bnx2 Linux Driver
Version 2.2.5r
02/03/2017
QLogic cnic Linux Driver
Version 2.5.20n
02/03/2017

Copyright (c) 2004 - 2014 Broadcom Corporation
Copyright (c) 2014 - 2017 QLogic Corporation
All rights reserved

bnx2x
=====
Version 1.714.0 (Aug 26, 2016)
==============================
Internal FW 7.13.2

Fixes:
------
1. Problem: Wrong len_on_bd reported for pure ACK packets, when TPA
and vlan stripping enabled.

Change: (FW) Fix packet padding flow.

Introduced: 1.70.06.

Relevance: LRO/GRO.

2. Problem: CQ84538 - SFP+ 2 wire management interface tBUF timing
violation.

Change: Fix the timing by adding software delay.

Introduced: Day 1.

Relevance: SFP.

3. Problem: CQ80835 - Link status incorrect for specific AOC cable.

Change: Identify specific AOC cable correctly.

Introduced: Day 1.

Relevance: SFP.

4. Problem: CQ84541 - Switch side Link is up when the optical cable of the
card receiver side is broken at power on.

Change: Enable MAC if module is attached.

Introduced: Day 1.

Relevance: SFP.

Enhancements:
-------------
1. Request: Allow vlan device creation while base interface is DOWN.

bnx2x
=====
Version 1.713.06 (Mar 22, 2016)
===============================
Internal FW 7.13.1

Fixes:
------
1. Problem: BZ1300681 [RH] - Parity recovery under traffic is very long.

Change: Don't wait for Tx completions on recovery.

Introduced: Day 1.

Relevance: All.

bnx2fc
======
Version 2.10.3 (March 23, 2016):
================================

Fixes & Features
================

1. Problem: Cont00085342 - host reboots while running interop
Cause: Try to return a request back to the SCSI layer that was already offlined.
Change: Check

bnx2 2.2.5p (Sept 17, 2015)
==========================
Enhancements
------------

1. Change: CQ81835 - Add rhel7.2 support

Impact: N/A

Fixes
-----

1. Problem: CQ82198 - SLES11SP4-getting error message 'unsupported' as
loading cnic driver from package 7.13.02

Cause: Missing Module.supported file in the package as the build
did not happen on primary build server

Change: Build another package using primary build server

Impact: SLES11SP4

cnic 2.5.20i (June 16, 2015)
=============================
Enhancements
------------

1. Change: Add the interfaces to get FC-NPIV table

Impact: N/A

bnx2 2.2.5m (January 20, 2015)
================================
Enhancements
-----
1. Change: Merge re-branding changes to the main branch.

Impact: N/A

Fixes
-----

1. Problem: Out of memory issue when the adapter is reset. This was reported by a customer.

Cause: kmalloc() failure in bnx2_gunzip_init() during memory fragmentation conditions
(~40K contiguous physical memory is not available).

Change: Use vmalloc() instead of kmalloc() for uncompressing the firmware buffer.


2. Problem: UDP packets cannot pass to the upper application, packets are filtered out by
our driver or firmware.

Cause: SORT mode was enabled in the code to fix a WOL issue on adapter series 5706/5708.


Change: We have found that disabling SORT mode in chip_init routine fixes the issue reported.
We have verified WOL is functioning on 5709/5716 adapters after disabling SORT mode
in chip_init.


cnic 2.5.20e (January 20, 2015)
============================
Enhancements
------------
1. Change: Merge re-branding changes to the main branch.

Impact: N/A


bnx2 2.2.5lr (September 05, 2014)
================================
Fixes
-----

1. Problem: Fix compilation warnings in newer kernels due to changes introduced in RHEL6.6 support.

Cause: Warnings due to incompatible pointer type initialization because netdev_features_t is 64-bits
in newer kernels whereas in RHEL6.6 kernel it is defined to 32-bit.

Change: Change Makefile to look for netdev_features.h to define netdev_features_t as appropriate.
Also added check to prevent calling set_netdev_ops_ext() API since kernel expects not to mix
ndo_fix_features/ndo_set_features with ethtool_ops.

Impact: Added fixes for RHEL6.6 and newer kernel.

bnx2 2.2.5kr (September 3, 2014)
===============================
Fixes
-----

1. Problem: Fix compilation errors in RHEL6.6.

Cause: Rearrangement of new hw_features flag with the introduction of new structure net_device_ops_ext and APIs
and multiple redefinitions.

Change: Added checks to avoid multiple redefinitions of APIs. The features and hw_features are assigned and
get_netdev_hw_features() and set_netdev_hw_features() for RHEL6.6 specific checks.

2. Problem: Fix netdev features for newer kernels.

Cause: hw_features in netdev for newer kernels was not getting set.

Change: hw_features field in nedev needs to be set for user selectable features. Added NETIF_F_RXCSUM
flag in hw_features and features field of netdev to change rx checksum using ethtool.

Impact: Added support for RHEL6.6 and newer kernel.

bnx2 2.2.5jr (August 21, 2014)
===========================
Enhancements
-----
1. Change: As part of re-branding Linux bnx2 driver, removed NetXtreme II/NX2/Nx2 keywords

Impact: N/A

cnic 2.5.20dr (August 21, 2014)
============================
Enhancements
------------
1. Change: As part of re-branding Linux cnic driver, removed NetXtreme II/NX2/Nx2 keywords

Impact: N/A

bnx2 2.2.5ir (July 30, 2014)
===========================
Enhancements
-----
1. Change: Added re-branding changes for Linux bnx2 driver

Impact: N/A

cnic 2.5.20cr (July 30, 2014)
============================
Enhancements
------------
1. Change: Added re-branding changes for Linux cnic driver

Impact: N/A

cnic 2.5.20c (July 29, 2014)
============================
Enhancements
------------
1. Change: (CQ74977) Fix Xenserver6.5 compilation warning warning: "rcu_access_pointer" redefined

Impact: N/A

bnx2 2.2.5i (July 22, 2014)
===========================
Enhancements
------------
1. Change: (CQ74921)Revert changes for Broadcom re-branding for Linux bnx2 &
cnic OOB drivers

Impact: N/A

cnic 2.5.20b (July 22, 2014)
============================
Enhancements
------------
1. Change: (CQ74921)Revert changes for Broadcom re-branding for Linux bnx2 &
cnic OOB drivers

Impact: N/A

2. Change: Added upstream patch to sync up with upstream driver
cnic,bnx2i,bnx2fc: Fix inconsistent use of page size

The bnx2/bnx2x rings are made up of linked pages. However there
is an upper limit on the page size as some the page size settings
are 16-bit in the hardware/firmware interface. In the current code,
Some parts use BNX2_PAGE_SIZE which has a 16K upper limit and some
parts use PAGE_SIZE. On archs with >= 64K PAGE_SIZE, it generates
some compile warnings. Define a new CNIC_PAGE_SZIE which has an
upper limit of 16K and use it consistently in all relevant parts.

Impact: FCoE, iSCSI

Fixes
-----

1. Problem: (CQ74840) Compilation Error in cnic driver for RHEL 6.3 and
SLES 11.1

Cause: Undefined rcu_access_pointer in RHEL 6.3 and SLES 11.1

Change: cnic need to use rcu_access_pointer to obtain the object reference
but this routine is not defined in older RHEL and SLES distros.
Added call to rcu_access_pointer using macro for RHEL 6.3 and
SLES 11.1

Impact: iSCSI and FCoE

2. Problem: Compilation failure in cnic driver for RHEL 6.5

Cause: Undefined enum _DEFINE_SKB_SET_HASH and skb_set_hash() in RHEL 6.5.

CNIC driver includes bnx2x.h header file. There were some changes
made in bnx2x driver using enum _DEFINE_SKB_SET_HASH and
skb_set_hash() API. As a result of this change the cnic build
failed due to those missing definitions.

Change: Added enum _DEFINE_SKB_SET_HASH and skb_set_hash() in
bnx2_compat.h under a new define D_DEFINE_SKB_SET_HASH. In the
Makefile, add a rule to check if skb_set_hash() is defined in
skbuff.h. If not, then D_DEFINE_SKB_SET_HASH is added to the
EXTRA_CFLAGS which would pickup the definitions from
bnx2_compat.h.

Impact: bnx2, iSCSI and FCoE

3. Problem: (CQ74942)Kernel panic on CNIC driver load on sles12

Cause: Bug in kernel version code check

Change: Use proper version check macro

Impact: bnx2, iSCSI and FCoE on sles12

bnx2 2.2.5h (June 24, 2014)
===========================
Enhancements
-----
1. Change: (CQ74364)Re-branding for Linux bnx2 driver

Impact: N/A

cnic 2.5.19e (June 24, 2014)
============================
Enhancements
------------
1. Change: (CQ74364)Re-branding for Linux cnic driver

Impact: N/A

package 2.710.52 (June 18, 2014)
============================
Fixes
-----
1. Problem: cnic module does not compile on Xen/REHL5 kernels

Cause: rcu_access_pointer macro is not part of Xen/RHEL5 kernels.

Change: (CQ74100) Define the macro rcu_access_pointer in
the driver code if required.

Impact: Xen/REHL5 kernels

2. Problem: (CQ74192) bnx2.c:4387: warning: assignment discards
qualifiers from pointer target type

Cause: N/A

Change: Cast the pointer as required

Impact: N/A

bnx2 2.2.5g (June 11, 2014)
===========================
Fixes
-----
1. Problem: (CQ74192)bnx2.c:8478:11: warning: unused variable " while
compiling QLogic bnx2 Gigabit drivers.

Cause: N/A

Change: Remove unused variable

Impact: N/A

cnic 2.5.19d (June 11, 2014)
============================
Enhancements
------------
1. Change: (CQ74187) Use proper netdev API for abstracting netdev upon
receiving any netdev event

Impact: N/A

Fixes
-----

1. Problem: (CQ73766, RHEL BZ1079384) bnx2fc: kernel BUG: sleeping function called from
invalid context

Cause: cnic_rcv_netevent() calls ulp_ops->indicate_netevent() under a rcu_read_lock(), that
makes the context atomic and bnx2fc_indicate_netevent() takes a mutex. Hence the
sleeping-in-atomic causing call trace.

Change: Because the called function, such as bnx2fc_indicate_netevent(), can sleep,
we cannot take rcu_lock(). To prevent the rcu protected ulp_ops from going away,
we use the cnic_lock mutex and set the ULP_F_CALL_PENDING flag.
The code already waits for ULP_F_CALL_PENDING flag to clear in cnic_unregister_device().

Impact: FCoE

2. Problem: (CQ73766, RHEL BZ1094613) ifdown/ifup repeatedly on a fcoe interface
causes call trace in cnic_alloc_uio_rings

Cause: We are allocating memory with GFP_KERNEL under spinlock.

Change: Don't take cnic_dev_lock in cnic_alloc_uio_rings(). Since this is the only call
manipulating the cnic_udev_list and it is always under rtnl_lock, cnic_dev_lock
can be safely removed.

Impact: FCoE

3. Problem: (CQ73766) Fix missing ISCSI_KEVENT_IF_DOWN message

Change: The iSCSI netlink message needs to be sent before the ulp_ops is cleared as it
is sent through a function pointer in the ulp_ops. This bug causes iscsid to not
get the message when the bnx2i driver is unloaded.

Impact: iSCSI

4. Problem: (CQ74100/BZ1087813) suspicious RCU usage in cnic driver

Cause: Calling rcu_dereference without rcu_read_lock.

Change: cnic need to access the object protected using rcu lock.
If rcu_dereference is called without proper read_rcu_lock,
RCU debug print stack with suspicious lock issue. If there is a need to access the
object without read lock rcu_access_pointer need to be used instead.

Impact: iSCSI and FCoE

cnic 2.5.19c (May 14, 2014)
============================
Enhancements
------------
1. Change: Added support for UFP FCOE

Impact: FCoE in UFP mode only.

Fixes
-----
1. Problem: (CQ73854)No LUNs discovered in UFP mode, (CQ73853)Kernel
stack trace at scsi_eh_2 in UFP mode, (CQ73820)bnx2x
driver asserted with driver v7.10.35

Cause: FCP command is going out with VLAN ID 0 (Null VLAN ID).
The VLAN tag was missing from the FCP packet as VLAN flag
was set to zero in offload_connection and enable_connection
ramrods.

Change: vlan_flag in the fcoe_kwqe_conn_offload3 should be set to 1 before
sending offload_connection and enable_connection ramrods. Removed
code block clearing vlan_flag in fcoe_kwqe_conn_offload3 before calling
offload_connection in UFP mode.

Impact: FCoE in UFP mode only.

cnic 2.5.19b (Mar 05, 2014)
============================
Enhancements
------------
1. Change: Add support for FCoE in UFP mode according to the UFP HSI.
The support is transparent to bnx2fc.

Impact: FCoE in UFP mode only.

package 2.710.10 (Feb 25, 2013)
===============================
Fixes
-----
1. Problem: Package does not compile on newer kernels

Cause: kernel compatibility issue.

Change: Added new CFLAGS from bnx2x Makefile for bnx2x_compat.h.

Impact: Newer distributions such as RHEL7.

bnx2 2.2.5f (Feb 20, 2014)
===========================
Fixes
-----
1. Problem: (CQ72407) "shutdown -h now" causes NMI on 5709 in some scenarios.

Cause: If the function has not been brought up (ifup), system shutdown
will cause a WAIT3 and D3 sequence without prior chip reset.
This may cause the firmware to power down the PHY which will
cause the function to become unresponsive to MMIO reads. The
CPU will timeout and NMI as a result.

Change: Added some logic to tell firmware to skip the PHY power down.

Impact: 5709 only. Only ifdown and system shutdown sequences are
affected. No run-time impact.

bnx2 2.2.5e (Feb 05, 2014)
===========================
Enhancements
------------
1. Change: Indication if the driver is beta or release in a printk
upon firmware dump.

Impact: ESX only.

cnic 2.5.18d (Feb 05, 2014)
============================
Fixes
-----
1. Problem: (CQ72694) Crash in bnx2x_cnic_notify() when getting iSCSI
statistics.

Cause: Calling bnx2i_get_stats() after bnx2i has unregistered the device.

Change: cnic should use the per device RCU protected cp->ulp_ops[] when
making the upcall to get statistics. It was incorrectly
using the global cnic_ulp_tbl which is always valid even if
individual devices have been unregistered.

Impact: iSCSI and FCoE

bnx2 2.2.5d (Jan 14, 2014)
===========================
Fixes
-----
1. Problem: (CQ71941) Kernel panic when loading bnx2 driver on RHEL6.5 with
inbox cnic driver loaded.

Cause: Incompatibility with inbox cnic driver.

Change: Added padding in bnx2 structure so that the inbox cnic driver
will always detect NULL in the cnic_probe field.

Impact: RHEL6.5 and newer kernels (SLES11SP3 is not affected)

bnx2 2.2.5c (Jan 06, 2014)
===========================
Enhancements
------------
1. Change: Added ability to read PCI config registers and indirect memory
via the ESX private IOCTL.

Impact: bnx2 ESX only.

2. Change: Add reporting of MDI/MDIX status to ethtool.

Impact: Copper devices only.

bnx2 2.2.5b (Nov 18, 2013)
===========================
Fixes
-----
1. Problem: (CQ71793) 5709 sometimes does not link up in 100Mbps forced
speed.

Cause: PHY advertisement register needs to be set to 0 when speed is
forced. The default advertisement register value is 10 Mbps
and it will not link up when the speed is 100 Mbps.

Change: Set advertisement register to 0 when speed is forced.

Impact: 5709C forced speed.

bnx2 2.2.4g (Nov 07, 2013)
===========================
Fixes
-----
1. Problem: PHY loopback test fails when set to 100Mbps on 5708 Copper.

Cause: Regression caused by enabling auto-MDIX (PHY reg 0x18 shadow 7
bit 9).

Change: Disable it on 5708.

Impact: 5708 only.

bnx2 2.2.4f (Oct 29, 2013)
===========================
Fixes
-----
1. Problem: Netqueue didn't get stop and re-initialized properly during
reset task, change coalece setting, and self test operations.

Cause: Normal Netqueue stop and re-initialized operations weren't
executed while the device went through a full reset.

change: Added proper Netqueue stop/start operations in the above
code paths.

Impact: ESX only.

cnic 2.5.18c (Oct 29, 2013)
============================
Enhancements
------------
1. Change: Add signature to the iSCSI TX doorbell to prevent iscsiuio
from getting the wrong value when using older kernel
drivers.

Impact: bnx2x iSCSI only.

bnx2 2.2.4e (Oct 23, 2013)
============================
Enhancements
------------
1. Change: (CQ69514) Enable auto-MDIX when autoneg is disabled by
setting copper PHY register 0x18 shadow 7 bit 9.

Impact: All bnx2 copper devices.

2. Change: Display driver version in vmkernel.log during ESX fw dump.

Impact: ESX only.

package 2.78.33 (Sept 23, 2013)
===============================
Fixes
-----
1. Problem: Package does not compile on Xen Server 6.2

Cause: kernel compatibility issue.

Change: Added new CFLAGS from bnx2x Makefile for bnx2x_compat.h.

Impact: All distributions. These fixes are only compatible with bnx2x
1.78.56 and newer.

bnx2 2.2.4d (Sept 12, 2013)
============================
Fixes
-----
1. Problem: cnic irq failed to run after esxcli network nic down/up
event.

Cause: esxcli network nic down/up event causes bnx2 driver go
through bnx2_close and bnx2_open. The sequence of events
will re-allocate status block memory and the new status
block memory address is not communicated to cnic after
bnx2_open.

Impact: bnx2 ESX only.

cnic 2.5.18b (Sept 12, 2013)
============================
Fixes
-----
1. Problem: iSCSI does not work with bnx2x 1.78.52.

Cause: bnx2x doorbell change not compatible with existing iscsiuio.

Change: Pass modified iSCSI CID to iscsiuio for backwards
compatibility.

Impact: bnx2x iSCSI.

2. Problem: Panic in cnic after ifdown/ifup bnx2x iSCSI device.

Cause: Accessing uninitialized FCoE EQ. Bug introduced in 2.5.17c
which started using bnx2x NO_FCOE macro. cnic did not
consistently use NO_FCOE, causing FCoE EQ to be accessed
by mistake.

Change: Use NO_FCOE macro consistently in cnic code.

Impact: FCoE.

bnx2 2.2.4c (Aug 30, 2013)
============================
Enhancements
------------
1. Change: Fix compile errors see on ESX
* struct chip_core_dmp definition conflicts with bnx2x,
scoped this struct to have a bnx2 prefix
* Compiled FW dump for ESX5.5

Impact: bnx2 ESX only.

cnic 2.5.17c (Aug 30, 2013)
============================
Fixes
-----
1. Problem: cnic crash when shutting down 57811 device.

Cause: 57811 Chip ID not reconized by cnic.

Change: Re-structured code to use common bnx2x macros for Chip ID,
port ID, pfid.

Impact: iSCSI and FCoE on all bnx2x devices.

bnx2 2.2.4b (Aug 12, 2013)
============================
Fixes
-----
1. Problem: CQ70286 IOVP: PSOD while executing NIC up/down command using
esxcli.

Cause: New bnx2_free_irq() also disable MSIX/MSI on the device during
bnx2_close. When bnx2_open is called, driver attempt to
get INTA interrupt instead of MSIX/MSI interrupt.

Change: Don't disable MSIX/MSI on the device upon close.

Impact: ESX only.

2. Problem: WoL does not work during suspend if device is not up.

Cause: WoL setup skipped in bnx2_suspend() if device is not up.

Change: Always setup WoL in bnx2_suspend().

Impact: bnx2 suspend.

Enhancements
------------
1. Change: Update 5709 firmware to 6.2.1.c to include mechanism to
flush the iscsi OOO ring to silence some error messages
about stale hardware index.

Impact: bnx2 iSCSI.

cnic 2.5.17b (Aug 12, 2013)
============================
Enhancements
------------
1. Change: Improved iSCSI license fix implemented in cnic 2.5.16j.

Impact: iSCSI on these bnx2x devices where the iSCSI license can only be
fully determined after firmware is loaded.

2. Change: Changes to match the new 5709 6.2.1.c firmware to flush the
iSCSI OOO ring.

Impact: 5709 iSCSI.

bnx2 2.2.3t (July 23, 2013)
============================
Fixes
-----
1. Problem: CQ70262 IVOP: PSOD HeavyIOChangeMTU test on 5709 card.

Cause: During ring size change, bnx2_free_irq() was called without
checking reset_irq flag.

Change: Don't call bnx2_free_irq() if reset_irq flag is false.

Impact: ESX only.

2. Problem: (CQ69619) ethtool NVRAM operations fail when device is down.

Cause: Driver checks and prevents NVRAM operations when device is down.

Change: Remove the check. The driver now stays in D0 power state when
the device is down and NVRAM operations are possible.

Impact: ethtool -e|-E

cnic 2.5.16j (July 23, 2013)
=============================
Fixes
-----
1. Problem: (RHEL BZ 759217) System hangs when attempting iSCSI connections
on 57711E.

Cause: iSCSI license changes from supported to unsupported between
bnx2x probe and bnx2x open. bnx2i is unaware that the device
does not support iSCSI and attempts to do offload which never
completes. The recent change to eliminate symbol_get() to
obtain bnx2x_cnic_probe() exposed the problem.

Change: Check iSCSI license again during ->drv_register_cnic(). If
there is no iSCSI license, skip ->ulp_start().

Impact: iSCSI on these bnx2x devices where the iSCSI license can only be
fully determined after firmware is loaded.

bnx2 2.2.3s (June 27, 2013)
============================
Fixes
-----
1. Problem: PCI shutdown function does not work on ESX.

Cause: system_state and SYSTEM_POWER_OFF not defined.

Change: Added compatibility code.

Impact: ESX only.

bnx2 2.2.3r (June 27, 2013)
============================
Enhancements
------------
1. Change: (CQ68271, 68277) In order to support ethtool NVRAM operations
when the device is down, the following changes were made:

- converted to use new WoL and PM kernel APIs
- removed power state changes during open and close
- added pci shutdown function to setup WoL during shutdown
- converted to new style suspend/resume driver APIs

Impact: Everything related to WoL, shutdown, suspend, resume. Because
of the significant changes, the system should be rebooted after
running "make install" for the new driver. Without reboot,
the new driver may not work as it is not aware that the older
driver has put the device into D3hot state.

bnx2 2.2.3q (May 24, 2013)
============================
Enhancements
------------
1. Change: Simplified compatibility code for driver section macros,
__devinit, __devexit, etc.

Impact: None.

bnx2 2.2.3p (May 23, 2013)
============================
Fixes
-----
1. Problem: Bootcode firmware may not detect new message from driver.
(VMWare reported issue)

Cause: The initial sequence number may not be unique enough.

Change: Read from the firmware mailbox and add one to it as the initial
sequence number.

Impact: All devices.

Enhancements
------------
1. Change: Made changes to compile on the latest 3.x kernels.

Impact: All.

cnic 2.5.16i (May 23, 2013)
=============================
Fixes
-----
1. Problem: (CQ69177) MTU change causes PSOD at bnx2x_drv_ctl

Cause: The OOO handler was falsely triggered to handle OOO tx
completions even when bnx2x has failed to allocate resources
for the OOO ring. This has caused bnx2x to hit a NULL
ptr dereference.

Change: Fixed the cnic OOO handler.

Impact: bnx2x iSCSI only.

cnic 2.5.16h (April 30, 2013)
=============================
Enhancements
------------
1. Change: Added max_fcoe_exchanges parameter so that bnx2fc can support
multiple FCoE ports on a device.

Impact: FcoE only.

bnx2 2.2.3o (April 30, 2013)
============================
Fixes
-----
1. Problem: (BDKL225) __napi_schedule assertion when bnx2 switch from
MSI to INTx.

Cause: NAPI was not disabled before IRQ is freed when switching from msi
mode to INTA mode which prevents VMkernel from updating the stale
napi->intr_cookie value.

Change: Disabled NAPI before free IRQ and then re-enable NAPI after
chip is re-initialized. In addition, enabling of NAPI should
always be done after chip_init().

Impact: All.

bnx2 2.2.3n (Mar 11, 2013)
==========================
cnic 2.5.16g (Mar 11, 2013)
==========================
Fixes
-----
1. Problem: cnic driver does not compile on XEN server.

Cause: Shared bnx2x_compat.h relies on some CFLAGs to compile properly
on XEN server.

Change: Added the proper CFLAGs to the Makefile.

Impact: None.

cnic 2.5.16f (Jan 31, 2013)
===========================
Fixes
-----
1. Problem: (CQ67220) bnx2x firmware assert during "Random TCP errors" test.

Cause: Firmware bug and cnic error handling bug for TCP_CLOSE ramrod.

Change: Added check for iscsi completion error when receiving the
TCP_CLOSE ramrod completion.

Impact: bnx2x iSCSI only.

bnx2 2.2.3m (Jan 28, 2013)
==========================
cnic 2.5.16e (Jan 28, 2013)
===========================
Fixes
-----
1. Problem: (CQ67528) cnic/bnx2 crash when both drivers are loaded on
some kernels.

Cause: Shared struct bnx2 compiled differently on bnx2 and cnic,
causing cnic to reference the wrong field.

Change: Added bnx2_compat0.h to define the common CFLAGs that affect
structure sizes for both drivers to include.

Impact: All (if cnic is loaded)

bnx2 2.2.3k (Jan 25, 2013)
==========================
Fixes
-----
1. Problem: CNIC driver didn't get started after bnx2_open().

Cause: CNIC driver is stopped when bnx2_close() is invoked.
However, there is no equivalent turn on mechanism when
bnx2_open() is called. The issue prevent bnx2i to offload
iscsi connections during session recovery.

Change: Added equivalent cnic start procedure in bnx2_open().

Impact: ESX only.

cnic 2.5.16d (Jan 25, 2013)
===========================
Fixes
-----
1. Problem: (CQ67375) Unable to turn iSCSI TCP delayed ACK on after it's
been turned off.

Cause: tcp_flags in cnic's socket structure not cleared between destroy
and create calls.

Change: Clear tcp_flags during socket create call.

Impact: iSCSI only.

2. Problem: (CQ67306) iSCSI TCP delayed ACK not working.

Cause: Firmware HSI change.

Change: Adapted to new firmware HSI which is now defining delayed ACK
globally for the HBA.

Impact: iSCSI only.

cnic 2.5.16c (Jan 15, 2013)
===========================
Fixes
-----
1. Problem: cnic does not compile on SLES11SP2.

Cause: bnx2x_compat.h conflicts with SLES11SP2 header files.

Change: Modilfed Makefile to detect SLES distribution so that the
proper CFLAG can be defined for bnx2x_compat.h

Impact: SLES distributions only.

cnic 2.5.16b (Dec 12, 2012)
===========================
bnx2 2.2.3j (Dec 12, 2012)
==========================
Enhancements
------------
1. Change: (CQ60429, 66302) Simplify cnic probing by not using symbol_get().
symbol_get() is unreliable as it fails while the network driver
is still initializing.

Impact: iSCSI and FCoE (driver loading and unloading).

cnic 2.5.14d (Nov 13, 2012)
===========================
Fixes
-----
1. Problem: (CQ64479) bnx2x assert running iSCSI async logout test.
bnx2fc.

Cause: Race condition during simultaneous remote reset and local
TCP close/reset. This may be a partial fix and additional
fixes in other areas/drivers may be necessary to completely
address all symptoms.

Change: If remote reset is detected to be in progress during local
close/reset, it will wait for outstanding RAMRODs to complete.
Without the wait, bnx2i will proceed to destroy the connection
while the SRCH_DELETE/TERM_OFFLOAD RAMRODs are still pending.

Impact: bnx2x iSCSI only.

bnx2 2.2.3i (Nov 05, 2012)
==========================
Enhancements
------------
1. Change: (CQ65960) Make minor compatibility changes to support RHEL6.4

Impact: None.

2. Change: Added support for latest 3.x kernels.

Impact: All supported kernels.

cnic 2.5.14c (Nov 05, 2012)
==========================
Fixes
-----
1. Problem: (CQ65178) Panic when loading and unloading cnic with bnx2i and
bnx2fc.

Cause: The iSCSI EQ does not get reset during cnic init. When we
get the first cnic IRQ, the iSCSI EQ index may be non-zero
in the status block, causing the cnic driver to dereference
NULL pointer.

Change: Added code to clear the iSCSI EQ index in the STORM memory.

Impact: 10G iSCSI.

bnx2 2.2.3h (Oct 16, 2012)
==========================
Fixes
-----
1. Problem: Netdump crash when runing with ESX6.0 OS.

Cause: bnx2 poll controller routine is not compatible with
ESX6.0.

Change: For ESX6.0, bnx2 will use ESX poll controller for
netdump.

Impact: ESX6.0.

bnx2 2.2.3g (Oct 09, 2012)
==========================
Fixes
-----
1. Problem: [bnx2] PSOD: Failed at vmkdrivers/src_92/vmklinux_92/
vmware/linux_net.c:3351 -- VMK_ASSERT(VMK_FALSE).

Cause: There is race condition where netdev_watchdog() could
erroneouly flag tx timeout in a small window when
bnx2_netif_stop() disabled tx queue state while carrier
is still on.

Change: Carrier must be turned off before netif_tx_disable() is
called.

Impact: Linux and ESX.

bnx2 2.2.3f (Oct 04, 2012)
==========================
Enhancements
------------
1. Change: Convert remaining iounmap() call to pci_iounmap() call.

Impact: None.

cnic 2.5.14b (Oct 04, 2012)
==========================
Fixes
-----
1. Problem: (CQ65250) Unloading bnx2x before unloading cnic with IOMMU
enabled causes panic.

Cause: Trying to free UIO DMA memory after the PCI device has been
unregistered.

Change: Free UIO DMA memory after the uio device has been closed.
Impact: iSCSI only.

bnx2 2.2.3e (Aug 27, 2012)
==========================
Fixes
-----
1. Problem: ESX 6.0 compile errors seen when disabling NetQueue

Cause: Unused variables were defined in the non-NetQueue path

Change: Clean up code to compile on ESX6.0 inbox

Impact: ESX only


2. Problem: ESX 6.0 firmware dump missing 1 dword.

Cause: MCP dump size is incorrect.

Change: Use correct MCP dump size.

Impact: ESX 6.0 only

cnic 2.5.12e (Aug 22, 2012)
==========================
Fixes
-----
1. Problem: (CQ 65270): bnx2x IRQ assert on 57712 and newer devices that
support iSCSI only.

Cause: Not arming IRQ properly when detecting that the device does not
support FCoE. Regression from cnic 2.5.12c enhancement #3.

Change: Added function pointer to arm IRQ correctly based on chip type.

Impact: iSCSI and FCoE on all 10G devices.

cnic 2.5.12d (Aug 21, 2012)
==========================
Fixes
-----
1. Problem: (CQ 65249): cnic panic on functions that support FCoE only.

Cause: Code accessing iSCSI resources that aren't initialized or
allocated on functions that don't support iSCSI.

Change: Check for valid UIO resource before trying to free it. Always
initialize iSCSI OOO resources.

Impact: 10G iSCSI and FCoE.

bnx2 2.2.3d (Aug 15, 2012)
==========================
Fixes
-----
1. Problem: (CQ 65163): unhandled NETQUEUE messages 16 and 17
seen in vmkernel logs

Cause: Not properly handling unsupported NetQueue ops

Change: Properly handle the NetQueue ops 16 and 17 without
printing the warning message

Impact: ESX only

Enhancements
------------
1. Change: Try to recover from PCI block reset during TX timeout.
Red Hat users have reported PCI block resets that could
not be recovered during tx timeout.

Impact: None.

2. Change: Added mk_kernel_patch.sh to patch bnx2 driver into kernel tree.

Impact: None.

cnic 2.5.12c (Aug 15, 2012)
==========================
Enhancements
------------
1. Change: Added firmware dump support for ESX6.0.

Impact: ESX6.0.

2. Change: Reduced maximum iSCSI abort delay to 5 seconds

Impact: iSCSI

3. Change: Allocate FCoE or iSCSI resources on a cnic only if the
device supports the protocol. This will reduce memory
consumption on multi-function devices.

Impact: iSCSI and FCoE

bnx2 2.2.3c (July 09, 2012)
==========================
Fixes
-----
1. Problem: Unmapping the wrong DMA address in bnx2_free_tx_skbs() in
rare cases.

Cause: Not skipping the last entry in the tx BD ring.

Change: Use the proper macro to get the next BD entry.

Impact: On systems with IOMMUs enabled, the bug can be triggered when
doing resets (ifdown, MTU change) during heavy TX traffic.

cnic 2.5.12b (July 03, 2012)
=============================
Enhancements
------------
1. Change: Updated to bnx2x firmware 7.4.8 HSI for TX BDs.

Impact: iSCSI on all bnx2x devices.

cnic 2.5.11d (June 28, 2012)
=============================
Fixes
-----
1. Problem: Kernel panic under iSCSI OOO condition.

Cause: Bug in cnic when max OOO resource is reached

Change: Initailized packet descriptor to fix the bug.

Impact: iSCSI only.

bnx2 2.2.3b (June 29, 2012)
==========================
Fixes
-----
1. Problem: Compile error in RHEL6.x kernel and similar kernels.

Cause: skb_frag_size() compatibility code not detected properly.

Change: Fixed Makefile to detect it from skbuff.h

Impact: None.

bnx2 2.2.2b (June 24, 2012)
==========================
Fixes
-----
1. Problem: (CQ63682)PSOD in ESX upon device open.

Cause: NAPI was not disabled properly upon device close.
Thus, ASSERT occurs upon reopening device.

Change: Add NAPI disable upon close and add netif_tx_disable
for both linux and ESX build.

Impact: bnx2.

2. Problem: Enableing RSS interferes with RX NETQ feature when
compiled for ESX build.

Cause: RSS is enabled by default in bnx2. The RSS feature
will lead to firmware bypass NETQ code path.

Change: Disable RSS by default when compiled for ESX.

Impact: ESX.

Enhancements
------------
1. Change: Partial sync-up with upstream driver. Please see Changelog.

Impact: All

cnic 2.5.11c (June 12, 2012)
=============================
Fixes
-----
1. Problem: (CQ62298 Partial fix) When running in INTA mode, MTU change
does not work. iSCSI/FCoE does not resume after MTU change.

Cause: During mtu change, bnx2x does not know that cnic is no longer
handling IRQs.

Change: Added a new flag to let bnx2x know that cnic is no longer
handling IRQ during reset.

Impact: bnx2x iSCSI and FCoE.

2. Problem: (CQ62937) bnx2x asserts during iSCSI test with corrupted
TCP NOP-IN.

Cause: Corrupted NOP-IN falls outside of TCP window, causing FW to
go into OOO mode. TCP close with outstanding OOO causes
problem and the close does not complete.

Change: FW change to return an error in this case and cnic driver
change to handle this error by proceeding to clean up the
connection.

Impact: bnx2x iSCSI.

cnic 2.5.11b (April 30, 2012)
=============================
Fixes
-----
1. Problem: (CQ62298 Partial fix) Fix for CQ62026 in cnic 2.5.9d introduced
a regression of clearing the CNIC_UP flag before all CIDs have
been deleted. The regression is causing warning messges that
some CIDs have not been deleted. After fixing this, we're
still encountering further bnx2x error messages in the INTA
code path.

Change: Wait for all CIDs to be deleted before clearing CNIC_UP flag.

Impact: iSCSI and FCoE on all bnx2x devices.

bnx2 2.2.1l (April 18, 2012)
============================
Fixes
-----
1. Problem: PSOD on ESX because of inconsistant NetQueue state
when the NetQueues are allocated/freed out of order

Cause: The forced freeing of the NetQueue before the
NetQueue allocation can cause the incorrect NetQueue
to be freed and marked incorrectly.

Change: Remove the freeing of the NetQueue in the allocation
path and allow the load balancer to control the
error path when NetQueue's could not be
allocated/freed.

Impact: ESX only.

cnic 2.5.10c (April 18, 2012)
=============================
Enhancements
------------
1. Change: Added iface_num parameter to cm_create() and
iscsi_nl_send_msg()to support bnx2i 2.7.2.2b.

Impact: iSCSI only.

bnx2 2.2.1k (April 04, 2012)
============================
Enhancements
------------
1. Change: Reduced code size of FTQ dump during tx_timeout.

Impact: None.

cnic 2.5.10b (April 04, 2012)
=============================
Enhancements
------------
1. Change: Added PCI pass through support for bnx2x E2/E3 devices.

Impact: bnx2x iSCSI/FCoE on E2/E3 devices.

bnx2 2.2.1j (Mar 07, 2012)
==========================
Enhancements
------------
1. Change: Added disable_msi_1shot parameter for debugging purposes.

Impact: VMWare only feature.

cnic 2.5.9d (Mar 07, 2012)
==========================
Fixes
-----
1. Problem: (CQ62026) NULL pointer dereference during cnic reboot test.

Cause: cp->ctx_tbl is NULL during cnic_ctl() call with COMPLETION_CMD.

Change: cnic is registered with the L2 drivers before we allocate
the cp->ctx_tbl so it is possible to get called while
cp->ctx_tbl is NULL. Added check for CNIC_UP flag before
proceeding to dereference cp->ctx_tbl. This together with
the RCU code will completely fix the problem.

Impact: iSCSI and FCoE on 10G.

bnx2 2.2.1i (Mar 06, 2012)
==========================
Fixes
-----
1. Problem: Driver doesn't build on SLES11.1-trace x32 kernel.

Cause: ARCH defined in Makefile conflicts with kernel tree scripts.

Change: Changed ARCH to __ARCH in Makefile

Impact: None.

bnx2 2.2.1h (Mar 05, 2012)
==========================
Fixes
-----
1. Problem: (CQ60393) Driver doesn't build in some RHEL-5.x distros with
just kernel-devel package installed.

Cause: Makefile does not include /usr/src/kernels/$(KVER)-$(uname -m)
in places to search.

Change: Added the additional path to check.

Impact: None.

cnic 2.5.9c (Feb 29, 2012)
==========================
Fixes
-----
1. Problem: (CQ61908) cnic does not compile on 3.x kernel.

Cause: Upstream patch titled:

ethernet/broadcom: ip6_route_output() never returns NULL.

backported carelessly.

Change: Fixed syntax errors.

Impact: 3.x kernel only.

cnic 2.5.9b (Feb 28, 2012)
==========================
Fixes
-----
1. Problem: (CQ61584) bnx2x asserts during middle-box iSCSI tests.

Cause: Middle-box test corrupts packets and causes iSCSI fw to
generate 0x4 (NIC_ERR) completion code. This conflicts
with new logic that uses NIC_ERR to convey parity error.

Change: Redefined parity error completion code to be 0x81 for
L4, iSCSI, and FCoE.

Impact: FCoE and iSCSI.

bnx2 2.2.1g (Feb 28, 2012)
==========================
Fixes
-----
1. Problem: Calling of bnx2_vlan_rx_kill_vid() is not rtnl_lock
protected.
Change: hold rtnl_lock when execute this routine under ESX4.0
and ESX4.1.
Impact: ESX4.0/4.1 only.

Enhancements
------------
1. Change: Added MSI-X table printout during tx timeout.

Impact: None.

bnx2 2.2.1f (Feb 8, 2012)
==========================
Fixes
-----
1. Problem: (CQ61327) Unable to pass traffic on RHEL5.x

Cause: bp->num_rx_rings not initialized due to backport errors. This
was introduced in 2.2.1e when adding ethtool -l|L support.

Change: Initialized bp->num_rx_rings to 1 on these older kernels.

Impact: RHEL5 and SLES10 only.

cnic 2.5.8f (Feb 06, 2012)
==========================
Enhancements
------------
1. Change: Added VLAN update from iscsiuio. This allows VLAN to be
specified in iface.

Impact: iSCSI only.

cnic 2.5.8e (Jan 24, 2012)
==========================
Enhancements
------------
1. Change: Enhanced FCoE parity recovery by sending immediate FW_DESTROY
completion with error during parity error recovery.

Impact: FCoE only.

bnx2 2.2.1e (Jan 24, 2012)
==========================
Enhancements
------------
1. Change: Added support for ethtool -[l|L]. Please refer to README.TXT
for details.

Impact: 5709 with support for MSIX only.

cnic 2.5.8d (Jan 19, 2012)
==========================
Enhancements
------------
1. Change: Enhanced FCoE driver registration to provide FCoE
capabilities to bnx2x driver.

Impact: Systems with Management support of these features. These
changes were made to match bnx2x 1.72.07.

2. Change: (CQ60867) Backed out earlier changes related to this CQ.
genksyms checksums are based on structure names and type
names, so the scheme of using an identical structure with
a different name will not work.

Impact: None.

cnic 2.5.8c (Jan 10, 2012)
==========================
1. Problem: (CQ60744) Lose connection to FCoE targets after parity error
recovery.

Cause: (Partial) DISABLE_CONN SPQ message does not complete, causing
delaying waiting for bnx2fc to timeout.

Change: Added immediate KCQ error completion for FCOE_DISABLE_CONN.
when SPQ fails.

Impact: FCoE.

2. Problem: (CQ60184) cnic parity error recovery fails (Part 2).

Cause: If a TCP connection fails due to parity error, termination
sequence does not follow the expedited error recovery path.
This causes unnecessary delay during parity error recovery.

Change: Set the HW_ERR bit when TCP connection fails due to SPQ
error. Termination will then follow the expedited error
recovery path.

Impact: iSCSI on bnx2x.

3. Problem: (CQ60867) Module versioning warning when installing cnic
driver on SLES11SP2 without matching bnx2i/bnx2fc.

Cause: cnic_register_driver() stub in cnic.c does not have
cnic_ulp_ops structure that matches inbox bnx2i/bnx2fc.

Change: Added dummy cnic_ulp_ops that match RHEL6.2 and SLES11SP2
structures.

Impact: None.

bnx2 2.2.1d (Jan 10, 2012)
==========================
Fixes
-----
1. Problem: PSOD seen in TX handling in either bnx2_tx_int()
or bnx2_start_xmit() routines

Cause: Memory re-ordering is occuring so that the TX BD is not
updated before the ringing of the TX doorbell.

Change: On ESX the wmb() macro is defined to only as a compiler
barrier. Redfine the wmb() macro to properly synchronize
memory using the sfence instruction.

Impact: ESX only.

cnic 2.5.8b (Jan 05, 2012)
==========================
Enhancements
------------
1. Change: Added CNIC_CTL_FCOE_ENHANCED_STATS_CMD and
CNIC_CTL_FCOE_CAPABILITIES_GET_CMD as stubs.

Impact: None.

cnic 2.5.7i (Dec 21, 2011)
==========================
Fixes
-----
1. Problem: (CQ60184) cnic parity error recovery fails.

Cause: SPQ errors during parity error recovery was not propagated to
L4 and ULP, causing unnecessary long timeouts.

Change: Added immediate KCQ error completion for L4 and iSCSI kwqes if
SPQ fails.

Impact: iSCSI on bnx2x.

bnx2 2.2.1c (Dec 21, 2011)
==========================
Fixes
-----
1. Problem: (CQ60281) BNX2 hang on ESX 4.1 when changing tx ring size
with Ethtool.

Cause: BNX2 set_ringparam() ethtool ops callback attempts to hold
rtnl_lock while vmlinux has already held this lock when
when invoking this callback. This leads to deadlock situation
and driver will hang forever.

Change: Make sure all ethtool ops callbacks don't hold rtnl_lock.

Impact: ESX only.

2. Problem: (BDKL87) PSOD in bnx2 start_xmit() path when stressing with
change ring size script on ESX 4.1u2.

Cause: When using ESX4.0/4.1u0-u2, the vmkernel doesn't not check
tx queue state properly in certain race condition. This can
lead to bnx2 start_xmit() to deference NULL tx buffer.

Change: check tx queue state before proceed with stat_xmit().

Impact: ESX4.0/4.1u0-u2.

cnic 2.5.7h (Dec 08, 2011)
==========================
Enhancements
------------
1. Change: Added iSCSI and FCoE driver status and counters support.

Impact: Systems with Management support of these features.

2. Change: Added upstream patches to sync up with upsteam driver:
net: treewide use of RCU_INIT_POINTER
net: remove ipv6_addr_copy()

Impact: None.

bnx2 2.2.1b (Dec 08, 2011)
==========================
Enhancements
------------
1. Change: Added several upstream patches to sync up with upsteam
driver:
net: treewide use of RCU_INIT_POINTER
bnx2: fix skb truesize underestimation
net: Remove unnecessary driver assignments of ethtool_ringparam fields to zero

Impact: None.

bnx2 2.1.12b (Oct 14, 2011)
===========================
Fixes
-----
1. Problem: (CQ59255) iSCSI warning messages appear and performance
drops when connected to a lefthand target.

Cause: Packets with invalid TTT generate warnings and exception
handling.

Change: Updated to 6.2.3 firmware for 5706 and 6.2.1.b for 5709

Impact: iSCSI

cnic 2.5.7g (Sep 23, 2011)
==========================
Enhancements
------------
1. Change: Added cnic_register_driver()/cnic_unregister_driver stubs
so that depmod will not return errors if native bnx2i/bnx2fc
drivers have not been updated.

Impact: None.

bnx2 2.1.11e (Sept 19, 2011)
===========================
Enhancements
------------
1. Change: Set the feature, NETIF_F_NO_SCHED, for ESX 5.0 and
greater releases only

Impact: ESX only

Fixes
-----
1. Problem: Compile errors on some older kernels.

Cause: Compatibility API pci_is_pcie() requires bool type which may
not be defined on older kernels.

Change: Moved bool type compatibility definition above pci_is_pcie().

Impact: None.

bnx2 2.1.11d (Aug 30, 2011)
===========================
Enhancements
------------
1. Change: Integrate Code Review Comments from VMware
* Add feature flag to reflect if a device is
compliant with network scheduling.
* Conditionally move bnx2 drivers to high memory
* Remove unused field/code

Impact: ESX only

2. Change: Remove unnecessary read of PCI_CAP_ID_EXP from upstream.

Impact: minor (5709 only).

cnic 2.5.7f (Sep 13, 2011)
=========================
Fixes
-----
1. Problem: Duplicate cp local variable in cnic_shutdown_rings().

Cause: Coding error.

Change: Removed duplicate variable.

Impact: None.

cnic 2.5.7e (Aug 8, 2011)
=========================
Fixes
-----
1. Problem: (CQ57498) System hangs during bnx2x parity error recovery.

Cause: cnic waits for RAMRODs to complete without timeout. During
parity error recovery, all DMAs will stop.

Change: Added timeouts to all RAMRODs.

Impact: iSCSI and FCoE on bnx2x

cnic 2.5.7d (July 28, 2011)
===========================
Enhancements
------------
1. Change: Increased the max number of FCoE sessions to 1024.

Impact: FCoE.

bnx2 v2.1.11c (July 26, 2011)
============================
Enhancements
------------
1. Change: Upstream sync to use ethtool_cmd_speed API.

Impact: None.

2. Change: Added memory barrier to sync transmit descriptor before updating
TX mailbox. We believe that this may fix some very rare panics
reported by VMWare.

Impact: bnx2 packet transmit.

cnic 2.5.7c (July 26, 2011)
===========================
Fixes
-----
1. Problem: FCOE_DESTROY_FUNC ramrod not completing, causing timeout
and OOO cleanup timeout during MTU change.

Cause: FCOE_DESTROY_FUNC was sent before all FCoE CIDs have been
deleted.

Change: Wait for all (2 seconds delayed) FCoE CFC_DELETE ramrods to
be completed before sending FCOE_DESTROY_FUNC.

Impact: FCoE only.


cnic 2.5.7b (July 19, 2011)
===========================
Enhancements
------------
1. Change: Re-instated vlan_id in ->indicate_netevent(). It is needed
by bnx2fc to handle NETDEV_UNREGISTER on VLAN devices.

Impact: bnx2fc.

2. Change: Allocate FCoE CID space only on E2+ devices.

Impact: None.

bnx2 v2.1.11b (July 19, 2011)
============================
Enhancements
------------
1. Change: Added tx_timeout error handling and made it common with
VMWare code.

Impact: bnx2 NETDEV WATCHDOG error handling

2. Change: Fix compile errors on the latest net-next upstream kernel.

Impact: compilation

cnic 2.5.6d (July 13, 2011)
===========================
Enhancements
------------
1. Change: Removed vlan_id from ->indicate_netevent().

Impact: None.

bnx2 v2.1.10d (July 12, 2011) cnic 2.5.6c (July 12, 2011)
=========================================================
Fixes
-----
1. Problem: Not compiling on 3.0.0 kernel.

Cause: Makefile not recognizing the 3.0.x kernel

Change: Modified Makefile and sync'ed with upstream drivers.

Impact: None.

bnx2 v2.1.10c (July 1, 2011)
============================
Fixes
-----
1. Problem: Not compiling on older kernels (such as RHEL5.4) and newer
kernels (such as 2.6.36)

Cause: Problems with compatibility code.

Change: Fixed compatibility code.

Impact: None.

bnx2 v2.1.10b (June 30, 2011)
============================
Enhancements
------------
1. Change: Added more complete MCP dump during error conditions.

Impact: None.

2. Change: Modified driver messages slightly to match upstream format
(by using netdev_printk, netdev_err, etc).

Impact: None.

Fixes
-----
1. Problem: Not reading iSCSI license on 570x devices reliably.

Cause: We were reading from the CP scratch pad before the CP firmware
is loaded.

Change: Read from MCP shmem location instead.

Impact: 1G iSCSI on bnx2 devices.

cnic 2.5.6b (June 30, 2011)
============================
1. Problem: (CQ56522, CQ56259) Unable to connect to iSCSI target, bnx2x
firmware assert during iSCSI connection

Cause: iSCSI L2 ring CID has been changed in bnx2x 1.70.14. uIP is
using a hardcoded value of 0x11.

Change: cnic now passes the CID to uIP.

Impact: iSCSI on bnx2x devices.

2. Problem: (CQ56230) Cannot compile on some 32-bit systems.

Cause: Passing 64-bit NULL pointer as 32-bit 0 dma_addr_t value.

Change: Use 0 instead of NULL for dma_addr_t values.

Impact: None.

cnic 2.5.5b (June 22, 2011)
============================
Enhancements
------------
1. Change: Added WWN info to cnic_eth_dev. This is a temporary solution
until ndo_fcoe_get_wwn() is implemented.

Impact: None.

bnx2 v2.1.9b (June 22, 2011)
============================
Enhancements
------------
1. Change: Added del_timer_sync() in bnx2_remove_one() from upstream
commit 8333a46ad3877485e4d67ef499c6dda36bfd1f9a. See
ChangeLog for details.

Impact: None.

bnx2 v2.1.8c (June 16, 2011)
============================
Enhancements
------------
1. Change: In ESX, bnx2 will setup int mode during .probe time.
However, the dev->name will be finalized only when
pci_announce_device is done. So, we assign irq->name
in bnx2_request_irq instead of in bnx2_setup_int_mode.

Impact: ESX only.

cnic 2.5.4b (June 1, 2011)
============================
Fixes
-----
1. Problem: (CQ55915) iSCSI does not connect on 57800 in 4-port mode.

Cause: cl_qzone_id was wrong on the 3rd and 4th port. uIP also has
some problems determining 4-port mode.

Change: Fixed the QZONE_ID macro.

Impact: bnx2x iSCSI.

bnx2 2.1.8b (June 1, 2011)
============================
Fixes
-----
1. Problem: (CQ55422) NCSI firmware version displayed backwards on PPC.

Cause: Endian bug when reading the data from shared memory.

Change: Fixed byte swapping issue.

Impact: None.

2. Problem: bnx2 does not compile on some PPC distros.

Cause: pci_enable_pcie_error_reporting() not properly defined in some
distros.

Cause: Added #ifdef to prevent compiling
pci_enable_pcie_error_reporting() on PPC since it uses EEH
instead of AER.

Impact: None.

cnic 2.5.3b (May 24, 2011)
============================
Enhancements
------------
1. Change: Updated to FW 7.0.18 HSI.

Impact: iSCSI and FCoE on bnx2x.

bnx2 2.1.7b (May 24, 2011)
============================
Enhancements
------------
1. Change: Added register read write functions for VMWare gdb

Impact: None.

2. Change: Fixed compile issues on VMWare by resolving KWQ symbol
conflicts between netq code and cnic code.

Impact: None.

cnic 2.5.2b (April 21, 2011)
============================
Enhancements
------------
1. Change: Updated 2.4.2b cnic to T7.0.

Impact: iSCSI and FCoE on bnx2x.

cnic 2.4.5b (May 16, 2011)
==========================
Enhancements
------------
1. Change: Check CFC delete error code during completion. If it is set,
do not reuse the CID. This change is only compatible with
bnx2x 1.64.30 or newer.

Impact: iSCSI and FCoE.

cnic 2.4.4b (May 04, 2011)
==========================
Fixes
-----
1. Problem: (CQ54938) iSCSI timeout during async logout.

Cause: TCP reset request may not complete if there is a race with
firmware receiving a remote RST.

Change: Added code to handle TCP reset racing with remote RST and
TCP close racing with remote FIN.

Impact: iSCSI

cnic 2.4.3b (April 28, 2011)
============================
Fixes
-----
1. Problem: cnic may lose interrupts after processing 64 kcq entries.

Cause: The driver handles a maximum of 64 entries before calling
the ulp drivers. If the chip has more entries, the driver
does not handle the rest but acknowledges the latest
status block index.

Change: Changed the logic to keep looping until all kcq entries
are handled.

Impact: iSCSI and FCoE on all devices.

cnic 2.4.2b (April 21, 2011)
============================
Fixes
-----
1. Problem: (CQ54715, CQ54717) XSEMI parity error detected during iSCSI
login on 57712 in NPAR mode.

Cause: Statistic counter ID greater than MAX_STAT_COUNTER_ID_E2 in
client init data for iSCSI L2 ring.

Change: Check client ID against MAX_STAT_COUNTER_ID_EXX before enabling
statistics.

Impact: iSCSI on bnx2x.

cnic 2.4.1d (April 14, 2011)
============================
Enhancements
------------
1. Change: Added silent VLAN 0 removal on iSCSI ring.

Impact: iSCSI on bnx2x.

cnic 2.4.1c (April 11, 2011)
============================
Fixes
-----
1. Problem: (CQ49586) iSCSI reboot test fails after a few iterations.

Cause: TCP port 60000 is used every time during boot. During reset,
the TCP connection is never terminated so using the same port
to connect to the target during reboot will not work.

Change: Added randomization of the first TCP port to use.

Impact: iSCSI.

bnx2 v2.1.6b (April 6, 2011)
============================
Enhancements
------------
1. Change: Get iSCSI license information to prevent cnic from registering
if there is no license. This will make it consistent with 10G
behavior.

Impact: iSCSI only.

cnic 2.4.1b (April 6, 2011)
===========================
Fixes
-----
1. Problem: (CQ53236) FCoE HBA not functional after reloading bnx2x.

Cause: In some distros, NETDEV_UP can happen immediately after
NETDEV_REGISTER while bnx2x module is still in init state.
At this time, cnic will not be able to symbol_get() from
bnx2x, preventing the cnic from registering.

Change: Check all events, and we should be able to catch NETDEV_CHANGE
abd register cnic.

Impact: iSCSI and FCoE.

Enhancements
------------
1. Change: Updated 10G HSI to firmware 6.4.32 (bnx2x 1.64.23)

Impact: iSCSI and FCoE.

cnic 2.4.0b (Mar 29, 2011)
==========================
Enhancements
------------
1. Change: Updated cnic to with with bnx2x 1.70.x and added support
for 578xx devices.

Impact: iSCSI and FCoE.

bnx2 v2.1.5d (Feb 28, 2011) cnic 2.3.5d (Feb 28, 2011)
======================================================
Fixes
-----
1. Problem: (CQ53174) iSCSI detected conn error and ping timeout.

Cause: Race condition between cnic driver and hardware DMA'ing a
new status block with new iSCSI events. The bug was
introduced when adding FCoE support.

Change: 1. Add proper memory barrier after reading status block.
2. After servicing FCoE EQ, we must loop back and check the
iSCSI EQ again because we may have a newer status block
index that is read after servicing the iSCSI EQ.

Impact: 57712 iSCSI and FCoE.

bnx2 v2.1.5c (Feb 15, 2011) cnic 2.3.5c (Feb 15, 2011)
======================================================
Enhancements
------------
1. Change: Updated 5709 firmware to 6.2.1a, with netq fixes and iSCSI
performance regression fixes.

Impact: 5709.

bnx2 v2.1.5b (Feb 08, 2011) cnic 2.3.5b (Feb 08, 2011)
======================================================
Fixes
-----
1. Problem: iSCSI does not connect in DCB environment.

Cause: iSCSI packets are tagged with the wrong ethertype.

Change: Added initialization of xstorm's reserved_vlan_type field.

Impact: bnx2x iSCSI.

bnx2 v2.1.4h (Jan 27, 2011) cnic 2.3.4h (Jan 27, 2011)
======================================================

Enhancements
------------
1. Change: Ported T6.4 HSI changes to support iSCSI.

Impact: bnx2x iSCSI.

2. Change: Fixed endian bug in setting up page table addresses.

Impact: iSCSI.

bnx2 v2.1.4g (Jan 20, 2011) cnic 2.3.4g (Jan 20, 2011)
=========================================================

Enhancements
------------
1. Change: Removed shared mem logic to read iSCSI and FCoE info.
This logic is now in the bnx2x driver.

Impact: iSCSI and FCoE on bnx2x.

2. Change: Removed FCoE support on 57711. This is no longer supported
by the HSI.

Impact: None.

bnx2 v2.1.4b (Jan 05, 2011) cnic 2.3.4b (Jan 05, 2011)
=========================================================

Enhancements
------------
1. Change: Merged with bnx2 2.0.22b.

bnx2 v2.1.3b (Dec 22, 2010) cnic 2.3.3b (Dec 22, 2010)
=========================================================

Enhancements
------------
1. Change: Merged with bnx2 2.0.21b.

bnx2 v2.1.2f (Dec 13, 2010) cnic 2.3.2f (Dec 13, 2010)
=========================================================
Enhancements
------------
1. Change: Added NPAR FCoE offload checking.

Impact: FCoE.

bnx2 v2.1.2c (Oct 28, 2010) cnic 2.3.2c (Oct 28, 2010)
=========================================================
Enhancements
------------
1. Change: Updated cnic to the latest 6.4.9 HSI.

Impact: bnx2x iSCSI and FCoE.

bnx2 v2.1.2b (Oct 12, 2010) cnic 2.3.2b (Oct 12, 2010)
=========================================================
Enhancements
------------
1. Change: Updated cnic to the latest 6.4.7 HSI.

Impact: bnx2x iSCSI - requires bnx2x 1.64.03 or above.

bnx2 v2.1.1b (Sep 28, 2010) cnic 2.3.1b (Sep 28, 2010)
=========================================================
Enhancements
------------
1. Change: Updated cnic to the latest 6.4.x HSI.

Impact: bnx2x iSCSI - requires bnx2x 1.64.02 or above.

bnx2 v2.0.23b (Feb 01, 2011) cnic v2.2.13b (Feb 01, 2011)
=========================================================
Fixes
-----
1. Problem: EEH errors on PPC when loading bnx2i

Cause: KWQ page tables set up in wrong endian order, causing EEH
errors when sending the first KWQ message.

Change: Fixes page tables endian order.

Impact: PPC only.

bnx2 v2.0.22f (Jan 18, 2011) cnic v2.2.12f (Jan 18, 2011)
=========================================================
Enhancements
------------
1. Prevent AER error messages on PPC. PPC does not support AER.

Impact: 5709 only.

2. Integrated with bnx2x 1.62.10.

Impact: bnx2x iSCSI only.

bnx2 v2.0.22e (Jan 12, 2011)
=========================================================
Fixes
-----
1. Problem: change MTU would fail for the CNIC IRQ.

Cause: Mismatched module IDs for request/free IRQ.

Change: Masquerade as CNIC when cnic ops are called from bnx2.

Impact: ESX only.

bnx2 v2.0.22d (Jan 11, 2011) cnic v2.2.12d (Jan 11, 2011)
=========================================================
Fixes
-----
1. Problem: NetQueue would not properly allocate RX queue

Cause: BNX2_NETQ_HW_OPENED bit was not properly set.

Change: When the NetQueue device is openned properly set the
BNX2_NETQ_HW_OPENED bit in the netq_flags field.

Impact: ESX NetQueue

2. Problem: NetQueue could possibly get out of sync with the uppper
layers

Cause: The queue cleanup code between the driver and upper layer
is not synchronized

Change: Introduce the NetQueue lock to synchronize the cleaning
of the queues between the vmkernel and the bnx2 driver.

Impact: ESX NetQueue

3. Problem: iSCSI may not work if multi-function is disabled in NPAR NICs.

Cause: Bug in logic in detecting NPAR mode.

Change: Offload bit should not be checked if iSCSI MAC address is invalid.

Impact: iSCSI on 57712 NPAR NIC.

bnx2 v2.0.22c (Jan 6, 2011) cnic 2.2.12c (Jan 6, 2011)
=========================================================
Enhancements
------------
1. Change: Updated to 6.2.1a firmware for 5709. It has fixes for
CQ51953 (ESX netqueue issue) and CQ51894 (iSCSI performance).

Impact: 5709 iSCSI and L2.

bnx2 v2.0.22b (Jan 4, 2011) cnic 2.2.12b (Jan 4, 2011)
=========================================================
Enhancements
------------
1. Change: Send netlink IF_DOWN message during cnic_unregister_device().
This fixes the problem of bnx2i referencing freed hba when we
used to send the netlink message during cnic_unregister_driver().

Impact: iSCSI.

2. Change: Upstream fix for memory leak in cnic_alloc_uio_rings() when
we cannot allocate all the memory.

Impact: None.

3. Change: Upstream fix to remove flush_scheduled_work() since it is
obsolete.

Impact: None.

4. Change: Do not allow iSCSI on bnx2x devices in MF mode. The
hardware does not yet support it.

Impact: iSCSI.

Fixes
-----
1. Problem: SPQ RAMROD type field does not consistently contain the
function ID.

Change: Fixed in cnic_submit_kwqe_16() for HSI 6.0 and above.

Impact: iSCSI in NPAR mode.

bnx2 v2.0.21b (Dec 21, 2010) cnic 2.2.11b (Dec 21, 2010)
=========================================================
Enhancements
------------
1. Change: Call cm_connect_complete() when an invalid path_response
netlink message is received. This will speed up iscsid in
disconnecting the connection. This helps to resolve
CQ49665.

Impact: iSCSI.

bnx2 v2.0.20g (Dec 17, 2010) cnic 2.2.10g (Dec 17, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ51766) cnic driver panics in cnic_service_bnx2() during
iscsid restart.

Cause: Referencing the cp->kcq1 pointer before checking that the device
is up.

Change: Fixed logic so that the cp->kcq1 pointer will only be
refernced after checking the device is up.

Impact: iSCSI.

Enhancements
------------
1. Change: Added retry logic in iscsi_nl_send_msg() to retry netlink
messages to userspace.

Impact: iSCSI.

bnx2 v2.0.20f (Dec 09, 2010) cnic 2.2.10f (Dec 09, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ51544) Unable to connect to iSCSI targets on 57712 NPAR
LOMs with NPAR disabled.

Cause: ff:ff:ff:ff:ff:ff iSCSI MAC address was used in this case.

Change: Add code to detect invalid MAC address and use port MAC address
instead. That's the only to determine NPAR is disabled.

Impact: 57712 iSCSI.

2. Problem: MTU change in INTA mode crashes occasionally.

Cause: Status block may be accessed if INTA is shared with another
device during reset. There is a short period that the status
block is freed.

Change: Free IRQ before freeing status block.

Impact: bnx2 MTU change/ring size change.

3. Problem: Heap corruption reported by VMWare.

Cause: list_del() is called after kfree() in OOO code.

Fix: call list_del() before kfree().

Impact: iSCSI OOO.

bnx2 v2.0.20e (Dec 06, 2010) cnic 2.2.10e (Dec 06, 2010)
=========================================================
Enhancements
------------
1. Change: Adjusted hc timeout for EQ to use the T6.0 value of 4. This
will match T5.x HC timeout values.

Impact: 10G iSCSI only.

2. Change: Minor changes to match upstream code.

Impact: None.

bnx2 v2.0.20d (Nov 16, 2010) cnic 2.2.10d (Nov 16, 2010)
=========================================================
Fixes
-----
1. Problem: VMware NetQueue not working properly on 5709.

Cause: HSI mismatch.

Change: Updated HSI to match T6.0 bnx2 firmware.

Impact: NetQueue on 5709.

Enhancements
------------
1. Change: Adjusted kernel compatibility code to compile on RHEL5.6.

Impact: bnx2 and cnic.

bnx2 v2.0.20c (Oct 28, 2010) cnic 2.2.10c (Oct 28, 2010)
=========================================================
Fixes
-----
1. Problem: NMI occurs during repeated load/unload of bnx2 driver on
5709.

Cause: The 5709 chip's DMA block wasn't stopped properly before reset.

Change: Fixed by clearing DMA_ENABLE in NEW_CORE_CTL register and
polling for pending bus transactions to stop.

Impact: 5709.

Enhancements
------------
1. Change: Update 5706/5708/5709 firmware to 6.2.1.

Impact: All 1G devices.

2. Change: Fixed one circular lock dependency issue with bnx2i when making
up call to send iSCSI NL message.

Impact: None.

bnx2 v2.0.20b (Oct 13, 2010) cnic 2.2.10b (Oct 13, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49481) pci_enable_pcie_error_reporting failed on
5706 and 5709.

Cause: AER not supported on non-PCIE devices.

Change: Enable AER only on PCIE devices (5709).

Impact: None.

Enhancements
------------
1. Change: (CQ49858) Support KVM pass-through mode by eliminating
config cycles to non-standard PCI registers
(PCICFG_MISC_CONFIG, PCICFG_REG_WINDOW*).

Impact: All chips.

bnx2 v2.0.18c (Sep 13, 2010) cnic 2.2.6c (Sep 13, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49832) bnx2 flow control not working

Cause: Mistakenly disabled in firmware in 2.0.17j to fix CQ46393.

Change: Re-enabled RV2P flow control with additional fixes to
for a number of odd flow control issues. New firmware
versions are 6.0.15 for 5706/5708 and 6.0.17 for 5709.

Impact: 5706/5708/5709.

Enhancements
------------
1. Change: Added zeroing of the iSCSI L2 ring's RX BD page to help
signal ring shutdown to uIP.

Impact: iSCSI.

2. Change: Fix compile issues on 2.6.36 kernel.

Impact: None.

bnx2 v2.0.18b (Sep 02, 2010) cnic 2.2.6b (Sep 02, 2010)
=========================================================
Enhancements
------------
1. Change: Slightly improve the cnic Netlink fix in cnic 2.2.5k.

Impact: iSCSI.

bnx2 v2.0.17l (Aug 19, 2010) cnic 2.2.5l (Aug 19, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49502) - bnx2x_panic_dump doing DHCP and Data/Header Digest

Cause: A mismatch was found in the txbd where the hw prod idx did not
match the sw prod idx (via the vlan_id field). The problem will
show when uIP restarts without cnic reload. Since uIP restarted,
it has lost all previous history about the uio ring.

Change: Added cnic_shutdown_rings to the uio_close path so whenever
uio_open is called from uIP, the rings will start off fresh.

Impact: 570X/5771X iSCSI.

2. Problem: (CQ49211) Connection via bnx2i path fails in SuSE 11 SP1

Cause: For 5708/09, the previous firmware set did not take the l2 frame
header length into account in the placement filter.

Change: Updated to 5706/08 fw 6.0.14 and 5709 fw 6.0.16 which addresses
this issue.

Impact: 570X iSCSI.


bnx2 v2.0.17k (Aug 18, 2010) cnic 2.2.5k (Aug 18, 2010)
=========================================================
Fixes
-----
1. Problem: iSCSI sessions do not recover when running under
heavy stress conditions with the socket layer.

Cause: The NetLink buffer would get congested, so that the response
to the PATH_UPDATE back to uIP would not be delivered.

Change: Use CNIC to throttle the number of outstanding PATH_REQ's
to uIP, easing the congestion on the Netlink buffer.

Impact: 570X/5771X iSCSI.

bnx2 v2.0.17j (Aug 15, 2010) cnic 2.2.5j (Aug 15, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49395) Session recovery occurs during heavy traffic.

Cause: The mapping of the 10g hw context id to l5 cid didn't consider
the port/vfid.

Change: Fixed the 10g hw context id to l5 cid mapping in TCP OOO

Impact: 5771X iSCSI.

2. Problem: (CQ49111) System freezes when unloading bnx2x drivers while
having active sessions.

Cause: The iro_arr was not initialized before deferencing which led to
a kernel panic. This is caused by a race condition between uIP
and cnic.

Change: Moved the initialization of the iro_arr to before uIP can call
uio open.

Impact: 5771X iSCSI.

3. Problem: (CQ49211) 5708/09 Connection via bnx2i path fails SuSE 11 sp1

Cause: For 5709, the fast coalescing algorithm had a bug in the fw.

Change: Updated 5709 MIPS firmware to 6.0.14 which contains a fix for
this issue.

Impact: 5709 iSCSI.

4. Problem: (CQ46393) 5706/08/09 NC-SI Traffic Stops After Host Kernel Panic

Cause: RV2P firmware was set to drop input packets at a rate which is
slower than input line rate when the host stops posting buffers.
This has caused the rxp ftq to backup which eventually led to the
rxp ftq hw to assert PAUSE and flood the network.

Change: RV2P firmware was modified to disable any waiting before dropping
the input packet when the host doesn't post buffers.

Impact: 5706/08/09.


bnx2 v2.0.17i (Aug 09, 2010) cnic 2.2.5i (Aug 09, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49159) 57710 firmware asserts running disktest.

Cause: CSTORM memory corruption.

Change: Do not initialize and use the FCoE EQ on 57710. The memory
offsets for the FCoE EQ ring are not defined on 57710.

Impact: 57710 iSCSI.

2. Problem: (CQ49271) Soft lockup during ifup/ifdown test with active iSCSI
connections.

Cause: rtnl_lock may have a circular dependency with another filesystem
mutex during uio_close().

Change: Removed rtnl_lock() in cnic_uio_close().

Impact: All iSCSI.

bnx2 v2.0.17h (Aug 03, 2010) cnic 2.2.5h (Aug 02, 2010)
=========================================================
Enhancements
------------
1. Change: Enabled new RV2P flow control on all bnx2 devices.

Impact: All bnx2 devices.

2. Change: Suppressed "OOO CQE is empty" kernel message.

Impact: None.

bnx2 v2.0.17g (Aug 02, 2010) cnic 2.2.5g (Aug 02, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49152) cnic driver crashes during iscsid restart.

Cause: cnic_wq destroyed while cnic_delete_task() is still queued
in the workqueue.

Change: Call destroy_workqueue() after cnic_release() which waits
for the cnic_delete_task() to finish.

Impact: 10G iSCSI.

bnx2 v2.0.17f (July 30, 2010) cnic 2.2.5f (July 30, 2010)
=========================================================
Fixes
-----
1. Problem: iSCSI license not read correctly on 57712 in NIC partitioning
mode.

Cause: Missing NIC partitioning license logic.

Change: Added NIC partitioning license logic.

Impact: 10G iSCSI.

Enhancements
------------
1. Change: Updated 5709 firmware to 6.0.13. The new 5709 firmware
has additional rx and tx performance improvements.

Impact: 5709.

bnx2 v2.0.17e (July 29, 2010) cnic 2.2.5e (July 29, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49117, CQ49111) Soft locup when unloading bnx2x with cnic
and bnx2fc/bnx2i loaded.

Cause: cnic_cm_stop_bnx2x_hw() thread under rtnl_lock() and pci_bus_sem
has to wait for cnic_delete_task() to finish the 2-second wait
and CFC DELETE of every FCoE or iSCSI connection. There may
be work structs scheduled on the common workqueue ahead of
cnic_delete_task() that require the same semaphores, leading
to the soft lockup.

Change: Use a dedicated workqueue for cnic_delete_task().

Impact: 10G iSCSI and FCoE.

2. Problem: (CQ49113) Compilation error with bnx2x 1.60.30.
(CQ48828) lediag fails with cnic loaded.

Cause: license_key structure changed to use all 32-bit fields. This
change is to fix CQ48828 (lediag fails with cnic loaded).
16-bit access causes lediag failure.

Change: Made corresponding change to read 32-bit values for the
iSCSI license.

Impact: 10G iSCSI.

3. Problem: (CQ49097) cnic panics when loading on 5708.

Cause: The driver uses NULL OOO ring pointers to initialize OOO
for 5708.

Change: Skip OOO completely on 5708.

Impact: bnx2 iSCSI.

bnx2 v2.0.17d (July 28, 2010) cnic 2.2.5d (July 28, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49071) Soft lockup during system shutdown after logging
in to 10G iSCSI sessions.

Cause: This was introduced in 2.2.5c when fixing CQ49003.
flush_scheduled_work() can deadlock because we're
holding rtnl_lock and linkwatch_event may be on the
workqueue.

Change: Fixed by using flags to wait for the cnic_delete_task()
to finish.

Impact: 10G iSCSI.

2. Problem: cnic driver does not load on 5708 devices.

Cause: Bug in driver that skips devices without OOO support.

Change: OOO setup has been changed so that cnic initialization will
continue even if OOO fails for whatever reason on all chips.

Impact: iSCSI.

Enhancements
------------
1. Change: Updated 5708 firmware to 6.0.11 and 5709 firmware to
6.0.12. The new 5709 firmware fixes small packet rx
performance issue. Some adiitional fixes for iSCSI
and OOO.

Impact: All bnx2 chips.

bnx2 v2.0.17c (July 23, 2010) cnic 2.2.5c (July 23, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49003) Panic in cnic_free_bnx2x_conn_resc() during
ifdown with many 10G iSCSI active sessions.

Cause: cancel_work_sync() is not available in RHEL5.x kernels to
wait for cnic_delete_task() to finish before freeing
the device's data structures (in particular the csk table).

Change: Use flush_scheduled_work() to wait instead.

Impact: 10G iSCSI on older kernels (e.g. RHEL5.x)

Enhancements
------------
1. Change: Added AER (Advanced Error Reporting) on bnx2.

Impact: None.

bnx2 v2.0.17b (July 20, 2010) cnic 2.2.5b (July 20, 2010)
=========================================================
Fixes
-----
1. Problem: Still seeing uio_release panics during ifup/ifdown test.

Cause: UIO device unregistered prematurely.

Change: Do not unregister UIO devices until rmmod.

Impact: iSCSI.

Enhancements
------------
1. Change: Various upstream patches. Please see ChangeLog for details.

bnx2 v2.0.16d (July 14, 2010) cnic 2.2.4d (July 14, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ44916) Unload bnx2/bnx2x fails after connecting to
iSCSI targets.

Cause: UIO device deleted before userspace has closed the device,
causing various failures including kernel panic.

Change: Separated UIO structure from cnic_dev structure so that
we can wait until UIO is closed before unregister and deleting
UIO.

Impact: iSCSI. This change should have possitive impact on ifup/ifdown,
MTU change/selftest/hotplug/etc with active iSCSI sessions.

Enhancements
------------
1. Change: Allocate the actual number of MSI-X vectors instead of always
9. Also, keep trying if the number of vectors is less than
the desired number.

Impact: 5709 networking and iSCSI.

bnx2 v2.0.16c (July 12, 2010) cnic 2.2.4c (July 12, 2010)
=========================================================
Enhancements
------------
1. Change: Added VLAN_TAG_PRESENT to distinguish between physical and
VLAN netevents in cnic.

Impact: FCoE.

bnx2 v2.0.16b (July 8, 2010) cnic 2.2.4b (July 8, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ48753) cnic will not compile with bnx2x 1.60.27.

Cause: IGU symbols not defined without ELINK_DEBUG defined.

Change: Added ELINK_DEBUG.

Impact: None.

2. Problem: (CQ48717) Kernel panic in bnx2x during ifdown with active iSCSI
sessions.

Cause: uio_close() is called after the device is already down. bnx2x
will crash when we try to shutdown the iSCSI ring.

Change: Shutdown the iSCSI ring even if uio_close() is not called in
the shutdown path.

Impact: 10G iSCSI.

Enhancements
------------
1. Change: Always run in MSI-X mode on 5709.

Impact: 5709.

2. Change: Added wait of 2 seconds when sending PATH_REQ if UIO has not
been opened yet. This improves the liklihood of login success
during the first login if using older iscsid.

Impact: iSCSI.

bnx2 v2.0.15k (July 1, 2010) cnic 2.2.3k (July 1, 2010)
=========================================================
Fixes
-----
1. Problem: Compile problems on various older kernels.

Cause: pci_save_state()/pci_restore_state incompatibility in older
kernel. DECLARE_PCI_UNMAP_ADDR() caused dma mapping
field to be undefined on kernels not using IOMMU.

Change: Do not use pci_save_state()/pci_restore_state() on older
kernels. Use dma_addr_t to declare mapping fields.

Impact: None.

bnx2 v2.0.15j (June 30, 2010) cnic 2.2.3j (June 30, 2010)
=========================================================
Fixes
-----
1. Problem: bnx2x firmware asserts if cnic is loaded on 57711E (MF)
functions 2 and higher and the device is brought up.

Cause: Statistics for iSCSI ring not implemented, casuing firmware to
assert when the iSCSI ring is initialized.

Change: Do not enable statistics if the clien ID is bigger than
MAX_STAT_COUNTER_ID.

Impact: bnx2x iSCSI on 57711E.

2. Problem: cnic terminations for iSCSI and FCoE connections may panic or
hang during repeated ifdown/ifup.

Cause: Data structures may be freed while cnic is still waiting for the
2 second CFC_DELETE wait time.

Change: Use cancel_work_sync() to wait for the completion of the
cnic_delete_task(). Check that the CTX_FL_DELETE_WAIT flag
has been set before waiting.

Impact: bnx2x iSCSI and FCoE.

3. Problem: (CQ48642) Compile errors on older kernels.

Cause: VMWARE_ESX_DDK_VERSION not defined in Linux.

Change: Added check for VMKLNX.

Impatc: None.

bnx2 v2.0.15i (June 30, 2010) cnic 2.2.3i (June 30, 2010)
=========================================================

Enhancements
------------
1. Change: Added iSCSI out-of-order support.

Impact: iSCSI.

bnx2 v2.0.15h (June 18, 2010) cnic 2.2.3g (June 10, 2010)
=========================================================
Enhancements
------------
1. Change: Enabled HW RSS indirection table on 5709.

Impact: RSS on 5709.

2. Change: Updated to 6.0.10 firmware.

Impact: all chips.

bnx2 v2.0.15g (June 10, 2010) cnic 2.2.3g (June 10, 2010)
=========================================================
Enhancements
------------
1. Change: Added FCoE statistics SPQ command.

Impact: FCoE.

bnx2 v2.0.15f (June 4, 2010) cnic 2.2.3f (June 4, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ46648) CID leaks while running iLAB 5.12 connection closure
test.

Cause: Race condition between bnx2i initiated TCP close and an
asynchronous RESET_COMP from firmware.

Change: Re-structured cnic code that handles close, abort, and various
completion events to ensure all scenarios are accounted for
with no race conditions.

Impact: All iSCSI connection termination scenarios.

Enhancements
------------
1. Change: Added host iSCSI IP address to the cnic_dev structure so that
bnx2i can report it to sysfs. This is needed for iSCSI boot
during pivot_root.

Impact: iSCSI boot.

bnx2 v2.0.15e (June 3, 2010) cnic 2.2.3d (June 2, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ48133) bnx2 fails to compile on older 2.6 kernels.

Cause: PCI MSIX attributes not defined in kernel .h files.

Change: Added compatibility code.

Impact: None.

bnx2 v2.0.15d (June 2, 2010) cnic 2.2.3d (June 2, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ47942) rmmod hangs if the device has been opened and closed
more than once.

Cause: netif_napi_add() called once during every ->open().
netif_napi_del() is only called once during rmmod.

Change: Call netif_napi_del() in ->close().

Impact: None.

bnx2 v2.0.15c (May 21, 2010) cnic 2.2.3c (April 21, 2010)
=========================================================
Fixes
-----
1. Problem: service iscsid restart on 5709 does not work.

Cause: Not restarting KWQ correctly due to stale context.

Change: Fixed by correctly zeroing KWQ/KCQ/RX context
memory.

Impact: bnx2 iSCSI.

2. Problem: iSCSI license not read correctly on 57711E in single
function mode.

Cause: Bug in reading the mf_cfg block.

Change: Bug fixed.

Change: 57711E iSCSI.

Enhancements
------------
1. Change: Added GRO support.

Impact: All devices on kernels supporting GRO.

bnx2 v2.0.15b (May 12, 2010) cnic 2.2.3b (April 12, 2010)
=========================================================
Fixes
-----
1. Problem: iSCSI does not work on 57712.

Cause: License checking always disabled on 57712.

Change: Added proper checking for 57712 iSCSI license.

Impact: None.

2. Problem: (CQ47360) Compile errors on older kernels not supporting
UIO and latest iSCSI.

Cause: New cnic driver will only compile on kernels newer than
2.6.31 and some selected distros that have the backport.

Change: Makefile changes to compile cnic only on supported kernels.

Impact: None.

Enhancements
------------
1. Change: Changed bnx2_cnic_probe() to bnx2_cnic_probe2() so
that out-of-tree driver componenets will not inter-
operate with upstream components. This avoids
compatibility problems that often lead to kernel
crashes.

Impact: Out-of-tree cnic will not operate with upstream
L2 drivers and vice versa.

2. Change: Revert the PRS_REG_NIC_MODE change done in 2.0.11h. Newer
bnx2x driver (1.60.18+) do not require this setting.

Impact: None.

bnx2 v2.0.14b (April 28, 2010) cnic 2.2.2b (April 28, 2010)
============================================================
Enhancements
------------
1. Change: Added compatibility code for RHEL5.4+ kernels.

Impact: None.

2. Change: Added VLAN ID to netdev event callback.

Impact: bnx2i.

bnx2 v2.0.13b (April 22, 2010) cnic 2.2.1c (April 30, 2010)
============================================================
Enhancements
------------
Add debug code to dump all KWQE's (RAMROD) posted to 5771x chipset.
This feature can be enabled/disabled using module parameter, by default
this feature is disabled. Also a exported function is introduced to
dump 3 pages worth of KCQE's

bnx2 v2.0.13b (April 22, 2010) cnic 2.2.1b (April 22, 2010)
============================================================
Enhancements
------------
1. Change: cnic has been updated to be similar to the upstream versions
using UIO with added T6.0 iSCSI support for 10G and other bug
fixes.

Impact: iSCSI now requires UIO, new bnx2i, and bnx2x 1.60.16+.

bnx2 v2.0.11j (April 22, 2010) cnic 1.10.2j (April 22, 2010)
============================================================
Fixes
-----
1. Problem: (CQ47298) Does not compile with bnx2x 1.60.16.

Cause: cnic_if.h has changed.

Change: Updated code to be compatible with new cnic_if.h.

Impact: None.

bnx2 v2.0.11i (April 15, 2010) cnic 1.10.2i (April 15, 2010)
============================================================
Fixes
-----
1. Problem: (RHBZ 511368) Driver loses one MSI-X vector after many hours
of traffic.

Cause: Chip timing out on write cycle to the MSI-X mask bit, causing
the unmask operation to be dropped.

Change: Increase GRC timeout in register 0x8cc.
(Same fix from 2.0.8e).

Impact: bnx2x MSI-X mode.

2. Problem: (RHBZ 554706) scheduling while atomic warning when bonding and
VLANs are used with cnic loaded.

Cause: bond_del_vlans_from_slave() holds bond->lock when calling
ndo_vlan_rx_register(). bnx2 calls bnx2_netif_stop() to
stop the rx handling while changing the vlgrp. The call
also calls bnx2_cnic_stop() which has many sleeping functions.

Change: Do not stop cnic when VLANs are changed. Since there is no
reset during VLAN change, there is no need to stop cnic.
(Same fix from 2.0.8e).

Impact: VLAN and iSCSI.

3. Problem: (CQ46940) Poor small packet performance on 5709.

Cause: FTQ discards caused by bottlenecks in firmware.

Change: Upgraded to 5.0.0.j15 MIPS firmware for 5709.
(Same fix from 2.0.8c)

Impact: 5709.

Enhancements
------------
1. Change: Improved rx performance by prefetching next entry's descriptor
header and SKB.

Impact: All chips.

2. Change: Updated cnic interface to support out-of-order processing. This
is needed for bnx2x 1.60.15 but the feature is not available in
cnic yet.

Impact: None.

bnx2 v2.0.11h (Mar 29, 2010) cnic 1.10.2h (Mar 29, 2010)
========================================================
Fixes
-----
1. Problem: iSCSI not functional with bnx2x 1.60.11.

Cause: PRS_REG_NIC_MODE set to 1, causing L2 to receive iSCSI traffic.

Change: Cleared PRS_REG_NIC_MODE.

Impact: bnx2x iSCSI.

bnx2 v2.0.11g (Mar 17, 2010) cnic 1.10.2g (Mar 17, 2010)
========================================================
Enhancements
------------
1. Problem: iSCSI not functional on 57712.

Cause: Bugs and incomplete support of 57712 in cnic driver.

Change: Fixed and completed 57712 support.

Impact: iSCSI.

bnx2 v2.0.11f (Mar 15, 2010) cnic 1.10.2f (Mar 15, 2010)
======================================================
Fixes
-----
1. Change: More 6.0.12 firmware HSI changes (bnx2x 1.60.10).

Impact: bnx2x iSCSI.

bnx2 v2.0.11e (Mar 9, 2010) cnic 1.10.2e (Mar 9, 2010)
======================================================
Enhancements
------------
1. Change: Updated to 6.0.12 firmware HSI (bnx2x 1.60.10).

Impact: bnx2x iSCSI.

bnx2 v2.0.11d (Feb 25, 2010) cnic 1.10.2d (Feb 25, 2010)
========================================================
Enhancements
------------
1. Change: Fixed shared memory base checking for T6.0 bnx2x HSI.

Impact: bnx2x iSCSI.

2. Change: Added new igu status block ID to handle iSCSI status
block acknowledgement in T6.0 HSI.

Impact: bnx2x iSCSI.

3. Change: Allow multiple ethtool speed advertisments when using
newer ethtool 6.

Impact: ethtool -s.

Fixes
-----
1. Problem: Statistics 64-bit counters may not be accurate after MTU
change.

Cause: Bug missing the carry when summing 64-bit counters.

Change: Fixed the missing carry.

Impact: statistics.

bnx2 v2.0.11c (Feb 04, 2010) cnic 1.10.2c (Feb 04, 2010)
========================================================
Enhancements
------------
2. Change: Added 57712 support in cnic driver.

Impact: None.

bnx2 v2.0.11b (Jan 28, 2010) cnic 1.10.2b (Jan 27, 2010)
========================================================
Enhancements
------------
1. Change: Saved bnx2 statistics block before MTU change, ring change,
etc.

Impact: bnx2 statistics.

bnx2 v2.0.10b (Jan 12, 2010) cnic 1.10.1b (Jan 12, 2010)
========================================================
Enhancements
------------
1. Change: Improved cnic's MTU change/reset logic to fix multiple problems
in VMWare.

Impact: iSCSI.

2. Change: Converted to bnx2x T6.0 HSI.

Impact: bnx2x iSCSI.

bnx2 v2.0.8e (April 13, 2010) cnic 1.9.13b (Dec 16, 2009)
=========================================================
Fixes
-----
1. Problem: (RHBZ 511368) Driver loses one MSI-X vector after many hours
of traffic.

Cause: Chip timing out on write cycle to the MSI-X mask bit, causing
the unmask operation to be dropped.

Change: Increase GRC timeout in register 0x8cc.

Impact: bnx2x MSI-X mode.

2. Problem: (RHBZ 554706) scheduling while atomic warning when bonding and
VLANs are used with cnic loaded.

Cause: bond_del_vlans_from_slave() holds bond->lock when calling
ndo_vlan_rx_register(). bnx2 calls bnx2_netif_stop() to
stop the rx handling while changing the vlgrp. The call
also calls bnx2_cnic_stop() which has many sleeping functions.

Change: Do not stop cnic when VLANs are changed. Since there is no
reset during VLAN change, there is no need to stop cnic.

Impact: VLAN and iSCSI.

bnx2 v2.0.8d (April 02, 2010) cnic 1.9.13b (Dec 16, 2009)
=========================================================
Enhancements
------------
1. Change: Improved rx performance by prefetching next entry's descriptor
header and SKB.

Impact: All chips.

bnx2 v2.0.8c (Mar 31, 2010) cnic 1.9.13b (Dec 16, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ46940) Poor small packet performance on 5709.

Cause: FTQ discards caused by bottlenecks in firmware.

Change: Upgraded to 5.0.0.j15 MIPS firmware for 5709.

Impact: 5709.

bnx2 v2.0.8b (Dec 16, 2009) cnic 1.9.13b (Dec 16, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44964) RHEL5.4 crashes when bnx2 driver is updated with
out-of-tree version.

Cause: Newer out-of-tree driver's cnic_eth_dev structure has been
updated, making it incompatible with RHEL5.4's cnic driver.

Change: Reverted the structure update for RHEL5.4.

Impact: None.

Enhancements
------------
1. Change: Improved the reset logic to prevent NETDEV WATCHDOG when
TSS is enabled.

Impact: MTU change, ring size change, selftest, etc.

2. Change: Fixed some compiler warnings when compiling bnx2 and cnic
drivers.

Impact: None.

bnx2 v2.0.7b (Dec 7, 2009) cnic 1.9.12b (Dec 7, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44620) Spurious KCQ entries leading to bnx2x assert.

Cause: Stale status block with old KCQ index after restarting hardware.

Change: Added some additional cleanup and initialization steps including
zeroing the status block.

Impact: None.

Enhancements
------------
1. Change: Updated RV2P P1 for 5709 to 5.0.0.j10 to address a flow control
issue that can lead to context corruption. Flow control
watermarks have also been optimized.

Impact: 5709 flow control.

bnx2 v2.0.6b (Dec 4, 2009) cnic 1.9.11b (Nov 19, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44801) Unable to compile bnx2 on most 2.6 kernels.

Cause: print_mac() kernel compatibility not defined correctly.

Fix: Simple compatibility fix.

Impact: None.

bnx2 v2.0.5b (Dec 4, 2009) cnic 1.9.11b (Nov 19, 2009)
=======================================================
Enhancements
------------
1. Change: Sync'ed up with latest upstream bnx2 driver. Please see
ChangeLog for details.

Impact: Yes, Linux and VMWare.

bnx2 v1.9.42b (Dec 1, 2009)
=======================================================
Fixes
-----
1. Problem: Compile error against the VMware ESX 4.0 DDK

Cause: vmk_IscsiNetHandle is not defined with the
VMware ESX 4.0 DDK

Change: Added compile flag

Impact: None.


Enhancements
------------

1. Change: Add BMAPILNX ioctl to allow for FW upgrade

Impact: bnx2 VMware ESX 4.0


bnx2 v1.9.41b (Nov 19, 2009) cnic 1.9.11b (Nov 19, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44617) Compile error on SLES10 and RHEL4 kernels.

Cause: bool not defined on older kernels.

Change: Added compatibility code.

Impact: None.

2. Problem: (CQ42096) iSCSI sessions do not recover after running
selftest/ifdown/etc with max sessions connected.

Cause: cnic_lock mutex has circular dependency, causing deadlock
when iscsid tries to cleanup connections.

Change: Merged in upstream cnic patches to avoid circular
dependency.

Impact: None.

Enhancements
------------
Change: (CQ43088) Changed the firmware version string format.

Impact: None.

bnx2 v1.9.40b (Nov 18, 2009) cnic 1.9.10b (Nov 12, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44528) Kernel runs out of memory after load/unload bnx2.

Cause: RX SKB buffers were not freed.

Change: Fixed the regression introduced by VMWare development.

Impact: None.

2. Problem: (CQ44399) iLAB 5.10 connection establishment test failure.

Cause: Firmware SYN-ACK handling issue.

Change: Updated firmware to 5.0.0.j6 in bnx2_fw.h and 5.0.0.j9 in
bnx2_fw2.h.

Impact: iSCSI.

Enhancements
------------
Change: (CQ43088) Added VPD-R V0 firmware version string to ethtool -i.

Impact: None.

bnx2 v1.9.39b (Nov 6, 2009) cnic 1.9.10b (Nov 12, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44470) Kernel panics when bnx2/bnx2x is unloaded with
active iSCSI sessions.

Cause: NETDEV_UNREGISTER will cause bcm570x_* transport to be
destroyed while sessions may still be active.

Change: Use module referencing to prevent bnx2/bnx2x from unloading.
This is a simple interim solution to revert back to the
old behavior. In T6.0, we will migrate to the upstream
driver architecture and network drivers will be able to be
unloaded again.

Impact: None.

Enhancements
------------
Change: Added a short register dump during NETDEV_WATCHDOG.

Impact: None.

bnx2 v1.9.38b (Nov 6, 2009) cnic 1.9.9b (Nov 6, 2009)
=====================================================
Fixes
-----
1. Problem: (CQ44446) cnic panics during 10G iSCSI initialization.

Cause: Recent interface changes introduced this regression.
cnic_service_bnx2x() panics when accessing uninitialized
status block pointer.

Change: Added state checking in cnic_service_bnx2x().

Impact: None.

2. Problem: (CQ44439) bnx2 does not compile on older 2.6 kernels.

Cause: mutex not defined on older kernels.

Change: Use rtnl_lock() to protect bnx2_reset_task().

Impact: None.

bnx2 v1.9.37b (Nov 4, 2009) cnic 1.9.8b (Nov 3, 2009)
=====================================================
Enhancements
------------

1. Change: Updated 5708/5706 firmware to 5.0.0.j5 for better small packet
performance.

Impact: 5706/5708.

Fixes
-----
1. Problem: (CQ43280) Cannot unload cnic after bnx2/bnx2x is loaded.

Cause: module referencing.

Change: Changed module referencing scheme.

Impact: None.

bnx2 v1.9.36b (Oct 22, 2009)
=======================================================
Enhancements
------------

1. Change: Expand on NetQueue module parameters.

Impact: bnx2 VMware NetQ.

bnx2 v1.9.35b (Oct 22, 2009)
=======================================================
Fixes
-----
1. Problem: If only 1 queue is used on VMware ESX, iSCSI
offload would fail.

Cause: The inboxed VMware driver would only use
1 MSI-X vector. Because of this the driver
would not setup MSI-X

Change: Always setup MSI-X reguardless of the
number of MSI-X vectors used.

Impact: 5709 iSCSI on VMware

bnx2 v1.9.34b (Oct 20, 2009)
=======================================================
Fixes
-----
1. Change: Updated xinan firmware to 5.0.0.j8
Nop timeout tuning (VMware PR467194)
Added a new data fw heartbeat to work with
the new bootcode and also handle older
bootcode.

Impact: 5709.

bnx2 v1.9.33b (Oct 8, 2009)
=======================================================
Enhancements
------------

1. Change: Make NetQueue module parameters more explict.

Impact: bnx2 VMware NetQ.

bnx2 v1.9.32b (Oct 8, 2009) cnic v1.9.7c (Oct 8, 2009)
=======================================================
Fixes
-----
1. Problem: CNIC unable to handle an unsolicited
RESET COMPLETE which would result in a hung
session.

Cause: The CNIC driver couldn't handle unexpected SYN.

Change: The CNIC driver will now handle an unsolicited
RESET COMPLETE and cleanup properly.

Impact: cnic

Enhancements
------------

1. Change: Allow the default NetQueue options to be
controlled through the macro,
BNX2_ENABLE_NETQUEUE.

Impact: bnx2 VMware NetQ.

bnx2 v1.9.31b (Oct 6, 2009)
=======================================================
Fixes
-----
1. Problem: PSOD would occur when alloc()'ing NetQueue's

Cause: With the removal of the global 'disable_netq'
parameters, the NetQueue CID's weren't being
mapped in some cases

Change: Always map the NetQueue CID's

Impact: bnx2 VMware ESX NetQueue

bnx2 v1.9.30b (Oct 5, 2009)
=======================================================
Fixes
-----
1. Problem: PSOD would occur because of TX timeouts

Cause: The VMware netdev watchdog timer was ran before
the reset task got a chance to run on a loaded
system.

Change: Elongated the TX timeout value for VMware ESX
only to allow for the reset task to run.

Impact: bnx2 VMware ESX


Enhancements
------------

1. Change: Updated vmkernel module parameter, 'force_netq',
to allow NetQueue setting to be adjusted per
function rather then globally for all functions.

Impact: bnx2 VMware ESX


bnx2 v1.9.29b (Oct 1, 2009)
=======================================================
Fixes
-----
1. Change: Updated xinan firmware to 5.0.0.j7 and
teton firmware to 5.0.0.j4 which will fix
L2 hang due to iSCSI PDU's padding byte
extended to another TCP segment

Impact: 5706/5708/5709.


bnx2 v1.9.28b (Sep 25, 2009)
=======================================================
Fixes
-----
1. Change: Updated firmware to 5.0.0.j6 which will add
the corresponding flow control trip point.

Impact: 5709.


bnx2 v1.9.27b (Sep 24, 2009) cnic v1.9.7b (Sep 24, 2009)
=======================================================
Fixes
-----
1. Problem: For the cnic users would see in the kernel logs:

"kcq abs(hw_prod(0) - sw_prod(65534)) >
MAX_KCQ_IDX(2047)"

Cause: The function was not taking into account the
wrapping of the software and hardware producer
indexes.

Change: Recaculate the difference between the index with
wrapping taken into account.

Impact: cnic


Enhancements
------------

1. Change: Updated firmware to 5.0.0.j5 which increased the
rxpq depth from 32 to 256 to enhance the performance
on systems without flow control.

Impact: 5709.


bnx2 v1.9.26c (Sep 17, 2009)
=======================================================
Enhancements
------------
1. Change: Cleanup the VMware NetQueue code. Eliminate unneeded
RX flush routine, fix the number of queues to be the
same on 1500 and 9000 MTU sized packets.

Impact: bnx2 VMware NetQ.

bnx2 v1.9.26b (Sep 14, 2009)
=======================================================
Fixes
-----
1. Problem: VMware PSOD on MTU change

Cause: MSI-X window was remapped to the beginning of the PCI
config space. The driver would disable the bar space
because the MSI-X window was remapped incorrectly. This
would eventually cause a PSOD.

Change: Before the chip reset, the driver would disable MSI-X,
after the chip reset, MSI-X is re-enabled.

Impact: VMware NetQueue


bnx2 v1.9.25b (Aug 21, 2009) cnic v1.9.6 (Aug 21, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ 43182/43252) Compile error on RHEL4

Cause: struct mutex not defined on older kernels.

Change: Wrap cnic_lock mutex structure and code with #ifdef BCM_CNIC.

Impact: None.

2. Problem: Unloading cnic after ifdown may crash.

Cause: cnic unregisters with bnx2/bnx2x twice.

Change: Fixed logic to unregister only once.

Impact: None.

bnx2 v1.9.24b (Aug 13, 2009) cnic v1.9.6 (Aug 13, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ 42778) Kernel occasionally panics when enabling jumbo
frames.

Cause: If the driver is unable to allocate memory for the buffers,
the device is not properly shutdown.

Change: Added logic to shutdown device if unable to allocate buffers
and complete the setup of the device.

Impact: bnx2, changing MTU and ring sizes.

Enhancements
------------
1. Change: Updated firmware to 5.0.0.j3 for better small packet rx
performance. Firmware also fixes header digest error during
I/O.

Impact: All bnx2 devices.

bnx2 v1.9.23b (July 29, 2009) cnic v1.9.5 (July 29, 2009)
==========================================================

Fixes
-----
1. Problem: (CQ 42723) KCQ not resetting to 0 problem

Cause: RCU deadlock during shutdown

Change: Move the bnx2_register_cnic() call out of the
above sequence. Instead, register and
unregister during NETDEV_UP/NETDEV_DOWN events.

Change all slow path RCU read locks to mutex.
In cnic, we also use reference counting to
protect some slow paths.

Impact: bnx2 iSCSI, bnx2x iSCSI


bnx2 v1.9.22b (July 23, 2009) cnic v1.9.4 (July 23, 2009)
==========================================================

Enhancements
------------
1. Change: If a TX timeout occurs, there could be the possiblity that the
chip is hung. By printing chip state into the kernel ring buffer,
it will be easier to determine this.

Impact: bnx2 iSCSI.

2. Change: The bnx2 firmware should always be matched with the proper bnx2
driver. The bnx2 firmware version string are now printed.
It will be easier to identify the running firmware.

Impact: bnx2

3. Change: When a TX timeout occurs and the chip is reset, the ability to
debug the chip further is lost. This is because the chip state
information is lost during the reset. The users have a choice
to prevent the chip reset.

Impact: bnx2

4. Change: Add a check to see if there was a KCQ overflow was
in the bnx2x firmware. Now this check has been moved to the
CNIC so that the driver could control the cleanup/recovery.

Impact: bnx2 iSCSI.


bnx2 v1.9.21b (July 16, 2009)
==========================================================
Enhancements
------------
1. Change: Updated firmware to 5.0.0.j2 to fix remote reset problem

Impact: bnx2 iSCSI.


bnx2 v1.9.20b (July 09, 2009), cnic v1.9.3 (July 09, 2009)
==========================================================
Fixes
-----
1. Problem: (CQ42534) cnic.c does not compile on older kernels.

Cause: Some iscsi_proto constants not defined in

Change: Added the constant definitions if not already defined.

Impact: None.

Enhancements
------------
1. Change: Updated firmware to 5.0.0.j to fix TMF releated iSCSI issues.

Impact: bnx2 iSCSI.

bnx2 v1.9.19b (July 01, 2009), cnic v1.9.2 (July 01, 2009)
==========================================================
Fixes
-----
1. Problem: (CQ42399) 10G iSCSI fails when initiator and target MTUs
don't match.

Cause: cnic driver sets the MSS without knowing the actual MSS
option and timestamp option during TCP connection.

Change: Changed driver to set MSS to 0xffff so that firmware can
calculate MSS on its own.

Impact: bnx2x iSCSI.

2. Problem: 1G iSCSI fails when initiator and target MTUs don't
match and timestamp is enabled.

Cause: Firmware was not adjusting for the 12-byte timestamp option
if MSS was reduced by MSS option.

Change Updated firmware to 5.0.0.i

Impact: bnx2 iSCSI.

3. Problem: (CQ42353) Unable to disable TCP timestamp on 10G iSCSI.

Cause: Timestamp was hardcoded to be enabled for 10G.

Change: Update global timestamp option during each TCP connection.

Impact: bnx2x iSCSI.

4. Problem: (CQ42329) bnx2x MC assert during IPv6 login/logout.

Cause: EQ filled with more than 128 L4 kcqes without MSI-X interrupt
for 2 seconds. The driver can only buffer 128 L4 kcqes.

Change: Increased L4 kcqe buffer to 256 entries as a temporary solution.
Need to understand the delayed interrupt issue.

Impact: None.

bnx2 v1.9.18b (June 25, 2009), cnic v1.9.1 (June 24, 2009)
==========================================================
Enhancements
------------
1. Change: Added FTQDiscard counter to the list of counters being
reported. During small packet test, there may be FTQ
overflow and this counter is very useful.

Impact: None.

2. Change: Updated firmware to 5.0.0.h to improve small packet L2
performance and to enhance iSCSI TMF handling.

Impact: 5706/5708/5709.

bnx2 v1.9.17b (June 24, 2009), cnic v1.9.1 (June 24, 2009)
==========================================
Fixes
-----
1. Problem: Leaking NetQueues if the firmware did not respond in time

Cause: System might be clogged and there is not enough time to
process the KCQ

Change: Updated driver/firmware to allow the calling of the free RX
queue request before a RX alloc request is issued

Impact: 5709

2. Problem: An offloaded iSCSI connection would get stuck

Cause: Issing an offload request might fail, and this was not handled
properly.

Change: Updated driver/firmware to return the proper return code and
handle offload connection failures.

Impact: 5706/5708/5709

3. Problem: tasklet_init() is being called on a task that is scheduled

Cause: When the CNIC calls register_device(), that task might already
be schedled.

Change: tasklet_disable() is insufficient because the tasklet remains
scheduled and stays on the tasklet list, instead tasklet_kill()
is now used.

Impact: 5706/5708/5709



bnx2 v1.9.16b (June 10, 2009), cnic v1.9.0 (June 10, 2009)
==========================================================
Enhancements
------------
1. Change: (CQ38228) Use symbol_get() for ipv6 symbols so that the
cnic driver will load without necessarily loading ipv6
modules.

Impact: iSCSI over IPv6.

2. Change: Updated 5706/08/09 MIPS firmware to 5.0.0.g.

Impact: 5706/08/09.

3. Change: Backported some dma_mapping_error() checking.

Impact: None.

bnx2 v1.9.15b (June 1, 2009), cnic v1.8.6 (June 1, 2009)
========================================================
Enhancements
------------
1. Change: Upstream bnx2 tx path optimizations. Please see ChangeLog.

Impact: bnx2 tx path.

2. Change: In the cnic driver, save the last allocated TCP port during
unregistration so that previously used TCP ports will not
be immediately re-used.

Impact: iSCSI.

3. Change: VMWare TCP port allocation changes.

Impact: VMWare iSCSI.

bnx2 v1.9.14b (May 21, 2009)
==========================================
Fixes
-----
1. Problem: NOPOUT timeouts on 570x iSCSI connections.

Cause: Bugs in TCP timestamp implementation.

Change: Updated MIPS firmware to 5.0.0.f.

Impact: 5706/5708/5709.

bnx2 v1.9.13b (May 18, 2009)
==========================================
Fixes
-----
1. Problem: Potentially exceeding the NetQueue limit recommendations
by VMware which could stress system resources

Cause: When system resources are strained.

Change: There are now limits on the number of NetQueues which the
driver will request:
When the MTU is 1500 the max number of queues per port is 8
When the MTU is 9000 the max number of queues per port is 4

Impact: NetQueue enabled version of VMware ESX

2. Problem: Getting conflicting NetQueue and iSCSI completions

Cause: When MSI-X is not used on a 5709, NetQueue is still enabled

Change: NetQueue is not disabled is MSI-X is not used.

Impact: NetQueue enabled version of VMware ESX


bnx2 v1.9.12b (May 13, 2009)
==========================================
Fixes
-----
1. Problem: Potentially returning a negative number of NetQueues

Cause: When calculating the number of rings, we use the calculation from
the number of msi-x vectors returned, The number of NetQueues
returned could potentially be negitive if only 1 vector was
returned. This is because the driver was subtracting 2
instead of subtracting 1 (for the default queue) from the total
number of rings.

Change: Return the proper number of queues not including the default
queue.

Impact: NetQueue enabled version of VMware ESX

bnx2 v1.9.11b (May 12, 2009), cnic v1.8.5 (May 13, 2009)
========================================================
Fixes
-----
1. Problem: TCP Delay ACK not working on bnx2x iSCSI

Cause: Disabled in cnic driver.

Change: Fixed csk->tcp_flags definitions and enabled the proper storm
bit for delay ACK.

Impact: bnx2x iSCSI.

bnx2 v1.9.11b (May 12, 2009)
==========================================
Fixes
-----
1. Problem: iSCSI timestamp TCP option not working.

Cause: Disabled in firmware.

Change: Updated to 5.0.0e MIPS firmware.

Impact: 5709.

bnx2 v1.9.10b, cnic v1.8.4 (May 11, 2009)
==========================================
Fixes
-----
1. Problem: NetQ and iSCSI do not work in Vmware environment.

Cause: 1. cnic driver is overwriting CP and COM mailbox bit values newly
defined to support multiple kcqs.

2. Firmware is completing some iSCSI kcqes on the NetQ's kcq.

Change: Fixed cnic driver to only set and clear bit 0 of the CP
and COM mailbox.

Firmware has been updated to 5.0.0d. This firmware also
supports TCP timestamp option for iSCSI connections.

Impact: 5706/5708/5709 iSCSI, NetQ.

bnx2 v1.9.9b (May 1, 2009)
==========================================
Fixes
-----
1. Problem: There is link, but can't pass traffic on ESXi

Cause: Bits in the RX context are being trampled during the
renegotiation of the link.

Change: RX context offset 0x6 should only be initialized once
during init and not be updated during run-time. Offset
4 contains the BIDX that's mapped to the mailbox.

Impact: VMware with NetQueue

bnx2 v1.9.8b, cnic v1.8.2 (April 27, 2009)
==========================================
Enhancements
------------
1. Change: Updated cnic driver to support 1.50.x HSI as well as the older
1.48.107 HSI. A compile flag will be used to select one or the
other.

Impact: iSCSI on bnx2x.

2. Change: Spec file and Makefile changes detect the proper module
install directory.

Impact: installation.

bnx2 v1.9.7b, cnic v1.8.1 (April 22, 2009)
==========================================
Fixes
-----
1. Problem: Compile error with redfinition of struct kwqe.

Cause: Both the CNIC and bnx2 defined this structure.

Change: Because the bnx2 definition is L2 specific, it was renamed to
struct l2_kwqe.

Impact: None.

2. Problem: Add context memory DMA alignment for 57710.

Cause: For the 57710 context memory needs to be 16k aligned.
Without this alignment you will see errors when trying to
establish more then 5 iSCSI connections on VMware ESX 4.0 U1.

Change: Properly aligned the context memory by allocating a bigger
chunk of memory and then finding the proper alignment.
This reduces the number of possible connections in half
but now we can properly establish more then 5 connections
on VMware.

Impact: iSCSI.


bnx2 v1.9.6b (April 17, 2009)
=============================
Enhancements
------------
1. Change: Added NetQueue support for VMware.

Impact: 5709.

bnx2 v1.9.5b (April 17, 2009)
=============================
Enhancements
------------
1. Change: Updated to 5.0.0.a firmware with NetQ support and iSCSI max
connection license information. RV2P firmware unchanged:
4.6.16 for 5706, 4.6.15 for 5709.

Impact: All chips.

2. Change: Set USE_INT_PARAM on 5709. This will switch the chip in
use "interrupt mode" coalescing after MSI/MSI-X.

Impact: 5709.

3. Change: Included 5706 when doing statistics block DMA workaround.

Impact: 5706.

bnx2 v1.8.8b (March 12, 2009)
=============================
Enhancements
------------
1. Change: Updated to latest 4.6.17 CP firmware for 5709.

Impact: iSCSI licensing on 5709.

bnx2 v1.8.7b, cnic v1.7.8 (March 10, 2009)
==========================================
Enhancements
------------
1. Change: Reverted 5706/5708 firmware to 4.6.16. Low latency interrupt
mode does not work on 5706/5708.

Impact: None.

2. Change: VMWare changes to expose max. number of iSCSI connections in
the cnic_device structure.

Impact: VMware iSCSI.

Fixes
-----
1. Problem: (CQ39867) Compile error on RHEL5.3 Xen kernel.

Cause: msi related symbols undefined because CONFIG_PCI_MSI is not
enabled on Xen kernels.

Change: Added CONFIG_PCI_MSI around the msi related code.

Impact: None.

2. Problem: (CQ39818) iSCSI targets do not reconnect after running self test.

Cause: Interrupt is disabled by bnx2 before notifying CNIC to clean up
and stop. As a result, bnx2i will not receive interrupts when
closing the connections if sharing INTA/MSI with network.

Change: Disable interrupt after notifying CNIC to stop.

Impact: iSCSI.

bnx2 v1.8.6b, cnic v1.7.7 (March 2, 2009)
=========================================
Enhancements
------------
1. Change: Updated to new 5706 firmware (4.6.17) and 5709 firmware (4.6.16).
New interrupt coalescing mode for improved latency and iSCSI
cache line fix on 5709.

Impact: All bnx2 chips.

2. Change: CNIC iSCSI changes for VMWare.

Impact: VMWare only.

bnx2 v1.8.5b, cnic v1.7.6 (Feb 9, 2009)
=======================================
Fixes
-----
1. Problem: (CQ39380) bnx2x iSCSI license not read correctly.

Cause: Using wrong variable to check the license.

Change: Fixed the logic.

Impact: bnx2x iSCSI.

2. Problem: Driver accesing MMIO registers during VLAN operations when
the device is in D3hot state in older kernels.

Cause: VLAN registration functions do not check for device state.

Change: Added if_running check before MMIO access in VLAN registration
functions.

Impact: VLAN operations on all bnx2 chips.

Enhancements
-----------
1. Problem: Updated 5706/5708 firmware to 4.6.16.

Impact: 5706/5708.

bnx2 v1.8.4b, cnic v1.7.5 (Jan 30, 2009)
========================================
Fixes
-----
1. Problem: (CQ39281) Management firmware stops passing traffic when
bnx2 driver is loaded with jumbo frames enabled.

Cause: Firmware bug.

Change: Updated to 4.6.15 firmware.

Impact: 5706/5708/5709.

2. Problem: iSCSI does not work on 57711 in single function mode.

Cause: Driver only allows iSCSI on 57711 if iSCSI is enabled.

Change: iSCSI config. not required in single function mode.

Impact: bnx2x iSCSI.

Enhancements
------------
1. Change: (CQ38576) Add 5709 to bnx2.4 man page.

Impact: None.

bnx2 v1.8.3b, cnic v1.7.4 (Jan 23, 2009)
========================================
Fixes
-----
1. Problem: (CQ38610, CQ39000, CQ39015, CQ39071, CQ39133) Various Jumbo
frames related data corruption issues.

Cause: Bug in RV2P firmware causing jumbo frames to be DMA'ed without
the frame header control structure occasionally.

Change: New firmware.

Impact: 5706/5708/5709.

bnx2 v1.8.2c, cnic v1.7.4 (Dec 30, 2008)
========================================
Fixes
-----
1. Problem: (CQ38955) Xen kernel panic when unloading bnx2 with jumbo MTU.

Cause: Bug in bnx2_free_rx_mem(). The jumbo page ring memory was
freed incorrectly using the wrong local variable as array
index.

Change: Fixed bug by using the correct variable as array index.

Impact: Jumbo frames.

2. Problem: (CQ38965) iSCSI connection timeout on bnx2x.

Cause: During CFC Delete RAMROD completion handling, the wrong (older)
iSCSI connection ID can sometimes be retrieved using the
harware CID. The CID in the mapping table was not cleared
after the CID was freed.

Fix: Adding clearing of the CID in the data structure after a CID
is freed.

Impact: bnx2x iSCSI.

Enhancements
------------
1. Change: (CQ38744) Reduced R2TQ memory usage to match new firmware
interface (firmware 4.8.9). This reduces the amount of
kernel memory substantially for each iSCSI connection on
bnx2x.

Impact: bnx2x iSCSI.

bnx2 v1.8.2b, cnic v1.7.3 (Dec 17, 2008)
========================================
Enhancements
------------
1. Change: Added iSCSI configuration check on 57711E devices before
allowing iSCSI connections.

Impact: bnx2x iSCSI.

bnx2 v1.8.2b, cnic v1.7.2 (Nov 25, 2008)
========================================
Fixes
-----
1. Problem: bnx2x iSCSI does not work on functions 2 or above.

Cause: This was caused by multiple problems:
a) Status block ID specified by bnx2x was wrong.
b) MSI-X vector assigned to CNIC was wrong.
c) New method to ack. status block using HC register was not
implemented.
d) Status block ID in CSTORM status block is always 0, and
as a result, the status block ID used to ack. the status
block was wrong.

All these problems only affect functions 2 and above.

Change: All problems fixed in bnx2x and cnic.

Impact: bnx2x iSCSI.

bnx2 v1.8.2b, cnic v1.7.1 (Nov 15, 2008)
========================================
Enhancements
------------
1. Change: Added CNIC support for Multi function bnx2x iSCSI.

Impact: bnx2x iSCSI.

bnx2 v1.8.2b, cnic v1.6.2 (Nov 12, 2008)
========================================
Enhancements
------------
1. Change: Updated to latest 4.6.13 5709 firmware to fix context corruption
with flow control enabled.

Impact: 5709.

2. Change: Added support for 5716S PCI ID.

Impact: None.

Fixes
-----
1. Problem: (CQ35904) Netdump does not work.

Cause: Problem introduced by MSI-X multiqueue. IRQ handlers were
changed to take bnx2_napi parameter instead of netdev parameter.

Change: Fixed by passing proper parameter to IRQ handler from netpoll.
All IRQ handlers are called when using multiple MSI-X vectors.

Impact: 5709 netpoll.

bnx2 v1.8.1f, cnic v1.6.1 (Nov 5, 2008)
========================================
Fixes
-----
1. Problem: All TSO packets corrupted on 5706/5708.

Cause: Firmware bug zeroing the wrong field in IP header.

Change: Updated to latest 4.6.11 5706/5708 firmware and 4.6.12 5709
Firmware.

Impact: 5706/5708/5709.

2. Problem: bnx2x chip asserts when trying to make iSCSI connection
to an unknown IP address.

Cause: When connection fails, the driver sends a command to an
unitialized CID.

Change: Added logic to only send deletion commands to initialized
CIDs.

Impact: bnx2x iSCSI.

Enhancements
------------
1. Change: Added support for one single VLAN to a bnx2x iSCSI interface.

Impact: bnx2x iSCSI.

bnx2 v1.8.1e, cnic v1.6.0 (Oct 27, 2008)
========================================
1. Change: Updated to latest 5709 firmware to fix iSCSI data integrity
problem.

Impact: 5709.

bnx2 v1.8.1d, cnic v1.6.0 (Oct 23, 2008)
========================================
Enhancements
------------
1. Change: Updated to latest bnx2 firmware to fix iSCSI data integrity
problem.

Impact: 5706/5708/5709.

2. Change: Updated to the latest bnx2x HSI files.

Impact: bnx2x iSCSI.

bnx2 v1.8.1c, cnic v1.5.9 (Oct 13, 2008)
========================================
Fixes
-----
1. Problem: (CQ37905) Unable to compile on SLES10 SP2.

Cause: DIV_ROUND_UP macro not defined in this kernel.

Change: Added it for compatibility.

Impact: None.

Enhancements
------------
1. Change: Updated to latest 5709 firmware that fixes an NCSI problem.

Impact: 5709.

2. Change: Handle TCP reset in the middle of TCP close more appropriately.

Impact: iSCSI.

3. Change: Handle iSCSI license checking in the same way as 5708/5709.

Impact: iSCSI on bnx2x.

bnx2 v1.8.1b, cnic v1.5.8 (Oct 13, 2008)
========================================
Fixes
-----
1. Problem: bnx2x iSCSI CIDs may be allocated outside the range of allocated
host memory.

Cause: CID range bigger than the amount of allocated host context
memory.

Change: Changed to match the CID range with memory range.

Impact: bnx2x iSCSI.

Enhancements
------------
1. Change: Sync'ed with the latest upstream driver bnx2 1.8.1.

Impact: None.

2. Change: Implemented iSCSI connection license enforcement for bnx2x
devices.

Impact: bnx2x iSCSI.

bnx2 v1.8.0j, cnic v1.5.7 (Oct 6, 2008)
========================================
Fixes
-----
1. Problem: (CQ37610) Chip hangs when changing MTU with active iSCSI
connections.

Cause: Both cnic and bnx2 drivers setting up the chip at the same
time.

Change: Added check so that the register_cnic function will fail
if the bnx2 driver is in reset.

Impact: iSCSI.

2. Problem: (CQ37762) Able to unload bnx2/bnx2x drivers while there are
active iSCSI connections.

Cause: CNIC driver does not have a reference count on the BNX2/BNX2X
drivers.

Change: This became a problem after the register_cnic function was
no longer exported. To solve the problem, the CNIC driver
will now get an explicit reference during register_cnic.

Impact: iSCSI.

3. Problem: (CQ37429) MMIO access while the chip is in D3hot state.

Cause: The driver does not check if_running state consistently during
ethtool operations.

Change: Added proper checks to all ethtool and multicast change
functions.

Impact: ethtool operations and multicast operations.

Enhancements
------------
1. Change: Simplified ipv4 TSO logic in the driver. This was made
possible with newer 5708 firmware.

Impact: 5708 TSO and other traffic.

2. Change: ethtool -p now blinks forever. This is the standard behavior
in most other net drivers.

Impact: ethtool -p.

bnx2 v1.8.0i, cnic v1.5.5 (Sep 30, 2008)
========================================
Fixes
-----
1. Problem: (CQ36787) iSCSI login/logout commands fail on 5709 after a
while.

Cause: Not handling the KWQ completion properly on 5709 in INTA/MSI
mode.

Change: Changed to handle KWQ completions by checking the
cmd_consumer_index instead of the rx_quick_index15.

Impact: 5709 ISCSI in INTA/MSI mode.

2. Problem: (CQ37497) CNIC driver does not compile on powerpc.

Cause: csum_ipv6_magic() not defined.

Change: Added #include

Impact: None.

v1.8.0g (Sep 24, 2008)
========================
Fixes
-----
1. Problem: (CQ37511) System locks up when loading cnic driver on 2.6.16
kernel.

Cause: symbol_put_addr() in 2.6.16 tries to acquire the same lock twice.

Change: Workaround by using __symbol_put() which does not have the same
problem.

Impact: None.

v1.8.0f (Sep 23, 2008)
========================
Fixes
-----
1. Problem: (CQ37405) Kernel panic when performing ifup/ifdown with iSCSI
connections on bnx2x devices.

Cause: Sending searcher delete to bnx2x devices when connection was
not established (due to Spanning Tree or other reasons).

Change: Check PG offload state before sending searcher delete.

Impact: iSCSI on bnx2x.

v1.8.0e (Sep 22, 2008)
========================
Enhancement
-----------
1. Change: Updated to latest driver firmware 4.6.6 for 5709.

Impact: 5709.

2. Change: Updated cnic so that it will not crash even if using older
bnx2/bnx2x drivers without CNIC support. The net driver
can also be loaded after cnic and it will still work without
crashing.

Impact: iSCSI.

3. Change: (CQ 37381) Updated driver to check Vaux PRESET before allowing
WoL. This is needed to support 5709 quad-port boards.

Impact: WoL on all devices.

v1.8.0d (Sep 15, 2008)
========================
Enhancements
------------
1. Change: Updated CNIC iSCSI setup for bnx2x devices.

Impact: iSCSI on bnx2x devices.

v1.8.0c (Aug 25, 2008)
========================
Fixes
-----
1. Problem: Does not compile on older kernels.

Cause: "__maybe_unused" undefined on older kernels. "num_online_cpus()"
undefined on 2.4 kernels.

Change: Added compatibility code to workaround.

Impact: None.

v1.8.0b (Aug 25, 2008)
========================
Enhancement
-----------
1. Change: Updated to latest driver firmware 4.6.2 for 5709.

Impact: 5709.

v1.7.9c (Aug 5, 2008)
========================
Fixes
-----
1. Problem: bnx2 does not compile on older kernels.

Cause: is missing on 2.6.19 and older kernels.

Change: Added compatibility code to check for kernel version before
including the file.

Impact: none.

v1.7.9b (Aug 5, 2008)
========================
Enhancements
------------
1. Change: Added multi-tx ring for 5709. This fetaure is available on
2.6.27 kernel when using MSI-X.

Impact: 5709

2. Change: Added support for 57710 iSCSI in the CNIC driver.

Impact: iSCSI.

v1.7.7c (July 14, 2008)
========================
Fixes
-----
1. Problem: Source RPM fails to build.

Cause: New file missing in tarball.

Change: Added missing file.

Impact: None.

v1.7.7b (July 9, 2008)
========================
Enhancements
------------
1. Change: Added probe function so that the CNIC driver can get the
pci_device pointer earlier before registration.

Impact: iSCSI.

2. Change: Added support for 5716.

Impact: None.

v1.7.6c (June 6, 2008)
========================
Enhancements
------------
1. Change: Added multi-ring RX support on 5709 using MSI-X. This feature
is only available on 2.6.24 and newer kernels running on SMP
machines.

Impact: 5709.

2. Change: Added secondary unicast address support. We now support up
to 5 unicast addresses. This feature is only available on
2.6.23 and newer kernels.

Impact: All chips.

v1.7.6b.1 (Aug 14, 2008)
========================
Fixes
-----
1. Problem: (CQ36808) VLAN tagged packets received by host stack without
the VLAN tag.

Cause: If no VLANs are set up using vconfig, and if the driver
configures the chip to strip the VLAN tag, the problem can
happen. With IPMI or UMP enabled, the driver is likely to
configure the chip to strip the VLAN tag.

Change: Modified the driver to re-insert the VLAN tag when necessary.
I.e. when IPMI/UMP is enabled and vconfig has not setup any
VLANs.

Impact: All chips receiving VLAN traffic.

v1.7.6b (May 29, 2008)
========================
Fixes
-----
1. Problem: IPv4 TSO generates bad packet when the TSO packet size
is 1-MSS.

Cause: Probably firmware does not expect this boundary condition.

Change: Detect this 1-MSS condition in driver and skip the TSO logic.
1-MSS TSO packet will be treated like a regular TX checksum
offload packet.

Impact: TSO on all chips.

2. Problem: Cannot disable VLAN stripping even when management firmware
is disabled.

Cause: The new logic to check firmware VLAN stripping capability
was buggy.

Change: Fixed the code so that VLAN stripping can always be disabled
if management firmware is disabled.

Impact: VLAN/management firmware.

v1.7.5d (May 13, 2008)
========================
Enhancements
------------
1. Change: Incorporated latest firmware 4.4.18. Bug fix is in
RV2P.

Impact: All chips.

v1.7.5c (May 7, 2008)
========================
Enhancements
------------
1. Change: Incorporated latest firmware 4.4.17. Bug fix is in
RV2P.

Impact: All chips.

v1.7.5b (May 5, 2008)
========================
Fixes
-----
1. Problem: (CQ35080) Hard lock when running ethtool -s on the device
that is in the down state.

Cause: I/O to the device to set link speed in D3-hot state can cause
lockup because the chip does not respond to I/O.

Change: ethtool -s will just store the new settings without configuring
the new speed. When the device is later brought up, the new
speed will be set as part of chip init.

Impact: All chips.

2. Problem: (CQ35075 CQ35042) Various compile errors on SuSE SLES 9 and SLES
10 distro kernels.

Cause: ip_hdr() and __le32/__le32 backported to the distro kernels.

Change: Adjusted compatibility defines.

Impact: None.

Enhancements
------------
1. Change: Incorporated latest 5709 firmware 4.4.16. Timer context
scanning is reduced with this firmware to 500us. With this,
the temporary enhancement in 1.7.4c #2 has been removed.

Impact: 5709 iSCSI.

v1.7.4e (April 26, 2008)
========================
Fixes
-----
1. Problem: (CQ34841) 5709 does not link up on some remote PHY systems.

Cause: No initial link interrupt.

Change: Added code to poll for link when remote PHY is present.

Impact: Remote PHY systems.

2. Problem: (CQ34767) Kernel panic on 5709 when using jumbo frames
with NCSI traffic.

Cause: RV2P bug causing RX packets to overwrite kernel memory.

Change: Updated to latest RV2P code for 5709 and 5708.

Impact: 5706/5708/5709.

v1.7.4d (April 17, 2008)
========================
Fixes
-----
1. Problem: IPv6 iSCSI does not work.

Cause: Added code in the last version 1.7.3c to check for CONFIG_IPV6
before enabling the IPv6 CNIC support. This failed to check
for CONFIG_IPV6_MODULE if IPv6 is configured as module in the
kernel configuration.

Change: Changed the checking to CONFIG_IPV6 or CONFIG_IPV6_MODULE.

Impact: None.

v1.7.4c (April 16, 2008)
========================
Fixes
-----
1. Problem: (CQ34814, CQ33984) Driver does not compile on 2.4 kernels.

Cause: __le32 and __be32 not defined in 2.4 kernels.

Change: Defined these as u32 on 2.4 kernels.

Impact: 2.4 kernels.

Enhancements
------------
1. Change: Incorporated latest 5709 4.4.12 firmware to fix various iSCSI
problems.

Impact: 5709.

2. Change: Slowed down the timer block reload time. It was noticed that
after the CNIC driver was unloaded, the timer context memory
was reloaded in a tight loop by the chip. This issue needs
to be properly addressed in the firmware at a future date.

Impact: iSCSI.

v1.7.4b (April 11, 2008)
=======================
Enhancements
------------
1. Change: Incorporated latest 5709 4.4.11 firmware to fix various iSCSI
problems.

Impact: 5709.

v1.7.3k (April 9, 2008)
=======================
Enhancements
------------
1. Change: Incorporated latest 5709 4.4.10 firmware to fix various iSCSI
problems. CID ranges are now read directly from shared memory.

Impact: 5709.

v1.7.3j (April 7, 2008)
=======================
Fixes
-----
1. Problem: (CQ33967) Ethtool register test fails.

Cause: Register 0x1004 context status register should not be tested.

Change: Removed 0x1004 from register test.

Impact: None.

Enhancements
------------
1. Change: Incorporated latest 5709 4.4.9 firmware to fix various iSCSI
problems.

Impact: 5709.

v1.7.3i (April 4, 2008)
=======================
Fixes
-----
1. Problem: (CQ33948) iSCSI over IPv6 does not work on SLES10.

Cause: The CNIC driver does not handle IPv6 on older kernels without
NETEVENTS support.

Change: Modified the logic to support older kernels.

Impact: All iSCSI connections using IPv4 or IPv6.

2. Problem: (CQ34315) Scanning iSCSI disks during max sessions test causes
connection problems.

Cause: 5709 context memeory allocated by CNIC driver does not match
the iSCSI and PG CID range used by the firmware.

Change: Changed to the matching CID range.

Impact: 5709 iSCSI.

v1.7.3h (March 28, 2008)
=======================
Fixes
-----
1. Problem: (CQ33984, CQ34210, CQ34310, CQ34597) Various compiler warnings
and errors on RHEL, SuSE, and 2.4 kernels.

Cause: New features not compatible with older kernels, or older
vendor kernels backported with newer features.

Change: Fine-tuned compatibility compiler directives.

Impact: All kernels.

v1.7.3g (March 10, 2008)
=======================
Enhancements
------------
1. Change: Updated to latest 5709 firmware version 4.4.7.

Impact: 5709.

v1.7.3f (March 10, 2008)
=======================
Fixes
-----
1. Problem: CNIC takes a long time to resolve ARP, causing iSCSI to fail.

Cause: NETEVENT_NEIGH_UPDATE event notifier sometimes takes a long time
to be called.

Change: This is under investigation. For now, the workaround is to
use the existing neighbour entry if it is in NUD_VALID state.
Previously, we would only use it if it was in NUD_CONNECTED
state.

Impact: iSCSI neighbour resolution.

2. Problem: iSCSI sometimes fails to initialize.

Cause: The KWQ is in full condition and prevents any KWQE to be sent
to the firmware. This is caused by the KWQ consumer index in
the status block not initializing to 0.

Change: Added workaround to skip the KWQ full condition check when
sending the first KWQE. This should be properly fixed in
firmware.

Impact: None.

v1.7.3d (February 15, 2008)
============================
Fixes
-----
1. Problem: System hangs with iSCSI traffic.

Cause: Infinite loop in NAPI poll.

Change: Fixed the problem of not comparing the CNIC tag properly when
determining whether there is more work in NAPI poll.

Impact: None.

2. Problem: iSCSI does not work on 5709

Cause: Not initializing 5709 properly for iSCSI. The chip_id field was
not propagated to the CNIC driver.

Change: Fixed the chip_id field.

Impact: None.

v1.7.3c (February 09, 2008)
============================
Enhancements
------------
1. Change: Updated 5708 and 5709 firmware to version 4.4.2.

Impact: All devices.

2. Change: Updated RV2P firmware to the latest. This may fix the jumbo
frame issue.

Impact: All devices, especially jumbo frames on 5709 Bx.

3. Change: Modified CNIC interface in preparation for 57710 devices.

Impact: iSCSI.

v1.7.2f (February 04, 2008)
============================
Fixes
-----
1. Problem: Temporary workaround for one prototype 5709S mezz. card not
working.

Cause: The driver was looking at the wrong shared memory location to
identify the card.

Change: Fixed the code to check the correct BNX2_SHARED_HW_CFG_CONFIG
location.

Impact: 5709S.

v1.7.2e (January 31, 2008)
============================
Fixes
-----
1. Problem: (CQ33704) CNIC driver fails MSI-X mode on 5709.

Cause: When implementing the fix, the wrong constant was used
for the CNIC MSI-X vector.

Change: Corrected to use the correct constant BNX2_CNIC_VEC.

Impact: None.

2. Problem: iSCSI outgoing packets over IPv6 are bigger than 1518 bytes.

Cause: MSS calculation was based on IPv4 and did not accout for the
IPv6 header size.

Change: Adjusted MSS calculation for IPv6.

Impact: None.

v1.7.2c (January 30, 2008)
============================
Fixes
-----
1. Problem: CNIC driver does not work in MSI-X mode on 5709.

Cause: This is a regression caused by moving the CNIC MSI-X
vector from 8 to 2. The context memory did not get
updated with the new vector.

Change: Changed the definition. All bits that depend on the
MSI-X vector will now have the proper definitions automatically.

Impact: None.

v1.7.2b (January 30, 2008)
============================
Enhancements
------------
1. Change: Updated 5709 firmware to 4.4.1.

Impact: 5709.

2. Change: Added temporary workaround for one prototype 5709S mezz. card.
The workaround will be removed once newer cards are available.

Impact: 5709S.

v1.7.1e (January 14, 2008)
============================
Enhancements
------------
1. Change: Updated 5709 firmware to 4.1.1 for IPv6 iSCSI support.

Impact: 5709.

2. Change: Updated 5708 RXP firmware to 4.1.1.

Impact: 5706/5708.

3. Change: Updated RV2P firmware for 5709.

Impact: 5709.

4. Change: Added IPv6 support to CNIC driver.

Impact: New BNX2I driver must be used with this new CNIC driver.

v1.7.1d.3 (February 7, 2008)
============================
Fixes
-----
1. Problem: 5706S continues to not link down occasionally on some blade
systems.

Cause: In some cases, even turning off the tx current does not
cause the link to go down.

Change: Link transition can be triggered based on the SYNC_FAILED bit
in the AN_DEBUG register when all else fails.

Impact: 5706S.

v1.7.1d.1 (February 1, 2008)
============================
Fixes
-----
1. Problem: 5706S still not linking down occasionally on some blade
systems when the switch blade is disconnected.

Cause: Occasionally, all the bits that we check will falsely
indicate link up and trigger the parallel detect logic on
this blade platform. Once in parallel detect mode with
autoneg disabled, the driver will never detect link down.

Change: Disabled parallel detect on this platform by checking
PCI sub IDs to identify the device.

Impact: Parallel detect not supported on this vendor device.

v1.7.1d (January 25, 2008)
============================
Fixes
-----
1. Problem: 5706S still not linking down on some blade systems when the
switch blade is disconnected.

Cause: This is the same problem that was fixed in 1.7.0b. After
switch module is removed, the SYNC_FAILED bit sometimes
toggles low, and this causes the parallel detect logic in the
driver to trigger and disable autoneg. Disabling autoneg
causes false link to come up immediately.

Change: It seems that the RUDI_INVALID bit can be used to prevent the
above from happening. Modified parallel detect code to
additionally check the RUDI_INVALID bit and trigger only when
the bit is cleared.

Impact: Parallel detect logic in 5706S.

v1.7.1c (December 27, 2007)
============================
Fixes
-----
1. Problem: Driver crashes when adding VLAN and bonding.

Cause: Bonding calls driver's VLAN function in interrupt context with lock
held. We recently added a VLAN feature in 1.6.8b which requires
chip reset when VLANs are added or removed. The reset will call
vmalloc/vfree which must not be called in interrupt context.

Change: Reverted the VLAN feature for now. Will workaround it in the
future.

Impact: 5709 only. This new VLAN feature is no longer available.

v1.7.1b (December 24, 2007)
============================
Fixes
-----
1. Problem: Driver crashes when using jumbo frames on 5709 A1.

Cause: RV2P firmware problem.

Change: Disabled jumbo page ring on 5709 Ax chips.

Impact: Jumbo receive page rings not supported on 5709 Ax.

2. Problem: CNIC driver prints "Failed waiting for ref count to go to zero"
when unloading the driver. This is a minor cosmetic issue.

Cause: Minor bug in driver comparing ref_count to 1 instead of zero
during exit.

Change: Fixed the code to check for ref_count == 0.

Impact: None.

v1.7.0b (December 12, 2007)
============================
Fixes
-----
1. Problem: (CQ33032) CPU utilization increases dramatically when TSO
is enabled.

Cause: Driver is spending a lot of unnecessary time in TX handling
code when TSO is enabled. This regression was introduced when
the TX handling code was changed to match the RX handling code.
The RX handling code was changed to fix a packet rot problem.
When TSO is enabled, the tx index can stop at non-packet
boundaries and the code will keep waiting until it gets to the
next packet boundary.

Change: Fixed it to handle this condition properly.

Impact: None.

2. Problem: 5706S does not link down in some blade systems.

Cause: Hardware problem.

Change: Added workaround logic to check periodically and force a
link down when the PHY reports SYNC status failed. This
only works when autoneg is enabled.

Impact: 5706S.

v1.6.8e (December 10, 2007)
============================
Fixes
-----
1. Problem: When using jumbo MTU with large RX ring sizes, system will
crash or the driver won't load.

Cause: Bug in driver where the page descriptor array was declared
too small.

Change: Fixed the array size.

Impact: None.

2. Problem: CNIC driver won't compile on kernels without CONFIG_PCI_MSI.

Cause: Some code needs to be conditionally compiled only when
CONFIG_PCI_MSI is set.

Change: Added #ifdef CONFIG_PCI_MSI where necessary.

Impact: None.

3. Change: Disabled iSCSI on 5709 until next release.

Impact: None.

v1.6.8d (December 07, 2007)
============================
Change: Reverted the 5706S workaround made in 1.6.8c because it was
unreliable.

Impact: None.

v1.6.8c (December 07, 2007)
============================
Fixes
-----
1. Problem: (CQ32794) Kernel panic (skb_over_panic) with jumbo frames.

Cause: RV2P firmware incorrectly placed jumbo data into SKB.

Change: New RV2P firmware.

Impact: Jumbo frames on all hardware.

2. Problem: (CQ32817) ethtool loopback test fails.
3. Problem: (CQ32842) Chariot test fails.

Cause: RX buffer size too small to contain MTU-sized frame.
This was introduced by the new Jumbo RX logic.

Change: Fixed RX buffer size logic.

Impact: Traffic on all hardware.

4. Problem: (CQ32862) Fails to compile on RH9u9.

Cause: Kernel API skb_fill_page_desc() backported to RH kernel
causing duplicate definition.

Change: Adjusted compatibility code.

Impact: None.

5. Problem: (CQ32866) ISCSI driver fails to compile with 1.6.8b.

Cause: print_mac() multiply defined when bnx2.h is included
in the bnx2i driver.

Change: Changed print_mac() to static inline.

Impact: None.

6. Problem: 5706S does not link down in some blade systems.

Cause: Hardware problem.

Change: Added workaround logic to check periodically.

Impact: 5706S.

Enhancements
------------
1. Change: Added flow control logic on 5709.

Impact: 5709.

2. Change: Updated all firmware to 4.0.5.

Impact: All hardware.

v1.6.8b (November 28, 2007)
============================
Enhancements
------------
1. Change: Added MSIX support for 5709 B0.

Impact: 5709 B0.

2. Change: Added multi-page buffer support for Receive Jumbo frames.

Impact: All chips. This feature is experimental at this point.

3. Change: Allow VLAN tags in receive packets when management firmware
is enabled.

Impact: 5709 only. This feature is experimental and requires new
boot code and UMP/IPMI code.

4. Change: Updated firmware to 4.0.3.

Impact: All chips.

v1.6.7b (October 16, 2007)
============================
Fixes
-----
1. Problem: (CQ31861) Remote copper PHY does not link up if WoL is enabled.

Cause: bnx2_set_power_state() assumes that only copper devices support
WoL and proceeds to configure the copper PHY to 10/100 Mbps.
This assumption is no longer valid after Serdes WoL support
was added in 1.6.3c.

Change: Fixed the code to take check for Serdes and copper when setting
up the PHY for WoL.

Impact: WoL.

v1.6.6b (October 10, 2007)
============================
1. Change: Update 5708 firmware to 3.7.19.

v1.6.5k (October 10, 2007)
============================
1. Problem: Will not compile on 2.6.23 kernel.

Cause: get_perm_addr no longer defined in struct ethtool_ops

Change: Adjusted kernel compatibility #ifdef.

Impact: None.

v1.6.5j (October 10, 2007)
============================
No change to bnx2. Updated cnic driver to 1.1.24.

v1.6.5i (October 8, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to 3.7.18.

v1.6.5h (October 4, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to 3.7.17.

v1.6.5g (October 1, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to 3.7.16.

v1.6.5f (September 30, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to newer 3.7.15.

v1.6.5e (September 29, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to 3.7.15.

v1.6.5d (September 28, 2007)
============================
Enhancements
------------
1. Change: Combined RPM package and tar file with CNIC driver.

v1.6.5c (September 26, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to 3.7.14.

v1.6.5b (September 25, 2007)
============================
Fixes
-----
1. Problem: (CQ30086) 5709 A1 does not link up when connected to
some Broadcom devices.

Cause: Early DAC wakeup workaround needed for 5709 A1.

Change: Added workaround.

Impact: None.

Enhancements
------------
1. Change: Added CNIC support for iSCSI.

Impact: Only enabled on 2.6.16 and newer kernels.

v1.6.3c (July 23, 2007)
=======================
Fixes
-----
1. Problem: (CQ30591) ethtool -t fails on remote PHY systems.

Cause: Link test and loopback test were not modified to support
remote PHY.

Change: Added remote PHY support to link test and changed the code
to skip PHY loopback on remote PHY since it's not supported.

Impact: None.

2. Problem: (CQ30625) ethtool speed settings are lost after ifdown.

Cause: The remote PHY settings stored in firmware is not the same
as the driver's last setting.

Change: Modified the code to keep the driver's setting unless there's
is change in the remote PHY media.

Impact: ethtool -s on remote PHY systems.

Enhancements
------------
1. Change: Change ethtool's wol setting to NVRAM's default and
add support for Serdes WoL if NVRAM supports it.

Impact: ethtool wol's default setting.

v1.6.3b (July 13, 2007)
=======================
1. Problem: Problems reading and writing flash on 5709.

Cause: Hardware changes in 5709.

Change: Rearranged current flash code to properly support 5709.

Impact: Changes will impact flash operations on 5706/5708/5709 devices.

2. Problem: (CQ30516) Management firmware version string disappears
on 2nd modprobe of the driver.

Cause: The 2nd modprobe will program the device back to D0 from D3hot.
This causes a reset and it will take some time before the
management firmware information will be available.

Change: Added a proper wait loop to wait for the firmware information
to be deposited in shared memory.

Impact: None.

v1.6.2f (July 3, 2007)
=======================
1. Problem: The fix for CQ29488 in the previous version is problematic
and needs to be reverted.

Cause: Adding the netif_carrier_off() call before register_netdev()
in bnx2_init_one() can cause problems if register_netdev()
fails. netif_carrier_off() can queue a link watch event
that can run later. If register_netdev() fails, the netdev
structure will be freed and the link watch event may panic
when it is scheduled to run.

Change: Moving the netif_carrier_off() to after register_netdev()
also will not work as it can cause race conditions with
the interrupt handler. So the best thing to do is to
revert the earlier fix and not address the CQ29488 issue.

Impact: CQ29488 is not fixed.

v1.6.2e (July 3, 2007)
=======================
Fixes:
------
1. Problem: (CQ29528) Link does not come up using remote PHY (continued).

Cause: ifup script may be using mii-tool to obtain link status,
and interfering with remote PHY firmware.

Change: Block mii-tool ioctl access when remote PHY firmware is present.

Impact: None.

2. Problem: (CQ29488) Driver reports link up in ethtool before the interface
is brought up.

Cause: The netdevice structure's initial link setting is up and that
gets reported directly by ethtool.

Change: Added netif_carrier_off() call in bnx2_init_one().

Impact: None.

v1.6.2d (June 22, 2007)
=======================
Fixes:
------
1. Problem: (CQ29528) Link does not come up using remote PHY.

Cause: The fix in 1.6.2b still has a problem. The copper or Serdes
default link setting does not follow the correct port when
the port is changed during chip reset.

Change: Fix the code to always refresh the port and link setting
during chip reset.

Impact: None.

2. Problem: (CQ30181) Cannot compile on 2.4 kernels.

Cause: USEC_TO_SEC constant is not defined on older kernels.

Change: Added conditional #define for this constant on older kernels.

Impact: None.

Enhancements:
-------------
1. Change: Update 5709 firmware to 3.7.1.

Impact: 5709 devices.

v1.6.2b (June 21, 2007)
=======================
Enhancements:
-------------
1. Change: Added management firmware version to ethtool -i.

Impact: None.

Fixes:
------
1. Problem: (CQ29528) Link does not come up using remote PHY.

Cause: The driver is using the wrong port when setting up the remote
PHY link.

Change: Fixed bug to always use the correct requested port or
default port when setting remote PHY link.

Impact: None.

2. Problem: (CQ30028) Advertised Autoneg not set in ethtool.

Cause: Remote PHY code is not setting the flag which is for
information only.

Change: Added code the set the flag for consistency.

Impact: None.

v1.6.1c (May 22, 2007)
=====================
Enhancements:
-------------
1. Change: (CQ28907) Added support for setting copper and fibre speeds.

Impact: Only available on Remote PHY systems.

v1.6.1b (May 7, 2007)
=====================
Fixes:
------
1. Problem: (CQ29301) Setting invalid speed setting causes driver to
crash.

Cause: Lock taken without unlock when exiting iwith error the
procedure to set speed.

Change: Fixed the code with proper unlock.

Impact: None.

v1.6.0b (April 30, 2007)
========================
Enhancements:
-------------
1. Change: Improved handshake with remote PHY firmware.

Impact: None.

v1.5.10c (May 4 , 2007)
=======================
Fixes:
------
1. Problem: Extremely low TSO performance when destination has a
smaller MSS than the source.

Cause: Packets smaller than MTU are not processed as TSO packets.

Change: Removed the SKB length check when doing TSO.

Impact: None.

v1.5.10b (May 1, 2007)
=========================
Enhancements:
-------------
1. Change: Removed Remote PHY until next release.

Impact: No Remote PHY support.

2. Change: Added check for 2.5G capability before enabling 2.5G on
5709S.

Impact: None.

Fixes:
------
1. Problem: (CQ28438) NETDEV WATCHDOG after OS boot.

Cause: The mailbox queue is halted after the OS reads config.
register 0x94.

Change: Set MQ_CONFIG_HALT_DIS in register MQ_CONFIG on 5709 A0 and
A1.

Impact: None.

v1.5.9b (April 20, 2007)
=======================
Enhancements:
-------------
1. Change: Enhanced remote PHY support for 5708S.

Impact: None.

Fixes:
------
1. Problem: (CQ29056) Driver does not compile on SLES 10 SP1 kernel.

Cause: Backported netif_tx_lock() causes compatibility problem.

Change: Adjuested compatibility #ifdef.

Impact: None.

2. Problem: (CQ28880) Driver fails register test after running traffic.

Cause: A reserved register 0x500c was mistakenly included in the test.

Change: Removed this register from the test.

Impact: None.

v1.5.8b (March 13, 2007)
=======================
Enhancements:
-------------
1. Change: Added remote PHY support for 5708S.

Impact: None.

v1.5.7b (March 2, 2007)
=======================
Enhancements:
-------------
1. Change: Added IPV6 TSO for 5709.

Impact: None.

2. Change: Added 2.5G parallel detection for 5709s.

Impact: None.

v1.5.6b (February 28, 2007)
===========================
Enhancements:
-------------
1. Change: Added Serdes support for 5709.

Impact: None.

Fixes:
------
1. Problem: (CQ28433) Driver does not compile on some early 2.6 and
2.4 kernels.

Cause: Kernel compatibility issue.

Change: Added some missing #ifdef CONFIG_PCI_MSI.

Impact: None.

2. Problem: (CQ28527) System hangs when running bonding scripts on 5709.

Cause: Bonding driver reads MDIO registers after the device is in
D3hot state.

Change: Added check to disallow MDIO access after the device is down.

Impact: None.

v1.5.5b (January 31, 2007)
===========================
Fixes:
------
1. Problem: (CQ28252) Driver reports the same MAC address for both
ports of 5709.

Cause: The driver was obtaining the MAC address from the same
shared memory area for both ports.

Change: Updated driver to read from the deicated shared memory
area for each port.

Impact: None.

2. Problem: (CQ28226) 5709C does not link up when connected to Dell
5324 and some other switches.

Cause: PHY's Early DAC Wakeup Enable bit's strapped value is set.

Change: Disable Early DAC Wakeup enable on 5709 A0 after PHY reset.

Impact: None.

v1.5.4b (January 8, 2006)
===========================
Fixes:
------
1. Problem: 5709 copper device detected as serdes.

Cause: Media detection code not complete.

Change: Added complete media detection code.

Impact: None.

Enhancement:
------------
1. Change: Add IPv6 checksum support.

Impact: None.

v1.5.2b (December 22, 2006)
===========================
Merged in all latest changes.

v1.5.1c (November 30, 2006)
===========================
Enhancement:
------------
1. Change: Remove 5709 FPGA code.

Impact: None.

v1.5.1b (November 15, 2006)
===========================
Enhancement:
------------
1. Change: Added support for 5709.

Impact: None.

v1.4.52c (March 07, 2007)
=========================
Enhancement:
------------
1. Change: Increase maximum receive ring size to 4080.
The default is kept the same at 255.

Impact: None.

v1.4.51b (December 21, 2006)
============================
Fixes:
------
1. Problem: (CQ27802) Cannot enable flow control in some cases.

Cause: In some cases when flow control is forced to on, the
driver detects no changes in advertisement, and as a
result, will not re-autoneg. Without the link change,
flow control settings will not change.

Change: Added some code to setup flow control when no other
PHY settings are made. This will ensure that flow
control changes will take effect immediately.

Impact: None.

v1.4.50b (December 15, 2006)
============================
Fixes:
------
1. Problem: (CQ27424) Panic when writing to nvram.

Cause: Bug in driver when an alignment buffer is used

Change: Fixed the bug so that the alignment buffer is freed with the
correct pointer.

Impact: None.

v1.4.49b (December 13, 2006)
============================
Fixes:
------
1. Problem: (CQ27459) Driver reports link down when link is up.

Cause: Hotplug scripts can cause bnx2_open() to be called immediately
after bnx2_init_one() calls register_netdev(). The initial
link state set after register_netdev() may overwrite the actual
link state set by the link handler on SMP systems.

Change: Move all initial state setup code to before calling
register_netdev().

Impact : None.

v1.4.48b (December 08, 2006)
============================
Fixes:
------
1. Problem: (RHBZ 212055) Panic in bnx2_poll().

Cause: Bug in determining tx ring space when the tx ring is
completely full.

Change: Fixed the flawed logic in bnx2_tx_avail().

Impact: None.

2. Problem: (CQ27424) Buffer overflow when writing to nvram.

Cause: Bug in driver when the beginning NVRAM offset is
not 4-byte aligned.

Change: Fixed the bug to allocate enough buffer space.

Impact: None.

3. Problem: (CQ27543) Loopback failed if MAC address is changed.

Cause: Driver uses permanent MAC address for loopback which may
be different from a locally administered address.

Change: Fixed by alwaysing using the current MAC address in the
netdevice structure.

Impact: None.

v1.4.47b (November 02, 2006)
===========================
Fixes:
------
1. Problem: (CQ25922) 5708S does not pass PHY loopback test on
some blade servers.

Cause: It takes longer (about 100msec) to link up in some
backplane environments when the Serdes is set to PHY
loopback mode.

Change: Increase delay loop to up to 1 sec when waiting for
link up after PHY loopback. Previous wait time was
100usec.

Impact: None.

v1.4.46b (October 30, 2006)
===========================
Fixes:
------
1. Problem: (CQ25916) Device does not receive packets when configured
by the Xen bridge script and when IPMI is enabled.

Cause: Firmware does not forward packets to the host when the
device is in promiscuous mode in some cases.

Change: Firmware change and driver change to enable the
BNX2_RPM_SORT_USER0_PROM_VLAN bit when going into
promiscuous mode.

Impact: None.

v1.4.45b (October 19, 2006)
===========================
Enhancement:
------------
1. Change: Added software parallel detection on 5708S to link at
1000Mbps or 2500Mbps automatically if the link partner is
forced at 2500Mbps.

Impact: None.

2. Change: Added 2500Mbps forced speed setting. Setting it requires
a future version of ethtool or custom apps.

Impact: None.

3. Change: Port driver to compile on 2.6.19 kernel.

Impact: None.

Fixes:
------
1. Problem: Driver does not complile on 2.4 kernels.

Cause: TSO symbols not defined in 2.4 kernels.

Change: Added #ifdef for compatibility.

Impact: None.

2. Problem: MSI doesn't work on 5706 when the host bridge is AMD8132.

Cause: Compatibility issue.

Change: Added code to disable MSI when 5706 is on a systems with
AMD8132.

Impact: 5706 cannot use MSI on such systems.

v1.4.44b (August 10, 2006)
==========================
Fixes:
------
1. Problem: A rare tx race window exists in the tx path.

Cause: CPU re-ordering can cause the tx queue to be stopped
forever when the tx ring is full in a very rare
condition. See ChangeLog for more details.

Change: Fixed the race condition with memory barriers.
See ChangeLog for more details.

Impact: None.

Enhancement:
------------
1. Change: Increase default rx ring size to 255 to prevent
packet drops under heavy load.

Impact: Higher memory usage.

2. Change: Port driver to run on 2.6.18 kernel.

Impact: None.


v1.4.43b (June 26, 2006)
=======================
Enhancement:
------------
1. Change: (CQ25508) Use DRV_MSG_CODE_UNLOAD_LNK_DN message on
5708 B1 and older chips so that the link will turn
off after ifdown.

Impact: None.

v1.4.42b (June 2, 2006)
=======================
Fixes:
------
1. Problem: (CQ22585) WoL cannot be enabled on 5708 B2.

Cause: Hardware limitation in previous 5708 versions required
driver to always disable driver WoL on 5708.

Change: With the issue fixed in B2, the driver was changed to
allow 5708 B2 and above to support driver WoL.

Impact: None.

2. Problem: (CQ21779) Driver does not report dropped receive packets.

Cause: Packets dropped by firmware are reported in a scratch pad
location in memory separate from other counters.

Change: Added code to report this firmware counter.

Impact: None.

Enhancements:
-------------
1. Change: (CQ24690) Allow driver to be compiled for non-running kernels.

Impact: None.

v1.4.41b (May 17, 2006)
=======================
Fixes:
------
1. Problem: Driver writes wrong data to non-buffered flash.

Cause: Bug in driver causing the unchanged portion of the page
to be corrupted.

Change: Fixed bug.

Impact: None.

v1.4.40b (April 17, 2006)
=========================
Enhancements:
-------------
1. Change: Combine 2 small memory allocations into 1.

Impact: None.

2. Change: Separate tx consumer and producer entries into separate
cache lines for better performance.

Impact: None.

3. Change: Compress firmware data to reduce driver size.

Impact: Driver now requires zib_inflate library which should be
available on most vendor kernels.

v1.4.39b (Mar. 10, 2006)
=======================
Fixes:
------
1. Problem: (CQ23181) Driver loses track of link changes in some cases.

Cause: In some cases, the status block gets a link change indication
that contradicts with the MII link status. This is due to
transient link signals during link changes.

Change: Add coalesce_now at the end of link change interrupt to flush
out the transient behavior.

Impact: None.

2. Problem: 5708 only supports 40-bit DMA addresses.

Cause: Limitation of the built-in PCIE-to-PCIX bridge.

Change: Add workaround code to make sure all DMA addresses are
less than 40 bits.

Impact: Some minor impact on performance on some 64-bits systems.
There should be practically no performance impact on i386 and
x86_64 systems.

3. Problem: "Copyright" deprecated in RPM spec file.

Change: Changed to "License".

Impact: Should be none on the distributions that we support.

v1.4.38b (Feb. 10, 2006)
=======================
Fixes:
------
1. Problem: Setting rx ring size to 255 causes memory allocation errors.

Cause: Multiple bugs that do not handle the full ring properly.

Change: Fixed all bugs related to full ring handling and changed
maximum ring size from 4080 to 1020 after discussion with
Dave Miller.

Impact: Maximum rx ring size is now smaller.

2. Problem: Compile warnings and panic on IA64.

Cause: not included.

Change: Added include .

Impact: None.

v1.4.36b (Jan. 19, 2006)
=======================
Version number update.

v1.3.36 (Jan. 17, 2006)
=======================
Fixes:
------
1. Problem: (CQ22827) bnx2 does not compile on 2.6.6 and earlier
kernels.

Cause: Introduced bug while fixing CQ22666.

Change: Fix compatibility code.

Impact: None.

2. Problem: (CQ22823) bnx2 reports extra .5 at the end of firmware
version string.

Change: Skip the last digit in the firmware version string.

Impact: None.

3. Problem: (CQ22585) WoL still does not work on 5708.

Cause: New WoL mechanism introduced in 1.3.34 has a flaw.

Change: Removed the workaround code and disabled WoL support
on 5708. During shutdown and suspend, the driver will
shutdown the device and WoL will be setup by the
bootcode according to the nvram's out-of-box WoL
setting.

Impact: 5708 will not support driver-initiated (ethtool-intiated)
WoL.

v1.3.35 (Jan. 17, 2006)
=======================
Fixes:
------
1. Problem: (CQ22666) bnx2 driver does not compile on RHEL3 U7.

Cause: if_mii() back-ported to RHEL3 U7.

Change: Adjusted the compatibility code.

Impact: None.

2. Problem: (CQ22718) UMP connection is lost after enabling WoL.

Cause: FORCE LINK was mistakenly set during WoL setup.

Change: Do not set FORCE LINK.

Impact: None.

v1.3.34 (Jan. 13, 2006)
=======================
Fixes:
------
1. Problem: (CQ22585) WoL does not work on 5708.

Cause: Internal bridge not in proper PME state.

Change: Added new firmware message to allow bootcode to help set up
WoL.

Impact: None.

Enhancements:
-------------
1. Change: Added compile option to include crc32 function for RH2.4
boot kernels.

Impact: None.

2. Change: Updated TSO firmware to handle ECN.

Impact: None.

v1.3.33 (Dec. 12, 2005)
=======================
Enhancements:
-------------
1. Change: Increased firmware hand-shake timeout from 50 msec to
100 msec. Also changed the delay from busy-wait udelay
to non-busy-wait msleep.

Impact: None.

2. Change: Added code to read nvram size from shared memory if
available. Otherwise, the size will come from the
flash table which only gives the smallest size for
that type of flash.

Impact: None.

3. Change: Added workaround to issue 2 separate IOs for interrupt
acknowledgement. The workaround is only used for INTA
(non-MSI) interrupts.

Impact: Slightly higher overhead for INTA interrupts.

v1.3.32 (Dec. 01, 2005)
=======================
Enhancements:
-------------
1. Change: Added PHY loopback to the loopback selftest.

Impact: None.

2. Change: (CQ21810) Added ethtool -d register dump.

Impact: None.

3. Change: Reduce the number of registers tested in selftest to make
the driver smaller.

Impact: None.

4. Change: Increased maximum rx ring size to 4080.

Impact: None.

5. Change: Changed rx checksum logic for better reliability.

Impact: None.

6. Change: Added 5708 B1 workarounds.

Impact: None.

v1.3.31 (Nov. 18, 2005)
=======================
Fixes:
------
1. Problem: (CQTO2080) Cannot pass traffic during 2nd ifup if IPMI
is enabled.

Cause: A flaw in driver/firmware handshake.

Change: Changed driver/firmware handshake by doing WAIT0 first before
writing the first signature.

Impact: None.

2. Problem: (CQTO2056) VLAN-tagged IPMI traffic fails after driver is
loaded.

Cause: Driver configures the NIC to keep the VLAN tag by default,
causing VLAN-tagged IPMI traffic to fail.

Change: Changed driver to always strip VLAN tags if IPMI is enabled.

Impact: VLAN will always be stripped when IPMI is enabled. This may
affect some applications that rely on raw VLAN packets.

Enhancements:
-------------
1. Change: Sync'ed up with latest upstream bnx2.

v1.3.29 (Oct. 6, 2005)
=======================
Fixes:
------
1. Problem: (CQTO1929) Traffic stops when MTU is greater than 1500
with TSO enabled.

Cause: TSO firmware bug.

Change: Updated to latest firmware.

Impact: None.

v1.3.28 (Sep. 29, 2005)
=======================
Fixes:
------
1. Problem: (CQTO1875) Traffic stops when running Nettack with TSO
turned on.

Cause: TSO firmware bug.

Change: Updated to latest firmware.

Impact: None.

2. Problem: (CQTO1575) ethtool -S shows non-zero rx_error_bytes.

Cause: Hardware errata.

Change: Ignore this counter and always report zero.

Impact: None.

v1.3.27 (Sep. 21, 2005)
=======================
Enhancements:
-------------
1. Change: Enabled ethernet@wirespeed on copper devices.

Impact: None.

2. Change: Enabled customized pre-emphasis and other serdes control
settings on 5708S backplane devices. A special PHY
register will be programmed according to the NVRAM value.

Impact: None.

3. Change: Modified Makefile to check for the source symbolic link
in the kbuild environment.

Impact: None.

4. Change: Improved NAPI poll processing so that all events will be
processed before interrupts are re-enabled. This will
reduce the number of unnecessary interrupts.

Impact: None.

5. Change: Add support for ETHTOOL_GPERMADDR (from John Linville)

Impact: None.

Fixes:
------
1. Problem: Bug in irq handler causing extra register read.

Cause: Bug in bnx2_interrupt() reading BNX2_PCICFG_MISC_STATUS
register when it is not necessary.

Change: Fixed the logic bug and added prefetch of status block in
msi handler.

Impact: None.

v1.3.25 (Aug. 22, 2005)
=======================
Fixes:
------
1. Problem: Ethtool register and memory tests fail on 5708.

Cause: Some code was not merged properly many versions ago.

Change: Merged in properly code.

Impact: None.

Enhancements:
-------------
1. Change: Slow down flash clock speeds

Impact: None.

2. Change: Code re-sync'ed with upstream driver.

Impact: None.

v1.3.24 (Aug. 16, 2005)
=======================
Enhancements:
-------------
1. Change: Changed all spin_lock_irqsave locks to spin_lock_bh for
better overall system performance. All code requiring
spin_lock runs in BH or user context.

Impact: None.

2. Change: Removed atomic operations in the transmit fast path.
Code should run a bit faster as atomic operations can be
quite slow.

Impact: None.

v1.3.23 (Aug. 10, 2005)
=======================
Enhancements:
-------------
1. Change: Added reporting of link speed to firmware.

Impact: None.

2. Change: Added shared memory base look-up.

Impact: None.

3. Change: Possible sparse fixes (from Peter Hagervall)
- use C99 struct initializers
- make a few arrays and structs static
- remove a few uses of literal 0 as NULL pointer
- use convenience function instead of cast+dereference in
bnx2_ioctl()
- remove superfluous casts to u8 * in calls to readl/writel

Impact: None.

4. Change: Updated documentation with the crc32 library requirement and
other minor updates.

Impact: None.

v1.3.22 (July 25, 2005)
=======================
Enhancements:
-------------
1. Change: Added check for default link speed setting in shared memory.
This allows some blade servers that don't support autoneg to
default to forced speed to speed up link-up time.

Impact: None.

2. Change: Changed timer code to speed up the timer after serdes autoneg.
This speeds up the time for parallel detection when the link
partner does not autoneg. After autoneg or parallel detction
completes, timer goes back to normal 1 HZ interval. With the
new scheme, link should be detected up using parallel detection
in less than 0.7 seconds. Autoneg normally completes in 120
msec exchanging base pages and 3 next pages.

Impact: None.

v1.3.21 (July 21, 2005)
=======================
Enhancements:
-------------
1. Change: Updated firmware to properly handle TSO packets with ECN
bits set.

Impact: None.

2. Change: Updated to latest rxp firmware.

Impact: None.

3. Change: Added check for the 2.5G capability in shared memory.

Impact: None.

4. Change: Expanded nvram support for 5708.

Impact: None.

Fixes:
------
1. Problem: (CQTO1511) Downing a team of bnx2 adapters causes hang.

Cause: Deadlock when the second adapter's close routine calls
flush_scheduled_work() because the linkwatch_event
is scheduled on the work queue when the first adapter
is closed. The linkwatch_event will try to get the rtnl_lock
which is already held by the bnx2_close routine.

Change: Fixed by not calling flush_scheduled_work(). Instead,
use a flag to indicate work is pending and wait until
the flag is cleared.

Impact: None.

2. Problem: (CQTO1439) ethtool -S on 5708 causes oops.

Cause: A pointer is not initialized if the device is 5708.

Change: Added proper initialization.

Impact: None.

3. Problem: Some error counters are mis-reporting.

Cause: The workaround for the hw errata is not applied properly
on the chips with the errata.

Change: Added proper checks for the workaround.

Impact: None.

4. Problem: High BER on 5708 SerDes.

Cause: hardware errata.

Change: Added workaround for 5708 A0 and B0.

Impact: None.

v1.3.19 (May 27, 2005)
=======================
Enhancements:
-------------
1. Change: Merged 5708 code with the latest 1.1.19.

Impact: None.

Fixes:
------
1. Problem: (CQTO1260) 5708S does not link at 1000Mbps when forced. It
links at 2500Mbps when connected back-to-back with another
5708S.

Cause: 2.5G bit is still turned on.

Change: Fixed by turning off 2.5G when the speed is forced.

Impact: None.

v1.1.19 (May 26, 2005)
=======================
Enhancements:
-------------
1. Change: Made significant changes to merge into the kernel. Among
them, consolidate all source files into bnx2.[ch] and
bnx2_fw.h, change structure style register definitions
to offset based.

Impact: None.

Fixes:
------
1. Problem: Excessive stack usage.

Cause: Use of local variable array.

Change: Fix excessive stack usage in bnx2_alloc_bad_rbuf() by
replacing local variable array with kmalloc array. Also
changed function to return error code, and changed some
of the callers to check for the return code.

Impact: None.

2. Problem: Bug in receive checksum.

Cause: Software bug.

Change: Fix bug in rx checksum by indicating CHECKSUM_UNNECESSARY
only when the hw calculated checksum is 0xffff.

Impact: None.

3. Problem: Excessive busy loop.

Cause: Software bug.

Change: Replaced one excessive udelay of 15msec with msleep since
the calling context is always process.

Impact: None.

4. Problem: Need to call flush_scheduled_work() and bnx2_netif_stop().

Cause: Bug in bnx2_close().

Change: Fix bug in bnx2_close() by calling flush_scheduled_work()
since we are using a work queue in netdev watchdog. Also
added bnx2_netif_stop() call in bnx2_close().

Impact: None.

5. Problem: Some symbols do not have bnx2 prefix and are not static.

Change: Add bnx2_ prefix to some remaining names and mark some
remaining names static.

Impact: None.

v1.1.17 (Apr. 7, 2005)
=======================
Fixes:
------
1. Problem: Driver does not compile on 2.6.12 kernel.

Cause: pci_dev->slot_name has been deprecated.

Change: replaced with pci_name.

Impact: None. All kernels supported by bnx2 including 2.4.21-*EL have
pci_name defined.

v1.1.16 (Mar. 16, 2005)
=======================
Fixes:
------
1. Problem: (CQTO936 & 1004) Tx carrier and rx_byte_errors reported
during normal operations.

Cause: 5706 hardware errata on these 2 statistics counters.

Change: Modified driver to skip these 2 counters.

Impact: These 2 counters will always report 0 and not the true
statistics.

v1.3.15 (Mar. 11, 2005)
======================
Enhancements:
-------------
1. Change: Added SGMII 10/100/1000 Mbps and fiber mode 1000/2500 Mbps
support.

Impact: None.

v1.1.15 (Mar. 09, 2005)
=======================
Enhancements:
-------------
1. Change: Added code to program proper phy settings for jumbo
frames on copper and serdes devices.

Impact: None.

2. Change: Changed INTx ISR to handle a valid case where INTx
arrives before status block update.

Impact: None.

3. Change: Added a separate ISR for MSI to handle subtle differences
between INTx and MSI.

Impact: None.

v1.1.14 (Mar. 03, 2005)
======================
Fixes:
------
1. Problem: netdump does not work on latest RH3EL errata kernel.

Cause: #define RED_HAT_LINUX_KERNEL removed from kernel
include files, causing netdump poll function to
be compiled wrong for RH kernels.

Change: Changed Makefile to workaround the problem.

Impact: None.

v1.1.12 (Feb. 25, 2005)
======================
Fixes:
------
1. Problem: (CQTO1062) Driver allows ethtool to set illegal speed/duplex
on fiber cards.

Cause: Missing checks for the case where autoneg is off.

Change: Added proper checks.

Impact: No.

v1.1.11 (Feb. 18, 2005)
======================
Enhancements:
-------------
1. Change: (CQTO901) Added bnx2(4) man page.

Impact: None.

v1.1.10 (Feb. 16, 2005)
======================
Fixes:
------
1. Problem: Wrong device ID in pci_dev_id table.

Change: Fixed ID.

Impact: None.

v1.1.9 (Feb. 10, 2005)
======================
Fixes:
------
1. Problem: (CQTO771) Driver fails to compile on RHEL3 update 4.

Cause: The RH kernel has back-ported some netif functions
not found in the same vanilla kernel version. Duplicate
function names are defined.

Change: Added intelligence in Makefile to detect such conditions
and change the CFLAGS accordingly.

Impact: None.

2. Problem: (CQTO1017) Driver allows 1000 half duplex autoneg off.

Cause: Missing validity check.

Change: Added check.

Impact: None.

Enhancements:
-------------
1. Change: The code to handle tx queue full condition was redone
to properly handle all boundary and race conditions.

Impact: Minimum tx ring size is now MAX_SKB_FRAGS+1.

2. Change: Tx timeout code was changed to work queue context.
This allows netif to be shutdown gracefully before
chip reset.

Impact: None.

3. Change: Added memory barriers to ISR and NAPI poll for
correctness.

Impact: None.

v1.1.8 (Feb. 01, 2005)
======================
Fixes:
------
1. Problem: (CQTO969) No interupts on a system that does not
support MSI.

Cause: On this system, the MSI generated in the MSI test
terminates with Master Abort which is a fatal
condition for the chip.

Change: A chip reset is added when MSI test fails to bring
the chip back to normal operations again (in INTx mode).

Impact: None.

Enhancements:
-------------
1. Change: Removed register 0x84 from the ethtool register test.
This is an interrupt control register that should
not be touched to prevent unwanted interrupts.

Impact: None.

v1.1.7 (Jan. 28, 2005)
======================
Enhancements:
-------------
1. Change: Added interrupt test when MSI is enabled. If MSI test
fails, driver will fallback to INTx mode.

Impact: None.

2. Change: Added test for certain chipsets where MSI is known
to fail, and disable MSI unconditionally when
such chipsets are found.

Impact: None.

3. Change: Removed support for 1000 Mbps half duplex.

Impact: 1000 Mbps half duplex will no longer work.

v1.1.6 (Jan. 26, 2005)
======================
Fixes:
------
1. Problem: (CQTO940) MTU size not set properly when device is down.

Cause: bnx2_change_mtu only handled the "up" case.

Change: Simple fix to handle the "down" case as well.

Impact: None

2. Problem: (CQTO926) 5706S does not autoneg properly after the
tx cable is pulled.

Cause: If the link partner is autonegotiating, autoneg will
fail when the tx cable is pulled. The software will
turn off autoneg seeing that the rx cable is still
attached with SIGNAL_DETECT. When the tx cable is
re-attached, autoneg is still off and the link partner
will not establish link.

Change: Added code to poll another PHY register to check if
configs are received when autoneg is disabled.

Impact: None

Enhancements:
-------------
1. Change: Added OEM product name strings.

Impact: None.

v1.1.5 (Jan. 25, 2005)
======================
Fixes:
------
1. Problem: PCI-X bus speed may not be detected correctly by the driver,
causing failure because certain register settings are done
based on bus speed.

Cause: hardware problem.

Change: Use a different register to detect PCI-X speed.

Impact: None.

v1.1.4 (Jan. 17, 2005)
======================
Fixes:
------
1. Problem: 5706S does not reliably detect link up or down.

Cause: hardware problem.

Change: Enabled hardware workaround which is effective in
A2 and newer chips only.

Impact: None.

v1.1.3 (Jan. 13, 2005)
======================
Fixes:
------
1. Problem: netdump does not work.

Cause: poll_controller routine does not work in NAPI mode.

Change: Fixed poll_controller routine for NAPI mode.

Impact: None.

Enhancements:
-------------
1. Change: Added the new mmiowb macro which is used mainly in NUMA
machines to guarantee PCI ordering.

Impact: None.

2. Change: Added OEM product name strings.

Impact: None.

3. Change: Changed ONE_TDMA workaround on systems with P64H bridge to
PING_PONG_DMA on all systems using PCI.

Impact: Better performance and better compatibility on all PCI
systems.

4. Change: Added "disable_msi" parameter to allow disabling MSI.

Impact: None.

5. Change: Reduced default tx coalescing parameters for better
tx only performance such as ttcp.

Impact: None.

6. Change: Changed NIC detection console message to display more
information.

Impact: None.

7. Change: Cleaned up some Linux .h files that are not needed.

Impact: None.

8. Change: Cleaned up the nvram routines.

Impact: None.

v1.1.2 (Nov. 11, 2004)
======================
Fixes:
------
1. Problem: Unable to load the driver on more than 2 or 3 devices.

Cause: Default register space is too big. System fails to map
the register space on the 3rd or 4th device.

Change: Changed driver to map a smaller register space as the higher
registers are not needed for standard operations.

Impact: None.

v1.1.1 (Nov. 9, 2004)
======================
Fixes:
------
1. Problem: (CQTO656) One remaining ethtool parameter can be set out of
range.

Cause: Wrong upper bounds in code.

Change: Fixed upper bound.

Impact: None.

1. Problem: 5706 A1 cannot be run on a PCI bus.

Cause: Hardware errata.

Change: Added workaround to detect 5706 A1 on PCI bus and abort.

Impact: Driver will not load 5706 A1 on PCI bus.

v1.1.0 (Oct. 29, 2004)
======================
Fixes:
------
1. Problem: (CQTO663) No link on fiber NIC set to autoneg when
the link partner is set to forced speed.

Cause: No code to handle this case.

Change: Added code to check SIGNAL DETECT when autoneg fails,
and turn off autoneg when appropriate. Also added code
to force a link down when speed settings are changed.

Impact: None.

2. Problem: (CQTO649) ifconfig up/down can cause system to
hang on 2.6 kernels using mmconfig.

Cause: Dummy read in the kernel's pci_mmcfg_write routine
may cause system to hang during D3hot -> D0
transition. The PLL may lose lock during the internal
D0 transition chip reset and cause the dummy read to
hang.

Change: The PLL problem will be fixed in A2. Meanwhile, the
driver is changed to go into D3hot only if wol is
enabled.

Impact: Minor impact in increased power consumption when
the driver is shutdown with wol disabled.

3. Change: Changed to use pci_get_device as pci_find_device
will be deprecated soon.

Impact: None.

4. Problem: (CQTO656) Some ethtool parameters can be set out of range.

Cause: Wrong upper bounds in code or documentation.

Change: Fixed code and documentation.

Impact: None.

v1.0.15 (Oct. 15, 2004)
======================
Fixes:
------
1. Problem: (CQTO644) Data corruption when sending FTP traffic on
Dell Precision 530MT.

Cause: PCI bridge errata.

Change: Added code to enable ONE_TDMA workaround when P64H
PCI bridge is detected.

Impact: Slower tx performance on systems using P64H bridge.

2. Problem: (CQTO643) Driver allows MTU to be set up to 9004.

Cause: Driver used the wrong upper bound limit.

Change: Fixed the upper bound.

Impact: None.

3. Problem: Driver does not support forced speed on 5706S.

Cause: Missing software logic.

Change: Added code to support forced 1000 Full and Half duplex.

Impact: None.

4. Change: Added workaround to disable PERR generation on
5706 A1 when it is in PCI 64-bit slot.

Impact: None.

v1.0.14 (Oct. 05, 2004)
======================
Fixes:
------
1. Problem: Driver load/unload hangs on some machines.

Cause: Transition delay required during D3hot -> D0 transition.

Change: Added necessary delay.

Impact: None.

v1.0.12 (Oct. 04, 2004)
======================
Fixes:
------
1. Problem: (CQTO609) New flow control parameter does not take
effect until ifdown/ifup or link down/up.

Cause: New flow control settings are only configured during
link up. The driver did not check flow control
advertisement changes and therefore no re-negotiation
and no link down.

Change: Fixed logic so that link will always go down whenever
there is a change a flow control advertisement.

Impact: None.

2. Problem: (CQTO612) VLAN packet reception not working.

Cause: VLAN #define not setup properly.

Change: Fixed #define for VLAN.

Impact: None.

3. Problem: (CQTO628) WoL not functioning correctly.

Cause: Multiple problems in the WoL code.

Change: Fixed by:
1. using sort mode.
2. setting up mac address correctly.

Impact: None.

Enhancements:
-------------
1. Change: Added support for non-dword and non-aligned write access
to eeprom, allowing ethtool -E to work.

Impact: None.

v1.0.11 (Sep. 24, 2004)
======================
Fixes:
------
1. Problem: (CQTO600) Kernel panic when attempting to ftp on
Fedora kernel.

Cause: skbuffs are 4-byte aligned on Fedora, causing
the rx headers to be misaligned. skbuffs are
16-byte aligned on other standard kernels.

Change: Removed any assumptions about skbuff alignment
and added code to align all rx skbuffs to 8-byte
boundaries.

Impact: None.

Enhancements:
-------------
1. Change: Added netif_carrier_off to Driver init code so that
the initial link state is off.

Impact: None.

v1.0.10 (Sep. 23, 2004)
======================
Fixes:
------
1. Problem: (CQTO599) Driver fails to compile on RH 3.0ES.

Cause: Bug in poll_bcm5706 where bp is referenced without
being defined.

Change: Fixed the minor bug.

Impact: None.

v1.0.9 (Sep. 23, 2004)
======================
Fixes:
------
1. Problem: Jumbo frames not working reliably.

Cause: Bug in bcm5706_reuse_rx_skb.

Change: Fixed the bug so that the host address is properly
copied from one BD to the other.

Impact: None.

Enhancements:
-------------
1. Change: Change the locking scheme for more reliable open/close/ioctl
operations where the spinlock is needed.

Impact: None.

2. Change: Added minimum MTU size check for MTU changes.

Impact: None.

v1.0.8 (Sep. 20, 2004)
======================
Fixes:
------
1. Problem: (CQTO561) Kernel panic on RH30EL after repeated
driver load/unload.

Cause: Occasionally, the system is unable to map device
registers, causing subsequent register access to fail.

Change: Added check for the return value from ioremap, and exit
gracefully if it fails.

Impact: None.

2. Problem: (CQTO574) NETDEV WATCHDOG when running 5706 A1 on
PCIX 133MHz slot.

Cause: Some hw register setup required for 133 Mhz.

Change: Added the register setup code.

Impact: None.

3. Problem: (CQTO468) Link does not go down after changing from
10Mbps full (forced) to 10Mbps half (forced) and vice versa
when the link partner is also using forced speed.

Cause: Delay not long enough for the link to go down.

Change: Not practical to increase delay as a very long delay is
needed for the link to go down. Added code to record the
proper link speed and duplex when speed is forced so that
ethtool will return the proper speed without the link going
down. Note that the link will go down if the link partner
has autoneg turned on, ensuring that the link partner will
see the link change.

Impact: None.

Enhancements:
-------------
1. Change: Added power management and WOL during device close. This
will allow WOL to work after Linux shutdown.

Impact: None.

2. Change: Changed driver so that ethtool will report invalid
speed after ifdown.

Impact: None.

3. Change: Updated tpatfw.h

Impact: None.

v1.0.7 (Sep. 14, 2004)
======================
Fixes:
------
1. Problem: (CQTO523) 5706 A1 hangs after a thousand iterations of
load/ifup/ifdown/unload.

Cause: The driver may be servicing an interrupt
within 15 msec of chip reset, causing the chip to hang.
The problem was aggravated by the timer mode
coalescing which created an excessive number of
interrupts (hardware problem).

The Driver may also occasionally see
the wrong firmware signature that will cause it to abort.

Change: Added synchronization to make sure all pending interrupts
are serviced before resetting the chip. Also changed to
collect mode coalescing. The firmware signature problem
will be fixed in boot code.

Impact: The use of collect mode coalescing may affect performance.

2. Problem: (CQTO558) Unable to load driver on some early 2.6 kernels.

Cause: pci_dma_sync_single_for_* routines not defined on early
2.6 kernels.

Change: Added compatibility defines for earlier kernels.

Impact: None.

v1.0.6 (Sep. 08, 2004)
======================
Fixes:
------
1. Problem: (CQTO523) 5706 A1 hangs during repeated driver ifup/down.

Cause: No delay after chip reset for A1.

Change: Added 15 msec delay after chip reset for A1.

Impact: None.

2. Problem: (CQTO468) Link does not go down after changing from
10Mbps full (forced) to 10Mbps half (forced) and vice versa.

Cause: Not enough delay after forcing link down.

Change: Added proper delay for link to go down.

Impact: None.

v1.0.5 (Sep. 02, 2004)
======================
Enhancements:
-------------
1. Change: Added support for ethtool -c, ethtool -C, ethtool -p,
and firmware version for ethtool -i.

Impact: None.

Fixes:
------
1. Problem: 5706C not advertising 1000 half duplex.

Cause: 1000 full duplex overwrites 1000 half duplex.

Change: Fixed the bug so that the 2 bits are or'ed together.

Impact: None.

2. Problem: ethtool -A does not change the flow control settings
in all cases.

Cause: Flow control settings not zeroed out before setting new
values.

Change: Minor bug fix to zero out the value.

Impact: None.

v1.0.4 (Sep. 02, 2004)
======================
Fixes:
------
1. Problem: (CQTO504) Multiple NFS transfers will hang some
connections.

Cause: Driver discards some receive packets when the
error status is non-zero.

Change: Changed the driver to only discard receive packets
when the defined error bits in the error status are
non-zero.

Impact: None.

v1.0.3 (Sep. 01, 2004)
======================
Enhancements:
-------------
1. Problem: Driver does not support ethtool -t self test and
ethtool -S statistics.

Change: Added ethtool self test and statistics.

Impact: None.

Fixes:
------
1. Problem: (CQTO478) Kernel still panics when transmitting certain
files using NFS after many iterations

Cause: Tx DMA stalls on certain UDP packets, causing NFS
client to stall.

Change: More fixes made in firmware.

Impact: None.

v1.0.2 (Aug. 26, 2004)
======================
Enhancements:
-------------
1. Problem: Driver does not work on big endian machines.

Change: Ported and tested on SPARC64 machine.

Impact: None.

Fixes:
------
1. Problem: (CQTO478) Kernel panics when transmitting certain
files using NFS.

Cause: Tx DMA stalls on certain UDP packets, causing NFS
client to stall.

Change: Fixed in firmware.

Impact: None.

2. Problem: (CQTO469) Unable to modify flow control parameters

Cause: Did not call setup_phy after the parameters are changed.

Change: Added call to setup_phy after parameters are changed.

Impact: None.

3. Problem: (CQTO467) 5706 does not autonegotiate properly after
changing settings with ethtool.

Cause: This is an ethtool limitation as the proper advertising
parameters are not passed to the driver properly.

Change: Implemented a new scheme to work around the problem to
allow users to specify full autoneg, single speed autoneg,
and fixed speed.

Impact: None.

4. Problem: ethtool -e does not work.

Cause: Various bugs in the nvram routines.

Change: Fixed and tested nvram routines on little endian and big endian
machines.

Impact: None.

v1.0.1 (Aug. 18, 2004)
======================
Fixes:
------
1. Problem: (CQTO459) 5706 NIC does not get link.

Cause: Boot code timing out in WAIT2 state before driver is ready.

Change: Moved the WAIT2 state ahead in the driver reset sequence
as a temporary workaround until it is fixed in boot code.

Impact: None.

2. Problem: (CQTO463) Kernel panics when loading the driver on
RH30EL (2.4.21-4.EL)

Cause: Older kernel used different API to allocate and register
netdev.

Change: Added older APIs to be used on older kernels.

Impact: None.

v1.0.0 (Aug. 13, 2004)
======================
Initial release
qlgc_dd_nic_nx2-2_2_5r-1_714_00g_sles11_32-64_chg