ServeRAID M1000 Series SAS/SATA Controller Firmware Update
Adapters Supported: ServeRAID M1115 SAS/SATA Controller for IBM System X (81Y4448) ServeRAID M1015 SAS/SATA Controller (46M0831)
Version 20.10.1-0107 - Suggested ------------------- Fixes: - Fixed grammatical errors in WebBIOS. - Fixed an issue in WebBIOS Drive Group Definition screen where enclosures should not be selectable in the Drives column. - Fixed an issue in uEFI-WebBIOS where the white bars do not match up under VD properties page. - Fixed an HII browser issue where a drive performing a copyback displayed the state as "Replacing" but other utilities showed the state as copyback. - Fixed an HII browser display issue where SATA drives showed "0" for the value of RPM under drive properties. - Fixed a display issue where the HDD port number showed incorrectly in an HII browser. - Fixed an HII browser issues where creating a global hotspare gave the user an error message. - Fixed an HII browser issue when security is changed with local key management the changing security report current mode is disabled as external keu management. - Fixed an HII browser issue where the user got the following error message, "The request command has invalid arguments," when changing the security key report. - Fixed an HII browser issue where the user was unable to save the configuration after adding an extra span during array creation. - Fixed an HII browser issue where the return value was not correct when the browser called extract config with a result of null.
Version 20.10.1-0101 - Suggested ------------------- Fixes: - Fixed an issue where a system uefi error will occur when the bootTargetId is set to 0. - Fixed a problem where the firmware will allocate the sata bbl entry for the drive when moved from unsupported to supported. - Fixed a firmware issue where the TargetId for the recon LD should be set to its original LD. - Fixed a HII error message "Question Value mismatch with Option value!" after selecting factory defaults in HII. - Fixed an issue where the firmware fails to create the configuration and utilities fail to report the VD size after the reconstruction.
Version 20.10.1-0091-01 - Non-Critical ------------------- Fix - Fixed issue where update may fail to find all supported controllers in SLES 11 SP 2. Note not change in the firmware; it is the same as package 20.10.1-0091.
Version 20.10.1-0091 - Suggested ------------------- Enhancement: - Add support for ServeRAID M1115
Fixes: - Fixed issue where after starting a reconstruction on a RAID 0 the progress %, does not increase. - Fixed an issue where a new drive, inserted after a drive failure, goes to JBOD and not auto rebuild. - Fixed physical drive count issue that stated more than (16) devices already exists
Version 20.10.1-0069- Suggested ------------------- Enhancement: - ServeRAID M1015 Dimmer Switches are disabled by default.
Fixes: - Fixed issue where enabling security causes the configuration to be missing, and a configured FDE array to be seen as foreign on reboot. - Fixed issue where WebBIOS gives garbled message when enabing FDE on an existing Disk Group - Fixed issue where the logical Unit ID (VPD page 0x83) changed after foreign import. - Fixed issue where the LDBBM entries are incorrect after foreign import. - Fixed a problem where firmware was taking to long to complete the PCI config read. Causing the system to generate an NMI. - Fixed issue where the controller does not work with pci set to nomsi in kdump kernel. - Fixed issue where the LED behavior is incorrect, wrong drive will blink activity. - Fixed issue where the configuration becomes foreign after the firmware fails multiple attempts to access raid key during boot. - Fixed firmware issue where a replacement drive is not seen if the replacement is added during power cycle. - Fixed an intermittent RAID key failure during power-on.
Version 20.10.1-0052- Critical ------------------- Enhancement: - Add support to pass SMART errors for JBOD drives to MSM
Fixes: - Added check to return SCSI sense Check condition if PMI is set and LBA is non zero for SCSI Read Cap 16. - Fixed issue where a bluescreen occurs handling RAID 1 with HSP and medium errors. The bluescreen occurs becausethe driver timesout while fw is retrying sense 0x02. Firmware causes Fatal Error when HSP drive responded with Sense 0x02 for Write/Verify or TUR - Fixed hang condition or condition where the uEFI driver does not load due to the uEFI Driver issuing a command in poll mode to firmware to early
Version 20.10.1-0045 - Critical ------------------- Fix: - Fixed issue where firmware has incomplete writes during power fail and recovery
Version 20.10.1-0036 - Critical ------------------- Fixes: - Fixed issue where uEFI WebBIOS version may not display the product name of the second controller - Fixed issue to prevent users to downlevel firmware to older versions - Fixed an issue where firmware reports "Unexpected sense, Invalid field in CDB" for LOG SENSE command sent to Seagate drives - Fixed issue where SMART failures can take longer then 5 minutes to report or in some cases fail to report - Fixed issue where it appears to the user the harddrive cache policy is changed when requested but the change did not occur
Version 20.10.1-0022 - Critical ------------------- - Fixed issue where Windows 2008 R2 WS08 cannot be installed properly on ServeRAID M1015 SATA JBOD with a uEFI boot. - Added warning message when user tried to change more then 16 drives to JBOD. - Addressed a problem where direct attached drives are given incorrect slot numbers - Added fixes from LSI channel products. - Fixed issue where a single JBOD drive will not boot after a Windows 2008 R2 installation.
Version 20.5.1-0014 - Critical ------------------- - Addressed data issue with database applications that use overlapping read write operating. - Addressed data issue which may occur during a reconstruction on some RAID levels that have an associated CacheCade virtual drive enabled. - Fixed problem where the controller may halt if a drive has medium errors that are being used in a check consistency, patrol read, or have delayed writes.
Version 20.1.1-0059 - Critical ------------------- Fixes: - Fixed an issue where a physical drive that is changed to JBOD from powersave will become unconfigured good again - Addresses an issue where data becomes inaccessible when a drive is secured after data has been written
Version 20.1.1-0049 - Suggested ------------------- Enhancement - Support M1000 key for RAID 5 and SED support
Fixes: - Fixed an issue in M3950M3 where webbios would hang - Fixed an issue where the controller properties in WebBIOS such as Rebuild, CC and BGI are not changing when we use up and down arrow keys. - Fixed an issue where Enclosure ID's are not being shown in MSM
Version 20.1.1-0046 - Suggested ------------------- - Enabled support for the ServeRAID M1000 Series Advanced Feature Key.
Note: All Logical Drives must previously have the encryption enabled before data is written on to the SED drives. Please read Retain TIP H123152 for more details.
Version 20.1.1-0042 ------------------- - Initial release ibm_fw_sraidmr_m1000-20_10_1-0107_linux_32-64_chg
=============================================================================== Emulex 16GB FC Firmware Package ===============================================================================
Firmware Version: 1.1.21.0
Incremental Interoperability:
Problems Fixed: - 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
ServeRAID M5100 Series SAS/SATA Controller Firmware Update for Linux
Adapters Supported: ServeRAID M5110 SAS/SATA Controller for IBM System x (81Y4481) ServeRAID M5110e SAS/SATA Controller for IBM System x ServeRAID M5120 SAS/SATA Controller for IBM System x (81Y4478)
NOTE TO SERVICE - Reference RETAIN #N/A
Version 23.7.1-0009 - Suggested ------------------- Fixes: - Fixed an issue where SoH is bad after a learn cycle but iBBUI shows good status. - Fixed an issue where hi-temp warning was not being displayed.
Version 23.7.0-0037 - Suggested ------------------- Fixes: - Corrected differential signals for Phys 2 and 3 that caused slot numbers in simple swap configurations to be incorrect. - Fixed an issue when 'maintain PD failed history' is enabled, and a cable is removed while a drive is added, the drives state goes to optimal instead of foreign unconfigured bad. - Fixed a problem where a capacity change is reported after a rebuild completes on a Cache Cade volume. - Fixed a controller firmware hang when the recovery of a medium error takes to long. - Fixed an issue where the SATA BBM (Bad Block Manager) list was being corrupted. - Fixed an issue where FoD (Feature on Demand) Options were being lost because of errors while accessing the TSOC. - Fixed a problem where the controller firmware would crash and drives would go offline when a bad block entry was created during a check consistency operation. - Fixed a problem where drives were being marked unconfigured bad (foreign) on reboot. - Fixed problem where a member of a CacheCade volume did not get marked as foreign when the drive was pulled with 'maintain PD failed history' enabled. - Fixed a problem where during a rebuild, a former hot spare that was now in a state of unconfigured good, moved back to the state hot spare, which then automatically started a copyback operation, causing the rebuild to restart. - Fixed a problem where a controller fault occurred during a reboot while a physical device was in progress of a PD Erase.
Version 23.7.0-0029 - Suggested ------------------- Enhancements: - Added support for Cache Cade 2.1 - Added Support for PI Drives
Fixes: - Fixed an issue where the firmware reports device initialization completion status to be greater than 100% at startup. - Fix an issue where when a secure foreign drive was present, VD creation fails because firmware becomes unresponsive - Added a check for the presence of PD before writing the data arms of a protected LD during BGI. - Fixed Firmware asserts in CacheMemAllocForPrebootApps() when memory was allocated twice by BIOS. - Fixed an issue with USB Cacheoffload restore fails after multiple power cycles onServeRAID M51xx controllers. - Fixed an issue where querying SMART / PFA Status returns "all zeros" in Sense Data. - Fixed an issue where the import of a config from MR to iMR resulted in a firmware crash. - Fixed an issue where iMR firmware crashed while creating 8/16/32 KB stripe size Lds. - Fixed background initialization watermark conversion to PD LBA. - Fixed write protected R1E data arms during initialization. - Fixed an issue where MR firmware crashed while discarding pinned cache. - Fixed an issue where a dirty LD dependency information of SSD pd has stale entries. - Corrected an issue during system booting from pinned cache, firmware goes to loop message BootMsgDcmd - Fixed an issue where a BGI was aborted and restarted, elapsed time was not reset. - Fixed an issue where the start ref for a shared cache line was not an indicator of the offset into the stripe. - Fixed an issue where the firmware hangs while running CC on a rebuilt R1 VD with SBBM. - Fixed an issue where the firmware was wrongly adding puncture entries. - Fixed an issue where rebuild was ran twice on a target drive with 100% full SBBM table. - Fixed an issue where the firmware was generating powersave change event when DS3 was not enabled, due to this application are not parsing the event. - Fixed an issue where recon from R0 to R1 using 3 TB drive causes firmware to report excessive unexpected sense events. - Fixed an issue, in which the bbuMode would revert to the factory default value of 5, when automatic learn cycle was enabled. - Fixed an issue where cache offload firmware reports unnecessary High Temp Event due to incorrect temp value. - Fixed an issue in which a Patrol Read may not start under certain conditions. - Fixed an issue where the firmware hits montask after discarding the cache when a snapshot VD was involved. - Fixed an issue where the firmware hangs during pin cache destage as dirty lines in that map never become zero. - Fixed an issue where CC fails to correct media error at 2TB location on 2 3TB SATA drives that support WU. - Fixed an issue where a new XML file was added to the nvdata, the buffer to hold the uncompressed nvdata overflowed. - Fixed an issue where an imported drive becomes unconfigured good when secure VD erase was running. - Fixed an issue where CC stops progressing on a R6 VD with media errors. - Fixed an issue where 3TB Hitachi HDD failed in immunity test (Electrostatic Noise test). - Fixed an issue where controller features are lost if RAID Key was not detected. - Fixed an issue where performance degraded in RAID 5 Sequential Writes due to command Out-of Ordering. - Fixed an issue where "Native configuration is no longer supported" message in post. - Fixed an issue where (DDR3) Initialization fails with fault 0x91a1 - initial DFIRL selected too low. - Fixed an issue where subsequent drives are dropped when all drives in the stagger spin up drives fails on boot sequence.
Version 23.2.1-0043 - Suggested ------------------- Fixes: - Fixed an issue where "Potential non-optimal configuration due to drive PD commissioned as emergency spare" alarm would trigger erroneously. - Fixed an issue where Copyback does not progress upon inserting drives. - Fixed an issue When allowMixInLD is Disabled, and causes Copyback Fails after Rebuild to Emergency Hot Spare. - Fixed an issue where the Firmware faults while flashing. - Fixed an issure where querying SMART / PFA Status to Return all zeros in Sense Data. - Fixed an issue where the Re-inserted Drives becomes Unconfigured_good causing auto rebuilds to fail to start.
Version 23.2.1-0033 ------------------- - Initial release ibm_fw_sraidmr_m5100-23_7_1-0009_linux_32-64_chg
BIOS/FW/UEFI Update for ServeRAID H1110 SAS/SATA Controller for IBM System x
Controller Supported: ServeRAID H1110 SAS/SATA Controller for IBM System x (81Y4492)
Fixes: - Fixed issue where HII do not report Multi-LUN devices from external RAID enclosure. - Do not show external RAID LUNs in HII RAID configuration page. - Report NVDATA version consistently in Hex or Decimal. - Fixed issue where update will not install with the 09.101 megaraid_sas device driver.
Note: HII changes may not affect all controllers. Changes for the controller are based on RAID volume support. - HII fix to return EFI_SUCCESS when RETRIEVE Action is given in HII Callback function. - HII fix for Write cache disabling fails for SATA HDD/SSD connected to the IT controller. - HII fix for saved Controller Events Filename. - Behvioral change for the way a volume is created in HII.
Note: The following fixes only effect blade systems that support Bofm. - Fixed boot issues in Windows 2008 where after installation in uEFI the os will not boot due to the BuildDevicePath not allocating enough memory for the DevicePathreturned to caller. - Fixed issue with Bofm configurations where the BOFM supplied addresses for external/switch attach Phys are being assigned to the internal/direct attach Phys. - Fixed a Bofm issue where the SAS WWIDs not reverting to Man Page 5 Default when a Blade is moved back to non-BOFM slot.
Note: HII changes may not affect all controllers. Changes for the controller are based on RAID volume support.
- HII change to Remove Legacy BIOS Enable/Disable option. - Fixed issue where after creating a volume using SATA SSD the Associated Physical Disks always show up as SATA HDD. - Fixed issue where a hotspare could not be created for any volume in the HII browser. - HII fix for the View Physical Disk Properties form where the Serial number of SATA disks were being displaced with a space. - HII fix for the IR help strings displayed when using an IT controller. - Fixed HII issue where a 'Question value mismatch with Option value' error occurs when saying No for creating RAID10/RAID1E volume. - Fixed HII issue where help is not available when having only RAID0 and RAID1 levels in Create Configuration form. - Fixed a problem where the UEFI driver ATA PassThru Protocol is corrupt while trying to access the Mode field. - HII behavior change for 'Manage Foreign Configurations.' - HII change to provide proper extended RAID Levels in help messages based on supported extended RAID Levels.
ServeRAID M and MR10 Series SAS Controller Driver for SLES 10 (also supports MegaRAID 8480 SAS Controller)
Adapters Supported: - ServeRAID M5110 SAS/SATA Controller for IBM System x (81Y4481) - ServeRAID M5110e SAS/SATA Controller for IBM System x - ServeRAID M5120 SAS/SATA Controller for IBM System x (81Y4478) - ServeRAID M5025 SAS/SATA controller (46M0830) - ServeRAID M5016 SAS/SATA Controller for IBM System x (90Y4304) - ServeRAID M5015 SAS/SATA controller (46M0829) - ServeRAID M5014 SAS/SATA controller (46M0916) - ServeRAID M1015 SAS/SATA Controller (46M0831) - IBM ServeRAID MR10il SAS controller (44E8767) - IBM ServeRAID MR10is SAS controller (44E8695) - IBM ServeRAID MR10ie (CIOv) SAS controller (46C7167) - IBM ServeRAID MR10i SAS controller (43W4296) - IBM ServeRAID MR10k SAS controller (43W4280) - IBM ServeRAID MR10M SAS controller (43W4339) - MegaRAID 8480 SAS controller (39R8850)
Version 00.00.06.19 - Suggested ------------------- Fixes: - Fixed an issue where a kernel crash may occur in some cases, when megaraid_sas driver is loaded but controller is not present.
Version 00.00.06.15 - Suggested ------------------- Enhancements: - Add support for fpRead/WriteCapable & fpRead/WriteAcrossStripe
Fixes: - Mask off MFI_FRAME_IEEE, MFI_FRAME_SGL64, MFI_FRAME_SENSE64 in megasas_mgmt_fw_ioctl() to prevent memory scribble issues from incorrectly built MegaCli frames. - Fixed reglockFlags for degraded RAID 5/6.
Version 00.00.06.12 - Suggested ------------------- Enhancement - Add support for ServeRAID M5016
Fixes - LSI Channel fixes
Version 00.00.04.38 - Non-critical ------------------- - Fixed issue where device driver could print message "kernel megasas: Command pool empty!" when the controller and megaraid driver are idle.
Version 00.00.04.37 - Suggested ------------------- - Fixed issue where the ServeRAID M1015 controller will halt during a OCR. - Fixed issue where OCR will not execute when the physical drives are in a power transition mode. - Fix issue where the ServeRAID M1015 controller will halt with a degraded RAID 5 array during IO.
Version 00.00.04.30 - Non-critical ------------------- - Added support for the ServeRAID M5025 SAS/SATA Controller.
Fixes: - Fixed issue where during IO firmware faults at line : MonTask: line 1193 in file ../../raid/1078dma.c - Fixed issue where After 64 VD's are created using MSM the 'fdisk -l' command does not work. - Fixed issue where the firmware faults at line 739 in file ../../raid/1078main.c when rebooting after a recon. - Fixed issue where the drive partition is no longer present on the OS after importing a foreign configuration. - Fixed issue where Linux does not show the correct size of VD the second time if the 'fdisk -l' command is executed.
Version 00.00.04.17 - Non-critical ------------------- - Added support for the ServeRAID M1015 SAS/SATA controllers. - Added support for the ServeRAID M5000 Series Advanced Feature Key.
Version 00.00.04.10 - Non-critical ------------------- - Added logic to support next-gen SAS2 controllers. - Added support for the ServeRAID M5015 and M5014 SAS/SATA controllers.
Version 00.00.03.23 - Non-critical ------------------- - Added support for the IBM ServeRAID MR10ie (CIOv) SAS controller. - Fixed an issue where, on a Xen kernel with guest OSs running, invoking kdump causes a system reboot. - Fixed an issue that results in a kernel panic when kdump is run on a system with heavy drive I/O.
Version 00.00.03.21 - Suggested ------------------- - Added support for the IBM ServeRAID MR10is SAS controller. - Fixed an issue where a command timeout would occur on a particular SAS hard drive, and would not recover. - Added a shutdown DCMD call to the shutdown routine to ensure a graceful shutdown. - Updated the list of required pre-built binaries. - Fixed an issue the could cause unexpected interrupts. - Fixed an issue where a memory sanity check would sometimes fail for a certain pointer on a 64-bit system, causing some enclosure components to not be seen.
Version 00.00.03.18 - Suggested ------------------- - Added support for the IBM ServeRAID MR10il SAS controller. - Fixed an issue where the OS would not reboot when a rebuild was in progress.
Version 00.00.03.13 - Non-critical ------------------- - Added support the IBM ServeRAID MR10i, MR10k, and MR10M SAS controllers. - Fixed an issue where, on boot to Xen kernel on Red Hat Enterprise Linux (RHEL) 5 64-bit, the user would encounter an “Error 13: Invalid or unsupported executable format” error.
Version 00.00.03.06 - Suggested ------------------- - Added diskdump support for Red Hat Enterprise Linux (RHEL) 3 and RHEL 4. - Set the reply_q_sz value to the maximum number of commands supported by the firmware. - On 2.4 kernels: fixed an issue where, when the system was rebooted, the shutdown routine did not get called; added a notifier for the reboot event and initiated a flush command from the reboot event handler. - Fixed issue where, on RHEL 3 Update 6, the driver would not install on AMD64 systems.
Version 00.00.03.01-1 --------------------- - Initial release ibm_dd_sraidmr_00_00_06_19_sles10_32-64_chg
=============================================================================== Emulex FC/FCoE Device Driver for Linux ===============================================================================
Linux FC/FCoE Driver Version 8.2.0.145
Problems Fixed: - Kernel panics with FCoE on HS23 in SLES 11.2 x86_64. Also requires a SLES11.2 kernel update - FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service
Interoperability since previous release: - RHEL6.3 GA Kernel
Problems Fixed: - Fixed system crash due to not providing SCSI error-handling host reset handler - Debug helper utility routines for dumping various SLI4 queues - Fix unsol abts xri lookup - Fixed issues with LPe16000 to LPe16000 discovery - Fix driver crash during back-to-back ramp events - Reregister VPI for SLI3 after cable moved to new Saturn port - Fix log message 2597 displayed when no error is detected - Fixed FCP LOG for easier Finisar trace correlation - Fix kernel panic when going into to sleep state - Fix error message displayed even when not an error - Fix Read Link status data - Fix unable to create vports on FCoE SLI4 adapter - Fix initiator sending flogi after acking flogi from target - Fix the case where an array controller does not apply FCP priority rules - Added support for handling SLI4-port XRI resource-provisioning profile change - Change default DA_ID support from disabled to enabled - Fix bug with driver unload leaving a scsi host for a vport around - Update copyright date for files modified in 2012 - Fix bug with mailbox handling of REG_VFI and cable pull - Used PCI configure space read to flush PCI function reset register write - Update copyright date for files modified in 2012 - Fixed system panic when extents enabled with large number of small blocks - Fixed system panic during EEH recovery - Fix resource leak when acc fails for received plogi - Fix SLI4 driver module load and unload test in a loop crashes the system - Fix missing CVL event causing round-robin FCF failover process to stop - Fix deadlock during adapter offline request - Fix same RPI registered multiple times after HBA reset (CR 127176) - Fix driver handling of XRI Aborted CQE response - Fix port and system failure in handling SLI4 FC port function reset - Fix bug with driver not sending a LOGO with vport delete (CR 126625) - Fix KERNEL allocation while lock held - Make BA_ACC work on a fully qualified exchange - Fix for SLI4 Port delivery for BLS ABORT ACC - Fix ndlp nodelist not empty wait timeout during driver unloading - Fix mailbox and vpi memory leaks - Fix for FDISC failures after firmware reset or link bounce (CR 126779) - Limit what management ELS and CT commands can be issued according to latest management specification - Fix for driver using duplicate RPIs after 16Gb/s adapter port reset - Fix discovery problem when in pt2pt - Fixed failure in handling large CQ/EQ identifiers in an IOV environment - Fix Locking code raises IRQ twice - Fix driver not returning when bad ndlp found in abts error event handling - Added more driver logs in area of SLI4 port error attention and reset recovery
- Fix bug with driver returning the wrong ndlp - Fix driver behavior when receiving an ADISC - Fixed PCI loopback diagnostic test through hbaCmd on SLI4 port failure - Fixed unbounded firmware revision string from port caused the system panic - Fix driver does not reset port when reset is needed during - Changed SLI4 FC port internal loopback from outer serDes to inner internal - Fix ELS FDISC failing with local reject / invalid RPI - Fix REG_RPI fails on SLI4 HBA putting NPort into NPR state - Fix NMI seen due to CQE starvation - Fixed SLI4 FC port obtain link type and number dependent on link connection - Fixed SLI4 FC port internal loopback without SFP and external link/loopback plug - Fix driver incorrectly building fcpCdb during scsi command prep - Fixed FCP EQ memory check prevent initialize to single interrupt vector case - Fixed system panic during EEH recovery on SLI4 FC port - Fix FLOGI fails with invalid RPI (0x04) after connecting to a arbitrated loop - Fix ELS SCR failing with local reject / invalid RPI - Fix SLI4 port failures after firmware reset or dump - Fix port reset log messages indicate error when no error is seen - Fixed an issue where HBQ buffers are uninitialized in the base driver - Fixed missing hbalock protection on setting/clearing bit in phba->link_flag - Fixed logging mailbox error log messages during SLI4 FW download using HbaCmd - Fixed illegal state transition during driver unload - Fixed SLI4 FC port Internal and External loopback diagnostic tests - Fix bug with driver erroneously logging a kernel error message - Fix a crash while deleting 256 vports - Fix vport never finished discovery if switch runs out of resources - Fix kernel build warnings - Fix kernel panic when putting board in offline state twice - Fix PCI read failure looks like a over temperature event - Fixed driver event reporting to mgmt on error attention due to forced dump - Fix not displaying firmware rev for BE UCNA boards - Fixed ABTS failure logic not rediscovering targets - Fix bug with driver not byte swapping extended mailbox data - Fix premature ndlp cleanup after second target LOGO - Fix Link pull causes I/O failures - Add loop support for sli4 fc - Fixed OCM failing COMN_READ_OBJECT and COMN_WRITE_OBJECT mailbox pass-through - No longer read fcoe parameters if board is not fcoe - Added restore state and error log when sysfs board_mode attribute access failed - Added support for SLI4_CONFIG non-embedded COMN_GET_CNTL_ADDL_ATTR pass-through - Added support for SLI4 FC port persistent linkdown through config region 23 - Fix for ABTS. Do not free original IOCB whenever ABTS fails - Fixed Linux driver inconsistency in reporting FC host port-state through OCM - Fix firmware upgrade attempt on unsupported adapter - Fix incomplete message number 2889 - Fix system crash when Lancer fails to initialize - Fixed fcpi param length when not using an sgl - Fix virtual fabrics bit set in FLOGI incorrectly - Fix unsupported link speed accepted by SLI4 port - Incremented minor management version to reflect additional "protocol" sysfs attribute - Fix kernel build warnings - Modify WQ handling to use entry_repost - Added a sysfs attribute "protocol" to report SLI4 port link protocol type - Added SLI4 INTF_TYPE and SLI_FAMILY as sub-field to the fwrev sysfs attribute - Added structure to support T10 DIF in SLI4 - Fix performance slowed due to too many register accesses - Fix a possible driver crash when cfg_fcp_eq_count is zero - Fixed non-embedded COMMON_GET_CNTL_ATTR mbox command failed with status 0x4 - Changed the way of SLI4 device detecting physical port name - Fixed FCP policy exchange management rule parsing - Add new check to lpfc_decode_firmware_rev to handle releases that have an 'X' - Fixed RPI leaks in ELS protocol handling - Fix kernel crash during boot with SLI4 card installed - Fixed NPIV FDISC failure on SLI4 if-type 2 ports - Moved fcp policy structs - Fixed driver failed to follow IP reset procedure in SLI4 error attention handler - Fixed fcp underrun reporting - Fix sysfs lists fabric name for port that has been disconnected from fabric - Added support for policy exchange management - Changed the timeout to 300 seconds for SLI_CONFIG (0x9B) mailbox command - Fixed a driver handling IP reset issue when PCI read return error - Fixed casting problem in calculating tx_words statistics - Fixed compiler warning due to uninitialized local variable - Added proper error code return for libdfc calling API to make proper decisions - Fix sli4 mailbox status code. Management software has dependencies - Made proper error code return for libdfc calling API to make proper decisions - Made error log include PCI BAR bitmap from kernel when enable PCI device failed - Fixed incomplete scsi messages displayed - Change log message in lpfc_sli_set_dma_length() - Completed missed FCF priority failover - Fixed not recovering SLI port in handling error attention with RN bit set - Fixed two crash cases when unsolicted ELS ECHO_CMD is received - Fix direct connect does not come up for SLI4 FC ports - Fixed long wait when firmware reset to a SLI port without required privilege - Fix driver firmware update to match new firmware image format - Fix SLI4 CT handling for sequences > 4K - Fixed handling of unsolicited frames for vports - Fixed crash when aborting els IOs - Fixed handling of CVL for vports - Fix up CT and oxid/rxid for unsol rcv frames - Fixed mailbox double free panic - Added fcf priority record selection for fcf failover - Fixed compiler warning for putting large amount of memory on stack - Fixed hbacmd listhbas took very long time when remote initiators present in zone - Fixed driver build not building in debugfs even if kernel CONFIG_DEBUG_FS=y is set - iDiag added SLI4 device PCI BAR memory mapped reigster access methods - iDiag changed command structure data array indexing by using macro defines - Ported iDiag pass-through multi-buffer mbox command capture and dump extension - Ported new SLI4 FC device loopback test and link diagnostic test supports - FLOGI payload has Multiple N_port_ID set when lpfc_enable_npiv clear - Add sysfs logging when writeable parameters are changed - Fixed new ASIC device-mgmt SYSFS pass-through failed multi-buffer fw download - Fixed memory leak due to failure to release mailbox command when completed - Brought debugfs accessing new ASIC extents information into the iDiag framework - Added wait for SLI port status register for readyness following firmware reset - Consolidated duplicating macro definitions - Implement debugfs support for resource extents - iDiag method for read write bitset bitclear access to new ASIC control registers - Fixed failure in pass-through mbox command with multiple number of large buffers - iDiag method for endian explicit dumping at iussue SLI4 mailbox command routine - iDiag ported debugfs method for dumping mbox from SLI4 issue mbox cmd routine - Added request for PCI funndamental reset to support EEH recover on P7 platform - iDiag ported debugfs inline mailbox command capture and dump utility - Fixed failure to enable PCIe AER prevent driver initialize and attach to device - Fix EEH recovery so state is saved after every PCI reset for SLI4 - Moved INIT_LIST_HEAD to the inside of lpfc_mgmt_issue_sli_cfg_ext_mbox routine - New ASIC device management pass-through mbox extension with multi- buffer support - Fix FC Port swap on SLI3 adapters - Fixed Virtual link loss during Face plate failover test - Fix vpi initialization in lpfc_init_vfi - Added driver capability of reseting new ASIC firmware and device from sysfs entry - Added capability of inducing new ASIC firmware dump obj file to flash filesystem - Add firmware upgrade code to driver - Added 100ms delay before driver action following IF_TYPE_2 function reset - Fragment ELS and SCSI SGE lists based on Extent regions - Fixed potential missed SLI4 device initialization failure conditions - Fixed Back to back Flogis sent without a logo - Add model names for new hardware - Fix bug with lpfc driver not updating the wwnn and wwpn after a name change - Set the maximum SGE size to 0x80000000 when HBA does not have any restriction - Fix SLI3 and non-NPIV crashes with new extent code - Fix CT command never completing on Big Endian system - Refactor lpfc_sli4_alloc_extent some more - Restore SLI4_PARAMETER mailbox can fail as nonerror functionality - Do not post RPI Headers to SLI4 port that support extents - Framework for new ASIC device management multi-buffer mbox passthrough support elx_dd_fc_ibm1206-8_2_0_145_sles10_32-64_chg
=============================================== Change History =============================================== Document Name: Change History Document Status: IBM General Avalibility Document Version: 3.1 Latest Driver Version: 3.1.0.0 Document Updated: 8/04/2011 Product: Brocade FC HBA / FCoE CNA
=================================================
Please visit www.brocade.com/hba for full documentation, additional drivers, and management applications.
Version 3.1.0.0 Fixes and Enhancements: - Added support for new kernels. - Added support for IBM FLEX System FC5022 2-port 16Gb FC Adapter
Version 3.0.0.0 Fixes and Enhancements: - Added support for Brocade 1860 AnyIO Fabric Adapter (User configurable port mode - FC or NIC or CNA) - Added Fibre Channel 16G Support - Enabled Fabric Assigned Address in Fibre Channel Fabric - Added PF based Virtualization – vHBA - Enhanced CLI, HCM GUI and CIM support in inbox drivers. - Added PF based Virtualization - vNIC - Added iSCSI over DCB Support - Added Multiple Tx Priority Queues Support - Added SNMP Support
Version 2.3.0.3 Fixes and Enhancements: - Enhanced SNIA API to report port speed of 4 and 8Gbps in SNIA format. - Enhanced XIV array interoperability that addresses a data integrity corner case. - Enhanced the transmit path handling in Linux Network Driver to avoid a corner case that could lead to transmit path stall. - Enhanced the Linux Adapter Software installer script to update the initrd with the correct name even when there are multiple copies of the OEM specific initrd(s).
Version 2.3.0.0 Enhancements: - Enabled HP DL120 server to support Boot over SAN with two Brocade HBAs installed. - Improved network driver CPU and performance optimization. - Enabled automated target and LUN discovery of enterprise HDS storage once LUN masking has occurred. - Improved Tivoli interoperability to meet device display requirements.
Version 2.2.0.1 Added capability to handle ADISC frames. Unhandled ADISC use can cause SAN boot failure when booting from IBM storage array.
Version 2.2.0.0 Adds support for bootcode updates to Bladecenter 10G Converged Network Adapters
Version 2.1.0.0 Adds support for bootcode updates to 10G Converged Network Adapters
Version 2.0.0.0 Initial release for 4/8G FC HBAs brcd_dd_fc_bfa-3_1_0_0_sles10_32-64_chg
Multi-boot Image for 4Gb FC HBAs Release Notes Package Version MB_1.90-3
This software license applies only to QLogic customers. QLogic Corporation. All rights reserved.
Table of Contents
1. Version 2. 4Gb BIOS 3. 4Gb EFI 4. 4Gb FCode 5. Trademarks 6. Notices 7. Contacting Support
1. Version
These release notes describe the changes, fixes, known issues, and release details that apply to the multi-boot package for 4Gb HBAs, version MB_1.90. This package is a compressed file that contains:
* BIOS version 2.16 * EFI version 2.27 * FCode version 3.13 * Firmware version 5.03.06
Rev 1.00 Jan.20, 2005 Initial release. Rev 1.01 Feb.18, 2005 Added code to put Port ID of device in IOCB. Rev 1.02 Mar.28, 2005 Added support for Serial Link Control. Addded code to display slot, bus number and function in CTRL-Q utility. Rev 1.03 Apr.18, 2005 Fixed bug when no drives attached and connected to switch. Added code to reset ISP if ISP is paused when ISR is called. Rev 1.04 June 8, 2005 Fixed bug in CTRL-Q utility that caused adapter id to be displayed at invalid id's. Added code to set Write Protect in Flash Status reg. Fixed bug in CTRL-Q utility where EAX reg was being corrupted by timer interrupt routine. Fixed bug in setting up LUN field in IOCB. Fixed bug in not setting port ID when connected to a switch. Rev 1.05 Sept 27, 2005 Changed code to suppress padding firmware version with leading zero's. Fixed bug in setting data direction flags in IOCB for 'seek command'. Changed code to not count device if device disabled by system BIOS. Fixed bug in setting flash Write Protect. Rev 1.06 Oct. 13, 2005 Fixed bug where anykey could invoke Fastutil. Rev 1.09 Nov. 22, 2005 Changed buffer request size to 2056 bytes for 'Report Luns' command. Fixed bug where GAN_NXT IN_ID was not always being set to zero causing GAN_NXT to fail. Rev 1.10 an. 31, 2006 Added check for optional boot mode flag to allow code to configure 1 drive/port when enabled. Bit 6 of host parameters in NVRAM is set to enable this mode. Fixed bug when Spinup-Delay and link is down. Added code to not display Data Rate option in CTRL-Q for QME2462. Rev 1.11 Feb. 7, 2006 Added support for interrupt polling. This option is controlled by bit 7 of NVRAM Host Parameters and by new Advanced Settings option in CTRL-Q. Rev 1.12 Feb. 21, 2006 Changed format of PnP string to display when Opt Boot Mode enabled in NVRAM. Added check for ELS reject status from Login IOCB. Rev 1.13 Apr. 04, 2006 Fixed bug in not always setting port id for logout IOCB. Changed code to support up to 16 adapters and 16 drives. Rev 1.14 Apr. 17, 2006 Changed code to ignore CLP '_hss' string. Rev 1.15 Apr. 20, 2006 Added code to wait for Login to complete when login pending status detected. Rev 1.16 May. 4, 2006 Fixed bug in not setting up Luns/Target in CTRL-Q. Added code to support Restore Default option CLP string (PCI3.0 BIOS only). Changed timeout value waiting for Linkup status from 6 seconds to 23 seconds. Rev 1.17 June 29, 2006 Added support for restoring defaults using CLP string (Pci3.0 only). Optimized code waiting for Linkup status. Added code to use Memory Map I/O for PCI express. Added code to check for correct Max Payload Size on QLE2464. Rev 1.18 July 19, 2006 Added code to load Nec switch port 1 and 2 pci config regs offset 68h with port 0 config offset 54h value. Fixed bug where task attributes in IOCB type 7 were not always being initialized. Rev 1.19 July 24, 2006 Fixed bug in CTRL-Q utility configuring Luns using Report Luns data when lun list has more lun entries after lun 255. Rev 1.20 Aug 2, 2006 Added code to support QLE2xx. Rev 1.21 Aug 24, 2006 Fixed bug in CTRL-Q cursor positioning for some user input displays. Rev 1.22 Sept 11, 2006 Added support for 'exit' CLP string. Changed CLP string to support new format: 'PermanentAddresses' was changed to 'PermanentAddress. Rev 1.23 Oct 16, 2006 Fixed bug in not setting rc_hba when different adapter types installed in system. Rev 1.24 Nov 29, 2006 Removed Extended Error Logging option from CTRL-Q. Removed code to use Memory Map I/O for PCI express. Rev 1.25 Dec 12, 2006 Added code so that set Defaults only to restores factory setting when value was modified by CLP string Rev 1.26 Dec 20, 2006 Fixed issue with the handling of CLP WWNN string. Also added code to always set firmware nodename optiom when set Default CLP is received. Rev 1.27 Feb. 26, 2007 Added support for Set Capabilities CLP string. Added code to load PLX switch port 1 and 2 pci config regs offset 68h with port 0 config offset 54h value (this is same code used for NEC switch). Rev 1.28 Apr. 12, 2007 Added code to check if need to restore HBA default portname. Added check for command fail status after login cmd. Restored code to read block 0 to determine drive geometry. Added NVRAM option (host_params bit 8) to enable support for HP boot order. Fixed bug in handling CLP Set Capabilities data. Rev 1.29 May. 22, 2007 Restored CTRL-Q Lun per Target option and changed text from 'Boot order' option to 'Controller order'. Rev 2.00 Dec. 03, 2007 Added support for ISP2532. Rev 2.01 Jan. 17, 2008 Added support for 1Gb data rate for 4Gb HBA. Rev 2.02 Feb. 18, 2008 Changed code to clear 'Disable Serdes' flag for CLP string Restore Default. Rev 2.03 Mar. 12, 2008 Added support for ISP8423. Added code to support new CLP 'set capability' spec. Rev 2.04 Mar. 23, 2008 Changed code to not used bit 13 of Host parameters. This avoids potential confict with inbox driver. Rev 2.05 Jun. 3, 2008 Added code to allow 2 min for link to come up when spinup delay enabled. Added code to poll for keyboard status. Removed external Loopback test option for ISP8432. Added check if IO support valid. Added check to CLP set_capablity string for the correct HBA port. Rev 2.06 Jun. 18, 2008 Added support for new CLP 'set capability' serial link spec for ISP2532. Rev 2.07 Sept. 3, 2008 Added additional error message for Verify Disk utility when device does not support SCSI cmd 2fh. Add support for Extended HBA CLP strings. Rev 2.07.6 Sept. 12, 2008 Fixed bug with 'restore netport defaults' when restoring NPIV's. Added code to reset ISP before accessing NVRAM the first time. Rev 2.07.8 Oct. 22, 2008 Added support for IDT PCIe switch Fixed bug in restoring NPIV after updating with CLP. Rev 2.08 Oct. 30, 2008 Removed TEST ONLY from BIOS banner. Rev 2.09 Dec. 02, 2008 Added code to save some pci data. Added new option to Advanced Option menu in CTRL-Q for Virtual Fabric Enable/Disable. Rev 2.10 Feb. 24, 2008 Added support for ISP8001 Added check for INT Polling before updating interrupt controller(PCI3.0) Fixed bug where eax register was being corrupted in nvram_config routine. Removed option in CTRL-Q for Virtual Fabric Enable. Fixed cosmetic bug in displaying selectable boot lun in CTRL-Q utility. Rev 2.11 Apr. 28,2009 Fixed issue with setting up Init FW MB command for using Extended Init Control Block Added option in CTRL-Q utility for Primary FCF VLAN ID for ISP8001 HBA. Added code to check version field of Extended ICB. Added code to correctly identify pci switch on 4 port HBA's. Changed code to suppport Loopback mode with new version of FW. Rev 2.12 May, 15,2009 Changed code to handle HSS CLP vendor id 3 same as vendor id 2. Rev 2.13 July 16, 2009 Added code to save backup copy of VPD/NVRAM data. Rev 2.14 Oct 9, 2009 Changed code to use FS segment register instead of GS in find_device routine. Change code to preserve MSB of WWPN Set Capablity CLP when updating WWPN/WWNN. Rev 2.15 Nov 23, 2009 Added code to handle 'About FW' mailbox command timeout. adapter. Rev 2.16 Mar 16, 2010 Fixed bug in not setting Write protect for single port adapter.
Driver Name : Fibre Channel Driver for UEFI Version : 2.27 Date : 05/9/2010 OS platform : N/A FW version : See MultiBoot release notes for FW version. Efiutil Version : 2.86
Table of Contents I. Overview II. Enhancements III. Bug Fixes IV. Known Issues V. Additional Information
I. Overview
The following document provides details of the Fibre Channel UEFI driver version 2.27, Efiutil version 2.86.
II. Enhancements
None
III. Bug Fixes
Driver: * Removed Extra character and NULL string message from HII. (ER71174, ER71175) * Add support for 8GB data rate for 25xx family in HII form. (ER71118) * Add fix in driver to avoid to print driver messages on splash screen during system boot up. (ER71099) * Add support for HII Protocol. (ER55486) * Added fix to allow W2K8 boot from local disk when target is mapped in passive path. (ER70069) * Added fix to diplay firmware version info correctly in HII "Adapter info" menu. (ER71412) * Display error message in HII form if invalid HBA parameter value is set (Execution Throttle). (ER71533) * Fixed a bug that caused VPD version numbers to be displayed wrong. (ER70907) * Add fix for NULL string message displayed on Hx5 system. (ER71771) * The "Enable Loop ID" bit in the HII menu is now set correctly. (ER71885) * Rename "Reconnect and Exit from Main Menu" HII entry to "Exit from Main Menu".
Efiutil: * Add fix to avoid, overwriiting of orignal SERDES file, if user give wrong command. (ER69941) * Added fix to avoid, "unaligned reference fault", while updating flash. (ER69793) * Add support, to ignore locked fileds while updating firmware area. (ER69531) * Add fix to display firmware version correctly. (ER71468) * Add fix to display new firmware version correctly while updating multiboot image. (ER71468) * Add support for 82xx family in Adapter list. (ER69230)
IV. Known Issues
* In the HII menus, Adding/Deleting a Target/LUN will require a reboot for changes to take effect.
V. Additional Information
* Efiutil and the EFI Driver are a matched set. Always make sure that Efiutil and the EFI Driver are from the same release package.
Release Notes for 4Gb FC HBAs (FCode) ================================================================
version 3.13 03/26/10 * Change REV_LEVEL in rev_level.m4 from 3.13b9 to 3.13. Offical Release.
version 3.13b9 03/24/10 * Remove Explicit logout to fabric(FLOGO) in close-hardware, put in v3.13b3. * Restructure fcode source files. Add: isp-init.fth, p3-init.fth, mailbox.fth, properties.fth, structs.fth, regs-isp.fth, regs-p3.fth, utils.fth.
Version 3.13b8 03/09/10 * Add Parameter 1 debug display on login IOCB faliure if debug-logi? is set. * Add force-open-ok? test flag in open method. Default = true(no real change). * Change get-to-params to set boot-wt = 8 secs if boot-wait-time is disabled. * Fix bug in VPD fetch, introduced in v3.13b1. vpd-buf increased to 512 bytes. * Change cbuff back to non instance buffer. Instance has no effect on buffer:.
Version 3.13b7 03/04/10 * Remove Hard-RICS-reset from reset-risc method. Causes problems on QMI2582. * Remove Eddy test= Reset RX-Serdes after 5 secs wait for in isp-fw-ready?. * Make old-sb (old sec-buf) an instance value. Problem on M3000 (ER70453).
Version 3.13b6 03/02/10 * Add Reset RX-Serdes after 5 secs wait for in isp-fw-ready?. Plus add debug.
Version 3.13b5 03/01/10 * Add more debugging in isp-fw-ready?. Print fw-state each time in get-state. * Change getnum to use the 'accept' word and make cbuff an 'instance' buffer:.
Version 3.13b4 02/24/10 * Fix Explicit logout-device IOCB to include the ISP PortID and Port WWN. * Changed debug? flags: 4000= Got-R2H-intr, 2000= IOCB-Dump, 800= FW-Ready-wait.
Version 3.13b4 02/22/10 * Fix Explicit logout-device IOCB to include the ISP PortID and Port WWN.
Version 3.13b3 02/19/10 * Use OpenBIOS Toke Tokenizer to make isp2500/8100/8200. isp2400 uses SUN toker. * Add Implicit logout-all and Explicit logout to fabric in close-hardware. * Add setting the FW ICB link-down-NOS/OLS value for isp2400/2500 (ER67806).
Version 3.13b2 02/11/10 * Change set-boot-wait-time to not affect link-down-to (timeout) for Fujitsu. * Change login-devices to not logout with FC_Initiators. * Change logout-device to use implicit Logout, not explicit. (Fix P3P problem)
Version 3.13b1 02/05/10 * Change set-boot-wait-time to be entered/display in decimal, not hex(Fujitsu). * Added OpenBIOS 'toke' Tokenizer to makefile. Now you can make either version. * Fixed bug introduced in ISP2400 v3.10. Defered word fmw_ofs, never defined.
Version 3.12 01/11/10 * No change to isp2400, fixed SSDID for Sun (SUNW,qlc) CNA QLE8142.
Version 3.11 12/11/09 * No change to isp2400, added support for Sun (SUNW,qlc) CNA QEM8152.
Version 3.10 12/02/09 * Change the name of the top level Fcode file from isp2xxx.fth to ispxxxx.fth. * Change makefile to include the creation of P3+ isp8200.xxxx.fc binaries. * Introduced bug for defered word fmw_ofs, never defined for ISP2400.
Version 3.09 10/26/09 * Change REV_LEVEL in rev_level.m4 from 3.09b1 to 3.09. Offical Release.
Version 3.09b1 10/22/09 * Fix Node-Name-Option bit preservation in restore-default-settings. ER68181.
Version 3.08 10/19/09 * Change REV_LEVEL in rev_level.m4 from 3.08b1 to 3.08. Offical Release. * Remove patch of PCI header image size byte at offset 0x2c from init version. * Fix flash-word! bug introduced in veersion 3.08b1. Affects ISP2400 only.
Version 3.08b1 10/14/09 * Fix default WWNN & WWPN preservation in restore-default-settings. ER67924. * Fix stack bug when link down. Introduced in v3.05 set-phandle word. ER67926. * Add standard properties. Use m4 utility to automaticly create date string. * Add file rev_level.m4 which has the revision level strings only. * Add FCoE & 4Gb IBM mezz cards QMI8142 QMC2462 QMI3472 QMI2472 to imezz? word. * Change messages "Login failed" to "Login Abort". "Error Subcode" to "Subcode". * Re-structure Flash/NVRAM access fnv-wd@/! words for the Netxen P3 integration. * Add 'make nx3031' to makefile for Netxen P3. #ifdef P3 used for delineation.
Version 3.08b1 09/25/09 * Add standard properties. Use m4 utility to automaticly create date string. * Add file rev_level.m4 which has the revision level strings only. * First version with some support for the Netxen P3 CNA.
Version 3.07 09/08/09 * Change version string from 3.07b2 to 3.07. Offical Release for IBM and SUN.
Version 3.07b2 09/04/09 * Fix read-cap16-cmd. Used when the LUN size is >2TB (i.e. #blocks > 32-bits). * Fix disk-test to work with large >2TB LUNs, where the LBA >32-bits.
Version 3.07b1 08/28/09 * Remove command retry when 8048 AEN is received. Caused DMA error found by IBM. This was an old workaround put in vers1.08b2, before IOCB timeouts were set.
Version 3.06 08/19/09 * Change version string from 3.06b6 to 3.06. Offical Release for IBM. * Fix qlgc-debug? option for IBM. Use find-method on IBMs and $find on SUNs.
Version 3.06b6 08/18/09 * Add option for qlgc-debug? in nvramrc. If the diag-switch? is true, then the debug? flag is set is set to the value of qlgc-debug?.
Version 3.06b5 08/18/09 * Add lba64 large disk capability (read-blocks64 write-blocks64) for SUN only. * Add support for QEM3572, SSDID = x172, for SUN only. * Add mbox1 & mbox2 display for 8048 interrupt if debug-asyc? flag (01) is on.
Version 3.06b4 08/13/09 * Fix bug in IBM fcp-luns method for the Controller LUN-0 check, lun0-check.
Version 3.06b3 08/12/09 * Check Inquiry Qualifier field of Controller LUN-0 in IBM fcp-luns method.
Version 3.06b2 08/10/09 * Add more IOCB debugging, Add Erase Response-Queue in mapmem. Had stale data.
Version 3.06b1 08/08/09 * Add more debugging for IOCBs, dma-map-in/out, & wait-for-interrupts.
Version 3.05 08/04/09 * Change version string from 3.05b2 to 3.05 Offical Release for IBM.
Version 3.05b2 08/03/09 * Fix set-fc-address issue found with IBM ioinfo. PortID was not getting set. * Re-structure devicepresent.fth. Add set-phandle to set obp-target & obp-portid
Version 3.05b1 07/31/09 * Fix multiple close issue found with IBM ioinfo utility.
Version 3.04 07/22/09 * Add "ibm,write-supported" property to disk child node, as per IBM's request.
Version 3.03 07/13/09 * No change, affected ISP2500 & ISP 8100 Fcode only.
Version 3.02 05/06/09 * No change, affected Schultz ISP8100 Fcode only.
Version 3.01 04/23/09 * No change, affected Schultz ISP8100 Fcode only.
Version 3.00 04/21/09 * Added more debugging information for AEN 8014.
Version 3.00b8 04/01/09 * No functional change, binary files differ. Only ISP2500 Fcode affected.
Version 3.00b7 03/31/09 * No change, Schultz ISP8100 Fcode only.
Version 3.00b6 03/04/09 * Change boot-wait-time to start timer(fw-ready-start) in isp-fw-ready method. * Change fix-rbios to check nvr-bad? before copying nvram to RAM.
Version 3.00b5 02/25/09 * Change link-down-timeout to boot-wait-time if bootwait-enable flag is true. * Add ILT support for SCHULTZ only. No effect on ISP2400 * Changed era-code (used in ldfcode) to use /code to determine #secs to erase. * Add set-cd-base+siz (used for ldfcode) to replace set-ld-base & set-/dlc.
Version 3.00b4 02/11/09 * No change. Changed flash-acc-data & offsets for ISP8100 only.
Version 3.00b3 01/21/09 * No change. Changed reg property for ISP2500 and ISP8100 only.
Version 3.00b2 01/08/09 * Added set-boot-wait-time commnad for all 4 & 8Gb HBAs/CNAs. Add NVRAM Fcode 2-byte parameter, boot-wait-time, at ofs x15a & enable-bit(x20) at ofs x158. This was requested by Fujitsu, for disks that take longer to come online.
Version 3.00b1 12/19/08 * Add Schultz ISP8100 support. No change to ISP2400 methods. * Added more SCSI sense debugging. * Reworked interrupt service routines with more debugging.
Version 2.04 12/03/08 * Change version string from 2.04b2 to 2.04 Offical Release.
Version 2.04b2 12/02/08 * Remove set-bootid, set-boot-wwn, & releated qla only words from IBM version. * Added IBM debugging to BOFM words and set debug?=C00 if diag-switch is true. * Added max-payload bridge fix for 4-port QMI2464 HBA. Used Gil's method. * Fix get-mail to handle Response-Queue interrupts (stat=13) & add debugging.
Version 2.04b1 07/23/08 * Preserve Flash area x40000-x80000 which has FW-Area, Flash Tables, NPIV data * Fix open to always return -1. Returning link-down fw-state fails on Serengetti
Version 2.03 06/30/08 * Change version string from 2.03b1 to 2.03 Offical Release.
Version 2.03b1 06/06/08 * Use complete NVRAM values for fwopt2 and fwopt3 in fw-init, initialize ICB.
Version 2.02 05/07/08 * Change version string from 2.02b3 to 2.02 (Offical Release). * Fix load-image to return error status so you can exit on failure. * Remove stop-fw from isp-probe method. It did nothing since FW is not loaded.
Version 2.02b3 04/17/08 * Change compatible property to append to existing property, if it exists. * Change all references in the Fcode of 'HBA' to 'Adapter' (for QLE8000 CNA).
Version 2.02b2 04/14/08 * Fix compatible prop for IBM. Return DDDD value back to DevID in strings: pciVVVV,DDDD.SSSS.ssss.RR & pciVVVV,DDDD.SSSS.ssss. DDDD was = SSDevID.
Version 2.02b1 03/27/08 * Fix blank lines in list-wwns for set-boot-wwn command in qla-mode. ER59591. * Change the d-mbox (dump-mailbox) word to use the .4z data format macro. * Add Access Menlo Data IOCB to allow displaying & changing Menlo configuration. * Add Menlo version number to the version command (Menlo only).
Version 2.01 03/27/08 * Change version string from 2.01b2 to 2.01 (Offical Release).
Version 2.01b2 03/05/08 * Change SubSystem Device ID from x0169 to x014B for Sun QEM3472 HBA. * Add sunid-bit = x10 to Fcode Parameter word (offset x158) in NVRAM.
Version 2.01b1 03/03/08 * Add support for Sun QEM3472 with SubSystem ID = 0x0169, node name SUNW,qlc. * Add QLE3000 Mercury HBA support. * Fix selftest mem-siz = x20000 (128KB) on IBM CFFe/CFFx mezz cards.
Version 2.00 02/15/08 * Change version string from 2.00b17 to 2.00 (Offical Release).
Version 2.00b17 02/07/08 * Modify ldfcode again to skip copy of WWN and checksum to BIOS-defaults area.
Version 2.00b16 02/05/08 * Modify ldfcode to copy all BIOS-defaults plus copy Model & DID to header. * Fix login-devices to return #ports, including non-target ports. This fixes Sun Bug ID 6645537, ER58525, where LUNs were not listed when Emulex present.
Version 2.00b15 01/29/08 * Fix target login problem with McData switch by adding GID_PT command. ER58769. * Modify ldfcode to poke BIOS default area of the MB-image with Model# & SSID.
Version 2.00b14 01/15/08 * Fix restore-default-setting to skip SSDID, OEM Specific Area, Feature Mask, and Model# copy to NVRAM. Also add revert-wwns on IBM. ER58465 & ER58509. * Replace load-stub-fw with stop-fw mbox command for PCIe 2400 HBAs. Firmware vers 4.00.25 or greater stop-fw command will do the same thing as stub FW. * Fix IBM BOFM bug where the default WWPN is lost if a new WWPN is written twice
Version 2.00b13 12/21/07 * Separate 2400/2500 Fcode into two binary output files (isp2400/isp2500). Remove isp2500? & use #ifdef ISP2500. Resulting in smaller 37KB image size. * Add use-cdb16? flag which is set in read-capacity if the target supports Large LBA. 16-byte CDBs are used only if use-cdb16? is set & LBA > 32-bits. ER58285. * Fix "chrp" string in papr-compliant? word (IBM BOFM support). * Change write-wwnn word to check for new-wwnn=0 (IBM BOFM support). * Add enab-nvr-acc to all 6 BOFM external words so they work on unopened dev.
Version 2.00b12 12/10/07 * Add init-chip? to sns-command & logout-devices for recovery from link-down. * Put ifp-abort back into wait-for-risc-int, which was taken out in vers 1.23.
Version 2.00b11 12/05/07 * Move clearing of flags link-up?, done-fw-init? port-updated? to reset-risc. This was for isp2500 set-boot-wwn failure because FW was stopped. ER58139.
Version 2.00b10 11/30/07 * 2500 change only. ER58002.
Version 2.00b9 11/28/07 * Fix find-image to check for last-image bit and exit loop if found. ER57989. * Fix init-fw problem. If NVRAM is blank, FW Option word-1 is not set in ICB.
Version 2.00b8 11/21/07 * Make BOFM support words external in IBM version. * Change my-wwnn@ to return WWNN based on current adapter WWPN. (IBM version) * Fix stop-risc bug. Clear done-fw-init? flag before calling mail. ER57926.
Version 2.00b7 11/12/07 * Remove 'ibm,' from the BOFM support words for IBM. Also update property. * Add check-managed-wwn which checks for PAPR-compliant & san_wwn string in root prop " ibm,managed-address-types" and then reverts WWNs if necessary.
Version 2.00b6 10/18/07 * Changed makefile to create separate isp2400 & isp2500 images(PCI header only). * Fix drate-val (default Auto Data-Rate value) w/o shift for selftest. * Fix n-port topology device-present problem. obp-portied was not getting set. * Add back architecture check (wrong-arch?) of PCI header DEVID during flashing. * Add rd-ram-wd and wr-ram-wd mailbox commands for debugging purposes. * Add BOFM support for the IBM version Fcode.
Version 2.00b5 09/24/07 * Combined 2400/2500 Fcode into a single binary output isp2x00 file. Use isp2500? word instead of #ifdef ISP2500. Resulting image size is now 38KB. * Changed Connection Mode & Data Rate debug messages during FW initialization.
Version 2.00b4 09/18/07 * Shrink code wherever possible. Remove unused words and shorten value names. * Fix find-fc method to add Func0 bc0_ofs. Otherwise it checksums Func1-fcode.
Version 2.00b3 09/07/07 * Add reset-risc to reopen-hardware method when init_link?=0, for INIT version.
Version 2.00b2 09/06/07 * Fix selftest to always use Auto-negoiate data-rate. ER56565. * Fix open for selftest to return OK status when link-down on a reopen. ER56566.
* Fix version number in PCI header. Should be 2.00.
Version 2.00b1 08/28/07 * Add 2500 support with major change in NVRAM and Flash utilities.
Version 1.27 08/21/07 * Change version string from 1.27b11 to 1.27 (offical release).
Version 1.27b11 07/31/07 * Move init-chip to reopen-hardware so FW loads in show-children if link-down. * Make chip-base, exprom, lun-index and port-update-occurred instance values. * Make link-up a Hard (not instance) so it stays set between instances. ER55858.
Version 1.27b10 07/11/07 * Fix find-dflts and dflt-wd@ to now handle 2-byte alignment in BIOS. ER55660.
Version 1.27b9 07/03/07 * Remove QLE2464 PCIe Dev control reg max-payload-siz set from 1.26b9. ER55588. * Added Data Rate command when debug-init is set, to display actual data rate.
Version 1.27b8 06/22/07 * Add setting WWPN bit-56. This bit is clear in the WWNN. This fixes a potential problem when OEM (DTI) uses oemutil to set the adapter's WWPN. Matches driver. * Add setting FW Option 1 word in ICB. Never reported as a problem, but... * Fix stack bug in login-device when comp-status is invalid(eg. 99). ER55423.
Version 1.27b7 06/11/07 * Fix stack bug created in 1.27b6 on Bad IOCB Entry Status. * Add Execute command error debug level x40 and rework debug levels.
Version 1.27b6 06/05/07 * Remove fc-mode, set-fc-mode (qla-mode) words from IBM version. * Change IOCB fail messages to show only when the debug? 08 bit is set. ER55150.
Version 1.27b5 05/24/07 * Fix restore-default-setting to skip the Adapter WWPN copy into NVRAM. ER55009.
Version 1.27b4 05/14/07 * Add re-login when IOCB status =x29|x28, which will init-chip & login-device. This change was made to handle cable-pulls during boot. ER54837. * Change debug messages: Loop Up/Down to Link Up/Down & add test-unit-ready. * Change makefile to create 256k byte Fcode-only images to be used with SCLI.
Version 1.27b3 05/03/07 * Add back restore-default-settings but restore entire NVRAM from BIOS defaults. * Fix ibm-encode-unit to drop LUN if =0 & remove leading zeros, like 2312 Fcode.
Version 1.27b2 04/03/07 (Sent to Lyle) * First pass at adding NVRAM max-frame-size in FW ICB. Based on vers 1.26b10.
Version 1.27b1 03/22/07 (beta version given to IBM) * Add 16-byte SCSI CDB read/write commands for LBA >2TB. Based on vers 1.26b10.
Version 1.26 05/17/07 * Change version string from 1.26b21 to 1.26 (offical release).
Version 1.26b21 04/26/07 * Remove error messages for 'TUR failed' & SCSI 'Retries exhausted'. ER54516.
Version 1.26b20 04/25/07 * Remove restore-default-settings for 1.26 rel. Put a complete restore in later.
Version 1.26b19 04/25/07 * Change version-prop "Host Adapter Driver" to "Host Adapter FCode". ER54455.
Version 1.26b18 04/24/07 * Fix list-wwns to not call get-portname-db if invalid topology. ER54434.
Version 1.26b17 04/19/07 * Add NVRAM parameters restore-default-settings, with confirm question. ER54346. * Stop using the bios-compatibility-mode bit in NVRAM and remove set-mode command since it is no longer used in the 4Gb FCode (needed for 2Gb only). * Move all of the NVRAM access methods into a separate file, nvram.fth.
Version 1.26b16 04/18/07 * Add show max-frame-size (show-maxfs) to show-settings. * Fix bug in VPD data fetch (vpd@) word. Need to poll ready bit. ER54345.
Version 1.26b15 04/13/07 * Fix max-frame-size typo in menu, should be 1024, was 1048. * Fix version number in PCI header, was 1b(1.27), should be 1a(1.26).
Version 1.26b14 04/13/07 * Change max-frame-size to use a 3 choice menu, 1-512, 2-1024, 3-2048. ER54229.
Version 1.26b13 04/12/07 * Add Fcode usage of NVRAM parameter, max-frame-size in FW initialize ICB. * Add word, set-max-frame-size, for changing this NVRAM parameter. ER53990.
Version 1.26b12 04/10/07 * Fix inquiry? to check for no-data xfer. Problem seen when LUN#>255. ER54103. * Add 16-byte SCSI CDB read/write (x88/x8a) commands for LBA >2TB. IBM request. This change does not effect the old 6-byte & 10-byte SCSI CDB reads/writes.
Version 1.26b11 04/04/07 * Change word show-boot-wwn from being 'external' to 'header', so it is not visible with fcode-debug? flag =false. Requires change to readme.txt. ER53873.
Version 1.26b10 03/02/07 * Fix stack bug, introduced in 1.26b8, in display-luns when report-luns fails. * Remove comp-status=6 error message on commnad timeout in execute-command. * Go back to using tar.Z instead of zip format for release files.
Version 1.26b9 03/01/07 * Set timeout field in IOCB prepare-command. Timeouts were disabled! ER50089. * Change qla-mode use-bid? flag back=0. It does not need to match the bootID. * Add QLE2464 max-payload-size in Device Config Reg, offset x54.
Version 1.26b8 02/07/07 * Remove debug? flag set if diag-switch? environment variable is true. * Add Work-around delay in show-children to give FW time before issuing IOCBs.
Version 1.26b7 02/06/07 * Add login-device in show-loop-devices to fix bug with StorEdge 3511 minnow. * Fix display-inquiry stack bug when inquiry command fails. * Fix sense buffer check for illegal request in report-luns method. * Remove LUN0 inquiry command execution in display-luns, when report-luns fails. * Removed "Warning: NVRAM boot-id should be=" when in qla-mode, & loop topology.
Version 1.26b6 02/01/07 * Reduce /lunbuf to x10000 for MACs. This reduces max-luns from 16k to 8k. * Change to use NVRAM boot-id when in qla-mode for fabric topology, use-bid?=-1.
Version 1.26b5 01/25/07 * Fix bug in fp.fth. logout-device was not present. Needed since v1.25b6. * Start using port-down-rc retry-count in spin-up and rw-blocks scsi commands. * Disallow 0 entry for set-link-timeout set-port-down-count & set-login-count. ER51830 and ER51857.
Version 1.26b4 01/17/07 * Change data-rate menu to use 'Gb/sec' instead of 'Gigabit'. ER51678.
Version 1.26b3 01/12/07 * Add LUN list and lun-present? check to qla-mode set-boot-wwn method. ER51224.
Version 1.26b2 01/05/07 * Add Atmel 26DF081A Flash support. * Fix ldfcode to set DevID field in all PCI image headers.
Version 1.26b1 12/21/06 * Add Fcode usage of NVRAM parameters: login-retry-count, link-down-timeout. Currently port-down-retry-count is still not used by the Fcode. * Add words: set-login-count, set-link-timeout. & set-port-down-count for changing these NVRAM parameters. * Add hidden words: show-logincnt, show-linkto. & show-portdcnt for displaying these NVRAM parameters. * Add these new words to the show-settings list and the show-commands list. * Change display of boot-lun and boot-id to be both hex and (decimal).
Version 1.25 12/11/06 * Change version string for the 1.25 offical release.
Version 1.25b7 12/08/06 * Do not use NVRAM boot-id in qla-mode unless use-bid? flag is set, normally=0.
Version 1.25b6 12/08/06 * Fix qla-mode boot-id bug in fabric-wwn-to-handle. Was not using NVRAM boot-id. * Set limits on qla-mode NVRAM boot-id <= 7ff and on boot-lun <= ff. ER50909. * Add logout-device (of target boot-device) in close of scsidisk child.
Version 1.25b5 12/05/06 * Fix stack bug in login-device. This bug was induced in 1.25b2, LS_RJT fix. * Remove GID_PN fail mesage from fabric-wwn-to-handle & display if debug? on. * Change SN# fetch in show-settings to get it from the VPD data, not the WWN. * Add debugging to fcp-targets and fcp-luns. * In qlc-mode, disallow set-boot-wwn, set-boot-id & don't list in show-commands.
Version 1.25b4 12/02/06 * Fix GID_PN (0x121) & GPN_ID (0x112) SNS commnads to handle a null buffer.
Version 1.25b3 12/01/06 * Fix link-down topology=f case bug in device-present?. * Change ext-loopback-test to separate diag-init-chip & lb-ext (external).
Version 1.25b2 11/29/06 Fix login-devices bug on LS_RJT (found by Lyle), logout to preserve phandles.
Version 1.25b1 11/22/06 * Add show-commands. ER50338. * Add decimal display of target & Lun # in show-children.
Version 1.24 11/13/06 * Change version 1.24b3 string to the official release 1.24. * Change max-luns=16K for qlc-mode. Limit LUN field range to 8-bits in qla-mode.
Version 1.24b3 11/13/06 * Fix report-luns buffer & commnad, add 8 bytes for # of LUNs field. ER50220.
Version 1.24b2 11/09/06 * Change max-luns=256 (max # of LUNs per target) to match the driver. Was 1024. * Change execute-command to check status returned by login-device, & fail if bad * Change selftest to use init-chip which waits for fw-ready, instead of a delay.
Version 1.24b1 11/03/06 * Execute external-LB test from selftest only if in FL-port or NL-port topology. * Create command ext-loopback-test. Allows manual execution of External Loopback * Change ldfcode in flash-pgm to allow flashing of 1MB multi-boot images.
Version 1.23 10/18/06 * Change version 1.23b1 string to the official release 1.23.
Version 1.23b1 10/11/06 * Add ~2 sec. delay before executing show-nport-devices in show-children. * Added Level debugging. * Move tools directory up one level, so we don't keep a copy in every version.
Version 1.22 10/02/06 * Change version 1.22b5 string to the official release 1.22.
Version 1.22b5 09/29/06 * Fix isp2400-probe bug on PCIe HBAs. HBA regs were not mapped when load-stub-fw was executed. Also, moved isp2400-probe execution to the end of ifp.fth.
Version 1.22b4 09/19/06 1 Fixed list-wwns word so set-boot-wwn will work for N-port topology . 2 Fix selftest again so connection-mode always = Auto, during the test.
Version 1.22b3 09/15/06 1 Fixed get-id-list word to work for N-port topology on the ISP2400. 1 Increase max-fab-devs to 2048. 3 Change initial value of topology to x0f. (invalid) 4 Add show-settings word to list the HBA's settings. Make version word external. 5 Fix selftest to work independent of NVRAM connection-mode setting.
Version 1.22b2 09/11/06 1 Fixed processing of get-id-for-fc4type GID_FT buffer to check for null buffer. 2 Changed names of prom output files to isp2400.sun.fc and isp2400.ibm.fc.
Version 1.22b1 08/21/06 1 Add FW initialization stub loader at probe time & in close method. This is done only on PCIe HBAs (i.e. Dev-ID not equal to 2422). 2 The Makefile was changed: The tokenizer directory was changed to tools and a local copy of cpp and makearray are kept in tools. Tokenize and fakeboot are no longer used, and .out files are no longer created, only raw .fc files with no header. ldfcode will not work on older fcode, update with init version
Version 1.21 08/01/06 * Change version to non-beta after testing.
Version 1.21b1 07/18/06 * Change info-count from an instance value to simple value. This will limit the version banner to be displayed only once during the boot process.
Version 1.20 06/22/06 * Prohibit connection-mode change if DevID=54xx. Print: Model # will Auto-negotiate.
Version 1.19 06/14/06 * Release. Add support for QLE210, SSDID=x132(Sun) & SSDID=x13E(Qlgc).
Version 1.19b2 06/13/06 1 Prohibit data-rate change if DevID=54xx. Print: Model # will Auto-negotiate. 2 Add get-model-prop word. For printing model # if data-rate change is rejected.
Version 1.19b1 06/09/06 1 The memory size tested in mem-test will now be cut in half on all HBAs with Device ID = 54xx, such as the QLE220. The word reduce-func? was created. 2 Word for reading config space regs, vid@, did@, ssvid@, & ssdid@ were created.
Version 1.18 05/24/06 * Make v1.18b2 release v1.18
Version 1.18b2 05/23/06 1 Fix problem found on Sun T2000 PCIe. pci-compat-str did not handle dev-id=5432 2 Remove class-code-string2 word. It was producing a bad string pciclass,0400.
Version 1.18b1 05/19/06 1 Add support for several HBAs including the Sun QLE220 HBA with SSDID=x14E. 2 Add restriction of qla-mode change on all SUNW type HBAs. 3 Remove extra version string display during selftest. 4 Fix read-block-ext to only use read-capacity command, not try mode-sense first 5 Add display of non-zero FCP/SCSI status during debug mode. 6 Fix initialization of port-update-occurred flag during wait for isp-fw-ready?
Version 1.17 03/31/06 1 Put in Asif's fix for retry?(scsi.fth) to check sense length before IOCB copy. 2 Make my-wwn value external for IBM users. 3 Put in Asif's fix for ibm-decode-unit, to correctly parse out WWN and LUN# in cases where the LUN# may or may not be specified in the path. 4 Fix IBM set-address to correctly set obp-lun-lo and opb-lun-hi.
Version 1.16b11 03/28/06 * Make qla-mode? value in qlc parent & qla-mode? word in fp child node externel. Before fix, would not work if fcode-debug? = false.
Version 1.16b10 03/20/06 1 Fix fcp-luns for FL-PORT. Add 2dup so WWN is on the stack for f-port-fcp-luns 2 Make qla-mode? not instance value so show-devs will work. 3 Change fnv-access-to back (from x10 to x800) 4 Add set-timeout word back (needed for IBM). It was removed in b1.16b1
Version 1.16b9 03/08/06 * Change Firmware load-image to run faster.(very slow on serengeti) change read-code-segment to rd-code-seg. Change dly-val from 50 to 10. Move FLASH-ERR ifpcsr! to get-addr-len. Change fnv-access-to from x1000 to x10
Version 1.16b8 03/07/06 * Serengeti fix child creation. Put all if statements inside colin definitions. * Move scsicom.fth words into scsidisk.fth
Version 1.16b7 03/03/06 * Mod child creation. Use qla-mode? flag, not the property. Remove prop qla-mode * Change Loop init error message to print only if in debug mode.
Version 1.16b6 02/27/06 * Fix encode-unit to encode the lun target integer pair. Used in qla-mode.
Version 1.16b5 02/23/06 * Swap order of boot-wwn-hi & boot-wwn-lo in NVRAM (hi is now first) Always prompt for boot-target-id in set-boot-wwn.
Version 1.16b4 02/09/06 * Remove periods in display-wwn & display-inquiry,LUN. Now show-children looks the same as it use to. * Add 2-bit fcode-host field to fcode-parameter word (wd offset x56) in NVRAM. Value can be 00-SPARC, 01-IBM, or 10-MAC. This will effect the version string. The 01-IBM value should not be used. The IBM version is still a separte binary
Version 1.16b3 02/03/06 * Change Initiator test in login-device also. Test TARG-BIT of Service params. * Change show-login-devices & show-fabric-devices to skip display-luns if display-port-db fails. Check target bit done in get-port-db. Now FL-port works
Version 1.16b2 01/31/06 * Remove all #ifdef MAC instrustions. Make SUN version the SPARC/MAC version * Fix problem found @SUN w/6920, Change Initiator test in get-portname-db.
Version 1.16b1 01/30/06 * Add support for Apple MAC Fcode, using #ifdefs. Make it 32-bit compatable. * Add disk-test (read-write-read-compare) selected target with sel-dev & sel-lun Moved read-block-ext, timed-spin, r/w-blocks from sd node to parent qlc node.
Version 1.15 Beta_2 12/15/05 * Modify beacon word to flash top and bottom LEDs only!
Version 1.15 Beta_1 12/09/05 * Change node name to QLGC,qla for qla-mode on Sun platforms. * Added boot ID NVRAM modification to the set-boot-wwn method.
Version 1.14 11/04/05 * Added support for qla-mode on Sun platforms. Added NVRAM modification words for Fcode parameter byte (fcode-mode) and Boot Port Name/Boot LUN. Including: set-fc-mode, set-boot-wwn, fc-mode@, boot-wwn@, boot-wwn!, and boot-lun@. * Add creation of qla-mode property if the fcode-mode bit is set. * Modify set-address and device-present? to handle #address-cells =2 in qla-mode * Modify set-address & prepare-command to correctly handle 64-bit LUNs. * Cleaned up code. Got rid of unneeded calls to get-id. Made all constants CAPs. * Added login-devices word to login to all fabric devices and return #ports. * Added display-port-db word used by list-wwns and show-children (fabric & loop) * Modified show-fabric-devices to call login-devices and the call get-port-db
Version 1.13 10/28/05 * Asif fixed retry? in scsi.fth to check sense length before copy to IOCB.
Version 1.12 10/10/05 * Fixed issue with multiple initiators on local loop
Version 1.11 (1.10.13) 10/3/05 * Fixed Sun defect CR 6308066 (ER43414) Boot failed from Pyramid targets * Fixed Sun defect CR 6328443 Failed to boot from SE6920/6130 target * Fixed Sun defect CR 6324644 (ER43580) SE6130 LUN information is not shown correctly
Version 1.10.11 09/28/05 * Fixed ER42627: selftest does not perfrom risc-test. * Populate fcp-luns data struct with LUN values in little-endian byte order.
Version 1.10.09 09/26/05 * Fixed ER42883: Getting illegal instruction following a probe-scsi-all. * Fixed ER43041: device name prop creation SUNW or QLGC or fibre-channel. * Fixed ER42627: risc-test causes unknow error. Incuded init-chip before test. * Fixed ER43571: Version property now includes the model string.
Version 1.10 09/13/05 * Included special steps in reset-risc.
Version 1.09 09/12/05 * Released 1.08.06 for test.
Version 1.08.06 09/09/05 * Fixed Sun defect 6309765 - (ER43064 same issue) Adapter information not printed the second time probe-scsi-all is typed. * Fixed Sun defect 6308468 - boot message is not generic. * Fixed Sun defect 6308071 - probe-scsi-all prints incorrect message if no cable connects to a port. * Fixed ER43133 - Displays Error: Unable to get Adapter ID when executing probe-scsi-all. * Fixed ER43135 - The header info indicate ISP2422 instead of ISP2432. * Fixed ER42880 - Mailbox or IOCB interrupt timeout occurred. * Fixed ER42883 - get-portname-db failed. * fcp-targets and show-children would cause login into initiators, and then subsequent scsi cmds to logged-in initiators would fail/timeout. Checked for device type (target/initiator) in PRLI parameters field in response iocb in words get-port-db and login-device, (performed a logout in the case of login-device word (which is fabric topology case)) and returned failure to ensure that no scsi cmds would be issued to initiator devices. * Device name property string dependent on ISP24xx subsystem-device-id for SPARC platform. * Model property dependent on ISP24xx device-id. * Compatible property string prefixed with "pci" (ISP2422) or "pciex" (ISP2432).
Version 1.08.05 07/29/05 * Fix bug in version-prop method for the IBM version (needed a swap).
Version 1.08.04 07/27/05 * Change version-prop method to concatinate long-string & short-verion string Now the date and version number are contained in one single place! * Make the beacon word external. * Add get-id to init-chip to set the topology. Take get-id out of open. * Reorganize the order of methods in ifp.fth * Fix get-sense (retry?) to use the sense data in completion IOCB, if available. * Modify report-luns to accept an "Illegal Request" unit check response. * Move all SCSI related commnads to hacom.fth and rename it "scsi.fth". *
Version 1.08.03 07/12/05 * Change version property string, Add date to the end. * Put LED test "beacon" word back in. It was removed in Version 1.08b6. * Fix login-device call in f-port-fcp-luns method (fcp-luns.fth). * Comment-out call to logout-device in f-port-fcp-luns. (need to stay logged in) * Add release-history.txt file to release package. * Include tokenizer directory in release package, change makefile to use it.
Version 1.08.02 07/05/05 * Fix show-children hang bug when no devices attached, re-wrote show-fabric-devices method. * Create common get-id method to get adapter's ID & portid, new value my-portid. * Add 8048 Async error retry return code (x99) to the do-cur-iocb method. * Create common method, process-async, called by do-cur-iocb and get-mail. * Implement logout-device and logout-devices. (Was a no-op) * Change login-device to return completion-status, clean-up process-login-err. * Changed mailbox command names from isp- to mbc-. * Shortened some messages and made them common. Shortened some value names.
Version 1.08.01 06/28/05 * Change the version string only, for release to Sun.
Version 1.08b7 06/28/05 * Add Serial-Transmit-Parameter mailbox command, set-isp-stp, to init-image. * Add set-slc method to set the Serial-Link-Control parameters in NVRAM. This allows the operator to change the output swing and output pre-emphasis for 1Gb, 2Gb & 4Gb. * Change FCode checksum to use checksum in FCode Header, we will not use our own checksum byte at offset 0xfffc in Flash. The check-fcode method, which is part of selftest, now works on a combined BIOS/FCode/EFI Flash Image. * Add check for "ISP " signature in NVRAM method, nvr-bad?, which is called before setting connection-mode, data-rate and bios-compatibility-mode. If the NVRAM is bad, default values will be used instead. * Fix NVRAM checksum to be the same as Flasutil. (sum words not bytes to = zero) * Added show-bootid & show-model methods to show the corresponding NVRAM values. * Clean up load-image method. * Got rid of set-adapter-loopid. No reference in NVRAM docs, and never used. * Got rid of starting-id stuff. * Changed makefile to not use fiximage or fill128 utility. Use dd cmd instead!
Version 1.08b6 06/20/05 * Shorten version property for luxadm problem. * Add selftest, including: check-nvram, check-fcode, mem-test, risc-test (isp online selftest) and diag-lb (internal, 10-bit, 1-bit, & external loopback) * Fix image size to pad image to 512 byte boundary, and update PCI header value. * Added map-dma to combined dma-alloc and dma-map-in methods. And add unmap-dma to combined dma-free and dma-map-out methods. * Added init-chip method to initialize & re-load FW, equivalent to re-selecting. * Add fiximage.c utility to calculated FCode checksum for Flash images.
Version 1.08b5 05/26/05 * Fix set-fc-address for IBM. Now "Select Boot/Install device" works! * Fix no-data command during IOCB build in prepare-command method. * Added sav-fc method to save a copy of the FCode to RAM at location x4030. * Moved FCode programming methods to a separate file, flash-pgm.fth.
Version 1.08b4 05/23/05 * Fix report-luns method problem when 0 LUNs is returned. * Add SST25LF080A flash support. Add getpid method to check PROM ID.
Version 1.08b3 05/20/05 (First delivery to Qlogic) * Fix BIOS compatible NVRAM parameter bit bug in set-mode method. * The show-children method is now working for loop (nl) and fabric topology, but n-port (point-to-point) is still not supported!
Version 1.08b2 05/19/05 * Change model = QLGC24xx, name = SUNW,qlc. * Add Asif's multiple IOCB interrupt fix. Using rsq-iocb-valid? method.
Version 1.08b1 05/18/05 * Got manual booting on IBM working! Many changes to fcp-luns & fcp-targets. * Fixed SUN/IBM version banner bug. * Modified verbiage in NVRAM mod? word.
Version 1.08x 05/16/05 * Fixed Endian problem w/phandle, now booting in loop topology on the Sun. * Added fcp-targets and fcp-luns methods for IBM platform compatibility.
Version 1.07 05/13/05 * Initial release with booting fabric device working on Sun. * Add ldfcode utility to program FCode at the OK prompt. * Fixed all of the NVRAM parameter set methods. * Combined various pieces of FCode from 2312 & 24xx code bases. qlgc_fw_fc_4g-mb1_90-3-sysx_linux_32-64_chg
Dynamic System Analysis (DSA) Preboot Change History
Version 9.31, Build ID DSYTAC2 o New System Support: o New Operating System support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: Refer to readme o Functional change: o Dependencies: o Special usage: - NGP-4Q(12B+ FixPack3) - IMMV2 system 2012 4Q-LFC
Version 9.27, Build ID DSYTA7I o New System Support: o New Operating System support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: Refer to readme o Functional change: o Dependencies: o Special usage: - IMMv1 system 2012 4Q-LFC
Version 9.26, Build ID DSYTA6G o New System Support: o New Operating System support: o New server options support: o Problem(s) Fixed: o Enhancement: DSA Performance Optimization o Limitations: Refer to readme o Functional change: o Dependencies: o Special usage: - 2012 ToolsCenter 12C
Version 9.21, Build ID DSYTA1U o New System Support: o New Operating System support: o New server options support: o Problem(s) Fixed: 1.Recovered LSI Rawdata: "MegaCli -FwTermLog -Dsply -aALL" o Enhancement: o Limitations: Refer to readme o Functional change: o Dependencies: o Special usage: - 2012 ToolsCenter 12B Plus
Version 9.20, Build ID DSYTA0R o New System Support: x3530 M4 (7160) x3630 M4 (7158) x3750 M4 (8722, 8733) HS23E (8038, 8039) Flex System x220 Compute Node (7906, 2585) o New Operating System support: vSphere Hypervisor 5.0u1 with IBM customization o New server options support: o Problem(s) Fixed: 1. PMR 05819,YL2,760 An error occured during the execution of DSA on Windows, DSA exits with an error at the eventlog plugin.
o Enhancement: o Limitations: Refer to readme o Functional change: 1. Add HW remote presence key collection for High volume systems. o Dependencies: o Special usage: - 2012 ToolsCenter 12B
Version 9.07, Build ID DSYT9CA o New System Support: x3750 M4 (8722, 8733) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 9.06, Build ID DSYT9BC o New System Support: Flex System x220 Compute Node (7906) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 9.05, Build ID DSYT9AA o New System Support: x3630 M4 (7158) x3530 M4 (7160) x3100 M4 Refresh1 (2582) x3250 M4 Refresh1 (2583) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 9.04, Build ID DSYT99E o New System Support: Flex System x240 Compute Node (8737, 8738, 7863) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies:
Version 9.03, Build ID DSYT98I o New System Support: HS23E (8038, 8039) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies:
Version 9.02, Build ID DSYT97C o New System Support: iDataPlex dx360 M4 server/2U chassis (7912/7913) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Functional change:
Version 9.01, Build ID DSYT96D o New System Support: x3500 M4 (7383) x3550 M4 (7914) x3650 M4 (7915) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage: o Special usage:
Version 9.00, Build ID DSYT95W o New System Support: BladeCenter HS23 (7875) BladeCenter HX5 (7873, 1910) Flex System x240 Compute Node (8737, 8738, 7863) Flex System Manager Node (8735) x3500 M4 (7383) x3550 M4 (7914) x3630 M4 (7158) x3650 M4 (7915) x3690 X5 (7192, 7147) x3850 X5 / x3950 X5 (7143, 7191) o New server options support: o Problem(s) Fixed: 1. PMR 24817,8QG,000, PMR 30680,499,000 After kicking off DSA on one of the management nodes (x3650 M2) of SONAS 1.2(RHEL5 based), the node became unresponsive and dropped out of the cluster.
2. PMR 53575,000,834, PMR 05961,YL4,760 After running DSA, when using linux dump command on a DDS5 usb internal tape drive attached in x3650M2 backup speed becomes very slowly or failed.
3. PMR 26905,095,866 Running DSA 4.0 as well as DSA 3.4 on x3850 X5 the server is freezing, users have to reboot the server.
4. DSA 4.00 and previous version segmentation fault issue
6. PMR 15086,OTH,760 DSA 9.00 with --no-imm-lan option does not work correctly on RHEL5.3. The USB port state is changed during the execution of DSA.
o Enhancement: o Limitations: o Dependencies: o Functional change: 1. Add GUI and CLI menu for Features on Demand (FoD) Activation Key Management o Special usage:
Version 4.02, Build ID DSYT92I o New System Support: iDataPlex Direct Water Cooled dx360 M4 server o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 4.01, Build ID DSYT92H o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage: - 2011 4Q lifecycle
Version 4.00, Build ID DSYT91S o New System Support: o New server options support: o Problem(s) Fixed: 1. PMR 15065,OTR,760 On Unisys ES7000 or x3850 X5, the Memory Card number with failed DIMM can not be reported in IPMI Eventlog if the Memory Card is bigger than 4.
o Enhancement: o Limitations: o Dependencies: o Functional change: 1. Added > 1TB memory test support o Special usage: - 2011 ToolsCenter 11D
Version 3.48, Build ID DSYT89PUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage: - 2011 3Q lifecycle
Version 3.47, Build ID DSYT89LUS o New System Support: x3100 M4 (2582) x3250 M4 (2583) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 3.46, Build ID DSYT89GUS o New System Support: System x iDataPlex dx360 M3 (6391) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 3.45, Build ID DSYT89EUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage: - x3850 X5 / x3950 X5 (7143, 7191) EXA scaling
Version 3.43, Build ID DSYT87HUS o New System Support: BladeCenter HX5 (7873,1910) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 3.43, Build ID DSYT87FUS o New System Support: x3850 X5 / x3950 X5 (7143, 7191) x3690 X5 (7192, 7147) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 3.40, Build ID DSYT85T o New System Support: BladeCenter HS22 (1911) x3650 M3 (5454) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Version 3.30, Build ID DSYT80S o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: 1. Correct a problem with LSI MegaRAID reporting for IBM Service o Special usage:
Version 3.20, Build ID DSYT75X o New System Support: x3630 M3 (7377) x3690 X5 (7148, 7149) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: - If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831 installed, you will need one of the following: - uEFI GYE133A or greater for x3200 M3 and x3250 M3 - uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3 - uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3 o Functional change: 1. Add LSI Hard Disk Drive (HDD) diagnostic back for both the onboard SAS chip and ServeRAID o Special usage:
Verion 3.20, Build ID DSYT75U o New System Support: x3755 M3 (7164) o New server options support: o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: o Special usage:
Verion 3.10, Build ID DSYT70X o New System Support: x3400 M3(7378, 7379) x3500 M3(7380) x3550 M3 (7944, 4254) x3620 M3 (7376) x3650 M3 (7945, 4255) x3690 X5 (7148, 7149) x3850 X5 Standard Single-node and Multi-node models(7145, 7146) x3950 X5 Specially configured Database Engine models (7145, 7146) iDataplex dx360 M3 (6391) HS22V (7871,1949) HX5 (7872, 1909) o New server options support: Emulex 10Gb/s Fibre Channel over Ethernet Dual Channel Converged Network Adapter(LP21002) Emulex PCI-e Gen2.0 Dual Port 10Gb NIC (49Y4250) 6Gb SSD HBA (46M0912) 6Gb SAS HBA (46M0907) Intel QuadPort Ethernet Server Adapter CFFh Intel Ethernet Daughter Card FCoE SRIOV Key (Ethernet) iSCSI Key (Ethernet) Secure Encryption HBA for 8Gb FC eHBA Emulex Brocade 4Gb FC HBA(59Y1992, 59Y1998) Emulex 2-Port 10Gb Multi-function IO Adapter (CFFh) (49Y4235) Brocade 10Gb Dual-port CNA (42C1820) Broadcom NetXtreme II 1000 Express Quad port Ethernet Adapter (49Y4220) Broadcom NetXtreme II 1000 Express Dual Port Ethernet Adapter (42C1780) MAX5 Memory Expansion Unit o Problem(s) Fixed: o Enhancement: o Limitations: o Dependencies: o Functional change: 1. Add a new option --disable-imm-lan to take down IMM USB Over Lan interface when DSA complete. 2. Added ServeRAID data collection o Limitations: - The following function has been temporarily removed from DSA Preboot for both the onboard SAS chip and ServeRAID: - LSI Hard Disk Drive (HDD) diagnostic o Dependencies: - If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831 installed, you will need one of the following: - uEFI GYE133A or greater for x3200 M3 and x3250 M3 - uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3 - uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3 o Special usage:
Version 3.02.56, Build ID DSYT56e o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - The following systems are supported when BoMC downloads the corresponding system enablement pack: HS22V (7871,1949) x3550 M3 (7944,4254) x3650 M3 (7945,4255) x3400 M3 (7378,7379) x3500 M3 (7839) dx360 M3 (6391) o Limitations: - No HDD diagnostics available - To ensure quality and stability of the DSA code, we have reverted some display functionality of RAID information to what was shown in previous versions of DSA. This affects RAID display on the following adapters: Megaraid 8480 Serveraid MR10i Serveraid MR10is Serveraid MR10m Serveraid MR10k Serveraid M1015 Serveraid M5014 Serveraid M5015 On these adapters, the RAID information is generated from the output of separate command line tools and the format may not match other output in DSA. Dependencies: o Dependencies: o Functional change: o Special usage:
Version 3.00, Build ID: DSYT55a o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - Added support for Machine Types 7327, 7328, 4251, 4252, 4261 o Limitations: - No HDD diagnostics available o Dependencies: o Functional change: o Special usage:
Version 1.16, Y4YT19AUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - Added support for Machine Types 7839, 7836, 7837 o Limitations: o Dependencies: o Functional change: o Special usage:
Version 1.15, TMYT20AUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - Added support for Machine Types 7321, 6380, 7323 o Limitations: o Dependencies: o Functional change: o Special usage:
Version 1.14, D6YT37AUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - Added support for Machine Types 7946, 4198, 7947, 4199 o Limitations: o Dependencies: o Functional change: o Special usage:
Version 1.13, P9YT48AUS o New System Support: o New server options support: o Problem(s) Fixed: o Enhancement: - Added support for Machine Types 7870, 1936, 7809 o Limitations: o Dependencies: o Functional change: o Special usage:
Version 1.00 - Initial release
(C) Copyright International Business Machines Corporation 2008 - 2012. All rights reserved. ibm_fw_dsa_dsytac2-9_31_anyos_anycpu_chg
=============================================================================== Emulex NIC Device Driver for Linux ===============================================================================
Linux NIC Device Driver Version: 4.2.389.0
Problems Fixed: - Unloading the driver hangs the system after running IPv6 traffic - Link status messages cleaned up when in Switch Agnostic mode - Miscellaneous network performance issues to improve throughput - Miscellaneous problems related to SRIOV to improve usability - Ethtool wol command displays wol enabled even when disabled - Ethtool speed reported as 10000Mb/s for disabled devices in Switch Agnostic mode
Incremental Interoperability: - RHEL6.3 GA Kernel - Increase default B/W for SRIOV vf's to 10Gb from 100Mb
Known Issues: - SR-IOV configuration section of the Linux NIC Driver Documentation will be modified as follows to improve clarity (noted by << >>):
11. Use the Virtual Machine Manager GUI to attach the VF (step 7 on page 34) to the guest operating system by using the add physical device option.
<< Note 1: If user wants to re-configure an already configured setup, it can be done by removing the attached VF from the respective guest operating system using the remove option after selecting the VF attached. And then attaching another VF (step 11).
Note 2: Consult the documentation for your host operating system for help using the Virtual Machine Manager to attach and detach virtual interfaces. >>
12. Start the RHEL 6.x guest operating system. Once the guest operating system is booted, use the lspci command to confirm the visibility of the OneConnect NIC function. The output shows a OneConnect NIC function, for example: 03:00.0 Ethernet controller: Emulex Corp. Emulex OneConnect 10Gb NIC (be3)
13. The OneConnect Ethernet driver automatically loads with the inbox driver, and creates the network interfaces. Use the ifconfig command to verify that the interface is created.
14. After configuring the network interfaces with proper IP addresses, you can send and receive network traffic from the VM. << (Consult the documentation for your host and guest operating systems for network configuration help). >>
- WOL changes for Linux NIC driver as mentioned in Bug# 24543 - SR IOV UE when attempt to do multiple (3 times) driver load/unload - Speed is 10000Mb/s for Disabled devices in UMC Mode - Incorrect Duplex value is shown for unconnected port of NC552m in Rhel6.1 32bit - SLES 11 SP2 GMC: Enable support for Lnx NIC Driver - SRIOV: When VGT is configured for a VF, ip link show doesn't display it for the VF configured. - RHEL 5.8 GA: Enable support for Lnx NIC Driver - ip link command with vlan = 4095 has toggling effect - ip link command with vlan =0 should remove guest VGT privilege
- SR-IOV: Can't load be2net driver in a VM after the VM has been rebooted - SR-IOV: Unload PF driver with VF driver loaded causes system instability - SR-IOV: VF MAC always gets Emulex OUI - SR-IOV: Partition the limited per port VLAN entries across VFs and PFs - Non Member VLAN packets not received in interface promiscuous mode in BE3 - Avoid CQ full condition in HW - be2net: use RX_FILTER cmd to program multicast addresses - account for skb allocation failures in ethtool stats - Support 60 second delay to Linux NIC driver to allow FAT dump completion on recovery from EEH - Link status is up [ethtool and OCM] when the bandwidth is assign 0 for UMC configuration - Remove msix module parameter - Use V1 version of COMMON_NTWK_LINK_STATUS_QUERY for Lancer. - Emulex: Ethtool failing to update FW - Emulex: Panic in be2net driver in SLES11-SP2-B7 on adapter - TCP ACKs from different connections are getting received in single queue - Multicast filtering feature not working on PPC - Exit of mcast promiscous mode not working - VLAN promiscous mode cannot be set on Lancer - Can't communicate after changing MAC address via VLAN interface - Improper memory accounting in received packets - WOL changes for Linux NIC driver as mentioned in bug - Transparent VLAN tagging feature not working in SR-IOV elx_dd_nic_ibm1206-4_2_389_0_sles10_32-64_chg
=============================================== Change History =============================================== Document Name: Change History Document Status: IBM General Avalibility Document Version: 3.1 Latest Driver Version: 3.1.0.0 Document Updated: 7/16/2012 Product: Brocade FC HBA / FCoE CNA
=================================================
Please visit www.brocade.com/hba for full documentation, additional drivers, and management applications.
Version 3.1.0.0 Fixes and Enhancements: - Added support for new kernels. - Added support for IBM FLEX System FC5022 2-port 16Gb FC Adapter
Version 3.0.0.0 Fixes and Enhancements: - Added support for Brocade 1860 AnyIO Fabric Adapter (User configurable port mode - FC or NIC or CNA) - Added Fibre Channel 16G Support - Enabled Fabric Assigned Address in Fibre Channel Fabric - Added PF based Virtualization – vHBA - Enhanced CLI, HCM GUI and CIM support in inbox drivers. - Added PF based Virtualization - vNIC - Added iSCSI over DCB Support - Added Multiple Tx Priority Queues Support - Added SNMP Support
Version 2.3.0.3 Fixes and Enhancements: - Enhanced SNIA API to report port speed of 4 and 8Gbps in SNIA format. - Enhanced XIV array interoperability that addresses a data integrity corner case. - Enhanced the transmit path handling in Linux Network Driver to avoid a corner case that could lead to transmit path stall. - Enhanced the Linux Adapter Software installer script to update the initrd with the correct name even when there are multiple copies of the OEM specific initrd(s).
Version 2.3.0.0 Enhancements: - Enabled HP DL120 server to support Boot over SAN with two Brocade HBAs installed. - Improved network driver CPU and performance optimization. - Enabled automated target and LUN discovery of enterprise HDS storage once LUN masking has occurred. - Improved Tivoli interoperability to meet device display requirements.
Version 2.2.0.1 Added capability to handle ADISC frames. Unhandled ADISC use can cause SAN boot failure when booting from IBM storage array.
Version 2.2.0.0 Adds support for bootcode updates to Bladecenter 10G Converged Network Adapters
Version 2.1.0.0 Adds support for bootcode updates to 10G Converged Network Adapters
Version 2.0.0.0 Initial release for 4/8G FC HBAs brcd_dd_nic_bna-3_1_0_0_sles10_32-64_chg
=============================================================================== Emulex 16GB FC Firmware Package ===============================================================================
Firmware Version: 1.1.21.0
Incremental Interoperability:
Problems Fixed: - 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
=============================================================================== Emulex iSCSI Device Driver for Linux ===============================================================================
Linux iSCSI Device Driver Version: 4.2.398.0
Problems Fixed: - Cleaned up a cosmetic problem with warning messages during driver compile from source
- LUN is not getting detected for OEM CNA in SLES 11 SP2 64 bit OS - ioctl semaphore deadlock when running load/unload loop with target - SLES 11 SP2 GMC: Enable support for Lnx iSCSI Driver - RHEL 5.8 GA: Enable support for Lnx iSCSI Driver
- Emulex: Warning messages seen while building Emulex drivers on RHEL platform - Unable to load be2iscsi driver during iSCSI boot OS install - Modprobe be2iscsi hangs when system with max targets login - be2iscsi unload hangs the system - fw rebooted on 1st mbox cmd after driver load > unload > load - Failed to initialize iscsi driver - need to define DMA_32BIT_MASK / DMA_64BIT_MASK in Linux kernel 3.x.x elx_dd_iscsi_ibm1206-4_2_398_0_sles10_32-64_chg
IBM Online SAS/SATA Hard Disk Drive Update Program
- ST3300657SS, ST3450857SS, ST3600057SS to BA5A VPCA300900EST1, VPCA600900EST1 to A3C2 Additions to VPD information used by manufacturing
- ST3750630SS, ST31000640SS to BC1I ST31000424SS, ST32000444SS to BC2C Mode Page change to address performance issues under certain system configurations
- ST33000650SS to BC3D ST1000NM0001, ST2000NM0001 to BC48 Protection Information Fix - see Retain Tip H206140
- HUS723020ALS64, HUS723030ALS64 to J26C Initial Code Release
SAS 2.5"
- ST9300603SS, ST9146803SS to B53E ST9600204SS to B549 Additions to VPD information used by manufacturing
- ST9300605SS, ST9600205SS, ST9900805SS to B55C ST9146853SS, ST9300653SS to B63A ST9500620SS, ST91000640SS to BD2C ST9300505SS to E555 ST9146753SS to E635 Protection Information Fix - see Retain Tip H206140
- ST9600105SS, ST9900705SS to E555 Inital Code Release
- HUC106030CSS60, HUC106060CSS60 to D3A6 Performance improvements, critical fixes for Protection Information (PI) operation - see Retain Tip H206140
- MK1401GRRB, MK3001GRRB to SC27 Additions to VPD information used by manufacturing
- WD9001BKHG-23D, WD6001BKHG-23D, WD3001BKHG-23D to ZA31 Initial Code Release
SATA 3.5"
- WD2502ABYS-23B7A0 to 02.03B08 WD1602ABYS-23B7A0 to 02.03B07 Critical fix to address premature drive failures.
- ST3500514NS, ST31000524NS, ST32000644NS to BB2A ST33000650NS to BB38 ST1000NM0011, ST2000NM0011, ST500NM0011 to BB47 Fixes a potential, but rare data corruption issue which requires a background reallocation that exceeds the error recovery timer.
- HUA723020ALA640 to MK70A900 HUA723030ALA640 to MKA0A900 Initial Code Release
SATA 2.5"
- ST9160511NS, ST9500530NS to BE1A ST9250610NS, ST9500620NS, ST91000640NS to BE25 Fixes a potential, but rare data corruption issue which requires a background reallocation that exceeds the error recovery timer.
SSD
- TX21B10200GE1IBM, TX21B10400GE1IBM, TX21B10100GE8IBM to PRO6SP36 TE22D10100GE8IBM to PRO6SR36 Initial Code Release
- MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA to MA52 Initial Code Release
- MTFDDAA512MAR-1K1AB, MTFDDAK064MAR-1J1AA, MTFDDAK512MAR-1K1AA, MTFDDAA064MAR-1K1AB, MTFDDAA128MAR-1K1AB, MTFDDAA256MAR-1K1AB to MA52 Fixes SMART attribute 190 (Current Temp) which caused warning messages with some versions of Linux
- STEC MACH8 IOPS to 2804 STEC M8PSB2 T4 to SM06 Additions to VPD information used by manufacturing Fixes potential drive failure if power loss occurs during firmware update.
*******************************************
Version 1.11.01 (Non-Critical) - Fixed issue where hard disk drives may not be detected in configurations with multiple Emulex adapters.
See Verion 1.11 for Hard Disk Drive support, firmware levels, and respective change History.
- ST33000650SS to BC3A ST1000NM0001, ST2000NM0001 to BC44 Additions and corrections to VPD information used by manufacturing
SAS 2.5"
- ST9300605SS, ST9600205SS, ST9900805SS to B559 ST9146853SS, ST9300653SS to B637 ST9500620SS, ST91000640SS to BD29 ST9300505SS to E553 SST9146753SS to E633 HUC106030CSS60, HUC106060CSS60 to D390 Additions and corrections to VPD information used by manufacturing
- MK1401GRRB, MK3001GRRB to SC23 Fixes a pottential data corruption bug if there is an unexpected power loss.
SATA 3.5"
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB15 ST3500514NS, ST31000524NS, ST32000644NS to BB29 ST33000650NS to BB36 ST1000NM0011, ST2000NM0011, ST500NM0011 to BB46
SATA SSD
- SG9XCS1B50GMIBM, SG9XCS1F200GEIBM to SA03SB6C SG9XCS2D200GEIBM to SA03SE6C Fix for potential hang during an unexpected power cycle
MTFDDAK128MAR-1JAAB, MTFDDAK256MAR-1JAAB to MA44 Initial Release
=========================================== Version 1.10 (Critical)
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA600900EST1 to A3C0 Correction to VPD information used by manufacturing
- ST31000424SS, ST32000444SS to BC2B Fixes to improve robustness from certain read errors due to encroachment
- ST33000650SS to BC37 Fixes to improve overall robustness.
- ST1000NM0001, ST2000NM0001 to BC42 Inital Release
SAS 2.5" (SFF)
- ST9300605SS, ST9600205SS, ST9900805SS to B556 - ST9146853SS, ST9300653SS to B635 Fixes to improve overall robustness.
ST9300505SS to E552 ST9146753SS to E632 Initial Release
- ST9500620SS, ST91000640SS to BD26 Improve general robustness and added support for DPICZ
- HUC106030CSS60, HUC106060CSS60 to D340 Improve general robustness
- MBF2300RC, MBF2600RC to SB28 Improves performance in certain benchmarks
SATA 3.5"
- ST33000650NS to BB34 Fixes to improve overall robustness.
- ST1000NM0011, ST2000NM0011, ST500NM0011 to BB45 Initial Release
- ST3500514NS, ST31000524NS, ST32000644NS to BB29 Fixes for intermittent drive hangs
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB15 Added enhancement for improved robustness
SATA 2.5"
- ST9250610NS, ST9500620NS, ST91000640NS to BE24 Initial Release
- ST9160511NS, ST9500530NS to BE19 Fixes for overall robustness.
SATA 2.5" SSD
- STEC MACH8 IOPS to 2765 STEC M8PSB2 T4 to SM05 Fixes potential drive lock up during cold or warm boots Fixes issues with RHEL 6.x installation
- SG9XCS2D200GEIBM to SA03SE6C Fixes default drive VPD information for manufacturing, the default LED behavior on certain systems and fixes issues with client install thru VMWare 5.x
SATA 1.8" SSD
- STEC M8PSB1 to 0409 STEC M8PSB1 T4 to SM16 Fixes potential drive lock up during cold or warm boots Fixes issues with RHEL 6.x installation
- SG9XCS1B50GMIBM to SA03SB6C SASG9XCS1F200GEIBM to SA03SB6C Fixes potential drive lock up during cold or warm boots and the default LED behavior on certain systems and fixes issues with client install thru VMWare 5.x
=========================================== Version 1.09 (Critical)
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- ST31000424SS, ST32000444SS to BC28 Added enhancement for improved RV robustness
- MBE2073RC, MBE2147RC to SC17 - MBA3073RC, MBA3147RC, MBA3300RC to SA0A Added VPD changes for manufacturing
SAS 2.5" (SFF)
- ST9300603SS, ST9146803SS to B53C ST9600204SS to B548 SST973452SS, ST9146852SS to B62C CBRCA146C3ETS0, CBRCA300C3ETS0 to C610 Added fixes for overall drive robustness
- MBD2147RC, MBD2300RC to SB1A Added VPD changes for manufacturing Addresses issues seen with DSA HDD Diagnostic test.
- MBF2300RC, MBF2600RC to SB25 Addresses issues seen with DSA HDD Diagnostic test.
- ST9500620SS, ST91000640SS to BD22 HUC106030CSS60, HUC106060CSS60 to D2F8 Inital Release
SATA 3.5"
- WD2502ABYS-23B7A0 , WD1602ABYS-23B7A0 to 02.03B07 Addresses firmware issues that may cause a drive to be marked defunct prematurely under certain application workloads.
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB14 ST3500514NS, ST31000524NS, ST32000644NS to BB28 Added enhancement for improved robustness
- WD5003ABYX-23 to WC31 Initial Release
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V10 (Critical) Addresses firmware issues that may cause a drive to be marked defunct prematurely under certain application workloads.
- ST9250610NS, ST9500620NS, ST91000640NS to BE21 Initial Release
SATA 2.5" SSD
- STEC MAC8 IOPS to 2732 STEC M8PSB2 T4 to SM04 Addresses an issue installing RHEL 6.0 onto this drive.
SATA 1.8" SSD
- SG9XCS1B50GMIBM, SG9XCS1F200GEIBM to SA03SB63 Addresses rare issue where the drive may not being seen on power up.
- STEC M8PSB1 to 0408 STEC M8PSB1 T4 to SM15 Addresses an issue installing RHEL 6.0 onto this drive.
- ST373455SS, ST3146855SS, ST3300655SS to BA2D - ST373355SS, ST3146755SS, ST3300555SS to BA38 - ST3146356SS, ST3300656SS, ST3450856SS to BA4C - ST3300657SS, ST3450757SS, ST3600057SS to BA58 - ST3750630SS, ST31000640SS to BC1G - ST31000424SS, ST32000444SS to BC26 (All Above Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- MBA3073RC, MBA3147RC, MBA3300RC to SA08 This code corrects a firmware bug that may cause the drive to not come ready on a cold boot.
SAS 2.5" (SFF)
- ST973402SS, ST9146802SS to B52B - ST936751SS, ST973451SS to B617 - ST9600204SS to B546 - ST973452SS, ST9146852SS to B629 - ST9300503SS to E536 - ST9146752SS to E625 - ST9500430SS to BD14 (All Above Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
SATA 3.5"
- ST3500514NS, ST31000524NS, ST32000644NS to BB26
- WD2003FYYS-23W0B0 to WA32 - WDC WD1003FBYX-23Y7B0 to WB31 Initial release
SATA 2.5" SSD
- STEC MACH8 IOPS to 2582 (Critical) Corrects firmware bug that may cause data corruption. For further information, please refer to retain tip H197650.
SATA 1.8" SSD
- STEC M8PSB1 to 0405 (Critical) Corrects firmware bug that may cause data corruption. For further information, please refer to retain tip H197650.
This package includes new updates to drives with product ID strings of:
SAS 3.5"
- VPCA300900EST1, VPCA450900EST, VPCA600900EST1 to A3B8 Initial Release
- VPBPA300C3EST1 to A529 Initial Release
- ST3300657SS, ST3450757SS, ST3600057SS to BA56 (Critical) Performance improvements under certain workloads. Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST31000424SS, ST32000444SS to BC21 Initial Release
SAS 2.5" (SFF)
- ST9300603SS, ST9146803SS to B53A (Critical) Performance improvements under certain workloads. Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST9600204SS to B544 (Critical) Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST973452SS, ST9146852SS to B626 Performance improvements under certain workloads.
- ST9500430SS to BD13 Performance improvements under certain workloads
- ST9300503SS to E534 and ST9146752SS to E623 Performance improvements under certain workloads.
- MBD2147RC, MBD2300RC to SB19 (Critical) Retain Tip H196899 MBE2073RC, MBE2147RC to SC16 (Critical) Retain Tip H196899 Corrects a firmware bug that erroneously reported medium errors which may cause the drive to report PFA alerts and in some cases be marked offline
SATA 3.5"
- WDC WD2502ABYS-23B7A0, WD2502ABYS-23B7A0, WD802ABYS-23B7A0, WD1602ABYS-23B7A0 to 02.03B05 (Critical) Corrects a firmware bug that may cause the drive to not come ready on a warm or cold reboot.
- ST3500514NS, ST31000524NS, ST32000544NS to BB26 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB13 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382.
- HUA722020ALA330 to JKAOA3GA HUA722050CLA330 to JP2OA3GB HUA722010CLA330 to JP4OA3GB Initial Release
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V09 (Critical) This code corrects an additional issue where the drive may be marked defunct.
- ST9160511NS, ST9500530NS to BE18 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. For further information, please refer to retain tip H197382. Also improves performance under certain workloads.
SATA 2.5" SSD
- STEC MACH8 IOPS to 2366 (critical) Corrects firmware bug that may cause degraded performance and in some cases the drive may not come ready after a warm or old boot.
SATA 1.8" SSD
- STEC M8PSB1 to 0404 Turns the default for write cache off
*******************************************
Version 1.06 (Critical)
Added support for the following controllers:
- IBM ServeRAID BR10il SAS controller v2 (49Y4731) - IBM ServeRAID M1015 SAS controller (46M0831) - IBM ServeRAID M5015 SAS controller (46M0829) - IBM ServeRAID M5014 SAS controller (46M0916)
The following is a list of drives and the firmware that they will be checked for and updated to as necessary.
This package includes new updates to drives with product ID strings of:
SAS 3.5" --------------
- ST373455SS, ST3146855SS, ST3300655SS to BA2A ST373355SS, ST3146755SS, ST3300555SS to BA36 (Critical) This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632.
- ST3750630SS, ST31000640SS to BC1E ST3146356SS, ST3300656SS, ST3450856SS to BA4A This code address an issue where the drive may report an erroneous hardware error to the controller.
- MBA3073RC, MBA3147RC, MBA3300RC to SA07 This code improves sequential write performance under certain workloads when write cache is turned on.
- ST3300657SS, ST3450757SS, ST3600057SS to BA52 NOTE: This is the first code release to be included in the hard drive update package.
SAS 2.5" (SFF)
- ST973402SS, ST9146802SS to B52A ST936751SS, ST973451SS to B616 (Critical) These codes addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632.
- MBB2073RC, MBB2147RC to SB07 MBD2147RC, MBD2300RC to SB17 MBE2073RC, MBE2147RC to SC14 CBRCA146C3ETS0, CBRCA300C3ETS0 to C370 This code improves sequential write performance under certain workloads when write cache is turned on.
- ST9500430SS to BD11 This is the first code release to be included in the hard drive update package.
SATA 3.5"
- WD2003FYYS-23T8B0 to 01.00D04 This is the first code releases to be included in the hard drive update package.
SATA 2.5"
- WD3000BLFS-23YBU0 to 04.04V08 (Critical) This code corrects an issue where the drive may generate a false PFA alert. It also corrects an issue where the drive may be marked defunct
- ST9160511NS, ST9500530NS to BE16 This is the first code releases to be included in the hard drive update package.
*******************************************
Version 1.05
The following is a list of drives and the firmware that they will be checked for and updated to as necessary.
This package includes new updates to drives with product ID strings of:
SAS 2.5" (SFF) -------------- ST9xxxx51SS to B616 ST9xxxx02SS to B52A - This code improves the robustness of write cache operations.
ST9xxxx52SS to B624 ST9xxxx03SS to B536 - This code improves the robustness of write cache operations and sequential write performance when write cache is enabled. NOTE: This is the first code for the ST9xxxx52SS and ST9xxxx02SS drives to be included in a hard drive update package. It is an update from the code that is shipped with the drive.
MBD2xxxRC to SB14 - Initial release
SAS 3.5" -------- ST3xxxxx6SS to BA49 ST3750630SS to BC1D - This code improves the robustness of write cache operations.
SATA 2.5" --------- WD3000xxxxx to 04.04V05 - Adjusted PHY setting for better signal quality margin.
SATA 2.5" SSD -------------- STEC MACH8 IOPS to 2269 GBRL0xxxxx to 4.17 GBRLBxxxxx to 4.26 - The new firmware will correct a rare data error condition in the drives where invalid data may be passed to the system without any error condition flagged.
Due to the severity of this potential issue, IBM strongly recommends applying this firmware as soon as possible.
For further information, please refer to retain tip H195663.
NOTE: This is the first code for the GBRLBxxxxx drives to be included in a hard drive update package. It is an update from the code that is shipped with the drive.
*******************************************
Version 1.04
The following is a list of drives and the firmware that they will be checked for and updated as necessary.
This package includes new updates to drives with product ID strings of:
SAS 2.5" (SFF) -------------- CBRBAxxxxxx to C49B - Modified VPD for JSxx Blades
MBBxxxxxx to SB05 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller.
MBC2073RC to SC04 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller.
SAS 3.5" -------- MBAxxxxxx to SA06 - Fixed a performance issue when synchronizing or rebuilding an array when used in a LSI 1064 based SAS controller.
ST3xxxxx6SS to BA48 - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632.
ST3750630SS to BC1A - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632. - Fixes a hang condition during failover operation on a BladeCenter-S chassis with an RSSM controller.
BBAxxxxxx to BH0K - Fixed an issue where a drive may prematurely report a PFA trip.
GNAxxxxxx to BH0J - Fixed an issue where a drive may prematurely report a PFA trip.
SATA 3.5" --------- ST31000340NS, ST370330NS, ST3250310NS, ST3500320NS to BB12 - This code addresses a rare potential for data corruption. For this issue to occur, the drive write cache must be enabled. When a write is issued while the drive write cache is enabled and a read-verify is performed immediately afterwards, undetected data corruption can occur. For further information, please refer to retain tip H194632. - This code addresses a rare potential for data loss. After a power cycle, the drive will no longer be available and becomes unresponsive. Data will become inaccessible due to the drive not responding. For further information, please refer to retain tip H194623.
WDC WD2502ABYSxxxxx to 02.03B04 - Fixed incorrect VPD data.
SATA 2.5" --------- WD3000xxxxx to 04.04V04 - Fixed a Critical issue - IBM recommends a backup of the data on the drive before attempting to update the firmware. This is a fix for an issue where data required for spin up of the drive may be overwritten, rendering the drive inoperable on a subsequent warm or cold system reboot. - Fixed a bug with an internal timer that may cause a drive to go offline when used in a non-RAID environment.
SATA 2.5" SSD ------------- STEC MACH8 IOPS to 2103 - Initial Release
*******************************************
Version 1.03
Added the capability to update SAS and SATA drives online under Windows or Linux. This capability is only supported if the drives are attached to one of the following SAS adapters: - IBM ServeRAID MR10k SAS Controller - IBM ServeRAID MR10i SAS Controller - IBM ServeRAID MR10M SAS Controller - IBM ServeRAID MR10il SAS Controller - IBM ServeRAID MR10is SAS Controller - MegaRAID 8480 SAS Controller - IBM ServeRAID BR10i SAS Controller - IBM ServeRAID BR10il SAS/SATA Controller - IBM SAS HBA - IBM SAS Expansion Card (CFFv) for IBM BladeCenter - IBM SAS Connectivity Card (CFFv) for IBM BladeCenter - Onboard LSI 1064 SAS controller (2MB only) - Onboard LSI 1068 SAS controller - Onboard LSI 1078 SAS controller
This package includes new updates to drives with product ID strings of:
SAS 2.5" (SFF) -------------- ST9146802SS, ST973402SS to B529 - Added support for JS2x Blades in a BladeCenter-S chassis. - Picked up the latest network roll of firmware fixes to address some unexpected system hangs.
ST936751SS, ST973451SS to B615 - Added support for JS2x Blades in a BladeCenter-S chassis. - Picked up the latest network roll of firmware fixes to address some unexpected system hangs.
CBRBAxxxxxx to C495 - Initial release
MBBxxxxxx to SB04 - Initial release
MBC2073RC to SC03 - Initial release
SAS 3.5" -------- VPBAxxxxxx to A496 - Added support for JS2x Blades in a BladeCenter-S chassis.
ST3146855SS, ST3300655SS, ST373455SS to BA29 - Added support for JS2x Blades in a BladeCenter-S chassis. - Picked up the latest network roll of firmware fixes to address some unexpected system hangs.
ST3450856SS to BA47 - IBM was notified by our vendor that there is a defect in a level of firmware used in the IBM 450GB 15K SAS 3.5" HS HDD (PN 41Y8454) in option 42D0519, which under certain conditions may lead to data being written or read back incorrectly on the drive. IBM has worked closely with the vendor to identify the problem and developed a firmware fix to resolve the problem. Customers should upgrade to firmware level BA47.
MBAxxxxxx to SA05 - Initial release
ST3750630SS to BC17 - Initial release
SATA 3.5" --------- ST3250620NS, ST3500630NS, ST3750640NS to 3.AEV - Initial release
ST3250621NS, ST3500631NS, ST3750641NS to 4AEV - Initial release
ST31000340NS, ST3750330NS, ST3250310NS, ST3500320NS to BB10 - Initial release
HUA721050KLA330, HUA721075KLA330, HUA721010KLA330, to AB4A - Initial Release
SATA 2.5" SSD ------------- GBRL001xxx, GBRL0031xxx to 4.14 - Corrects intermittent hangs during operations.
============================ R E L E A S E N O T E S ============================
Broadcom Linux bnx2 and 10GigE Virtual Bus Drivers(VBD)
Version 2.2.1j 04/11/2012
NOTE: These driver files are the original files 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.
Disclaimer ========== - FCoE: Broadcom only officially supports the FCoE and DCB feature set on adapters that are licensed for FCoE, and for which EMC e-Labs certification is already complete or in progress. Broadcom will *not* provide field support for unqualified platforms. Please refer to the EMC e-Labs certification matrix for existing support matrix postings, or contact your Broadcom liaison to inquire about configurations currently in the qualification queue for eventual support. Exercising either FCoE or DCB on an unsupported platform may lead to unpredictable results.
Prerequisite ============ - For FCoE evaluation, 57712A1+8727C NIC adapters with valid FCoE license - For FCoE, NVRAM flag 105 must be enabled for DCB/DCBX - DCB/DCBX is required for FCoE - In order to enable FCoE, only the new 'MFW' firmware image can be used. Please use the eDiag supplied in this kit and upgrade the legacy boot code (and NCSI) to the new 'MFW' image
Notables ======== - 10G MBA driver release no longer supports RPL protocol. All files with xMMBA.NIC and xMMBA.LOM are removed - iSCSI Initiator: [1] when using T6.x driver, there is *only* iSCSI Initiator support for the following Linux OS's: - RH6.0 and RH5.5 - SLES11-U1 [2] for any OS prior to RH5.5, or SLES11-U1, the T5.2 driver set will need to be used [3] Only static and link-local IPv6 address supported in Linux iSCSI offload [4] Linux iSCSI VLAN tag dependent on L2 VLAN tag, must also be on same subnet [5] Linux iSCSI Path MTU not yet implemented [6] No routing support for Linux iSCSI. Broadcom still working with open-iscsi community to implement gateway and subnet mask addressing in the code - BASP w/ RSS enable can support a maximum of up to 4 processors - The default Flow Control setting in the Linux driver for 5771x 10g Fiber devices is now set to disabled.
Highlighted Fixes: ================== - Fixes CQ59931 - UEFI enhancement: Driver Health Protocol - Fixes CQ61639 - Expand documentation on LACP teaming requirements when changing hardware - Fixes CQ61833 - NX2 and NX2_EV UEFI HII help menu doesn't show correct VLAN range of 1 - 4094 - Fixes CQ55950/59951/59953 - Adding CCMCFG utility to meet BBSIG requirements for full featured online configuration tool required for NX1, NX2 and NX2_EV
Feature Additions: ================== - Non-switch dependent NIC Partitioning support added to all components for 57712 based mezzanine cards. - BOFM support added for NIC Partitioned devices - Added support for Red Hat 5.7 & 5.8, SLES 10 SP4, and SLES 11 SP1 & SP2
********* Currently known issues and limitations with Broadcom NetXtreme drivers and devices. **********
1. BASP (the Broadcom Advanced Server Program) will appear to be bound to all adapters in the system once loaded. This binding is normal and is used only to determine compatibility with BASP. The binding is not active, as indicated by the gray background of the selection box. This pre-binding will not interfere with bindings to other software protocols.
2. Network Teaming limitation with iSCSI offload: When iSCSI offload is enabled on Broadcom NetXtreme II NIC's or LOM's, only SLB teaming mode is supported. In order to create other teaming modes like 802.3ad and FEC/GEC, you will need to disable iSCSI offload. You can disable the iSCSI offload by a. launching the Broadcom Advanced Control Suite 3 (BACS 3). b. select the adapter you want to add to the team c. click the configurations tab, extend resource reservations. d. Uncheck iSCSI resource.
3. Restoring the team configuration with static IPv6 addresses may fail. Use either DHCP addresses for team configuration, or restore the team and re-apply the IP address manually if this issue is encountered.
4. Flow control statistics (MAC Sent X-ON, MAC Sent X-OFF and MAC Rx w/ no Pause Command) are reported incorrectly within BACS for 57710 based adapters. There is no functional impact and device is working as expected.
5. WoL with NPar: When using Wake on LAN (WoL) with NIC Partitioning, all of the devices that comprise a port must be shut down to cause the WoL configuration to be written to the controller during operating system shutdown. If only a single function is shut down, the WoL configuration might not be written to the controller, and the controller might not wake.
6. Editing BASP teams: There is a known problem where editing a BASP team in BACS can sometimes cause a failover to occur on another team. This is currently believed to be a Microsoft issue, and Broadcom is pursuing a fix or workaround.
7. NC-SI with IOMMU: There is a known problem using NC-SI with IOMMU enabled, that can cause link down/up under stress conditions. If this occurs, disabled IOMMU in the BIOS.
Software Compatibility ====================== This release of software supports: - BCM5706 NetXtreme II Gigabit Ethernet Adapter - BCM5706S NetXtreme II Gigabit Ethernet Adapter - BCM5708 NetXtreme II Gigabit Ethernet Adapter - BCM5708S NetXtreme II Gigabit Ethernet Adapter - BCM5709 NetXtreme II Gigabit Ethernet Adapter - BCM5709S NetXtreme II Gigabit Ethernet Adapter - BCM57710 NetXtreme II Gigabit Ethernet Adapter - BCM57711 NetXtreme II Gigabit Ethernet Adapter - BCM57712 NetXtreme II Gigabit Ethernet Adapter
Files included are:
A. Broadcom bnx2 Linux Driver B. Broadcom BCM57710/BCM57711/BCM57711E 10 GigE VBD for Linux C. Broadcom NetXtreme II iSCSI Driver For Linux D. Broadcom NetXtreme II bnx2fc FCoE Modules for Linux
****************************************************************************************** A. Release Notes Release Notes Broadcom bnx2 Linux Driver Version 2.2.1j 03/07/2012 Broadcom cnic Linux Driver Version 2.5.9d 03/07/2012
Broadcom Corporation 5300 California Avenue, Irvine, CA 92617
Copyright (c) 2004 - 2012 Broadcom Corporation All rights reserved
Cause: cp->ctx_tbl is NULL during cnic_ctl() call with COMPLETION_CMD.
Change: cnic is registered with the L2 drivers before we allocate the cp->ctx_tbl so it is possible to get called while cp->ctx_tbl is NULL. Added check for CNIC_UP flag before proceeding to dereference cp->ctx_tbl. This together with the RCU code will completely fix the problem.
Cause: Middle-box test corrupts packets and causes iSCSI fw to generate 0x4 (NIC_ERR) completion code. This conflicts with new logic that uses NIC_ERR to convey parity error.
Change: Redefined parity error completion code to be 0x81 for L4, iSCSI, and FCoE.
Impact: FCoE and iSCSI.
bnx2 2.2.1g (Feb 28, 2012) ========================== Fixes ----- 1. Problem: Calling of bnx2_vlan_rx_kill_vid() is not rtnl_lock protected. Change: hold rtnl_lock when execute this routine under ESX4.0 and ESX4.1. Impact: ESX4.0/4.1 only.
bnx2 2.2.1f (Feb 8, 2012) ========================== Fixes ----- 1. Problem: (CQ61327) Unable to pass traffic on RHEL5.x
Cause: bp->num_rx_rings not initialized due to backport errors. This was introduced in 2.2.1e when adding ethtool -l|L support.
Change: Initialized bp->num_rx_rings to 1 on these older kernels.
Impact: RHEL5 and SLES10 only.
cnic 2.5.8f (Feb 06, 2012) ========================== Enhancements ------------ 1. Change: Added VLAN update from iscsiuio. This allows VLAN to be specified in iface.
Impact: iSCSI only.
cnic 2.5.8e (Jan 24, 2012) ========================== Enhancements ------------ 1. Change: Enhanced FCoE parity recovery by sending immediate FW_DESTROY completion with error during parity error recovery.
Impact: FCoE only.
bnx2 2.2.1e (Jan 24, 2012) ========================== Enhancements ------------ 1. Change: Added support for ethtool -[l|L]. Please refer to README.TXT for details.
Impact: 5709 with support for MSIX only.
cnic 2.5.8d (Jan 19, 2012) ========================== Enhancements ------------ 1. Change: Enhanced FCoE driver registration to provide FCoE capabilities to bnx2x driver.
Impact: Systems with Management support of these features. These changes were made to match bnx2x 1.72.07.
2. Change: (CQ60867) Backed out earlier changes related to this CQ. genksyms checksums are based on structure names and type names, so the scheme of using an identical structure with a different name will not work.
Impact: None.
cnic 2.5.8c (Jan 10, 2012) ========================== 1. Problem: (CQ60744) Lose connection to FCoE targets after parity error recovery.
Cause: (Partial) DISABLE_CONN SPQ message does not complete, causing delaying waiting for bnx2fc to timeout.
Change: Added immediate KCQ error completion for FCOE_DISABLE_CONN. when SPQ fails.
Cause: If a TCP connection fails due to parity error, termination sequence does not follow the expedited error recovery path. This causes unnecessary delay during parity error recovery.
Change: Set the HW_ERR bit when TCP connection fails due to SPQ error. Termination will then follow the expedited error recovery path.
Impact: iSCSI on bnx2x.
3. Problem: (CQ60867) Module versioning warning when installing cnic driver on SLES11SP2 without matching bnx2i/bnx2fc.
Cause: cnic_register_driver() stub in cnic.c does not have cnic_ulp_ops structure that matches inbox bnx2i/bnx2fc.
Change: Added dummy cnic_ulp_ops that match RHEL6.2 and SLES11SP2 structures.
Impact: None.
bnx2 2.2.1d (Jan 10, 2012) ========================== Fixes ----- 1. Problem: PSOD seen in TX handling in either bnx2_tx_int() or bnx2_start_xmit() routines
Cause: Memory re-ordering is occuring so that the TX BD is not updated before the ringing of the TX doorbell.
Change: On ESX the wmb() macro is defined to only as a compiler barrier. Redfine the wmb() macro to properly synchronize memory using the sfence instruction.
Impact: ESX only.
cnic 2.5.8b (Jan 05, 2012) ========================== Enhancements ------------ 1. Change: Added CNIC_CTL_FCOE_ENHANCED_STATS_CMD and CNIC_CTL_FCOE_CAPABILITIES_GET_CMD as stubs.
Cause: SPQ errors during parity error recovery was not propagated to L4 and ULP, causing unnecessary long timeouts.
Change: Added immediate KCQ error completion for L4 and iSCSI kwqes if SPQ fails.
Impact: iSCSI on bnx2x.
bnx2 2.2.1c (Dec 21, 2011) ========================== Fixes ----- 1. Problem: (CQ60281) BNX2 hang on ESX 4.1 when changing tx ring size with Ethtool.
Cause: BNX2 set_ringparam() ethtool ops callback attempts to hold rtnl_lock while vmlinux has already held this lock when when invoking this callback. This leads to deadlock situation and driver will hang forever.
Change: Make sure all ethtool ops callbacks don't hold rtnl_lock.
Impact: ESX only.
2. Problem: (BDKL87) PSOD in bnx2 start_xmit() path when stressing with change ring size script on ESX 4.1u2.
Cause: When using ESX4.0/4.1u0-u2, the vmkernel doesn't not check tx queue state properly in certain race condition. This can lead to bnx2 start_xmit() to deference NULL tx buffer.
Change: check tx queue state before proceed with stat_xmit().
Impact: ESX4.0/4.1u0-u2.
cnic 2.5.7h (Dec 08, 2011) ========================== Enhancements ------------ 1. Change: Added iSCSI and FCoE driver status and counters support.
Impact: Systems with Management support of these features.
2. Change: Added upstream patches to sync up with upsteam driver: net: treewide use of RCU_INIT_POINTER net: remove ipv6_addr_copy()
Impact: None.
bnx2 2.2.1b (Dec 08, 2011) ========================== Enhancements ------------ 1. Change: Added several upstream patches to sync up with upsteam driver: net: treewide use of RCU_INIT_POINTER bnx2: fix skb truesize underestimation net: Remove unnecessary driver assignments of ethtool_ringparam fields to zero
Impact: None.
bnx2 2.1.12b (Oct 14, 2011) =========================== Fixes ----- 1. Problem: (CQ59255) iSCSI warning messages appear and performance drops when connected to a lefthand target.
Cause: Packets with invalid TTT generate warnings and exception handling.
Change: Updated to 6.2.3 firmware for 5706 and 6.2.1.b for 5709
Impact: iSCSI
cnic 2.5.7g (Sep 23, 2011) ========================== Enhancements ------------ 1. Change: Added cnic_register_driver()/cnic_unregister_driver stubs so that depmod will not return errors if native bnx2i/bnx2fc drivers have not been updated.
Impact: None.
bnx2 2.1.11e (Sept 19, 2011) =========================== Enhancements ------------ 1. Change: Set the feature, NETIF_F_NO_SCHED, for ESX 5.0 and greater releases only
Impact: ESX only
Fixes ----- 1. Problem: Compile errors on some older kernels.
Cause: Compatibility API pci_is_pcie() requires bool type which may not be defined on older kernels.
Change: Moved bool type compatibility definition above pci_is_pcie().
Impact: None.
bnx2 2.1.11d (Aug 30, 2011) =========================== Enhancements ------------ 1. Change: Integrate Code Review Comments from VMware * Add feature flag to reflect if a device is compliant with network scheduling. * Conditionally move bnx2 drivers to high memory * Remove unused field/code
Impact: ESX only
2. Change: Remove unnecessary read of PCI_CAP_ID_EXP from upstream.
Impact: minor (5709 only).
cnic 2.5.7f (Sep 13, 2011) ========================= Fixes ----- 1. Problem: Duplicate cp local variable in cnic_shutdown_rings().
Cause: Coding error.
Change: Removed duplicate variable.
Impact: None.
cnic 2.5.7e (Aug 8, 2011) ========================= Fixes ----- 1. Problem: (CQ57498) System hangs during bnx2x parity error recovery.
Cause: cnic waits for RAMRODs to complete without timeout. During parity error recovery, all DMAs will stop.
Change: Added timeouts to all RAMRODs.
Impact: iSCSI and FCoE on bnx2x
cnic 2.5.7d (July 28, 2011) =========================== Enhancements ------------ 1. Change: Increased the max number of FCoE sessions to 1024.
Impact: FCoE.
bnx2 v2.1.11c (July 26, 2011) ============================ Enhancements ------------ 1. Change: Upstream sync to use ethtool_cmd_speed API.
Impact: None.
2. Change: Added memory barrier to sync transmit descriptor before updating TX mailbox. We believe that this may fix some very rare panics reported by VMWare.
Impact: bnx2 packet transmit.
cnic 2.5.7c (July 26, 2011) =========================== Fixes ----- 1. Problem: FCOE_DESTROY_FUNC ramrod not completing, causing timeout and OOO cleanup timeout during MTU change.
Cause: FCOE_DESTROY_FUNC was sent before all FCoE CIDs have been deleted.
Change: Wait for all (2 seconds delayed) FCoE CFC_DELETE ramrods to be completed before sending FCOE_DESTROY_FUNC.
Impact: FCoE only.
cnic 2.5.7b (July 19, 2011) =========================== Enhancements ------------ 1. Change: Re-instated vlan_id in ->indicate_netevent(). It is needed by bnx2fc to handle NETDEV_UNREGISTER on VLAN devices.
Impact: bnx2fc.
2. Change: Allocate FCoE CID space only on E2+ devices.
Impact: None.
bnx2 v2.1.11b (July 19, 2011) ============================ Enhancements ------------ 1. Change: Added tx_timeout error handling and made it common with VMWare code.
Impact: bnx2 NETDEV WATCHDOG error handling
2. Change: Fix compile errors on the latest net-next upstream kernel.
bnx2 v2.1.10d (July 12, 2011) cnic 2.5.6c (July 12, 2011) ========================================================= Fixes ----- 1. Problem: Not compiling on 3.0.0 kernel.
Cause: Makefile not recognizing the 3.0.x kernel
Change: Modified Makefile and sync'ed with upstream drivers.
Impact: None.
bnx2 v2.1.10c (July 1, 2011) ============================ Fixes ----- 1. Problem: Not compiling on older kernels (such as RHEL5.4) and newer kernels (such as 2.6.36)
Cause: Problems with compatibility code.
Change: Fixed compatibility code.
Impact: None.
bnx2 v2.1.10b (June 30, 2011) ============================ Enhancements ------------ 1. Change: Added more complete MCP dump during error conditions.
Impact: None.
2. Change: Modified driver messages slightly to match upstream format (by using netdev_printk, netdev_err, etc).
Impact: None.
Fixes ----- 1. Problem: Not reading iSCSI license on 570x devices reliably.
Cause: We were reading from the CP scratch pad before the CP firmware is loaded.
Change: Read from MCP shmem location instead.
Impact: 1G iSCSI on bnx2 devices.
cnic 2.5.6b (June 30, 2011) ============================ 1. Problem: (CQ56522, CQ56259) Unable to connect to iSCSI target, bnx2x firmware assert during iSCSI connection
Cause: iSCSI L2 ring CID has been changed in bnx2x 1.70.14. uIP is using a hardcoded value of 0x11.
Change: cnic now passes the CID to uIP.
Impact: iSCSI on bnx2x devices.
2. Problem: (CQ56230) Cannot compile on some 32-bit systems.
Cause: Passing 64-bit NULL pointer as 32-bit 0 dma_addr_t value.
Change: Use 0 instead of NULL for dma_addr_t values.
Impact: None.
cnic 2.5.5b (June 22, 2011) ============================ Enhancements ------------ 1. Change: Added WWN info to cnic_eth_dev. This is a temporary solution until ndo_fcoe_get_wwn() is implemented.
Impact: None.
bnx2 v2.1.9b (June 22, 2011) ============================ Enhancements ------------ 1. Change: Added del_timer_sync() in bnx2_remove_one() from upstream commit 8333a46ad3877485e4d67ef499c6dda36bfd1f9a. See ChangeLog for details.
Impact: None.
bnx2 v2.1.8c (June 16, 2011) ============================ Enhancements ------------ 1. Change: In ESX, bnx2 will setup int mode during .probe time. However, the dev->name will be finalized only when pci_announce_device is done. So, we assign irq->name in bnx2_request_irq instead of in bnx2_setup_int_mode.
Impact: ESX only.
cnic 2.5.4b (June 1, 2011) ============================ Fixes ----- 1. Problem: (CQ55915) iSCSI does not connect on 57800 in 4-port mode.
Cause: cl_qzone_id was wrong on the 3rd and 4th port. uIP also has some problems determining 4-port mode.
Change: Fixed the QZONE_ID macro.
Impact: bnx2x iSCSI.
bnx2 2.1.8b (June 1, 2011) ============================ Fixes ----- 1. Problem: (CQ55422) NCSI firmware version displayed backwards on PPC.
Cause: Endian bug when reading the data from shared memory.
Change: Fixed byte swapping issue.
Impact: None.
2. Problem: bnx2 does not compile on some PPC distros.
Cause: pci_enable_pcie_error_reporting() not properly defined in some distros.
Cause: Added #ifdef to prevent compiling pci_enable_pcie_error_reporting() on PPC since it uses EEH instead of AER.
cnic 2.4.5b (May 16, 2011) ========================== Enhancements ------------ 1. Change: Check CFC delete error code during completion. If it is set, do not reuse the CID. This change is only compatible with bnx2x 1.64.30 or newer.
Cause: TCP reset request may not complete if there is a race with firmware receiving a remote RST.
Change: Added code to handle TCP reset racing with remote RST and TCP close racing with remote FIN.
Impact: iSCSI
cnic 2.4.3b (April 28, 2011) ============================ Fixes ----- 1. Problem: cnic may lose interrupts after processing 64 kcq entries.
Cause: The driver handles a maximum of 64 entries before calling the ulp drivers. If the chip has more entries, the driver does not handle the rest but acknowledges the latest status block index.
Change: Changed the logic to keep looping until all kcq entries are handled.
Impact: iSCSI and FCoE on all devices.
cnic 2.4.2b (April 21, 2011) ============================ Fixes ----- 1. Problem: (CQ54715, CQ54717) XSEMI parity error detected during iSCSI login on 57712 in NPAR mode.
Cause: Statistic counter ID greater than MAX_STAT_COUNTER_ID_E2 in client init data for iSCSI L2 ring.
Change: Check client ID against MAX_STAT_COUNTER_ID_EXX before enabling statistics.
cnic 2.4.1c (April 11, 2011) ============================ Fixes ----- 1. Problem: (CQ49586) iSCSI reboot test fails after a few iterations.
Cause: TCP port 60000 is used every time during boot. During reset, the TCP connection is never terminated so using the same port to connect to the target during reboot will not work.
Change: Added randomization of the first TCP port to use.
Impact: iSCSI.
bnx2 v2.1.6b (April 6, 2011) ============================ Enhancements ------------ 1. Change: Get iSCSI license information to prevent cnic from registering if there is no license. This will make it consistent with 10G behavior.
Impact: iSCSI only.
cnic 2.4.1b (April 6, 2011) =========================== Fixes ----- 1. Problem: (CQ53236) FCoE HBA not functional after reloading bnx2x.
Cause: In some distros, NETDEV_UP can happen immediately after NETDEV_REGISTER while bnx2x module is still in init state. At this time, cnic will not be able to symbol_get() from bnx2x, preventing the cnic from registering.
Change: Check all events, and we should be able to catch NETDEV_CHANGE abd register cnic.
cnic 2.4.0b (Mar 29, 2011) ========================== Enhancements ------------ 1. Change: Updated cnic to with with bnx2x 1.70.x and added support for 578xx devices.
Cause: Race condition between cnic driver and hardware DMA'ing a new status block with new iSCSI events. The bug was introduced when adding FCoE support.
Change: 1. Add proper memory barrier after reading status block. 2. After servicing FCoE EQ, we must loop back and check the iSCSI EQ again because we may have a newer status block index that is read after servicing the iSCSI EQ.
Impact: 57712 iSCSI and FCoE.
bnx2 v2.1.5c (Feb 15, 2011) cnic 2.3.5c (Feb 15, 2011) ====================================================== Enhancements ------------ 1. Change: Updated 5709 firmware to 6.2.1a, with netq fixes and iSCSI performance regression fixes.
Impact: 5709.
bnx2 v2.1.5b (Feb 08, 2011) cnic 2.3.5b (Feb 08, 2011) ====================================================== Fixes ----- 1. Problem: iSCSI does not connect in DCB environment.
Cause: iSCSI packets are tagged with the wrong ethertype.
Change: Added initialization of xstorm's reserved_vlan_type field.
Cause: BNX2_NETQ_HW_OPENED bit was not properly set.
Change: When the NetQueue device is openned properly set the BNX2_NETQ_HW_OPENED bit in the netq_flags field.
Impact: ESX NetQueue
2. Problem: NetQueue could possibly get out of sync with the uppper layers
Cause: The queue cleanup code between the driver and upper layer is not synchronized
Change: Introduce the NetQueue lock to synchronize the cleaning of the queues between the vmkernel and the bnx2 driver.
Impact: ESX NetQueue
3. Problem: iSCSI may not work if multi-function is disabled in NPAR NICs.
Cause: Bug in logic in detecting NPAR mode.
Change: Offload bit should not be checked if iSCSI MAC address is invalid.
Impact: iSCSI on 57712 NPAR NIC.
bnx2 v2.0.22c (Jan 6, 2011) cnic 2.2.12c (Jan 6, 2011) ========================================================= Enhancements ------------ 1. Change: Updated to 6.2.1a firmware for 5709. It has fixes for CQ51953 (ESX netqueue issue) and CQ51894 (iSCSI performance).
Impact: 5709 iSCSI and L2.
bnx2 v2.0.22b (Jan 4, 2011) cnic 2.2.12b (Jan 4, 2011) ========================================================= Enhancements ------------ 1. Change: Send netlink IF_DOWN message during cnic_unregister_device(). This fixes the problem of bnx2i referencing freed hba when we used to send the netlink message during cnic_unregister_driver().
Impact: iSCSI.
2. Change: Upstream fix for memory leak in cnic_alloc_uio_rings() when we cannot allocate all the memory.
Impact: None.
3. Change: Upstream fix to remove flush_scheduled_work() since it is obsolete.
Impact: None.
4. Change: Do not allow iSCSI on bnx2x devices in MF mode. The hardware does not yet support it.
Impact: iSCSI.
Fixes ----- 1. Problem: SPQ RAMROD type field does not consistently contain the function ID.
Change: Fixed in cnic_submit_kwqe_16() for HSI 6.0 and above.
Impact: iSCSI in NPAR mode.
bnx2 v2.0.21b (Dec 21, 2010) cnic 2.2.11b (Dec 21, 2010) ========================================================= Enhancements ------------ 1. Change: Call cm_connect_complete() when an invalid path_response netlink message is received. This will speed up iscsid in disconnecting the connection. This helps to resolve CQ49665.
Cause: Referencing the cp->kcq1 pointer before checking that the device is up.
Change: Fixed logic so that the cp->kcq1 pointer will only be refernced after checking the device is up.
Impact: iSCSI.
Enhancements ------------ 1. Change: Added retry logic in iscsi_nl_send_msg() to retry netlink messages to userspace.
Impact: iSCSI.
bnx2 v2.0.20f (Dec 09, 2010) cnic 2.2.10f (Dec 09, 2010) ========================================================= Fixes ----- 1. Problem: (CQ51544) Unable to connect to iSCSI targets on 57712 NPAR LOMs with NPAR disabled.
Cause: ff:ff:ff:ff:ff:ff iSCSI MAC address was used in this case.
Change: Add code to detect invalid MAC address and use port MAC address instead. That's the only to determine NPAR is disabled.
Impact: 57712 iSCSI.
2. Problem: MTU change in INTA mode crashes occasionally.
Cause: Status block may be accessed if INTA is shared with another device during reset. There is a short period that the status block is freed.
Change: Free IRQ before freeing status block.
Impact: bnx2 MTU change/ring size change.
3. Problem: Heap corruption reported by VMWare.
Cause: list_del() is called after kfree() in OOO code.
Fix: call list_del() before kfree().
Impact: iSCSI OOO.
bnx2 v2.0.20e (Dec 06, 2010) cnic 2.2.10e (Dec 06, 2010) ========================================================= Enhancements ------------ 1. Change: Adjusted hc timeout for EQ to use the T6.0 value of 4. This will match T5.x HC timeout values.
Impact: 10G iSCSI only.
2. Change: Minor changes to match upstream code.
Impact: None.
bnx2 v2.0.20d (Nov 16, 2010) cnic 2.2.10d (Nov 16, 2010) ========================================================= Fixes ----- 1. Problem: VMware NetQueue not working properly on 5709.
Cause: HSI mismatch.
Change: Updated HSI to match T6.0 bnx2 firmware.
Impact: NetQueue on 5709.
Enhancements ------------ 1. Change: Adjusted kernel compatibility code to compile on RHEL5.6.
Impact: bnx2 and cnic.
bnx2 v2.0.20c (Oct 28, 2010) cnic 2.2.10c (Oct 28, 2010) ========================================================= Fixes ----- 1. Problem: NMI occurs during repeated load/unload of bnx2 driver on 5709.
Cause: The 5709 chip's DMA block wasn't stopped properly before reset.
Change: Fixed by clearing DMA_ENABLE in NEW_CORE_CTL register and polling for pending bus transactions to stop.
Impact: 5709.
Enhancements ------------ 1. Change: Update 5706/5708/5709 firmware to 6.2.1.
Impact: All 1G devices.
2. Change: Fixed one circular lock dependency issue with bnx2i when making up call to send iSCSI NL message.
Enhancements ------------ 1. Change: (CQ49858) Support KVM pass-through mode by eliminating config cycles to non-standard PCI registers (PCICFG_MISC_CONFIG, PCICFG_REG_WINDOW*).
Impact: All chips.
bnx2 v2.0.18c (Sep 13, 2010) cnic 2.2.6c (Sep 13, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49832) bnx2 flow control not working
Cause: Mistakenly disabled in firmware in 2.0.17j to fix CQ46393.
Change: Re-enabled RV2P flow control with additional fixes to for a number of odd flow control issues. New firmware versions are 6.0.15 for 5706/5708 and 6.0.17 for 5709.
Impact: 5706/5708/5709.
Enhancements ------------ 1. Change: Added zeroing of the iSCSI L2 ring's RX BD page to help signal ring shutdown to uIP.
Cause: A mismatch was found in the txbd where the hw prod idx did not match the sw prod idx (via the vlan_id field). The problem will show when uIP restarts without cnic reload. Since uIP restarted, it has lost all previous history about the uio ring.
Change: Added cnic_shutdown_rings to the uio_close path so whenever uio_open is called from uIP, the rings will start off fresh.
Impact: 570X/5771X iSCSI.
2. Problem: (CQ49211) Connection via bnx2i path fails in SuSE 11 SP1
Cause: For 5708/09, the previous firmware set did not take the l2 frame header length into account in the placement filter.
Change: Updated to 5706/08 fw 6.0.14 and 5709 fw 6.0.16 which addresses this issue.
Impact: 570X iSCSI.
bnx2 v2.0.17k (Aug 18, 2010) cnic 2.2.5k (Aug 18, 2010) ========================================================= Fixes ----- 1. Problem: iSCSI sessions do not recover when running under heavy stress conditions with the socket layer.
Cause: The NetLink buffer would get congested, so that the response to the PATH_UPDATE back to uIP would not be delivered.
Change: Use CNIC to throttle the number of outstanding PATH_REQ's to uIP, easing the congestion on the Netlink buffer.
Cause: RV2P firmware was set to drop input packets at a rate which is slower than input line rate when the host stops posting buffers. This has caused the rxp ftq to backup which eventually led to the rxp ftq hw to assert PAUSE and flood the network.
Change: RV2P firmware was modified to disable any waiting before dropping the input packet when the host doesn't post buffers.
Cause: cnic_wq destroyed while cnic_delete_task() is still queued in the workqueue.
Change: Call destroy_workqueue() after cnic_release() which waits for the cnic_delete_task() to finish.
Impact: 10G iSCSI.
bnx2 v2.0.17f (July 30, 2010) cnic 2.2.5f (July 30, 2010) ========================================================= Fixes ----- 1. Problem: iSCSI license not read correctly on 57712 in NIC partitioning mode.
Cause: Missing NIC partitioning license logic.
Change: Added NIC partitioning license logic.
Impact: 10G iSCSI.
Enhancements ------------ 1. Change: Updated 5709 firmware to 6.0.13. The new 5709 firmware has additional rx and tx performance improvements.
Impact: 5709.
bnx2 v2.0.17e (July 29, 2010) cnic 2.2.5e (July 29, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49117, CQ49111) Soft locup when unloading bnx2x with cnic and bnx2fc/bnx2i loaded.
Cause: cnic_cm_stop_bnx2x_hw() thread under rtnl_lock() and pci_bus_sem has to wait for cnic_delete_task() to finish the 2-second wait and CFC DELETE of every FCoE or iSCSI connection. There may be work structs scheduled on the common workqueue ahead of cnic_delete_task() that require the same semaphores, leading to the soft lockup.
Change: Use a dedicated workqueue for cnic_delete_task().
Impact: 10G iSCSI and FCoE.
2. Problem: (CQ49113) Compilation error with bnx2x 1.60.30. (CQ48828) lediag fails with cnic loaded.
Cause: license_key structure changed to use all 32-bit fields. This change is to fix CQ48828 (lediag fails with cnic loaded). 16-bit access causes lediag failure.
Change: Made corresponding change to read 32-bit values for the iSCSI license.
Impact: 10G iSCSI.
3. Problem: (CQ49097) cnic panics when loading on 5708.
Cause: The driver uses NULL OOO ring pointers to initialize OOO for 5708.
Change: Skip OOO completely on 5708.
Impact: bnx2 iSCSI.
bnx2 v2.0.17d (July 28, 2010) cnic 2.2.5d (July 28, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49071) Soft lockup during system shutdown after logging in to 10G iSCSI sessions.
Cause: This was introduced in 2.2.5c when fixing CQ49003. flush_scheduled_work() can deadlock because we're holding rtnl_lock and linkwatch_event may be on the workqueue.
Change: Fixed by using flags to wait for the cnic_delete_task() to finish.
Impact: 10G iSCSI.
2. Problem: cnic driver does not load on 5708 devices.
Cause: Bug in driver that skips devices without OOO support.
Change: OOO setup has been changed so that cnic initialization will continue even if OOO fails for whatever reason on all chips.
Impact: iSCSI.
Enhancements ------------ 1. Change: Updated 5708 firmware to 6.0.11 and 5709 firmware to 6.0.12. The new 5709 firmware fixes small packet rx performance issue. Some adiitional fixes for iSCSI and OOO.
Impact: All bnx2 chips.
bnx2 v2.0.17c (July 23, 2010) cnic 2.2.5c (July 23, 2010) ========================================================= Fixes ----- 1. Problem: (CQ49003) Panic in cnic_free_bnx2x_conn_resc() during ifdown with many 10G iSCSI active sessions.
Cause: cancel_work_sync() is not available in RHEL5.x kernels to wait for cnic_delete_task() to finish before freeing the device's data structures (in particular the csk table).
Change: Use flush_scheduled_work() to wait instead.
Cause: UIO device deleted before userspace has closed the device, causing various failures including kernel panic.
Change: Separated UIO structure from cnic_dev structure so that we can wait until UIO is closed before unregister and deleting UIO.
Impact: iSCSI. This change should have possitive impact on ifup/ifdown, MTU change/selftest/hotplug/etc with active iSCSI sessions.
Enhancements ------------ 1. Change: Allocate the actual number of MSI-X vectors instead of always 9. Also, keep trying if the number of vectors is less than the desired number.
Impact: 5709 networking and iSCSI.
bnx2 v2.0.16c (July 12, 2010) cnic 2.2.4c (July 12, 2010) ========================================================= Enhancements ------------ 1. Change: Added VLAN_TAG_PRESENT to distinguish between physical and VLAN netevents in cnic.
Impact: FCoE.
bnx2 v2.0.16b (July 8, 2010) cnic 2.2.4b (July 8, 2010) ========================================================= Fixes ----- 1. Problem: (CQ48753) cnic will not compile with bnx2x 1.60.27.
Cause: IGU symbols not defined without ELINK_DEBUG defined.
Change: Added ELINK_DEBUG.
Impact: None.
2. Problem: (CQ48717) Kernel panic in bnx2x during ifdown with active iSCSI sessions.
Cause: uio_close() is called after the device is already down. bnx2x will crash when we try to shutdown the iSCSI ring.
Change: Shutdown the iSCSI ring even if uio_close() is not called in the shutdown path.
Impact: 10G iSCSI.
Enhancements ------------ 1. Change: Always run in MSI-X mode on 5709.
Impact: 5709.
2. Change: Added wait of 2 seconds when sending PATH_REQ if UIO has not been opened yet. This improves the liklihood of login success during the first login if using older iscsid.
Cause: pci_save_state()/pci_restore_state incompatibility in older kernel. DECLARE_PCI_UNMAP_ADDR() caused dma mapping field to be undefined on kernels not using IOMMU.
Change: Do not use pci_save_state()/pci_restore_state() on older kernels. Use dma_addr_t to declare mapping fields.
Impact: None.
bnx2 v2.0.15j (June 30, 2010) cnic 2.2.3j (June 30, 2010) ========================================================= Fixes ----- 1. Problem: bnx2x firmware asserts if cnic is loaded on 57711E (MF) functions 2 and higher and the device is brought up.
Cause: Statistics for iSCSI ring not implemented, casuing firmware to assert when the iSCSI ring is initialized.
Change: Do not enable statistics if the clien ID is bigger than MAX_STAT_COUNTER_ID.
Impact: bnx2x iSCSI on 57711E.
2. Problem: cnic terminations for iSCSI and FCoE connections may panic or hang during repeated ifdown/ifup.
Cause: Data structures may be freed while cnic is still waiting for the 2 second CFC_DELETE wait time.
Change: Use cancel_work_sync() to wait for the completion of the cnic_delete_task(). Check that the CTX_FL_DELETE_WAIT flag has been set before waiting.
Impact: bnx2x iSCSI and FCoE.
3. Problem: (CQ48642) Compile errors on older kernels.
Cause: VMWARE_ESX_DDK_VERSION not defined in Linux.
Cause: Race condition between bnx2i initiated TCP close and an asynchronous RESET_COMP from firmware.
Change: Re-structured cnic code that handles close, abort, and various completion events to ensure all scenarios are accounted for with no race conditions.
Impact: All iSCSI connection termination scenarios.
Enhancements ------------ 1. Change: Added host iSCSI IP address to the cnic_dev structure so that bnx2i can report it to sysfs. This is needed for iSCSI boot during pivot_root.
Cause: PCI MSIX attributes not defined in kernel .h files.
Change: Added compatibility code.
Impact: None.
bnx2 v2.0.15d (June 2, 2010) cnic 2.2.3d (June 2, 2010) ========================================================= Fixes ----- 1. Problem: (CQ47942) rmmod hangs if the device has been opened and closed more than once.
Cause: netif_napi_add() called once during every ->open(). netif_napi_del() is only called once during rmmod.
Change: Call netif_napi_del() in ->close().
Impact: None.
bnx2 v2.0.15c (May 21, 2010) cnic 2.2.3c (April 21, 2010) ========================================================= Fixes ----- 1. Problem: service iscsid restart on 5709 does not work.
Cause: Not restarting KWQ correctly due to stale context.
Change: Fixed by correctly zeroing KWQ/KCQ/RX context memory.
Impact: bnx2 iSCSI.
2. Problem: iSCSI license not read correctly on 57711E in single function mode.
bnx2 v2.0.15b (May 12, 2010) cnic 2.2.3b (April 12, 2010) ========================================================= Fixes ----- 1. Problem: iSCSI does not work on 57712.
Cause: License checking always disabled on 57712.
Change: Added proper checking for 57712 iSCSI license.
Impact: None.
2. Problem: (CQ47360) Compile errors on older kernels not supporting UIO and latest iSCSI.
Cause: New cnic driver will only compile on kernels newer than 2.6.31 and some selected distros that have the backport.
Change: Makefile changes to compile cnic only on supported kernels.
Impact: None.
Enhancements ------------ 1. Change: Changed bnx2_cnic_probe() to bnx2_cnic_probe2() so that out-of-tree driver componenets will not inter- operate with upstream components. This avoids compatibility problems that often lead to kernel crashes.
Impact: Out-of-tree cnic will not operate with upstream L2 drivers and vice versa.
2. Change: Revert the PRS_REG_NIC_MODE change done in 2.0.11h. Newer bnx2x driver (1.60.18+) do not require this setting.
2. Change: Added VLAN ID to netdev event callback.
Impact: bnx2i.
bnx2 v2.0.13b (April 22, 2010) cnic 2.2.1c (April 30, 2010) ============================================================ Enhancements ------------ Add debug code to dump all KWQE's (RAMROD) posted to 5771x chipset. This feature can be enabled/disabled using module parameter, by default this feature is disabled. Also a exported function is introduced to dump 3 pages worth of KCQE's
bnx2 v2.0.13b (April 22, 2010) cnic 2.2.1b (April 22, 2010) ============================================================ Enhancements ------------ 1. Change: cnic has been updated to be similar to the upstream versions using UIO with added T6.0 iSCSI support for 10G and other bug fixes.
Impact: iSCSI now requires UIO, new bnx2i, and bnx2x 1.60.16+.
bnx2 v2.0.11j (April 22, 2010) cnic 1.10.2j (April 22, 2010) ============================================================ Fixes ----- 1. Problem: (CQ47298) Does not compile with bnx2x 1.60.16.
Cause: cnic_if.h has changed.
Change: Updated code to be compatible with new cnic_if.h.
Impact: None.
bnx2 v2.0.11i (April 15, 2010) cnic 1.10.2i (April 15, 2010) ============================================================ Fixes ----- 1. Problem: (RHBZ 511368) Driver loses one MSI-X vector after many hours of traffic.
Cause: Chip timing out on write cycle to the MSI-X mask bit, causing the unmask operation to be dropped.
Change: Increase GRC timeout in register 0x8cc. (Same fix from 2.0.8e).
Impact: bnx2x MSI-X mode.
2. Problem: (RHBZ 554706) scheduling while atomic warning when bonding and VLANs are used with cnic loaded.
Cause: bond_del_vlans_from_slave() holds bond->lock when calling ndo_vlan_rx_register(). bnx2 calls bnx2_netif_stop() to stop the rx handling while changing the vlgrp. The call also calls bnx2_cnic_stop() which has many sleeping functions.
Change: Do not stop cnic when VLANs are changed. Since there is no reset during VLAN change, there is no need to stop cnic. (Same fix from 2.0.8e).
Impact: VLAN and iSCSI.
3. Problem: (CQ46940) Poor small packet performance on 5709.
Cause: FTQ discards caused by bottlenecks in firmware.
Change: Upgraded to 5.0.0.j15 MIPS firmware for 5709. (Same fix from 2.0.8c)
Impact: 5709.
Enhancements ------------ 1. Change: Improved rx performance by prefetching next entry's descriptor header and SKB.
Impact: All chips.
2. Change: Updated cnic interface to support out-of-order processing. This is needed for bnx2x 1.60.15 but the feature is not available in cnic yet.
bnx2 v2.0.11b (Jan 28, 2010) cnic 1.10.2b (Jan 27, 2010) ======================================================== Enhancements ------------ 1. Change: Saved bnx2 statistics block before MTU change, ring change, etc.
Impact: bnx2 statistics.
bnx2 v2.0.10b (Jan 12, 2010) cnic 1.10.1b (Jan 12, 2010) ======================================================== Enhancements ------------ 1. Change: Improved cnic's MTU change/reset logic to fix multiple problems in VMWare.
Impact: iSCSI.
2. Change: Converted to bnx2x T6.0 HSI.
Impact: bnx2x iSCSI.
bnx2 v2.0.8e (April 13, 2010) cnic 1.9.13b (Dec 16, 2009) ========================================================= Fixes ----- 1. Problem: (RHBZ 511368) Driver loses one MSI-X vector after many hours of traffic.
Cause: Chip timing out on write cycle to the MSI-X mask bit, causing the unmask operation to be dropped.
Change: Increase GRC timeout in register 0x8cc.
Impact: bnx2x MSI-X mode.
2. Problem: (RHBZ 554706) scheduling while atomic warning when bonding and VLANs are used with cnic loaded.
Cause: bond_del_vlans_from_slave() holds bond->lock when calling ndo_vlan_rx_register(). bnx2 calls bnx2_netif_stop() to stop the rx handling while changing the vlgrp. The call also calls bnx2_cnic_stop() which has many sleeping functions.
Change: Do not stop cnic when VLANs are changed. Since there is no reset during VLAN change, there is no need to stop cnic.
Impact: VLAN and iSCSI.
bnx2 v2.0.8d (April 02, 2010) cnic 1.9.13b (Dec 16, 2009) ========================================================= Enhancements ------------ 1. Change: Improved rx performance by prefetching next entry's descriptor header and SKB.
Cause: Stale status block with old KCQ index after restarting hardware.
Change: Added some additional cleanup and initialization steps including zeroing the status block.
Impact: None.
Enhancements ------------ 1. Change: Updated RV2P P1 for 5709 to 5.0.0.j10 to address a flow control issue that can lead to context corruption. Flow control watermarks have also been optimized.
Impact: 5709 flow control.
bnx2 v2.0.6b (Dec 4, 2009) cnic 1.9.11b (Nov 19, 2009) ======================================================= Fixes ----- 1. Problem: (CQ44801) Unable to compile bnx2 on most 2.6 kernels.
Cause: print_mac() kernel compatibility not defined correctly.
Fix: Simple compatibility fix.
Impact: None.
bnx2 v2.0.5b (Dec 4, 2009) cnic 1.9.11b (Nov 19, 2009) ======================================================= Enhancements ------------ 1. Change: Sync'ed up with latest upstream bnx2 driver. Please see ChangeLog for details.
Impact: Yes, Linux and VMWare.
bnx2 v1.9.42b (Dec 1, 2009) ======================================================= Fixes ----- 1. Problem: Compile error against the VMware ESX 4.0 DDK
Cause: vmk_IscsiNetHandle is not defined with the VMware ESX 4.0 DDK
Change: Added compile flag
Impact: None.
Enhancements ------------
1. Change: Add BMAPILNX ioctl to allow for FW upgrade
2. Problem: (CQ42096) iSCSI sessions do not recover after running selftest/ifdown/etc with max sessions connected.
Cause: cnic_lock mutex has circular dependency, causing deadlock when iscsid tries to cleanup connections.
Change: Merged in upstream cnic patches to avoid circular dependency.
Impact: None.
Enhancements ------------ Change: (CQ43088) Changed the firmware version string format.
Impact: None.
bnx2 v1.9.40b (Nov 18, 2009) cnic 1.9.10b (Nov 12, 2009) ======================================================= Fixes ----- 1. Problem: (CQ44528) Kernel runs out of memory after load/unload bnx2.
Cause: RX SKB buffers were not freed.
Change: Fixed the regression introduced by VMWare development.
Impact: None.
2. Problem: (CQ44399) iLAB 5.10 connection establishment test failure.
Cause: Firmware SYN-ACK handling issue.
Change: Updated firmware to 5.0.0.j6 in bnx2_fw.h and 5.0.0.j9 in bnx2_fw2.h.
Impact: iSCSI.
Enhancements ------------ Change: (CQ43088) Added VPD-R V0 firmware version string to ethtool -i.
Impact: None.
bnx2 v1.9.39b (Nov 6, 2009) cnic 1.9.10b (Nov 12, 2009) ======================================================= Fixes ----- 1. Problem: (CQ44470) Kernel panics when bnx2/bnx2x is unloaded with active iSCSI sessions.
Cause: NETDEV_UNREGISTER will cause bcm570x_* transport to be destroyed while sessions may still be active.
Change: Use module referencing to prevent bnx2/bnx2x from unloading. This is a simple interim solution to revert back to the old behavior. In T6.0, we will migrate to the upstream driver architecture and network drivers will be able to be unloaded again.
Impact: None.
Enhancements ------------ Change: Added a short register dump during NETDEV_WATCHDOG.
bnx2 v1.9.35b (Oct 22, 2009) ======================================================= Fixes ----- 1. Problem: If only 1 queue is used on VMware ESX, iSCSI offload would fail.
Cause: The inboxed VMware driver would only use 1 MSI-X vector. Because of this the driver would not setup MSI-X
Change: Always setup MSI-X reguardless of the number of MSI-X vectors used.
Impact: 5709 iSCSI on VMware
bnx2 v1.9.34b (Oct 20, 2009) ======================================================= Fixes ----- 1. Change: Updated xinan firmware to 5.0.0.j8 Nop timeout tuning (VMware PR467194) Added a new data fw heartbeat to work with the new bootcode and also handle older bootcode.
1. Change: Make NetQueue module parameters more explict.
Impact: bnx2 VMware NetQ.
bnx2 v1.9.32b (Oct 8, 2009) cnic v1.9.7c (Oct 8, 2009) ======================================================= Fixes ----- 1. Problem: CNIC unable to handle an unsolicited RESET COMPLETE which would result in a hung session.
Cause: The CNIC driver couldn't handle unexpected SYN.
Change: The CNIC driver will now handle an unsolicited RESET COMPLETE and cleanup properly.
Impact: cnic
Enhancements ------------
1. Change: Allow the default NetQueue options to be controlled through the macro, BNX2_ENABLE_NETQUEUE.
Impact: bnx2 VMware NetQ.
bnx2 v1.9.31b (Oct 6, 2009) ======================================================= Fixes ----- 1. Problem: PSOD would occur when alloc()'ing NetQueue's
Cause: With the removal of the global 'disable_netq' parameters, the NetQueue CID's weren't being mapped in some cases
Change: Always map the NetQueue CID's
Impact: bnx2 VMware ESX NetQueue
bnx2 v1.9.30b (Oct 5, 2009) ======================================================= Fixes ----- 1. Problem: PSOD would occur because of TX timeouts
Cause: The VMware netdev watchdog timer was ran before the reset task got a chance to run on a loaded system.
Change: Elongated the TX timeout value for VMware ESX only to allow for the reset task to run.
Impact: bnx2 VMware ESX
Enhancements ------------
1. Change: Updated vmkernel module parameter, 'force_netq', to allow NetQueue setting to be adjusted per function rather then globally for all functions.
Impact: bnx2 VMware ESX
bnx2 v1.9.29b (Oct 1, 2009) ======================================================= Fixes ----- 1. Change: Updated xinan firmware to 5.0.0.j7 and teton firmware to 5.0.0.j4 which will fix L2 hang due to iSCSI PDU's padding byte extended to another TCP segment
Impact: 5706/5708/5709.
bnx2 v1.9.28b (Sep 25, 2009) ======================================================= Fixes ----- 1. Change: Updated firmware to 5.0.0.j6 which will add the corresponding flow control trip point.
Impact: 5709.
bnx2 v1.9.27b (Sep 24, 2009) cnic v1.9.7b (Sep 24, 2009) ======================================================= Fixes ----- 1. Problem: For the cnic users would see in the kernel logs:
Cause: The function was not taking into account the wrapping of the software and hardware producer indexes.
Change: Recaculate the difference between the index with wrapping taken into account.
Impact: cnic
Enhancements ------------
1. Change: Updated firmware to 5.0.0.j5 which increased the rxpq depth from 32 to 256 to enhance the performance on systems without flow control.
Impact: 5709.
bnx2 v1.9.26c (Sep 17, 2009) ======================================================= Enhancements ------------ 1. Change: Cleanup the VMware NetQueue code. Eliminate unneeded RX flush routine, fix the number of queues to be the same on 1500 and 9000 MTU sized packets.
Impact: bnx2 VMware NetQ.
bnx2 v1.9.26b (Sep 14, 2009) ======================================================= Fixes ----- 1. Problem: VMware PSOD on MTU change
Cause: MSI-X window was remapped to the beginning of the PCI config space. The driver would disable the bar space because the MSI-X window was remapped incorrectly. This would eventually cause a PSOD.
Change: Before the chip reset, the driver would disable MSI-X, after the chip reset, MSI-X is re-enabled.
Cause: If the driver is unable to allocate memory for the buffers, the device is not properly shutdown.
Change: Added logic to shutdown device if unable to allocate buffers and complete the setup of the device.
Impact: bnx2, changing MTU and ring sizes.
Enhancements ------------ 1. Change: Updated firmware to 5.0.0.j3 for better small packet rx performance. Firmware also fixes header digest error during I/O.
Enhancements ------------ 1. Change: If a TX timeout occurs, there could be the possiblity that the chip is hung. By printing chip state into the kernel ring buffer, it will be easier to determine this.
Impact: bnx2 iSCSI.
2. Change: The bnx2 firmware should always be matched with the proper bnx2 driver. The bnx2 firmware version string are now printed. It will be easier to identify the running firmware.
Impact: bnx2
3. Change: When a TX timeout occurs and the chip is reset, the ability to debug the chip further is lost. This is because the chip state information is lost during the reset. The users have a choice to prevent the chip reset.
Impact: bnx2
4. Change: Add a check to see if there was a KCQ overflow was in the bnx2x firmware. Now this check has been moved to the CNIC so that the driver could control the cleanup/recovery.
Impact: bnx2 iSCSI.
bnx2 v1.9.21b (July 16, 2009) ========================================================== Enhancements ------------ 1. Change: Updated firmware to 5.0.0.j2 to fix remote reset problem
Impact: bnx2 iSCSI.
bnx2 v1.9.20b (July 09, 2009), cnic v1.9.3 (July 09, 2009) ========================================================== Fixes ----- 1. Problem: (CQ42534) cnic.c does not compile on older kernels.
Cause: Some iscsi_proto constants not defined in
Change: Added the constant definitions if not already defined.
Impact: None.
Enhancements ------------ 1. Change: Updated firmware to 5.0.0.j to fix TMF releated iSCSI issues.
Cause: cnic driver sets the MSS without knowing the actual MSS option and timestamp option during TCP connection.
Change: Changed driver to set MSS to 0xffff so that firmware can calculate MSS on its own.
Impact: bnx2x iSCSI.
2. Problem: 1G iSCSI fails when initiator and target MTUs don't match and timestamp is enabled.
Cause: Firmware was not adjusting for the 12-byte timestamp option if MSS was reduced by MSS option.
Change Updated firmware to 5.0.0.i
Impact: bnx2 iSCSI.
3. Problem: (CQ42353) Unable to disable TCP timestamp on 10G iSCSI.
Cause: Timestamp was hardcoded to be enabled for 10G.
Change: Update global timestamp option during each TCP connection.
Impact: bnx2x iSCSI.
4. Problem: (CQ42329) bnx2x MC assert during IPv6 login/logout.
Cause: EQ filled with more than 128 L4 kcqes without MSI-X interrupt for 2 seconds. The driver can only buffer 128 L4 kcqes.
Change: Increased L4 kcqe buffer to 256 entries as a temporary solution. Need to understand the delayed interrupt issue.
Impact: None.
bnx2 v1.9.18b (June 25, 2009), cnic v1.9.1 (June 24, 2009) ========================================================== Enhancements ------------ 1. Change: Added FTQDiscard counter to the list of counters being reported. During small packet test, there may be FTQ overflow and this counter is very useful.
Impact: None.
2. Change: Updated firmware to 5.0.0.h to improve small packet L2 performance and to enhance iSCSI TMF handling.
Impact: 5706/5708/5709.
bnx2 v1.9.17b (June 24, 2009), cnic v1.9.1 (June 24, 2009) ========================================== Fixes ----- 1. Problem: Leaking NetQueues if the firmware did not respond in time
Cause: System might be clogged and there is not enough time to process the KCQ
Change: Updated driver/firmware to allow the calling of the free RX queue request before a RX alloc request is issued
Impact: 5709
2. Problem: An offloaded iSCSI connection would get stuck
Cause: Issing an offload request might fail, and this was not handled properly.
Change: Updated driver/firmware to return the proper return code and handle offload connection failures.
Impact: 5706/5708/5709
3. Problem: tasklet_init() is being called on a task that is scheduled
Cause: When the CNIC calls register_device(), that task might already be schedled.
Change: tasklet_disable() is insufficient because the tasklet remains scheduled and stays on the tasklet list, instead tasklet_kill() is now used.
Impact: 5706/5708/5709
bnx2 v1.9.16b (June 10, 2009), cnic v1.9.0 (June 10, 2009) ========================================================== Enhancements ------------ 1. Change: (CQ38228) Use symbol_get() for ipv6 symbols so that the cnic driver will load without necessarily loading ipv6 modules.
Impact: iSCSI over IPv6.
2. Change: Updated 5706/08/09 MIPS firmware to 5.0.0.g.
Impact: 5706/08/09.
3. Change: Backported some dma_mapping_error() checking.
2. Change: In the cnic driver, save the last allocated TCP port during unregistration so that previously used TCP ports will not be immediately re-used.
bnx2 v1.9.13b (May 18, 2009) ========================================== Fixes ----- 1. Problem: Potentially exceeding the NetQueue limit recommendations by VMware which could stress system resources
Cause: When system resources are strained.
Change: There are now limits on the number of NetQueues which the driver will request: When the MTU is 1500 the max number of queues per port is 8 When the MTU is 9000 the max number of queues per port is 4
Impact: NetQueue enabled version of VMware ESX
2. Problem: Getting conflicting NetQueue and iSCSI completions
Cause: When MSI-X is not used on a 5709, NetQueue is still enabled
Change: NetQueue is not disabled is MSI-X is not used.
Impact: NetQueue enabled version of VMware ESX
bnx2 v1.9.12b (May 13, 2009) ========================================== Fixes ----- 1. Problem: Potentially returning a negative number of NetQueues
Cause: When calculating the number of rings, we use the calculation from the number of msi-x vectors returned, The number of NetQueues returned could potentially be negitive if only 1 vector was returned. This is because the driver was subtracting 2 instead of subtracting 1 (for the default queue) from the total number of rings.
Change: Return the proper number of queues not including the default queue.
Impact: NetQueue enabled version of VMware ESX
bnx2 v1.9.11b (May 12, 2009), cnic v1.8.5 (May 13, 2009) ======================================================== Fixes ----- 1. Problem: TCP Delay ACK not working on bnx2x iSCSI
Cause: Disabled in cnic driver.
Change: Fixed csk->tcp_flags definitions and enabled the proper storm bit for delay ACK.
bnx2 v1.9.10b, cnic v1.8.4 (May 11, 2009) ========================================== Fixes ----- 1. Problem: NetQ and iSCSI do not work in Vmware environment.
Cause: 1. cnic driver is overwriting CP and COM mailbox bit values newly defined to support multiple kcqs.
2. Firmware is completing some iSCSI kcqes on the NetQ's kcq.
Change: Fixed cnic driver to only set and clear bit 0 of the CP and COM mailbox.
Firmware has been updated to 5.0.0d. This firmware also supports TCP timestamp option for iSCSI connections.
Impact: 5706/5708/5709 iSCSI, NetQ.
bnx2 v1.9.9b (May 1, 2009) ========================================== Fixes ----- 1. Problem: There is link, but can't pass traffic on ESXi
Cause: Bits in the RX context are being trampled during the renegotiation of the link.
Change: RX context offset 0x6 should only be initialized once during init and not be updated during run-time. Offset 4 contains the BIDX that's mapped to the mailbox.
Impact: VMware with NetQueue
bnx2 v1.9.8b, cnic v1.8.2 (April 27, 2009) ========================================== Enhancements ------------ 1. Change: Updated cnic driver to support 1.50.x HSI as well as the older 1.48.107 HSI. A compile flag will be used to select one or the other.
Impact: iSCSI on bnx2x.
2. Change: Spec file and Makefile changes detect the proper module install directory.
Impact: installation.
bnx2 v1.9.7b, cnic v1.8.1 (April 22, 2009) ========================================== Fixes ----- 1. Problem: Compile error with redfinition of struct kwqe.
Cause: Both the CNIC and bnx2 defined this structure.
Change: Because the bnx2 definition is L2 specific, it was renamed to struct l2_kwqe.
Impact: None.
2. Problem: Add context memory DMA alignment for 57710.
Cause: For the 57710 context memory needs to be 16k aligned. Without this alignment you will see errors when trying to establish more then 5 iSCSI connections on VMware ESX 4.0 U1.
Change: Properly aligned the context memory by allocating a bigger chunk of memory and then finding the proper alignment. This reduces the number of possible connections in half but now we can properly establish more then 5 connections on VMware.
Impact: iSCSI.
bnx2 v1.9.6b (April 17, 2009) ============================= Enhancements ------------ 1. Change: Added NetQueue support for VMware.
Impact: 5709.
bnx2 v1.9.5b (April 17, 2009) ============================= Enhancements ------------ 1. Change: Updated to 5.0.0.a firmware with NetQ support and iSCSI max connection license information. RV2P firmware unchanged: 4.6.16 for 5706, 4.6.15 for 5709.
Impact: All chips.
2. Change: Set USE_INT_PARAM on 5709. This will switch the chip in use "interrupt mode" coalescing after MSI/MSI-X.
Impact: 5709.
3. Change: Included 5706 when doing statistics block DMA workaround.
Impact: 5706.
bnx2 v1.8.8b (March 12, 2009) ============================= Enhancements ------------ 1. Change: Updated to latest 4.6.17 CP firmware for 5709.
Impact: iSCSI licensing on 5709.
bnx2 v1.8.7b, cnic v1.7.8 (March 10, 2009) ========================================== Enhancements ------------ 1. Change: Reverted 5706/5708 firmware to 4.6.16. Low latency interrupt mode does not work on 5706/5708.
Impact: None.
2. Change: VMWare changes to expose max. number of iSCSI connections in the cnic_device structure.
Cause: msi related symbols undefined because CONFIG_PCI_MSI is not enabled on Xen kernels.
Change: Added CONFIG_PCI_MSI around the msi related code.
Impact: None.
2. Problem: (CQ39818) iSCSI targets do not reconnect after running self test.
Cause: Interrupt is disabled by bnx2 before notifying CNIC to clean up and stop. As a result, bnx2i will not receive interrupts when closing the connections if sharing INTA/MSI with network.
Change: Disable interrupt after notifying CNIC to stop.
Impact: iSCSI.
bnx2 v1.8.6b, cnic v1.7.7 (March 2, 2009) ========================================= Enhancements ------------ 1. Change: Updated to new 5706 firmware (4.6.17) and 5709 firmware (4.6.16). New interrupt coalescing mode for improved latency and iSCSI cache line fix on 5709.
Cause: Bug in bnx2_free_rx_mem(). The jumbo page ring memory was freed incorrectly using the wrong local variable as array index.
Change: Fixed bug by using the correct variable as array index.
Impact: Jumbo frames.
2. Problem: (CQ38965) iSCSI connection timeout on bnx2x.
Cause: During CFC Delete RAMROD completion handling, the wrong (older) iSCSI connection ID can sometimes be retrieved using the harware CID. The CID in the mapping table was not cleared after the CID was freed.
Fix: Adding clearing of the CID in the data structure after a CID is freed.
Impact: bnx2x iSCSI.
Enhancements ------------ 1. Change: (CQ38744) Reduced R2TQ memory usage to match new firmware interface (firmware 4.8.9). This reduces the amount of kernel memory substantially for each iSCSI connection on bnx2x.
bnx2 v1.8.2b, cnic v1.7.2 (Nov 25, 2008) ======================================== Fixes ----- 1. Problem: bnx2x iSCSI does not work on functions 2 or above.
Cause: This was caused by multiple problems: a) Status block ID specified by bnx2x was wrong. b) MSI-X vector assigned to CNIC was wrong. c) New method to ack. status block using HC register was not implemented. d) Status block ID in CSTORM status block is always 0, and as a result, the status block ID used to ack. the status block was wrong.
All these problems only affect functions 2 and above.
Change: All problems fixed in bnx2x and cnic.
Impact: bnx2x iSCSI.
bnx2 v1.8.2b, cnic v1.7.1 (Nov 15, 2008) ======================================== Enhancements ------------ 1. Change: Added CNIC support for Multi function bnx2x iSCSI.
Impact: bnx2x iSCSI.
bnx2 v1.8.2b, cnic v1.6.2 (Nov 12, 2008) ======================================== Enhancements ------------ 1. Change: Updated to latest 4.6.13 5709 firmware to fix context corruption with flow control enabled.
Impact: 5709.
2. Change: Added support for 5716S PCI ID.
Impact: None.
Fixes ----- 1. Problem: (CQ35904) Netdump does not work.
Cause: Problem introduced by MSI-X multiqueue. IRQ handlers were changed to take bnx2_napi parameter instead of netdev parameter.
Change: Fixed by passing proper parameter to IRQ handler from netpoll. All IRQ handlers are called when using multiple MSI-X vectors.
Impact: 5709 netpoll.
bnx2 v1.8.1f, cnic v1.6.1 (Nov 5, 2008) ======================================== Fixes ----- 1. Problem: All TSO packets corrupted on 5706/5708.
Cause: Firmware bug zeroing the wrong field in IP header.
Change: Updated to latest 4.6.11 5706/5708 firmware and 4.6.12 5709 Firmware.
Impact: 5706/5708/5709.
2. Problem: bnx2x chip asserts when trying to make iSCSI connection to an unknown IP address.
Cause: When connection fails, the driver sends a command to an unitialized CID.
Change: Added logic to only send deletion commands to initialized CIDs.
Impact: bnx2x iSCSI.
Enhancements ------------ 1. Change: Added support for one single VLAN to a bnx2x iSCSI interface.
Impact: bnx2x iSCSI.
bnx2 v1.8.1e, cnic v1.6.0 (Oct 27, 2008) ======================================== 1. Change: Updated to latest 5709 firmware to fix iSCSI data integrity problem.
Impact: 5709.
bnx2 v1.8.1d, cnic v1.6.0 (Oct 23, 2008) ======================================== Enhancements ------------ 1. Change: Updated to latest bnx2 firmware to fix iSCSI data integrity problem.
Impact: 5706/5708/5709.
2. Change: Updated to the latest bnx2x HSI files.
Impact: bnx2x iSCSI.
bnx2 v1.8.1c, cnic v1.5.9 (Oct 13, 2008) ======================================== Fixes ----- 1. Problem: (CQ37905) Unable to compile on SLES10 SP2.
Cause: DIV_ROUND_UP macro not defined in this kernel.
Change: Added it for compatibility.
Impact: None.
Enhancements ------------ 1. Change: Updated to latest 5709 firmware that fixes an NCSI problem.
Impact: 5709.
2. Change: Handle TCP reset in the middle of TCP close more appropriately.
Impact: iSCSI.
3. Change: Handle iSCSI license checking in the same way as 5708/5709.
Impact: iSCSI on bnx2x.
bnx2 v1.8.1b, cnic v1.5.8 (Oct 13, 2008) ======================================== Fixes ----- 1. Problem: bnx2x iSCSI CIDs may be allocated outside the range of allocated host memory.
Cause: CID range bigger than the amount of allocated host context memory.
Change: Changed to match the CID range with memory range.
Impact: bnx2x iSCSI.
Enhancements ------------ 1. Change: Sync'ed with the latest upstream driver bnx2 1.8.1.
Impact: None.
2. Change: Implemented iSCSI connection license enforcement for bnx2x devices.
Impact: bnx2x iSCSI.
bnx2 v1.8.0j, cnic v1.5.7 (Oct 6, 2008) ======================================== Fixes ----- 1. Problem: (CQ37610) Chip hangs when changing MTU with active iSCSI connections.
Cause: Both cnic and bnx2 drivers setting up the chip at the same time.
Change: Added check so that the register_cnic function will fail if the bnx2 driver is in reset.
Impact: iSCSI.
2. Problem: (CQ37762) Able to unload bnx2/bnx2x drivers while there are active iSCSI connections.
Cause: CNIC driver does not have a reference count on the BNX2/BNX2X drivers.
Change: This became a problem after the register_cnic function was no longer exported. To solve the problem, the CNIC driver will now get an explicit reference during register_cnic.
Impact: iSCSI.
3. Problem: (CQ37429) MMIO access while the chip is in D3hot state.
Cause: The driver does not check if_running state consistently during ethtool operations.
Change: Added proper checks to all ethtool and multicast change functions.
Impact: ethtool operations and multicast operations.
Enhancements ------------ 1. Change: Simplified ipv4 TSO logic in the driver. This was made possible with newer 5708 firmware.
Impact: 5708 TSO and other traffic.
2. Change: ethtool -p now blinks forever. This is the standard behavior in most other net drivers.
Impact: ethtool -p.
bnx2 v1.8.0i, cnic v1.5.5 (Sep 30, 2008) ======================================== Fixes ----- 1. Problem: (CQ36787) iSCSI login/logout commands fail on 5709 after a while.
Cause: Not handling the KWQ completion properly on 5709 in INTA/MSI mode.
Change: Changed to handle KWQ completions by checking the cmd_consumer_index instead of the rx_quick_index15.
Impact: 5709 ISCSI in INTA/MSI mode.
2. Problem: (CQ37497) CNIC driver does not compile on powerpc.
Cause: csum_ipv6_magic() not defined.
Change: Added #include
Impact: None.
v1.8.0g (Sep 24, 2008) ======================== Fixes ----- 1. Problem: (CQ37511) System locks up when loading cnic driver on 2.6.16 kernel.
Cause: symbol_put_addr() in 2.6.16 tries to acquire the same lock twice.
Change: Workaround by using __symbol_put() which does not have the same problem.
Impact: None.
v1.8.0f (Sep 23, 2008) ======================== Fixes ----- 1. Problem: (CQ37405) Kernel panic when performing ifup/ifdown with iSCSI connections on bnx2x devices.
Cause: Sending searcher delete to bnx2x devices when connection was not established (due to Spanning Tree or other reasons).
Change: Check PG offload state before sending searcher delete.
Impact: iSCSI on bnx2x.
v1.8.0e (Sep 22, 2008) ======================== Enhancement ----------- 1. Change: Updated to latest driver firmware 4.6.6 for 5709.
Impact: 5709.
2. Change: Updated cnic so that it will not crash even if using older bnx2/bnx2x drivers without CNIC support. The net driver can also be loaded after cnic and it will still work without crashing.
Impact: iSCSI.
3. Change: (CQ 37381) Updated driver to check Vaux PRESET before allowing WoL. This is needed to support 5709 quad-port boards.
v1.8.0c (Aug 25, 2008) ======================== Fixes ----- 1. Problem: Does not compile on older kernels.
Cause: "__maybe_unused" undefined on older kernels. "num_online_cpus()" undefined on 2.4 kernels.
Change: Added compatibility code to workaround.
Impact: None.
v1.8.0b (Aug 25, 2008) ======================== Enhancement ----------- 1. Change: Updated to latest driver firmware 4.6.2 for 5709.
Impact: 5709.
v1.7.9c (Aug 5, 2008) ======================== Fixes ----- 1. Problem: bnx2 does not compile on older kernels.
Cause: is missing on 2.6.19 and older kernels.
Change: Added compatibility code to check for kernel version before including the file.
Impact: none.
v1.7.9b (Aug 5, 2008) ======================== Enhancements ------------ 1. Change: Added multi-tx ring for 5709. This fetaure is available on 2.6.27 kernel when using MSI-X.
Impact: 5709
2. Change: Added support for 57710 iSCSI in the CNIC driver.
v1.7.7b (July 9, 2008) ======================== Enhancements ------------ 1. Change: Added probe function so that the CNIC driver can get the pci_device pointer earlier before registration.
Impact: iSCSI.
2. Change: Added support for 5716.
Impact: None.
v1.7.6c (June 6, 2008) ======================== Enhancements ------------ 1. Change: Added multi-ring RX support on 5709 using MSI-X. This feature is only available on 2.6.24 and newer kernels running on SMP machines.
Impact: 5709.
2. Change: Added secondary unicast address support. We now support up to 5 unicast addresses. This feature is only available on 2.6.23 and newer kernels.
Impact: All chips.
v1.7.6b.1 (Aug 14, 2008) ======================== Fixes ----- 1. Problem: (CQ36808) VLAN tagged packets received by host stack without the VLAN tag.
Cause: If no VLANs are set up using vconfig, and if the driver configures the chip to strip the VLAN tag, the problem can happen. With IPMI or UMP enabled, the driver is likely to configure the chip to strip the VLAN tag.
Change: Modified the driver to re-insert the VLAN tag when necessary. I.e. when IPMI/UMP is enabled and vconfig has not setup any VLANs.
Impact: All chips receiving VLAN traffic.
v1.7.6b (May 29, 2008) ======================== Fixes ----- 1. Problem: IPv4 TSO generates bad packet when the TSO packet size is 1-MSS.
Cause: Probably firmware does not expect this boundary condition.
Change: Detect this 1-MSS condition in driver and skip the TSO logic. 1-MSS TSO packet will be treated like a regular TX checksum offload packet.
Impact: TSO on all chips.
2. Problem: Cannot disable VLAN stripping even when management firmware is disabled.
Cause: The new logic to check firmware VLAN stripping capability was buggy.
Change: Fixed the code so that VLAN stripping can always be disabled if management firmware is disabled.
Impact: VLAN/management firmware.
v1.7.5d (May 13, 2008) ======================== Enhancements ------------ 1. Change: Incorporated latest firmware 4.4.18. Bug fix is in RV2P.
Impact: All chips.
v1.7.5c (May 7, 2008) ======================== Enhancements ------------ 1. Change: Incorporated latest firmware 4.4.17. Bug fix is in RV2P.
Impact: All chips.
v1.7.5b (May 5, 2008) ======================== Fixes ----- 1. Problem: (CQ35080) Hard lock when running ethtool -s on the device that is in the down state.
Cause: I/O to the device to set link speed in D3-hot state can cause lockup because the chip does not respond to I/O.
Change: ethtool -s will just store the new settings without configuring the new speed. When the device is later brought up, the new speed will be set as part of chip init.
Impact: All chips.
2. Problem: (CQ35075 CQ35042) Various compile errors on SuSE SLES 9 and SLES 10 distro kernels.
Cause: ip_hdr() and __le32/__le32 backported to the distro kernels.
Change: Adjusted compatibility defines.
Impact: None.
Enhancements ------------ 1. Change: Incorporated latest 5709 firmware 4.4.16. Timer context scanning is reduced with this firmware to 500us. With this, the temporary enhancement in 1.7.4c #2 has been removed.
Impact: 5709 iSCSI.
v1.7.4e (April 26, 2008) ======================== Fixes ----- 1. Problem: (CQ34841) 5709 does not link up on some remote PHY systems.
Cause: No initial link interrupt.
Change: Added code to poll for link when remote PHY is present.
Impact: Remote PHY systems.
2. Problem: (CQ34767) Kernel panic on 5709 when using jumbo frames with NCSI traffic.
Cause: RV2P bug causing RX packets to overwrite kernel memory.
Change: Updated to latest RV2P code for 5709 and 5708.
Impact: 5706/5708/5709.
v1.7.4d (April 17, 2008) ======================== Fixes ----- 1. Problem: IPv6 iSCSI does not work.
Cause: Added code in the last version 1.7.3c to check for CONFIG_IPV6 before enabling the IPv6 CNIC support. This failed to check for CONFIG_IPV6_MODULE if IPv6 is configured as module in the kernel configuration.
Change: Changed the checking to CONFIG_IPV6 or CONFIG_IPV6_MODULE.
Impact: None.
v1.7.4c (April 16, 2008) ======================== Fixes ----- 1. Problem: (CQ34814, CQ33984) Driver does not compile on 2.4 kernels.
Cause: __le32 and __be32 not defined in 2.4 kernels.
Change: Defined these as u32 on 2.4 kernels.
Impact: 2.4 kernels.
Enhancements ------------ 1. Change: Incorporated latest 5709 4.4.12 firmware to fix various iSCSI problems.
Impact: 5709.
2. Change: Slowed down the timer block reload time. It was noticed that after the CNIC driver was unloaded, the timer context memory was reloaded in a tight loop by the chip. This issue needs to be properly addressed in the firmware at a future date.
Impact: iSCSI.
v1.7.4b (April 11, 2008) ======================= Enhancements ------------ 1. Change: Incorporated latest 5709 4.4.11 firmware to fix various iSCSI problems.
Impact: 5709.
v1.7.3k (April 9, 2008) ======================= Enhancements ------------ 1. Change: Incorporated latest 5709 4.4.10 firmware to fix various iSCSI problems. CID ranges are now read directly from shared memory.
v1.7.3g (March 10, 2008) ======================= Enhancements ------------ 1. Change: Updated to latest 5709 firmware version 4.4.7.
Impact: 5709.
v1.7.3f (March 10, 2008) ======================= Fixes ----- 1. Problem: CNIC takes a long time to resolve ARP, causing iSCSI to fail.
Cause: NETEVENT_NEIGH_UPDATE event notifier sometimes takes a long time to be called.
Change: This is under investigation. For now, the workaround is to use the existing neighbour entry if it is in NUD_VALID state. Previously, we would only use it if it was in NUD_CONNECTED state.
Impact: iSCSI neighbour resolution.
2. Problem: iSCSI sometimes fails to initialize.
Cause: The KWQ is in full condition and prevents any KWQE to be sent to the firmware. This is caused by the KWQ consumer index in the status block not initializing to 0.
Change: Added workaround to skip the KWQ full condition check when sending the first KWQE. This should be properly fixed in firmware.
Impact: None.
v1.7.3d (February 15, 2008) ============================ Fixes ----- 1. Problem: System hangs with iSCSI traffic.
Cause: Infinite loop in NAPI poll.
Change: Fixed the problem of not comparing the CNIC tag properly when determining whether there is more work in NAPI poll.
Impact: None.
2. Problem: iSCSI does not work on 5709
Cause: Not initializing 5709 properly for iSCSI. The chip_id field was not propagated to the CNIC driver.
Change: Fixed the chip_id field.
Impact: None.
v1.7.3c (February 09, 2008) ============================ Enhancements ------------ 1. Change: Updated 5708 and 5709 firmware to version 4.4.2.
Impact: All devices.
2. Change: Updated RV2P firmware to the latest. This may fix the jumbo frame issue.
Impact: All devices, especially jumbo frames on 5709 Bx.
3. Change: Modified CNIC interface in preparation for 57710 devices.
Impact: iSCSI.
v1.7.2f (February 04, 2008) ============================ Fixes ----- 1. Problem: Temporary workaround for one prototype 5709S mezz. card not working.
Cause: The driver was looking at the wrong shared memory location to identify the card.
Change: Fixed the code to check the correct BNX2_SHARED_HW_CFG_CONFIG location.
2. Change: Added temporary workaround for one prototype 5709S mezz. card. The workaround will be removed once newer cards are available.
Impact: 5709S.
v1.7.1e (January 14, 2008) ============================ Enhancements ------------ 1. Change: Updated 5709 firmware to 4.1.1 for IPv6 iSCSI support.
Impact: 5709.
2. Change: Updated 5708 RXP firmware to 4.1.1.
Impact: 5706/5708.
3. Change: Updated RV2P firmware for 5709.
Impact: 5709.
4. Change: Added IPv6 support to CNIC driver.
Impact: New BNX2I driver must be used with this new CNIC driver.
v1.7.1d.3 (February 7, 2008) ============================ Fixes ----- 1. Problem: 5706S continues to not link down occasionally on some blade systems.
Cause: In some cases, even turning off the tx current does not cause the link to go down.
Change: Link transition can be triggered based on the SYNC_FAILED bit in the AN_DEBUG register when all else fails.
Impact: 5706S.
v1.7.1d.1 (February 1, 2008) ============================ Fixes ----- 1. Problem: 5706S still not linking down occasionally on some blade systems when the switch blade is disconnected.
Cause: Occasionally, all the bits that we check will falsely indicate link up and trigger the parallel detect logic on this blade platform. Once in parallel detect mode with autoneg disabled, the driver will never detect link down.
Change: Disabled parallel detect on this platform by checking PCI sub IDs to identify the device.
Impact: Parallel detect not supported on this vendor device.
v1.7.1d (January 25, 2008) ============================ Fixes ----- 1. Problem: 5706S still not linking down on some blade systems when the switch blade is disconnected.
Cause: This is the same problem that was fixed in 1.7.0b. After switch module is removed, the SYNC_FAILED bit sometimes toggles low, and this causes the parallel detect logic in the driver to trigger and disable autoneg. Disabling autoneg causes false link to come up immediately.
Change: It seems that the RUDI_INVALID bit can be used to prevent the above from happening. Modified parallel detect code to additionally check the RUDI_INVALID bit and trigger only when the bit is cleared.
Impact: Parallel detect logic in 5706S.
v1.7.1c (December 27, 2007) ============================ Fixes ----- 1. Problem: Driver crashes when adding VLAN and bonding.
Cause: Bonding calls driver's VLAN function in interrupt context with lock held. We recently added a VLAN feature in 1.6.8b which requires chip reset when VLANs are added or removed. The reset will call vmalloc/vfree which must not be called in interrupt context.
Change: Reverted the VLAN feature for now. Will workaround it in the future.
Impact: 5709 only. This new VLAN feature is no longer available.
v1.7.1b (December 24, 2007) ============================ Fixes ----- 1. Problem: Driver crashes when using jumbo frames on 5709 A1.
Cause: RV2P firmware problem.
Change: Disabled jumbo page ring on 5709 Ax chips.
Impact: Jumbo receive page rings not supported on 5709 Ax.
2. Problem: CNIC driver prints "Failed waiting for ref count to go to zero" when unloading the driver. This is a minor cosmetic issue.
Cause: Minor bug in driver comparing ref_count to 1 instead of zero during exit.
Change: Fixed the code to check for ref_count == 0.
Impact: None.
v1.7.0b (December 12, 2007) ============================ Fixes ----- 1. Problem: (CQ33032) CPU utilization increases dramatically when TSO is enabled.
Cause: Driver is spending a lot of unnecessary time in TX handling code when TSO is enabled. This regression was introduced when the TX handling code was changed to match the RX handling code. The RX handling code was changed to fix a packet rot problem. When TSO is enabled, the tx index can stop at non-packet boundaries and the code will keep waiting until it gets to the next packet boundary.
Change: Fixed it to handle this condition properly.
Impact: None.
2. Problem: 5706S does not link down in some blade systems.
Cause: Hardware problem.
Change: Added workaround logic to check periodically and force a link down when the PHY reports SYNC status failed. This only works when autoneg is enabled.
Impact: 5706S.
v1.6.8e (December 10, 2007) ============================ Fixes ----- 1. Problem: When using jumbo MTU with large RX ring sizes, system will crash or the driver won't load.
Cause: Bug in driver where the page descriptor array was declared too small.
Change: Fixed the array size.
Impact: None.
2. Problem: CNIC driver won't compile on kernels without CONFIG_PCI_MSI.
Cause: Some code needs to be conditionally compiled only when CONFIG_PCI_MSI is set.
Change: Added #ifdef CONFIG_PCI_MSI where necessary.
Impact: None.
3. Change: Disabled iSCSI on 5709 until next release.
Impact: None.
v1.6.8d (December 07, 2007) ============================ Change: Reverted the 5706S workaround made in 1.6.8c because it was unreliable.
Cause: RV2P firmware incorrectly placed jumbo data into SKB.
Change: New RV2P firmware.
Impact: Jumbo frames on all hardware.
2. Problem: (CQ32817) ethtool loopback test fails. 3. Problem: (CQ32842) Chariot test fails.
Cause: RX buffer size too small to contain MTU-sized frame. This was introduced by the new Jumbo RX logic.
Change: Fixed RX buffer size logic.
Impact: Traffic on all hardware.
4. Problem: (CQ32862) Fails to compile on RH9u9.
Cause: Kernel API skb_fill_page_desc() backported to RH kernel causing duplicate definition.
Change: Adjusted compatibility code.
Impact: None.
5. Problem: (CQ32866) ISCSI driver fails to compile with 1.6.8b.
Cause: print_mac() multiply defined when bnx2.h is included in the bnx2i driver.
Change: Changed print_mac() to static inline.
Impact: None.
6. Problem: 5706S does not link down in some blade systems.
Cause: Hardware problem.
Change: Added workaround logic to check periodically.
Impact: 5706S.
Enhancements ------------ 1. Change: Added flow control logic on 5709.
Impact: 5709.
2. Change: Updated all firmware to 4.0.5.
Impact: All hardware.
v1.6.8b (November 28, 2007) ============================ Enhancements ------------ 1. Change: Added MSIX support for 5709 B0.
Impact: 5709 B0.
2. Change: Added multi-page buffer support for Receive Jumbo frames.
Impact: All chips. This feature is experimental at this point.
3. Change: Allow VLAN tags in receive packets when management firmware is enabled.
Impact: 5709 only. This feature is experimental and requires new boot code and UMP/IPMI code.
4. Change: Updated firmware to 4.0.3.
Impact: All chips.
v1.6.7b (October 16, 2007) ============================ Fixes ----- 1. Problem: (CQ31861) Remote copper PHY does not link up if WoL is enabled.
Cause: bnx2_set_power_state() assumes that only copper devices support WoL and proceeds to configure the copper PHY to 10/100 Mbps. This assumption is no longer valid after Serdes WoL support was added in 1.6.3c.
Change: Fixed the code to take check for Serdes and copper when setting up the PHY for WoL.
v1.6.5b (September 25, 2007) ============================ Fixes ----- 1. Problem: (CQ30086) 5709 A1 does not link up when connected to some Broadcom devices.
Cause: Early DAC wakeup workaround needed for 5709 A1.
Change: Added workaround.
Impact: None.
Enhancements ------------ 1. Change: Added CNIC support for iSCSI.
Cause: Link test and loopback test were not modified to support remote PHY.
Change: Added remote PHY support to link test and changed the code to skip PHY loopback on remote PHY since it's not supported.
Impact: None.
2. Problem: (CQ30625) ethtool speed settings are lost after ifdown.
Cause: The remote PHY settings stored in firmware is not the same as the driver's last setting.
Change: Modified the code to keep the driver's setting unless there's is change in the remote PHY media.
Impact: ethtool -s on remote PHY systems.
Enhancements ------------ 1. Change: Change ethtool's wol setting to NVRAM's default and add support for Serdes WoL if NVRAM supports it.
Impact: ethtool wol's default setting.
v1.6.3b (July 13, 2007) ======================= 1. Problem: Problems reading and writing flash on 5709.
Cause: Hardware changes in 5709.
Change: Rearranged current flash code to properly support 5709.
Impact: Changes will impact flash operations on 5706/5708/5709 devices.
2. Problem: (CQ30516) Management firmware version string disappears on 2nd modprobe of the driver.
Cause: The 2nd modprobe will program the device back to D0 from D3hot. This causes a reset and it will take some time before the management firmware information will be available.
Change: Added a proper wait loop to wait for the firmware information to be deposited in shared memory.
Impact: None.
v1.6.2f (July 3, 2007) ======================= 1. Problem: The fix for CQ29488 in the previous version is problematic and needs to be reverted.
Cause: Adding the netif_carrier_off() call before register_netdev() in bnx2_init_one() can cause problems if register_netdev() fails. netif_carrier_off() can queue a link watch event that can run later. If register_netdev() fails, the netdev structure will be freed and the link watch event may panic when it is scheduled to run.
Change: Moving the netif_carrier_off() to after register_netdev() also will not work as it can cause race conditions with the interrupt handler. So the best thing to do is to revert the earlier fix and not address the CQ29488 issue.
Impact: CQ29488 is not fixed.
v1.6.2e (July 3, 2007) ======================= Fixes: ------ 1. Problem: (CQ29528) Link does not come up using remote PHY (continued).
Cause: ifup script may be using mii-tool to obtain link status, and interfering with remote PHY firmware.
Change: Block mii-tool ioctl access when remote PHY firmware is present.
Impact: None.
2. Problem: (CQ29488) Driver reports link up in ethtool before the interface is brought up.
Cause: The netdevice structure's initial link setting is up and that gets reported directly by ethtool.
Change: Added netif_carrier_off() call in bnx2_init_one().
Impact: None.
v1.6.2d (June 22, 2007) ======================= Fixes: ------ 1. Problem: (CQ29528) Link does not come up using remote PHY.
Cause: The fix in 1.6.2b still has a problem. The copper or Serdes default link setting does not follow the correct port when the port is changed during chip reset.
Change: Fix the code to always refresh the port and link setting during chip reset.
Impact: None.
2. Problem: (CQ30181) Cannot compile on 2.4 kernels.
Cause: USEC_TO_SEC constant is not defined on older kernels.
Change: Added conditional #define for this constant on older kernels.
Impact: None.
Enhancements: ------------- 1. Change: Update 5709 firmware to 3.7.1.
Impact: 5709 devices.
v1.6.2b (June 21, 2007) ======================= Enhancements: ------------- 1. Change: Added management firmware version to ethtool -i.
Impact: None.
Fixes: ------ 1. Problem: (CQ29528) Link does not come up using remote PHY.
Cause: The driver is using the wrong port when setting up the remote PHY link.
Change: Fixed bug to always use the correct requested port or default port when setting remote PHY link.
Impact: None.
2. Problem: (CQ30028) Advertised Autoneg not set in ethtool.
Cause: Remote PHY code is not setting the flag which is for information only.
Change: Added code the set the flag for consistency.
Impact: None.
v1.6.1c (May 22, 2007) ===================== Enhancements: ------------- 1. Change: (CQ28907) Added support for setting copper and fibre speeds.
v1.5.10c (May 4 , 2007) ======================= Fixes: ------ 1. Problem: Extremely low TSO performance when destination has a smaller MSS than the source.
Cause: Packets smaller than MTU are not processed as TSO packets.
Change: Removed the SKB length check when doing TSO.
Impact: None.
v1.5.10b (May 1, 2007) ========================= Enhancements: ------------- 1. Change: Removed Remote PHY until next release.
Impact: No Remote PHY support.
2. Change: Added check for 2.5G capability before enabling 2.5G on 5709S.
Impact: None.
Fixes: ------ 1. Problem: (CQ28438) NETDEV WATCHDOG after OS boot.
Cause: The mailbox queue is halted after the OS reads config. register 0x94.
Change: Set MQ_CONFIG_HALT_DIS in register MQ_CONFIG on 5709 A0 and A1.
Impact: None.
v1.5.9b (April 20, 2007) ======================= Enhancements: ------------- 1. Change: Enhanced remote PHY support for 5708S.
Impact: None.
Fixes: ------ 1. Problem: (CQ29056) Driver does not compile on SLES 10 SP1 kernel.
v1.5.1b (November 15, 2006) =========================== Enhancement: ------------ 1. Change: Added support for 5709.
Impact: None.
v1.4.52c (March 07, 2007) ========================= Enhancement: ------------ 1. Change: Increase maximum receive ring size to 4080. The default is kept the same at 255.
Impact: None.
v1.4.51b (December 21, 2006) ============================ Fixes: ------ 1. Problem: (CQ27802) Cannot enable flow control in some cases.
Cause: In some cases when flow control is forced to on, the driver detects no changes in advertisement, and as a result, will not re-autoneg. Without the link change, flow control settings will not change.
Change: Added some code to setup flow control when no other PHY settings are made. This will ensure that flow control changes will take effect immediately.
Impact: None.
v1.4.50b (December 15, 2006) ============================ Fixes: ------ 1. Problem: (CQ27424) Panic when writing to nvram.
Cause: Bug in driver when an alignment buffer is used
Change: Fixed the bug so that the alignment buffer is freed with the correct pointer.
Impact: None.
v1.4.49b (December 13, 2006) ============================ Fixes: ------ 1. Problem: (CQ27459) Driver reports link down when link is up.
Cause: Hotplug scripts can cause bnx2_open() to be called immediately after bnx2_init_one() calls register_netdev(). The initial link state set after register_netdev() may overwrite the actual link state set by the link handler on SMP systems.
Change: Move all initial state setup code to before calling register_netdev().
Cause: Bug in determining tx ring space when the tx ring is completely full.
Change: Fixed the flawed logic in bnx2_tx_avail().
Impact: None.
2. Problem: (CQ27424) Buffer overflow when writing to nvram.
Cause: Bug in driver when the beginning NVRAM offset is not 4-byte aligned.
Change: Fixed the bug to allocate enough buffer space.
Impact: None.
3. Problem: (CQ27543) Loopback failed if MAC address is changed.
Cause: Driver uses permanent MAC address for loopback which may be different from a locally administered address.
Change: Fixed by alwaysing using the current MAC address in the netdevice structure.
Impact: None.
v1.4.47b (November 02, 2006) =========================== Fixes: ------ 1. Problem: (CQ25922) 5708S does not pass PHY loopback test on some blade servers.
Cause: It takes longer (about 100msec) to link up in some backplane environments when the Serdes is set to PHY loopback mode.
Change: Increase delay loop to up to 1 sec when waiting for link up after PHY loopback. Previous wait time was 100usec.
Impact: None.
v1.4.46b (October 30, 2006) =========================== Fixes: ------ 1. Problem: (CQ25916) Device does not receive packets when configured by the Xen bridge script and when IPMI is enabled.
Cause: Firmware does not forward packets to the host when the device is in promiscuous mode in some cases.
Change: Firmware change and driver change to enable the BNX2_RPM_SORT_USER0_PROM_VLAN bit when going into promiscuous mode.
Impact: None.
v1.4.45b (October 19, 2006) =========================== Enhancement: ------------ 1. Change: Added software parallel detection on 5708S to link at 1000Mbps or 2500Mbps automatically if the link partner is forced at 2500Mbps.
Impact: None.
2. Change: Added 2500Mbps forced speed setting. Setting it requires a future version of ethtool or custom apps.
Impact: None.
3. Change: Port driver to compile on 2.6.19 kernel.
Impact: None.
Fixes: ------ 1. Problem: Driver does not complile on 2.4 kernels.
Cause: TSO symbols not defined in 2.4 kernels.
Change: Added #ifdef for compatibility.
Impact: None.
2. Problem: MSI doesn't work on 5706 when the host bridge is AMD8132.
Cause: Compatibility issue.
Change: Added code to disable MSI when 5706 is on a systems with AMD8132.
Impact: 5706 cannot use MSI on such systems.
v1.4.44b (August 10, 2006) ========================== Fixes: ------ 1. Problem: A rare tx race window exists in the tx path.
Cause: CPU re-ordering can cause the tx queue to be stopped forever when the tx ring is full in a very rare condition. See ChangeLog for more details.
Change: Fixed the race condition with memory barriers. See ChangeLog for more details.
Impact: None.
Enhancement: ------------ 1. Change: Increase default rx ring size to 255 to prevent packet drops under heavy load.
Impact: Higher memory usage.
2. Change: Port driver to run on 2.6.18 kernel.
Impact: None.
v1.4.43b (June 26, 2006) ======================= Enhancement: ------------ 1. Change: (CQ25508) Use DRV_MSG_CODE_UNLOAD_LNK_DN message on 5708 B1 and older chips so that the link will turn off after ifdown.
Impact: None.
v1.4.42b (June 2, 2006) ======================= Fixes: ------ 1. Problem: (CQ22585) WoL cannot be enabled on 5708 B2.
Cause: Hardware limitation in previous 5708 versions required driver to always disable driver WoL on 5708.
Change: With the issue fixed in B2, the driver was changed to allow 5708 B2 and above to support driver WoL.
Impact: None.
2. Problem: (CQ21779) Driver does not report dropped receive packets.
Cause: Packets dropped by firmware are reported in a scratch pad location in memory separate from other counters.
Change: Added code to report this firmware counter.
Impact: None.
Enhancements: ------------- 1. Change: (CQ24690) Allow driver to be compiled for non-running kernels.
Impact: None.
v1.4.41b (May 17, 2006) ======================= Fixes: ------ 1. Problem: Driver writes wrong data to non-buffered flash.
Cause: Bug in driver causing the unchanged portion of the page to be corrupted.
Change: Fixed bug.
Impact: None.
v1.4.40b (April 17, 2006) ========================= Enhancements: ------------- 1. Change: Combine 2 small memory allocations into 1.
Impact: None.
2. Change: Separate tx consumer and producer entries into separate cache lines for better performance.
Impact: None.
3. Change: Compress firmware data to reduce driver size.
Impact: Driver now requires zib_inflate library which should be available on most vendor kernels.
v1.4.39b (Mar. 10, 2006) ======================= Fixes: ------ 1. Problem: (CQ23181) Driver loses track of link changes in some cases.
Cause: In some cases, the status block gets a link change indication that contradicts with the MII link status. This is due to transient link signals during link changes.
Change: Add coalesce_now at the end of link change interrupt to flush out the transient behavior.
Impact: None.
2. Problem: 5708 only supports 40-bit DMA addresses.
Cause: Limitation of the built-in PCIE-to-PCIX bridge.
Change: Add workaround code to make sure all DMA addresses are less than 40 bits.
Impact: Some minor impact on performance on some 64-bits systems. There should be practically no performance impact on i386 and x86_64 systems.
3. Problem: "Copyright" deprecated in RPM spec file.
Change: Changed to "License".
Impact: Should be none on the distributions that we support.
v1.4.38b (Feb. 10, 2006) ======================= Fixes: ------ 1. Problem: Setting rx ring size to 255 causes memory allocation errors.
Cause: Multiple bugs that do not handle the full ring properly.
Change: Fixed all bugs related to full ring handling and changed maximum ring size from 4080 to 1020 after discussion with Dave Miller.
Impact: Maximum rx ring size is now smaller.
2. Problem: Compile warnings and panic on IA64.
Cause: not included.
Change: Added include .
Impact: None.
v1.4.36b (Jan. 19, 2006) ======================= Version number update.
v1.3.36 (Jan. 17, 2006) ======================= Fixes: ------ 1. Problem: (CQ22827) bnx2 does not compile on 2.6.6 and earlier kernels.
Cause: Introduced bug while fixing CQ22666.
Change: Fix compatibility code.
Impact: None.
2. Problem: (CQ22823) bnx2 reports extra .5 at the end of firmware version string.
Change: Skip the last digit in the firmware version string.
Impact: None.
3. Problem: (CQ22585) WoL still does not work on 5708.
Cause: New WoL mechanism introduced in 1.3.34 has a flaw.
Change: Removed the workaround code and disabled WoL support on 5708. During shutdown and suspend, the driver will shutdown the device and WoL will be setup by the bootcode according to the nvram's out-of-box WoL setting.
Impact: 5708 will not support driver-initiated (ethtool-intiated) WoL.
v1.3.35 (Jan. 17, 2006) ======================= Fixes: ------ 1. Problem: (CQ22666) bnx2 driver does not compile on RHEL3 U7.
Cause: if_mii() back-ported to RHEL3 U7.
Change: Adjusted the compatibility code.
Impact: None.
2. Problem: (CQ22718) UMP connection is lost after enabling WoL.
Cause: FORCE LINK was mistakenly set during WoL setup.
Change: Do not set FORCE LINK.
Impact: None.
v1.3.34 (Jan. 13, 2006) ======================= Fixes: ------ 1. Problem: (CQ22585) WoL does not work on 5708.
Cause: Internal bridge not in proper PME state.
Change: Added new firmware message to allow bootcode to help set up WoL.
Impact: None.
Enhancements: ------------- 1. Change: Added compile option to include crc32 function for RH2.4 boot kernels.
Impact: None.
2. Change: Updated TSO firmware to handle ECN.
Impact: None.
v1.3.33 (Dec. 12, 2005) ======================= Enhancements: ------------- 1. Change: Increased firmware hand-shake timeout from 50 msec to 100 msec. Also changed the delay from busy-wait udelay to non-busy-wait msleep.
Impact: None.
2. Change: Added code to read nvram size from shared memory if available. Otherwise, the size will come from the flash table which only gives the smallest size for that type of flash.
Impact: None.
3. Change: Added workaround to issue 2 separate IOs for interrupt acknowledgement. The workaround is only used for INTA (non-MSI) interrupts.
Impact: Slightly higher overhead for INTA interrupts.
v1.3.32 (Dec. 01, 2005) ======================= Enhancements: ------------- 1. Change: Added PHY loopback to the loopback selftest.
2. Change: Enabled customized pre-emphasis and other serdes control settings on 5708S backplane devices. A special PHY register will be programmed according to the NVRAM value.
Impact: None.
3. Change: Modified Makefile to check for the source symbolic link in the kbuild environment.
Impact: None.
4. Change: Improved NAPI poll processing so that all events will be processed before interrupts are re-enabled. This will reduce the number of unnecessary interrupts.
Impact: None.
5. Change: Add support for ETHTOOL_GPERMADDR (from John Linville)
Impact: None.
Fixes: ------ 1. Problem: Bug in irq handler causing extra register read.
Cause: Bug in bnx2_interrupt() reading BNX2_PCICFG_MISC_STATUS register when it is not necessary.
Change: Fixed the logic bug and added prefetch of status block in msi handler.
Impact: None.
v1.3.25 (Aug. 22, 2005) ======================= Fixes: ------ 1. Problem: Ethtool register and memory tests fail on 5708.
Cause: Some code was not merged properly many versions ago.
Change: Merged in properly code.
Impact: None.
Enhancements: ------------- 1. Change: Slow down flash clock speeds
Impact: None.
2. Change: Code re-sync'ed with upstream driver.
Impact: None.
v1.3.24 (Aug. 16, 2005) ======================= Enhancements: ------------- 1. Change: Changed all spin_lock_irqsave locks to spin_lock_bh for better overall system performance. All code requiring spin_lock runs in BH or user context.
Impact: None.
2. Change: Removed atomic operations in the transmit fast path. Code should run a bit faster as atomic operations can be quite slow.
Impact: None.
v1.3.23 (Aug. 10, 2005) ======================= Enhancements: ------------- 1. Change: Added reporting of link speed to firmware.
Impact: None.
2. Change: Added shared memory base look-up.
Impact: None.
3. Change: Possible sparse fixes (from Peter Hagervall) - use C99 struct initializers - make a few arrays and structs static - remove a few uses of literal 0 as NULL pointer - use convenience function instead of cast+dereference in bnx2_ioctl() - remove superfluous casts to u8 * in calls to readl/writel
Impact: None.
4. Change: Updated documentation with the crc32 library requirement and other minor updates.
Impact: None.
v1.3.22 (July 25, 2005) ======================= Enhancements: ------------- 1. Change: Added check for default link speed setting in shared memory. This allows some blade servers that don't support autoneg to default to forced speed to speed up link-up time.
Impact: None.
2. Change: Changed timer code to speed up the timer after serdes autoneg. This speeds up the time for parallel detection when the link partner does not autoneg. After autoneg or parallel detction completes, timer goes back to normal 1 HZ interval. With the new scheme, link should be detected up using parallel detection in less than 0.7 seconds. Autoneg normally completes in 120 msec exchanging base pages and 3 next pages.
Impact: None.
v1.3.21 (July 21, 2005) ======================= Enhancements: ------------- 1. Change: Updated firmware to properly handle TSO packets with ECN bits set.
Impact: None.
2. Change: Updated to latest rxp firmware.
Impact: None.
3. Change: Added check for the 2.5G capability in shared memory.
Impact: None.
4. Change: Expanded nvram support for 5708.
Impact: None.
Fixes: ------ 1. Problem: (CQTO1511) Downing a team of bnx2 adapters causes hang.
Cause: Deadlock when the second adapter's close routine calls flush_scheduled_work() because the linkwatch_event is scheduled on the work queue when the first adapter is closed. The linkwatch_event will try to get the rtnl_lock which is already held by the bnx2_close routine.
Change: Fixed by not calling flush_scheduled_work(). Instead, use a flag to indicate work is pending and wait until the flag is cleared.
Impact: None.
2. Problem: (CQTO1439) ethtool -S on 5708 causes oops.
Cause: A pointer is not initialized if the device is 5708.
Change: Added proper initialization.
Impact: None.
3. Problem: Some error counters are mis-reporting.
Cause: The workaround for the hw errata is not applied properly on the chips with the errata.
Change: Added proper checks for the workaround.
Impact: None.
4. Problem: High BER on 5708 SerDes.
Cause: hardware errata.
Change: Added workaround for 5708 A0 and B0.
Impact: None.
v1.3.19 (May 27, 2005) ======================= Enhancements: ------------- 1. Change: Merged 5708 code with the latest 1.1.19.
Impact: None.
Fixes: ------ 1. Problem: (CQTO1260) 5708S does not link at 1000Mbps when forced. It links at 2500Mbps when connected back-to-back with another 5708S.
Cause: 2.5G bit is still turned on.
Change: Fixed by turning off 2.5G when the speed is forced.
Impact: None.
v1.1.19 (May 26, 2005) ======================= Enhancements: ------------- 1. Change: Made significant changes to merge into the kernel. Among them, consolidate all source files into bnx2.[ch] and bnx2_fw.h, change structure style register definitions to offset based.
Impact: None.
Fixes: ------ 1. Problem: Excessive stack usage.
Cause: Use of local variable array.
Change: Fix excessive stack usage in bnx2_alloc_bad_rbuf() by replacing local variable array with kmalloc array. Also changed function to return error code, and changed some of the callers to check for the return code.
Impact: None.
2. Problem: Bug in receive checksum.
Cause: Software bug.
Change: Fix bug in rx checksum by indicating CHECKSUM_UNNECESSARY only when the hw calculated checksum is 0xffff.
Impact: None.
3. Problem: Excessive busy loop.
Cause: Software bug.
Change: Replaced one excessive udelay of 15msec with msleep since the calling context is always process.
Impact: None.
4. Problem: Need to call flush_scheduled_work() and bnx2_netif_stop().
Cause: Bug in bnx2_close().
Change: Fix bug in bnx2_close() by calling flush_scheduled_work() since we are using a work queue in netdev watchdog. Also added bnx2_netif_stop() call in bnx2_close().
Impact: None.
5. Problem: Some symbols do not have bnx2 prefix and are not static.
Change: Add bnx2_ prefix to some remaining names and mark some remaining names static.
Impact: None.
v1.1.17 (Apr. 7, 2005) ======================= Fixes: ------ 1. Problem: Driver does not compile on 2.6.12 kernel.
Cause: pci_dev->slot_name has been deprecated.
Change: replaced with pci_name.
Impact: None. All kernels supported by bnx2 including 2.4.21-*EL have pci_name defined.
v1.1.16 (Mar. 16, 2005) ======================= Fixes: ------ 1. Problem: (CQTO936 & 1004) Tx carrier and rx_byte_errors reported during normal operations.
Cause: 5706 hardware errata on these 2 statistics counters.
Change: Modified driver to skip these 2 counters.
Impact: These 2 counters will always report 0 and not the true statistics.
v1.1.15 (Mar. 09, 2005) ======================= Enhancements: ------------- 1. Change: Added code to program proper phy settings for jumbo frames on copper and serdes devices.
Impact: None.
2. Change: Changed INTx ISR to handle a valid case where INTx arrives before status block update.
Impact: None.
3. Change: Added a separate ISR for MSI to handle subtle differences between INTx and MSI.
Impact: None.
v1.1.14 (Mar. 03, 2005) ====================== Fixes: ------ 1. Problem: netdump does not work on latest RH3EL errata kernel.
Cause: #define RED_HAT_LINUX_KERNEL removed from kernel include files, causing netdump poll function to be compiled wrong for RH kernels.
Change: Changed Makefile to workaround the problem.
Impact: None.
v1.1.12 (Feb. 25, 2005) ====================== Fixes: ------ 1. Problem: (CQTO1062) Driver allows ethtool to set illegal speed/duplex on fiber cards.
Cause: Missing checks for the case where autoneg is off.
Enhancements: ------------- 1. Change: The code to handle tx queue full condition was redone to properly handle all boundary and race conditions.
Impact: Minimum tx ring size is now MAX_SKB_FRAGS+1.
2. Change: Tx timeout code was changed to work queue context. This allows netif to be shutdown gracefully before chip reset.
Impact: None.
3. Change: Added memory barriers to ISR and NAPI poll for correctness.
Impact: None.
v1.1.8 (Feb. 01, 2005) ====================== Fixes: ------ 1. Problem: (CQTO969) No interupts on a system that does not support MSI.
Cause: On this system, the MSI generated in the MSI test terminates with Master Abort which is a fatal condition for the chip.
Change: A chip reset is added when MSI test fails to bring the chip back to normal operations again (in INTx mode).
Impact: None.
Enhancements: ------------- 1. Change: Removed register 0x84 from the ethtool register test. This is an interrupt control register that should not be touched to prevent unwanted interrupts.
Impact: None.
v1.1.7 (Jan. 28, 2005) ====================== Enhancements: ------------- 1. Change: Added interrupt test when MSI is enabled. If MSI test fails, driver will fallback to INTx mode.
Impact: None.
2. Change: Added test for certain chipsets where MSI is known to fail, and disable MSI unconditionally when such chipsets are found.
Impact: None.
3. Change: Removed support for 1000 Mbps half duplex.
Impact: 1000 Mbps half duplex will no longer work.
v1.1.6 (Jan. 26, 2005) ====================== Fixes: ------ 1. Problem: (CQTO940) MTU size not set properly when device is down.
Cause: bnx2_change_mtu only handled the "up" case.
Change: Simple fix to handle the "down" case as well.
Impact: None
2. Problem: (CQTO926) 5706S does not autoneg properly after the tx cable is pulled.
Cause: If the link partner is autonegotiating, autoneg will fail when the tx cable is pulled. The software will turn off autoneg seeing that the rx cable is still attached with SIGNAL_DETECT. When the tx cable is re-attached, autoneg is still off and the link partner will not establish link.
Change: Added code to poll another PHY register to check if configs are received when autoneg is disabled.
Impact: None
Enhancements: ------------- 1. Change: Added OEM product name strings.
Impact: None.
v1.1.5 (Jan. 25, 2005) ====================== Fixes: ------ 1. Problem: PCI-X bus speed may not be detected correctly by the driver, causing failure because certain register settings are done based on bus speed.
Cause: hardware problem.
Change: Use a different register to detect PCI-X speed.
Impact: None.
v1.1.4 (Jan. 17, 2005) ====================== Fixes: ------ 1. Problem: 5706S does not reliably detect link up or down.
Cause: hardware problem.
Change: Enabled hardware workaround which is effective in A2 and newer chips only.
Impact: None.
v1.1.3 (Jan. 13, 2005) ====================== Fixes: ------ 1. Problem: netdump does not work.
Cause: poll_controller routine does not work in NAPI mode.
Change: Fixed poll_controller routine for NAPI mode.
Impact: None.
Enhancements: ------------- 1. Change: Added the new mmiowb macro which is used mainly in NUMA machines to guarantee PCI ordering.
Impact: None.
2. Change: Added OEM product name strings.
Impact: None.
3. Change: Changed ONE_TDMA workaround on systems with P64H bridge to PING_PONG_DMA on all systems using PCI.
Impact: Better performance and better compatibility on all PCI systems.
4. Change: Added "disable_msi" parameter to allow disabling MSI.
Impact: None.
5. Change: Reduced default tx coalescing parameters for better tx only performance such as ttcp.
Impact: None.
6. Change: Changed NIC detection console message to display more information.
Impact: None.
7. Change: Cleaned up some Linux .h files that are not needed.
Impact: None.
8. Change: Cleaned up the nvram routines.
Impact: None.
v1.1.2 (Nov. 11, 2004) ====================== Fixes: ------ 1. Problem: Unable to load the driver on more than 2 or 3 devices.
Cause: Default register space is too big. System fails to map the register space on the 3rd or 4th device.
Change: Changed driver to map a smaller register space as the higher registers are not needed for standard operations.
Impact: None.
v1.1.1 (Nov. 9, 2004) ====================== Fixes: ------ 1. Problem: (CQTO656) One remaining ethtool parameter can be set out of range.
Cause: Wrong upper bounds in code.
Change: Fixed upper bound.
Impact: None.
1. Problem: 5706 A1 cannot be run on a PCI bus.
Cause: Hardware errata.
Change: Added workaround to detect 5706 A1 on PCI bus and abort.
Impact: Driver will not load 5706 A1 on PCI bus.
v1.1.0 (Oct. 29, 2004) ====================== Fixes: ------ 1. Problem: (CQTO663) No link on fiber NIC set to autoneg when the link partner is set to forced speed.
Cause: No code to handle this case.
Change: Added code to check SIGNAL DETECT when autoneg fails, and turn off autoneg when appropriate. Also added code to force a link down when speed settings are changed.
Impact: None.
2. Problem: (CQTO649) ifconfig up/down can cause system to hang on 2.6 kernels using mmconfig.
Cause: Dummy read in the kernel's pci_mmcfg_write routine may cause system to hang during D3hot -> D0 transition. The PLL may lose lock during the internal D0 transition chip reset and cause the dummy read to hang.
Change: The PLL problem will be fixed in A2. Meanwhile, the driver is changed to go into D3hot only if wol is enabled.
Impact: Minor impact in increased power consumption when the driver is shutdown with wol disabled.
3. Change: Changed to use pci_get_device as pci_find_device will be deprecated soon.
Impact: None.
4. Problem: (CQTO656) Some ethtool parameters can be set out of range.
Cause: Wrong upper bounds in code or documentation.
Change: Fixed code and documentation.
Impact: None.
v1.0.15 (Oct. 15, 2004) ====================== Fixes: ------ 1. Problem: (CQTO644) Data corruption when sending FTP traffic on Dell Precision 530MT.
Cause: PCI bridge errata.
Change: Added code to enable ONE_TDMA workaround when P64H PCI bridge is detected.
Impact: Slower tx performance on systems using P64H bridge.
2. Problem: (CQTO643) Driver allows MTU to be set up to 9004.
Cause: Driver used the wrong upper bound limit.
Change: Fixed the upper bound.
Impact: None.
3. Problem: Driver does not support forced speed on 5706S.
Cause: Missing software logic.
Change: Added code to support forced 1000 Full and Half duplex.
Impact: None.
4. Change: Added workaround to disable PERR generation on 5706 A1 when it is in PCI 64-bit slot.
Impact: None.
v1.0.14 (Oct. 05, 2004) ====================== Fixes: ------ 1. Problem: Driver load/unload hangs on some machines.
Cause: Transition delay required during D3hot -> D0 transition.
Change: Added necessary delay.
Impact: None.
v1.0.12 (Oct. 04, 2004) ====================== Fixes: ------ 1. Problem: (CQTO609) New flow control parameter does not take effect until ifdown/ifup or link down/up.
Cause: New flow control settings are only configured during link up. The driver did not check flow control advertisement changes and therefore no re-negotiation and no link down.
Change: Fixed logic so that link will always go down whenever there is a change a flow control advertisement.
Impact: None.
2. Problem: (CQTO612) VLAN packet reception not working.
Cause: VLAN #define not setup properly.
Change: Fixed #define for VLAN.
Impact: None.
3. Problem: (CQTO628) WoL not functioning correctly.
Cause: Multiple problems in the WoL code.
Change: Fixed by: 1. using sort mode. 2. setting up mac address correctly.
Impact: None.
Enhancements: ------------- 1. Change: Added support for non-dword and non-aligned write access to eeprom, allowing ethtool -E to work.
Impact: None.
v1.0.11 (Sep. 24, 2004) ====================== Fixes: ------ 1. Problem: (CQTO600) Kernel panic when attempting to ftp on Fedora kernel.
Cause: skbuffs are 4-byte aligned on Fedora, causing the rx headers to be misaligned. skbuffs are 16-byte aligned on other standard kernels.
Change: Removed any assumptions about skbuff alignment and added code to align all rx skbuffs to 8-byte boundaries.
Impact: None.
Enhancements: ------------- 1. Change: Added netif_carrier_off to Driver init code so that the initial link state is off.
Impact: None.
v1.0.10 (Sep. 23, 2004) ====================== Fixes: ------ 1. Problem: (CQTO599) Driver fails to compile on RH 3.0ES.
Cause: Bug in poll_bcm5706 where bp is referenced without being defined.
Change: Fixed the minor bug.
Impact: None.
v1.0.9 (Sep. 23, 2004) ====================== Fixes: ------ 1. Problem: Jumbo frames not working reliably.
Cause: Bug in bcm5706_reuse_rx_skb.
Change: Fixed the bug so that the host address is properly copied from one BD to the other.
Impact: None.
Enhancements: ------------- 1. Change: Change the locking scheme for more reliable open/close/ioctl operations where the spinlock is needed.
Impact: None.
2. Change: Added minimum MTU size check for MTU changes.
Impact: None.
v1.0.8 (Sep. 20, 2004) ====================== Fixes: ------ 1. Problem: (CQTO561) Kernel panic on RH30EL after repeated driver load/unload.
Cause: Occasionally, the system is unable to map device registers, causing subsequent register access to fail.
Change: Added check for the return value from ioremap, and exit gracefully if it fails.
Impact: None.
2. Problem: (CQTO574) NETDEV WATCHDOG when running 5706 A1 on PCIX 133MHz slot.
Cause: Some hw register setup required for 133 Mhz.
Change: Added the register setup code.
Impact: None.
3. Problem: (CQTO468) Link does not go down after changing from 10Mbps full (forced) to 10Mbps half (forced) and vice versa when the link partner is also using forced speed.
Cause: Delay not long enough for the link to go down.
Change: Not practical to increase delay as a very long delay is needed for the link to go down. Added code to record the proper link speed and duplex when speed is forced so that ethtool will return the proper speed without the link going down. Note that the link will go down if the link partner has autoneg turned on, ensuring that the link partner will see the link change.
Impact: None.
Enhancements: ------------- 1. Change: Added power management and WOL during device close. This will allow WOL to work after Linux shutdown.
Impact: None.
2. Change: Changed driver so that ethtool will report invalid speed after ifdown.
Impact: None.
3. Change: Updated tpatfw.h
Impact: None.
v1.0.7 (Sep. 14, 2004) ====================== Fixes: ------ 1. Problem: (CQTO523) 5706 A1 hangs after a thousand iterations of load/ifup/ifdown/unload.
Cause: The driver may be servicing an interrupt within 15 msec of chip reset, causing the chip to hang. The problem was aggravated by the timer mode coalescing which created an excessive number of interrupts (hardware problem).
The Driver may also occasionally see the wrong firmware signature that will cause it to abort.
Change: Added synchronization to make sure all pending interrupts are serviced before resetting the chip. Also changed to collect mode coalescing. The firmware signature problem will be fixed in boot code.
Impact: The use of collect mode coalescing may affect performance.
2. Problem: (CQTO558) Unable to load driver on some early 2.6 kernels.
Cause: pci_dma_sync_single_for_* routines not defined on early 2.6 kernels.
Change: Added compatibility defines for earlier kernels.
Change: Added 15 msec delay after chip reset for A1.
Impact: None.
2. Problem: (CQTO468) Link does not go down after changing from 10Mbps full (forced) to 10Mbps half (forced) and vice versa.
Cause: Not enough delay after forcing link down.
Change: Added proper delay for link to go down.
Impact: None.
v1.0.5 (Sep. 02, 2004) ====================== Enhancements: ------------- 1. Change: Added support for ethtool -c, ethtool -C, ethtool -p, and firmware version for ethtool -i.
Impact: None.
Fixes: ------ 1. Problem: 5706C not advertising 1000 half duplex.
Cause: 1000 full duplex overwrites 1000 half duplex.
Change: Fixed the bug so that the 2 bits are or'ed together.
Impact: None.
2. Problem: ethtool -A does not change the flow control settings in all cases.
Cause: Flow control settings not zeroed out before setting new values.
Change: Minor bug fix to zero out the value.
Impact: None.
v1.0.4 (Sep. 02, 2004) ====================== Fixes: ------ 1. Problem: (CQTO504) Multiple NFS transfers will hang some connections.
Cause: Driver discards some receive packets when the error status is non-zero.
Change: Changed the driver to only discard receive packets when the defined error bits in the error status are non-zero.
Impact: None.
v1.0.3 (Sep. 01, 2004) ====================== Enhancements: ------------- 1. Problem: Driver does not support ethtool -t self test and ethtool -S statistics.
Change: Added ethtool self test and statistics.
Impact: None.
Fixes: ------ 1. Problem: (CQTO478) Kernel still panics when transmitting certain files using NFS after many iterations
Cause: Tx DMA stalls on certain UDP packets, causing NFS client to stall.
Change: More fixes made in firmware.
Impact: None.
v1.0.2 (Aug. 26, 2004) ====================== Enhancements: ------------- 1. Problem: Driver does not work on big endian machines.
Change: Ported and tested on SPARC64 machine.
Impact: None.
Fixes: ------ 1. Problem: (CQTO478) Kernel panics when transmitting certain files using NFS.
Cause: Tx DMA stalls on certain UDP packets, causing NFS client to stall.
Change: Fixed in firmware.
Impact: None.
2. Problem: (CQTO469) Unable to modify flow control parameters
Cause: Did not call setup_phy after the parameters are changed.
Change: Added call to setup_phy after parameters are changed.
Impact: None.
3. Problem: (CQTO467) 5706 does not autonegotiate properly after changing settings with ethtool.
Cause: This is an ethtool limitation as the proper advertising parameters are not passed to the driver properly.
Change: Implemented a new scheme to work around the problem to allow users to specify full autoneg, single speed autoneg, and fixed speed.
Impact: None.
4. Problem: ethtool -e does not work.
Cause: Various bugs in the nvram routines.
Change: Fixed and tested nvram routines on little endian and big endian machines.
Impact: None.
v1.0.1 (Aug. 18, 2004) ====================== Fixes: ------ 1. Problem: (CQTO459) 5706 NIC does not get link.
Cause: Boot code timing out in WAIT2 state before driver is ready.
Change: Moved the WAIT2 state ahead in the driver reset sequence as a temporary workaround until it is fixed in boot code.
Impact: None.
2. Problem: (CQTO463) Kernel panics when loading the driver on RH30EL (2.4.21-4.EL)
Cause: Older kernel used different API to allocate and register netdev.
Change: Added older APIs to be used on older kernels.
2. Problem: CQ62310 - RSS should be disabled with NETQ.
Change: Initialize RSS according to BNX2X_NETQ.
Introduced: 1.72.13.
Relevance: ESX only.
Version 1.72.17 (Mar 20, 2012) ============================== Internal FW 7.2.18
Fixes: ------ 1. Problem: Compilation failed on SLES10.x XEN kernels.
Change: Add MSIX defines if not defined in kernel headers.
Introduced: 1.72.16.
Relevance: SLES10.x XEN kernels.
Version 1.72.16 (Mar 19, 2012) ============================== Internal FW 7.2.18
Fixes: ------ 1. Problem: CQ62046 - No link on 57712 + 8727 designs in which the TX laser is controller via GPIO, after T6.0 drivers/MFW were loaded previously without reboot. On these designs the TX_LASER is enabled by logic AND between the PHY(through MDIO), and the GPIO. When old driver which doesn't support these designs is used, it disables the MDIO part, thus the GPIO control has no affect.
Change: Enable the TX_LASER on the PHY for those design to enable the GPIO control it.
Introduced: 1.62.01.
Relevance: BCM8727 designs with GPIO controlling the TX laser.
2. Problem: CQ62136 - boards get stuck after boot from SAN.
Change: Changed UNDI unload by incrementing the producer's ring by one each iteration.
Introduced: 1.72.13.
Relevance: boot from SAN.
3. Problem: Consistent statistics does not work for old FW.
Change: Statistics are kept locally, copied to shmem upon update.
Introduced: 1.72.09.
Relevance: firmware-version prior to bc 6.4.0.
4. Problem: FW sequence of requests to MCP is wrong after parity recovery.
Change: Learn sequence number from shmem in nic load step.
Introduced: 1.72.13.
Relevance: All.
5. Problem: PXP2 is in wrong state due to double initialization occuring after global parity, one from the driver and one from the MCP.
Change: Don't clear value of relevant register after resetting the MCP as a part of the recovery process to avoid the double init.
Introduced: MFW 7.0.45.
Relevance: All.
6. Problem: CQ62169 - XEN: Failed to bring up interface if the system can't allocate enough MSIX vectors.
Change: Disable PCI MSIX capability if pci_enable_msix fails.
Introduced: Day one.
Relevance: XEN kernel only.
Enhancements: ------------- 1. Request: Initiated FLR via MFW command no longer requires re-enabling the target read. This code can be removed since the MFW minimal required version for initiated FLR was updated.
2. Request: Remove BNX2X_MSG_CNIC debug level as it is not used.
3. Request: If the system can allocate at least one MSI-X vector - use it instead of failing to MSI or INTx modes.
Version 1.72.15 (Mar 12, 2012) ============================== Internal FW 7.2.18
Fixes: ------ 1. Problem: CQ62104 - Intermittent link failure on 5771x + 8727. The "Unapproved module" flag had an indirect impact on the fix for CQ62046, which ended up in no link.
Change: Clear "Unapproved module" flag in case only "warning message" is required for such modules (common case).
Introduced: 1.72.14.
Relevance: 5771x + 8727.
Version 1.72.14 (Mar 08, 2012) ============================== Internal FW 7.2.18
Fixes: ------ 1. Problem: Driver build fails on kernels with ARCH variable defined.
Change: Remove references to ARCH in Makefile.
Introduced: 1.72.13.
Relevance: All.
2. Problem: CQ62046 - No link on 57712 + 8727 designs in which the TX laser is controller via GPIO, after T6.0 drivers/MFW were loaded previously without reboot. This issue occurs since old drivers control the 8727 TX laser only by changing PHY register, and new drivers assumed this register had a default value, despite that this register is not actually controlling the TX laser in those designs. Note that this issue is not likely to occur because T6.0 driver don't support these kind of boards, and loading new drivers afterwards without reset, is not common practice.
Change: Check SW flag instead of querying the TX_DIS register.
Introduced: 1.62.01.
Relevance: BCM8727 designs with GPIO controlling the TX laser.
3. Problem: insmod bnx2x more than twice may causes MCP assert during initialization of device.
Change: Study MCP command sequence before sending first command.
Introduced: 1.72.13.
Relevance: All.
4. Problem: CQ62061 - No link on the second port of 57711 + 84823, since PHY was left in reset.
Change: Unreset PHY on the second port.
Introduced: 1.70.01.
Relevance: 57711 + 84823.
Version 1.72.13 (Mar 07, 2012) ============================== Internal FW 7.2.18
Fixes: ------ 1. Problem: TC-related warning message.with the additional call to upper stack to set real num of queues to 1.
Change: Reset tc during unload to avoid warning messages. Change the call to upper stack to set real num of queues to number of RSS (rather than 1) Move setup-tc back to be after setting real number of queues.
Introduced: 1.72.12.
Relevance: All.
2. Request: CQ61426 - 4-port device with 2x10G and 2x1G ports is displayed as 4x10G ports.
Change: Update the pci.updates and pcitable files which are part of the release process to map the pci ids of the 1G ports to corresponding 1G identification strings. Change the identification string of the entire device from 10G to 1/10G.
Introduced: Day one.
Relevance: 57800.
3. Problem: Debug print of 'ioctl received while the device is down' appears frequently on the debug log.
Change: Remove this debug print.
Introduced: 1.72.12.
Relevance: All.
4. Problem: CQ61720 - MDC/MDIO access timeout message may appear on driver load due to missing clock setting before resetting the LED.
Change: Relocate setting the MDC/MDIO clock before resetting the LED since this operation involves access to the PHY registers.
Introduced: 7.0.0.
Relevance: All.
5. Problem: When a TPA aggregation is open and a packet is accepted with timestamp OOO, the new packet begins a new aggregation instead of being indicated separately.
Change: (FW ETH) Fix the relevant firmware flow.
Introduced: 1.72.09 (FW 7.2.14).
Relevance: All.
6. Problem: CQ61596 - There exists a corner case where firmware will send out only a single 'pure ACK' (TCP acknowledgement segment that has no payload) while 255 or more 'pre ACKs' and a 'delayed ACK' are queued and awaiting transmission. The other ACKs in the queue are sent with a payload of one byte and all have identical sequence number and valid TCP/IP checksum. When the very next TCP/IP packet is sent for the offloaded connection, the receiver will trim a single byte off the incoming packet because of the ACK received with payload of one byte.
Change: (FW iSCSI) Fix the relevant firmware flow.
Introduced: 1.62.01 (iSCSI FW 6.2.1).
Relevance: iSCSI only.
7. Problem: FW statistics per queue does not increasing in queue counters, but properly increasing in device conters.
Change: Fixed lack of queue statistics update.
Introduced: 1.72.09.
Relevance: All.
8. Problem: CQ61763 - parity recover might fail on devices with two ports on the same path.
Change: Clear validity map of correct port before resetting MCP, as because of wrong clearance nic load after recovery can fail due to race between mailbox messages to MFW initialization process.
Introduced: day one.
Relevance: 57710 + 57711 + 4 port devices.
9. Problem: CQ60448 - Rare case of no link due to missed interrupt may occur due to a race condition between acknowledging the IGU via the BAR and restoring the NIG interrupt mask via the GRC.
Change: Make sure that the IGU ack command is completed before restoring the NIG interrupt mask.
Introduced: Day 1.
Relevance: All.
10. Problem: Wrong debug prints in self-test. Disturbing debug prints on BNX2X_MSG_ETHTOOL filter.
Change: Remove the problematic debug prints.
Introduced: 1.72.12.
Relevance: All.
11. Problem: CQ60042 - Flow control is not functional when OEM 57810s devices set to auto and evaluated via 1gb PT Module.
Change: Added code to handle CL37 AN when link is achieved via CL37 in 578xx-KR.
Introduced: T7.0.
Relevance: 578xx-KR.
12. Problem: CQ61967 - Compilation fails on RH when only kernel-devel package is installed.
Change: Fix Makefile to look for the kernel.
Introduced: Day one.
Relevance: All.
13. Problem: CQ61511, CQ61099 - Unable to bring up device without proper shutdown or device reset.
Change: Implemented a new scheme to unload existing driver at the probe and restore states.
2. Request: CQ61934 - Update default Tx Equalization settings for SFP+ mode after analysis at all PVT corners.
Relevance: 578xx SFP+.
3. Request: Remove `gro check' workaround from driver.
Version 1.72.12 (Feb 28, 2012) ============================== Internal FW 7.2.16
Fixes: ------ 1. Problem: 1G LED stays on with cable unplugged on 57712+8727 designs.
Change: Restored the MODE_LED_OFF mode to explicitly keep the LEDs off.
Introduced: 1.72.07.
Relevance: LED manipulation for 54616/18 and 8727 PHYs.
2. Problem: When getting / setting the number of queues via ethtool -l/L need to use 'combined' rather than 'rx'/'tx', as we we don't have independant rx and tx queues. The number of rings cannot exceed the number assumed during probe, as there will not be msi-x vector or napi object to the extra rings. When waking / starting the entire range of tx rings (which is 16*coses + non-ethernet) we may get old transmit requests on non-existing queues.
Change: Use the 'combined' field rather than the 'rx'/'tx' fields. Limit the number of rings to the number assumed during probe. When waking / starting the tx rings start only the 'real' rings (and not the entire range).
Introduced: 1.72.04.
Relevance: All.
3. Problem: CQ61532 - System halts when driver is loaded after fan failure has occurred. This can be seen also after reboot in fan failure status. This problem happens in 578xx only where the MFW stops the clocks which prevents the host to map the PCI IO registers to BAR0, and cause fatal error.
Change: MFW signals the fan failure by setting the PCI version number to 0xff (reflected in PCI address 0x8), thus allowing the driver to check this failure before mapping the bar. Fix requires MFW version 7.2.15 (and above).
Introduced: MFW 7.0.51 /MFW 7.2.0.
Relevance: 578xx boards with fan.
4. Problem: CQ61720: MDC/MDIO access timeout right after driver is loaded. This warning message is printed since the link periodic function is called before the link interface is initialized.
Change: Start link periodic function only after link is initialized.
Introduced: 1.70.12.
Relevance: All.
5. Problem: CQ61680 - 57810 KR link may not come up in 1G after running loopback test.
Change: Restore the 10G KR force register to their default value before starting KR autoneg.
Introduced: 1.70.00.
Relevance: 57810-KR when connected to 1G only link partner.
6. Problem: CQ61439 - when installing RHEL 5.7 on an iSCSI HDD, network interfaces get DMAE timeouts.
Change: When enabling IGU interrupts for INTA, also remove the INTA disabled bit in the pci command register.
Introduced: Day 1.
Relevance: BCM57712, BCM57810.
7. Problem: CQ61628, CQ61381 - PFC frames are not honored, due to incorrect link attributes synchronization which happen following PMF migration or remote-fault detection.
Change: Update link_status with the PFC_ENABLE flag on link update in addition to the pfc update function.
Introduced: 1.70.00.
Relevance: Multi-function(1.70.00) or SFP+ devices (1.72.07).
9. Problem: When decreasing the number of queues comparing to the previous load we may get old transmit requests on non-existing queues.
Change: Temporary and non-upstream solution: Add call to upper stack to set real num of queues to 1. This will flush all qdisc queues greater than 1. Move setup_tc to be before set_real_num_queues to prevent warning messages.
Introduced: 1.72.04.
Relevance: All.
Enhancements: ------------- 1. Request: Update debug prints to the appropriate mask. During probe use debug print which doesn't include eth%d. Add an error debug print when an error code (-Exx) is returned. Remove the 'releasing a lock on resource n" debug print. In debug prints put the printed string on a single line even if exceeding 80 characters. The updates described above were done only on the following files: bnx2x_main.c, bnx2x_cmn.c, bnx2x_cmn.h, bnx2x_ethtool.c, bnx2x_dcb.c, bnx2x_compat.h, bnx2x_stats.c, bnx2x.h.
Relevance: All.
Version 1.72.11 (Feb 21, 2012) ============================== Internal FW 7.2.16
Fixes: ------ 1. Problem: Memory leak in bnx2x_tpa_stop() if build_skb() fails while using the build_skb infrastructure.
Change: Fixed.
Introduced: 1.72.04.
Relevance: Only new kernels with build_skb support.
2. Problem: CQ61625 - Statistics code cause prints of BUG to dmesg.
Change: Missing checks in statistics code inserted.
Introduced: 1.72.09.
Relevance: All.
3. Problem: Unable to query/configure DCB parameters when in OFF state.
Change: Remove the limitation for the IOCTLs.
Relevance: DCBx supported devices.
4. Problem: CQ60873 - ethtool reports duplex/speed of closed functions.
Change: If closed function/link is down, then ethtool reports duplex/speed as unknown.
Relevance: All.
5. Problem: Ethtool allows forced speed of 20G to pass.
Change: Return -EINVAL on forced speed of 20G (unsupported).
Relevance: All.
6. Problem: CQ61601 - The FW version for 84833 PHY was captured incorrectly. As a result, the major number is always reported as '1'.
Change: Fixed to read the correct field of the PHY register.
Introduced: 1.72.04.
Relevance: 84833 PHY.
7. Problem: Removing driver causes NULL pointer dereference when trying to reset the Forwarding ring's non existent netdev queue.
Change: Only attempt to reset netdev queues for fastpaths that really have netdev queues.
Introduced: 1.72.07.
Relevance: iSCSI OOO.
8. Problem: CQ61564 - PFC statistics are ticking backwards.
Change: PFC statistics are now consistent, both with HW and with inner reload.
Relevance: BCM57712.
9. Problem: On rare cases, when link speed changes from 10G to 1G or lower, then remote fault may be reported.
Change: Check remote fault indication on link speed of 10G and above, since UMAC and EMAC do not support it.
Relevance: BCM578xx, BCM848x3, BCM872x.
Introduced: 1.72.07.
10. Problem: CQ61678 - System crash after running IO and pulling cable. Occurs since TX pipe is stalled due to missed XON indication (from MAC did to NIG). See related CQ56434 which fixed the problem for 57712.
Change: Force XON on NIG on link down/up.
Introduced: 1.70.00.
Relevance: 578xx.
11. Problem: FCoE capabilities values written to scratchpad are wrong, and doesn't match the values arrived from cnic.
Change: (FW iSCSI) Firmware fix to MSL timer tolerance.
Introduced: Day one.
Relevance: iSCSI.
13. Problem: Aggregation may stall TCP connection, since bytes to place on SGE improperly calculated.
Change: (FW ETH) Firmware fix to TPA flow.
Introduced: 1.72.09 (FW 7.2.14).
Relevance: All.
Enhancements: ------------- 1. Request: link read_status updates link partner's capabilities (fc, speed) whenever autoneg was used. New versions of ethtool output these capabilities.
Relevance: All boards with phys that support autoneg.
2. Request: Remove deprecated SAFC suport from driver code. bnx2x propriatery SAFC support has been trumped out by upstream Multi COS support.
Version 1.72.10 (Feb 06, 2012) ============================== Internal FW 7.2.14
Fixes: ------ 1. Problem: Kernel crash while "ethtool -K lro off" during traffic.
Change: Use fp flag for TPA mode.
Introduced: 1.72.09.
Relevance: All.
2. Problem: GRO still on, while rx checksum is off.
Change: Update GRO feature according to checksum configuration.
Introduced: 1.72.09.
Relevance: All.
3. Problem: Unable to shut GRO on kernel with dev->hw_feature.
Change: Mark GRO as HW feature.
Introduced: 1.72.09.
Relevance: Feature supported on kernels above 2.6.39. On other kernels module parameter "disable_tpa" should be used to disable GRO.
4. Problem: CQ61214 - Network kdump fails on bnx2x device.
Change: Make driver to wait 5 sec when 'reset_devices' is on. This to allow HW to detect driver disappearance from normal kernel and properly initialize FW.
Relevance: Kdump environment.
5. Problem: Not all statistics are reset in MF mode upon close/open.
Change: Every function erases its function statistics' SP upon init.
Introduced: 1.72.09.
Relevance: Boards in MF mode.
6. Problem: WWN parameters are incorrect in FCoE SD mode.
Change: Properly load the parameters in FCoE SD mode.
Introduced: 1.72.08.
Relevance: FCoE SD mode.
Enhancements: ------------- 1. Request: When autoneg is on, ethtool -a outputs the pause configuration instead of the pause result.
Relevance: All boards with autoneg-capabale phys.
2. Request: Remove redundant allocation-failure messages in places that there is already a similar message from the kernel.
3. Request: Write zeros to driver_version in NC-SI shmem structure, as it should not be supported under Linux at all.
4. Request: Clarify the driver defaults in the readme file.
5. Request: CQ58557 - Allow reading the external PHY FW from any driver instance even if it is not loaded since the value is stored in shared memory and does not require any locking or any special access.
Version 1.72.09 (Feb 01, 2012) ============================== Internal FW 7.2.14
Fixes: ------ 1. Problem: Possible soft-lockup in driver code.
Change: Release lock in case of error.
Introduced: 1.72.07.
Relevance: All.
2. Problem: Driver didn't mark in shmem that driver capabilities are supported, so MFW ignored those values.
Change: Mark in shmem feature is supported.
Introduced: 1.72.04 (when new NC-SI commands were added).
Relevance: BCM57712/BCM578xx.
3. Problem: CQ60672 - iSCSI boot fails in 57810+84833 NIC when running at 100HD link achieved via auto-neg.
Change: Added configuration to set MAC controller in half duplex mode when PHY links up in half duplex mode.
Introduced: Day 1.
Relevance: 578xx+848x3.
Enhancements: ------------- 1. Request: Statistics are consistent (i.e. not resetted) when using operations which require an implicit nic_unload/nic_load. MTU change, LRO change, and self-test are examples of functionalities benefiting from this change.
Relevance: All.
2. Request: CQ61246 - update dropless_fc section in README.
Relevance: 57712/578xx.
3. Request: CQ59527 - Update README with handling low memory conditions on 32-bit platforms.
4. Request: CQ58302 - Update README and man page with regard to ethtool -L: The number of rx and tx rings should be the same, other and combined should be zero.
5. Request: CQ59122 - Added new TPA mode GRO. In this mode packets are aggregated such that the original packets can be reconstructed by the OS. All packets in the aggregation have the same ACK number and Timestamp.
Relevance: Kernels with GRO support.
Version 1.72.08 (Jan 24, 2012) ============================== Internal FW 7.2.11
2. Problem: CQ60808 - dcbxinfo prints 'DCB is out of sync'.
Change: Use driver flags as bit-mask.
Introduced: 1.70.17.
Relevance: DCBX capable devices.
3. Problem: FCoE/iSCSI interface initialization fails after recovery process.
Change: Enable driver to approach the chip during nic load performed at the end of the recovery process.
Introduced: Day 1.
Relevance: All.
Enhancements: ------------- 1. Request: Support FCoE SD mode.
Relevance: BCM57712/BCM578xx.
Version 1.72.07 (Jan 19, 2012) ============================== Internal FW 7.2.11
Fixes: ------ 1. Problem: CQ59723 - drv_pulse doesn't match mcp_pulse.
Change: Learn mcp pulse at nic load step instead of during probe step.
Introduced: Day 1.
Relevance: All.
2. Problem: CQ60838 - Occasionally the KR link does not come up.
Change: Invoke auto-neg restart at the end of the KR link configuration.
Introduced: 1.72.00.
Relevance: 578xx KR.
3. Problem: CQ61028 - No LED at 1G on 57712+8727 designs.
Change: Removed a logic error checking for a different PHY.
Introduced: 1.70.00.
Relevance: LED manipulation for 54616/18 and 8727 PHYs.
4. Problem: CQ60094 - soft kernel panic in bnx2x_execute_vlan_mac.
Change: Released consumed credits when removing pending commands.
Introduced: 1.72.00.
Relevance: All.
5. Problem: MAC addresses responded to mcp for get_drv_info request are not aligned as requested by MCP.
Change: Align MAC addresses appropriately.
Introduced: 1.72.00.
Relevance: 578xx.
6. Problem: BCM84833 is able to link up when link speed is set to 10G force while link partner is set to 1G force.
Change: When requested speed is 10G force, advertise only 10G speed.
Introduced: 1.70.00.
Relevance: BCM84833.
7. Problem: Unable to load device when CNIC is not selected.
Change: Fix feature initialization.
Introduced: 1.70.51.
Relevance: All.
8. Problem: If nic load fails after recovery flow, recovery is still marked as in progress, hence recovery flow will be performed again.
Change: In such a case, detach failed function but mark that recovery has already been performed.
Introduced: Day one.
Relevance: All.
9. Problem: If failed during nic load, MISC register holding function status might hold wrong value, causing logical errors in parity recovery flow.
Change: Mark function as loaded in MISC register only if nic load succeeded.
Introduced: Day one.
Relevance: All.
Enhancements: ------------- 1. Request: CQ59363 - Display the link partner FC capabilities when FC is not autoneg.
Relevance: All.
2. Request: Added support for Byte Queue Limiting.
Relevance: Linux kernel version 3.3.
3. Request: CQ57932 - Add Tx-Fault link detection. In case TX errors are detected by the MAC layer, the elink will signal the OS that the link went down, and when the error is gone, a link up signal will be sent.
Relevance: BCM84823.
4. Request: Support Multiple Concurrent COSes on 57710/57711E devices. Reinstate 'pri_map' module parameter for controlling the mapping of Priorities to Classes of Service.
Relevance: 57710/57711E.
5. Request: Reinstate pri_map module parameter which allows direct user control over the mapping of skb priority to traffic classes.
Relevance: All.
6. Request: CQ60175 - Add Multiple RX filters support per NetQueue.
Relevance: ESX only.
7. Request: Change marking whether function is loaded or not in MISC register to be bitwise and not a global counter, so that MFW will be able to mark function as not loaded in case driver pulse is timed out (for physical device assigment).
Relevance: All.
Version 1.72.06 (Jan 17, 2012) ============================== Internal FW 7.2.11
Fixes: ------ 1. Problem: CQ60906 - nic loading after recovery flow failed due to DMAE timeout.
Change: Wait for DMAE completions inside nic load performed at the end of the recovery flow. Don't wait for DMAE completions during all recovery flow besides inside the nic load.
Introduced: 1.72.05.
Relevance: All.
2. Problem: CQ60731 - DCBX/VIC traffic is dropped after recovery flow.
Change: When running recovery flow on the non global leader, send driver load before performing the recovery and driver unload when the recovery process is done. By that, MFW will restore NIG values upon the driver unload at the end of the process.
Introduced: Day one.
Relevance: BCM57712/BCM578xx. Requires MFW 7.2.9 and above.
3. Problem: CQ58306, CQ58507 Intermittent KR link failure after link enable.
Change: Reset rx and tx path if link is not up.
Introduced: Day 1.
Relevance: 57810-KR, when MFW used is older than 7.0.48.
Enhancements: ------------- 1. Request: CQ57889 - Less memory is allocated for Rx buffers of 1G ports.
Relevance: BCM578xx 4-port only.
2. Request: Support FCoE capabilities command from CNIC. Once this command arrives store the values in appropriate scratchpad address.
3. Request: Add module parameter to enable support of tx-switching.
Relevance: BCM57712/BCM578xx.
4. Request: CQ57932 - Add Tx-Fault link detection. In case TX errors are detected by the MAC layer, the elink will signal the OS that the link went down, and when the error is gone, a link up signal will be sent.
Relevance: BCM57712/BCM57800/BCM57810 with BCM8727/BCM8726/BCM84833 PHYs.
5. Request: CQ60699 - Disable auto-grEEEn for 84833 PHY.
Relevance: 84833 PHY only.
Version 1.72.05 (Jan 10, 2012) ============================== Internal FW 7.2.11
Fixes: ------ 1. Problem: Ethtool statistics omitted function statistics when in Multi-queue, MF mode.
Change: Fixed.
Relevance: All.
2. Problem: CQ59825, CQ60741 - system crash during 'ethtool -t'.
Change: Fixed insufficient memory allocation.
Introduced: 1.72.04.
Relevance: All.
Enhancements: ------------- 1. Request: CQ55885 - Added recoverable/unrecoverable statistics for ethtool. Currently counting parity errors and panic_dump.
Version 1.72.04 (Jan 03, 2012) ============================== Internal FW 7.2.11
Fixes: ------ 1. Problem: bnx2x_panic does not show idle_chk prints.
Change: Fix idle_chk to print with NETIF_MSG_PROBE msg level.
Change: Treat missing TLVs as an error - do not configure the feature.
Relevance: DCBx supported devices.
3. Problem: The common PHY init function for 84833 was split, but the second half of the call was not invoked to capture the PHY FW version.
Change: Added code to invoke the second half. Also, use a different PHY register to collect the version info.
Relevance: 84833 only.
4. Problem: CQ60377 - Task was corrupted when working with CONF REQ.
Change: FCoE Firmware fix to relevant RX flows.
Introduced: 1.72.00 (FW 7.2.0).
Relevance: BCM57712/BCM578xx.
5. Problem: Compilation problem on kernel 3.1.6.
Change: skb_frag_dma_map was introduced only in kernel 3.2.0. bnx2x_get_rxnfc parameter change was introduced only in kernel 3.2.0.
Introduced: Day one.
Relevance: All.
6. Problem: Compilation problem with SOE enabled.
Change: struct sw_rx_bd contains 'data' member rather than 'skb'.
Introduced: 1.72.03.
Relevance: All.
7. Problem: DMA opertaions are waiting for completion during recovery flow.
Change: Return immediately that timeout expired when pending for DMA completion during recovery flow.
Introduced: day one.
Relevance: All.
Enhancements: ------------- 1. Request: use build_skb() kernel infrastructure in RX path.
2. Request: Use kcalloc instead of kzalloc when allocating arrays.
3. Request: Use a kernel ethtool function to build the default indirection table (supported from kernel version 3.2.0).
4. Request: Decrease stack size in NVRAM self-test function.
5. Request: Add support for getting and setting the number of queues via ethtool (using -l / -L options).
6. Request: Support 3 new NC-SI OEM commands (insert data requested from MFW).
7. Request: Support RH5.8.
8. Request: Use the 'unlikely' macro with the debug printk() macros (DP, DP_CONT, BNX2X_DBG_ERR) and with the BNX2X_DEV_INF macro.
9. Request: Protect bnx2x from races due to lack of RTNL lock protection between PFs in physical device assignment: 1. Added per PF HW lock for nvram accesses. 2. Added per PF HW lock for recovery reg accessed. 3. Modified Undi presence detection to verify doorbell queue block is out of reset and so under the per PF HW lock.
10. Request: When bnx2x is loaded on an engine where FW was already loaded verify FW matches loading driver (in Physical Device Environment FW may have been loaded by a different bnx2x from another VM).
Version 1.72.03 (Dec 20, 2011) ============================== Internal FW 7.2.10
Fixes: ------ 1. Problem: PFC in 4-port mode is not functional.
Change: Take port index into account when configuring NIG registers.
Relevance: 4-port + DCB devices.
2. Problem: CQ59565 - FW version does not show the VPD FFV when applicable.
Change: The chip VPD was extended and now it can be longer than 128B, while the driver failed the FFV read if the offset was larger than 128B.
Introduced: 1.62.xx - where the device started to support longer VPD.
Relevance: Boards that require FFV reporting.
3. Problem: CQ60236 - Possible false positive self-test idle check failure while performed under traffic on 578x0 B0: "ERROR UCM: FIC1_INIT_CRD is not 64".
Change: On 578x0 B0 the value of FIC1 can be different than 64 under traffic. The test was updated to reflect that.
Introduced: Day one.
Relevance: 578x0 B0.
4. Problem: No link detected at speed 100m AN connected to 10BaseT/100BaseTx switch.
Change: Remove the supported limitation from setting 100Mb speed.
Introduced: 1.70.100.
Relevance: 57712 + 84833.
5. Problem: CQ59823 - Driver hang when FCoE IO starts.
Change: (FW FCoE) Firmware fix to data transmission flow.
Introduced: 1.72.00 (FW 7.2.0).
Relevance: All.
6. Problem: CQ59828 - iSCSI connection fails to send write commands when NPAR-SD mode is enabled.
Change: (FW iSCSI) Firmware fix to TCP establishment flow of iSCSI connection.
Introduced: 1.72.00 (FW 7.2.0).
Relevance: 57712/578xx.
Enhancements: ------------- 1. Request: Support Basic Physical Device Assignment. Bnx2x was adapted to allow loading it in paravirtualized environment. This means: 1. Bus device function is obtained from Me register. 2. Wide bus sequence interruption by ZLR is avoided via the indirect interface only in E1. Post E1 chips use direct register access. 3. FLR final cleanup failure results in nic load failure (previously this was ignored).
Version 1.72.02 (Dec 08, 2011) ============================== Internal FW 7.2.9
Fixes: ------ 1. Problem: No link is established at 100M on 57712+84833 combination. 100Mb force is not supported, and is limiting the advertising speed for 84833 firmware version of 1.39 and older.
Change: Modify the advertised speed to include 100Mb even if this speed is not supported for current 84833 firmware version. Note however, that since 100Mb force speed is not supported, in order to advertise 100Mb, user will need to specify this speed explicitly as one of the advertised speeds when using the ethtool command.
Introduced: Since support of 57712+84833 is introduced.
Relevance: 57712/578xx + 84833.
2. Problem: 84833 PHY firmware size has grown to cause timeout on initialization. This leads to PHY misconfiguration due to PHY register clobbering between software and the PHY firmware.
Change: Extend firmware initialization timeout period for all ports.
Introduced: Day one.
Relevance: 84833 PHY designs with a single SPIROM
Enhancements: ------------- 1. Request: Add PFC tx/rx frames counter to port statistics exposed to ethtool.
2. Request: Support Ethernet statistics request from MFW, and forward iSCSI/FCoE statistics request to cnic.
3. Request: 84833 PHY FW team recommended a few changes when configuring the PHY: (1) Use super isolate feature when the PHY is no longer use (e.g. unloading driver). (2) Bring PHY out of super isolate mode as the last step of initialization.
Relevance: 84833 PHY only
Version 1.72.01 (Nov 30, 2011) ============================== Internal FW 7.2.9
Fixes: ------ 1. Problem: CQ57679 - "FATAL HW block attention set1 0x8" message in syslog when running ethtool -d under traffic.
Change: Remove registers which should not be read during traffic.
Introduced: Day one.
Relevance: ethtool -d under traffic.
2. Problem: CQ59765 - Link loss on 10G port after running ethtool test on 1G port, since the MAC loopback test was done on XMAC causing the 10G port to lose link.
Change: On 1G port, run UMAC loopback.
Introduced: 1.70.53
Relevance: 57800 only (2x10G + 2x1G)
3. Problem: CQ59828 - Unable to connect to iSCSI target in NPAR-SD mode.
Change: Allow setting MAC in NIG for NPAR-SD mode.
Introduced: Day one.
Relevance: NPAR-SD mode.
4. Problem: CQ59448 - Chip hangs when target sends FIN out-of-order or with isles open at the initiator side.
Change: Fin dropped if received out of order or with isles still open.
Introduced: 1.60.00 (FW 6.0.0)
Relevance: All.
5. Problem: CQ59904 - Unable to create VLAN interface on RHEL6.2.
Change: Adopt VLAN scheme to RHEL6.2 kernel.
Introduced: Day one.
Relevance: RHEL6.2.
Enhancements: ------------- 1. Request: Support iSCSI SD mode.
2. Request: Support DCBNL CEE calls on RHEL6.2.
Version 1.72.00 (Nov 13, 2011) ============================== Internal FW 7.2.7
Fixes: ------ 1. Problem: CQ59471 - DCBx does not work with NPAR on kernels with multi-CoS support.
Change: The DCBx negotiation result was not propagated to all functions.
Introduced: Day one.
Relevance: DCBx and kernels with multi-CoS (2.6.39 and above).
2. Problem: Compilation failed on SLES11SP2 beta7 kernel.
Change: Fix compat.h.
Introduced: Day one.
Relevance: SLES11SP2 beta7 kernel.
3. Problem: CQ59626 - set skb_record_rx_queue for FCoE ring out of range.
Change: Introduce fp->rx_queue and use it instead of fp->index.
Introduced: 1.70.53.
Relevance: FCoE + kernel with skb_record_rx_queue support.
4. Problem: CQ59651 - GRC-timeout messages run in syslog.
Change: Fix race between two statistic-related flows by using local state in bnx2x_stats_handle().
Introduced: Day one.
Relevance: All.
5. Problem: CQ59454 - Port identify test fails on 54616 PHY.
Change: Updated driver to driver LEDs through MDIO for 54616
Introduced: T7.0
Relevance: 54616 PHY based boards.
6. Problem: In NPAR-SD mode on FCOE packets VLAN priority is not taken from DCB results, i.e. default priority is always used even if a change was negotiated.
Change: Fixed in FW 7.2.7.
Introduced: Day one.
Relevance: All.
7. Problem: CQ57927 - Chip hangs when a retransmission occurs which is not aligned to 4-bytes from the beginnig of iSCSI PDU.
Change: Fixed in FW 7.2.5.
Introduced: FW 7.0.16.
Relevance: All.
8. Problem: Arrival of packets beyond task IO size can lead to crash.
Change: Fixed in FW 7.2.5.
Introduced: Day one.
Relevance: All.
9. Problem: CQ57933 - iSCSI does not support Traffic Class 2.
Change: Fixed in FW 7.2.3.
Introduced: Version 1.71.00.
Relevance: All platforms running DCB enabled with COS 2 and higher.
Version 1.70.200 (Nov 01, 2011) ============================== Internal FW 7.2.2
Fixes: ------ 1. Problem: CQ58580 System becomes unresponsive or unstable after running self test. This was due to kernel stack overflow by the self test during load/unload.
Change: Located stack-hungry code in the nic load flow and modified it to consume reasonable amount of stack.
Introduced: Day one.
Relevance: All Chips. This issue only occurs in low stack kernels - specifically kernels using 4kb stack depth such as 32bit PAE kernel.
Version 1.70.53 (Oct 24, 2011) ============================== Internal FW 7.2.2
Fixes: ------ 1. Problem: CQ58884: On 1G copper ports, the RX UMAC is not close to prevent arrival of partial segments during link reset process.
Change: Close the UMAC and the NIG RX during link reset process.
Introduced: T7.0
Relevance: 578xx.
2. Problem: Traffic blink rate LED is too fast.
Change: Adjust the blink rate to 578xx clock.
Introduced: T7.0
Relevance: 578xx.
3. Problem: CQ58887 - System with low memory PSOD when running mtu change.
Change: Switch between FP indexes in order to avoid mapping of FP with napi to to one napi-less, during memory allocation.
Introduced: Version 1.60.27.
Relevance: ESX-5.0.
4. Problem: Traffic LED blink rate for 10GBase-T designs is a bit slow.
Change: Adjust the slow clock counter in the PHY to increase the blink rate.
Introduced: T7.0: a fix for CQ56846
Relevance: 84823 and 84833 PHYs
5. Problem: CQ58996 - After 20 iterations of reboot test, adapter does not dcbx-sync with switch.
Change: Perform hard reset to the XMAC during link establishment to clear possible left-overs.
Introduced: T7.0
Relevance: 57810/57800
6. Problem: CQ57952 - Chip consumes too much power in case of fan failure.
Change: unload driver and power down chip.
Relevance: 57810.
7. Problem: CQ58990 - KR link occasionally comes up at 1G when 10G is expected. This is exposed only when a previous software entity (e.g. MFW, prior to OS driver loading up) that owns the KR PHY left it at 1G.
Change: Keep auto-neg disabled while configuring the capability advertisement. Re-enable it after configuration is done.
Introduced: Day One
Relevance: 578xx blade designs.
8. Problem: skb truesize is under estimated.
Change: bnx2x allocates a full page per fragment. It should account in skb->truesize, the size of the fragment, not the used part of it.
Introduced: Day One
Relevance: All.
9. Problem: 84833 PHY FW command handler interface requires further refinement as they don't seem to work.
Change: Made further adjustments and consolidated the command handler routine (in anticipation for other commands besides auto-grEEEn)).
Introduced: Version 1.70.50.
Relevance: 84833 PHY.
Enhancements: ------------- 1. Request: Add LED functionality to 54618SE PHY based boards.
2. Request: Put 84833 PHY in super isolate mode regardless of the strapping pin. The PHY stays in this mode until driver is loading up.
Relevance: 84833 PHY only.
Version 1.70.52 (Oct 04, 2011) ============================== Internal FW 7.2.2
Fixes: ------ 1. Problem: CQ58418 - WoL does not work after driver unload.
Change: The PME was not enabled in the configuration space.
Introduced: Day one.
2. Problem: CQ58516 - DCBX ioctls return without error on non-DCB capable devices.
Change: Check DCB state in IOCTLs code.
Introduced: 1.64.00.
Relevance: Non-DCB capable devices.
3. Problem: Compilation failed on RHEL6.2 kernel.
Change: Fix in compat.h.
Relevance: RHEL6.2 - alpha.
4. Problem: Lack of handling some HW failure indications.
Change: Fix improper initialization of mask register.
Introduced: 1.60.00.
Relevance: 57712/578xx only.
5. Problem: bnx2x_dcbnl_get_cap returns error for DCB_CAP_ATTR_DCBX.
Change: Add missing brake statement.
Relevance: DCB capable devices.
6. Problem: CQ57274 - Zero queues are used when num_queues was set to -1.
change: Make sure num_queues is treated as unsigned number.
Relevance: All.
7. Problem: Unable to change the speed with ethtool while using DAC (direct attached cable).
Change: The port was matched against fiber only without considering DAC.
Introduced: Version 1.60.28.
Relevance: Optic ports with DAC.
Enhancements: ------------- 1. Request: Immediately return an error from the bnx2x_cnic_sp_post() if we are in the middle of the parity error recovery flow. This will significantly speed up the CNIC_STOP command flow when called in the parity recovery context.
Relevance: CNIC only.
2. Request: Allow DCBNL functionality for RHEL6.1 and RHEL6.2.
3. Request: Changed 'pri_map' module parameter to control mapping from priority to traffic class instead of deprecated role in SAFC configuration.
Version 1.70.51 (Sep 13, 2011) ============================== Internal FW 7.2.2
Fixes: ------ 1. Problem: Forced 100M speed cannot pass traffic with 578xx+84833.
Change: Configure the Warpcore to SGMII auto-neg when interfacing the 84833 PHY.
2. Problem: Cannot establish link with 84833 PHY using PHY FW v1.27.
Change: The FW has been changed to fully support superisolate mode. That requires the PHY initialization sequence to change.
Introduced: Day 1
Relevance: 84833 PHY, PHY FW v1.27 is required.
3. Problem: Overflow occurs during init, when generating statistics ramrod toward the FW (writing to index outside of array bounds).
Change: Increase number of elements in the array inside struct bnx2x_fw_stats_req.
Introduced: Day 1.
Enhancements: ------------- 1. Request: Collect FCoE statistics from FW (both offloaded and non offloaded), and add them to the statistics response toward the MCP in NPAR-SD mode. These statistics are not counted in the ones published to ethtool.
Relevance: 57712 + 578xx.
Version 1.70.50 (Sep 08, 2011) ============================== Internal FW 7.2.2
Fixes: ------ 1. Problem: MC assert while initializing iSCSI on some 57711E boards.
Change: Adjust iSCSI license at bnx2x_open.
Introduced: 1.64.00.
Relevance: 57711E.
2. Problem: CQ57274 - kernel panic when trying to load bnx2x with negative amount of receive queues.
Change: Changed all module parameters from integer to unsigned integer.
Introduced: Day 1.
3. Problem: CQ58271 – Improper array initialization in call to get_dcbx_params_ioctl.
Change: Take array size into account when data is copied.
Introduced: 1.64.00.
Relevance: 57712/578xx.
4. Problem: Ethtool Advertised pause frame use don't show the pause capability when flow-control not set to autoneg.
Change: Display the advertised pause frame use even if flow-control is not set to autoneg.
Introduced: 1.70.27.
5. Problem: On-chip TCP connection establishment on iSCSI connections is broken.
Change: Fixed in FW 7.2.2.
Introduced: In FW 7.2.1.
Relevance: iSCSI only.
Enhancements: ------------- 1. Request: Reduce power consumption for 57810 fan failure by: * Powering down the Warpcore. * Kill clocks to all driver present blocks. * Clear BME(Bus Master Enable) and MS(Memory Space). Note that if fan failure occurs when using drivers released before this date will result in system crash.
2. Request: Prevent link flap on 1G copper ports when driver unloads in case the PHY is already initialized and link is up.
Relevance: 57800 + 5461x.
Version 1.71.00 (Sep 02, 2011) ============================== Internal FW 7.2.1
Fixes: ------ 1. Problem: Driver compilation failed on 2.6.38.x kernels.
Change: Fix compat for these kernels.
Introduced: 1.70.21.
2. Problem: Error messages "FATAL HW block attention set2 0x20" in the kernel log on specific systems.
Change: Recoverable LCRC errors due to not masking CPL_OF caused the print while it should be ignored.
Introduced: Day one.
Relevance: 57710 and 57711.
3. Problem: PCI scan could lead to GRC read.
Change: Second function indirect windows were not cleared by the driver since the driver used the port index before it was initialized and therefore cleared only function 0. Since the driver is not using these indirect windows, it will clear them all.
Introduced: Day one.
4. Problem: CQ57061 - GRC timeout messages appear on some systems during driver load.
Change: Take HW LOCK before resetting the HW, which prevents from undi_unload reading registers while block is in reset state.
Introduced: Day one.
5. Problem: Compilation failed on SLES11 SP1 update 1.
Change: Fix conflict on backported feature in bnx2x_compat.h.
Introduced: 1.70.20.
Relevance: SLES11 SP1 update 1 only.
6. Problem: The GPHY ports are not completely powered down on driver unload if the GPHYs have no external pins to bring them to reset state. As a result, their link partner may still see link.
Change: Put the GPHY in low power mode.
Introduced: 7.0.0.
Relevance: T0000G boards.
7. Problem: CQ56991, CQ57007 - PFC pauses non pausible traffic. This was because FW was configured to work in STATIC_COS on 57712 and 578xx regardless of kernel version. In kernels where multiple traffic classes are not supported this essentially blocked network traffic from being assigned any tc other than 0. If pausible traffic was assigned tc 0 the network traffic would necessarily collide with it.
Change: Configure FW to work in STATIC_COS only in kernels which support multiple traffic classes.
Introduced: 1.70.15.
Relevance: 57712 and 578xx on kernels before 2.6.39.
8. Problem: CQ57469, CQ57377, CQ56861, CQ57296 - CFC HW attention, XSTORM assert or kernel panic when changing the MTU under the TCP traffic (on the Tx side). Tx queues were stopped before bp->state was changed to a value different from BNX2X_STATE_OPEN, which allowed the bnx2x_tx_int() called from the NAPI context to re-enable it. This then allowed the netdev->ndo_start_xmit() to be called in the middle of the function reset and rings freeing, which caused the above failures.
Change: Change bp->state to a value different from BNX2X_STATE_OPEN BEFORE disabling the Tx queues in order to restore the protection against the above race in the bnx2x_tx_int().
Introduced: In 1.70.16 in the fix for CQ56438.
9. Problem: CQ57566 - During link down event "stats updated but no MAC active" messages appear in system log.
Change: Lowered the debug level of the message.
Introduced: Day one.
10. Problem: PMF migration during remote fault result in invalid link state.
Change: Sync link attributes during remote fault periodic check.
Change: Path correct parameter to netdev_alloc_ms()
Introduced: In 1.70.15
12. Problem: CQ57250 - The LED Link light does not turn on at 1Gb/s speed
Change: Adjust elink_set_led to allow for correct LED behavior.
Introduced: Day one.
Relevance: 578xx with direct connection.
13. Problem: CQ56820 - XMAC loopback (within "ethtool -t" test) may fail due to timing issue related to the CORE loopback type used.
Change: Change XMAC loopback to local line loopback.
Introduced: In 1.70.00.
Relevance: 578xx.
14. Problem: CQ57841 - NIG timer error and connection loss after driver is loaded.
Change: Apply NIG drain when remote fault is detected.
Introduced: In 1.70.00.
Relevance: Fiber ports.
15. Problem: CQ57738, CQ57719, CQ55158 - Remote fault detection occasionally causes link issues, and traffic problems.
Change: Remove remote-fault detection for T7.0.
Introduced: In 1.70.00.
Relevance: Fiber ports.
16. Problem: CQ56894 - packet drops during UDP stress test on 578xx.
Change: Recalculate thresholds configuration according to 578xx HW.
Introduced: In 1.70.00.
Relevance: 578xx.
17. Problem: CQ57842 - Message "Illegal configuration detected for Max BW" appears in syslog when link toggles.
Change: Adjust number of VNICs for 4-port devices.
Introduced: In 1.70.00.
Relevance: 578xx 4-port.
18. Problem: CQ56409, CQ57534 - Initiator periodically sends out Discovery Solicitation after login is established. This was caused by a missing VLAN filtering on the bnx2fc side. To enable such a filtering on the ESX bnx2fc needs to be aware of the currently configured VLANs on the CNA device.
Change: Expose the CNA VLANs configuration to the CNIC.
Relevance: FCoE on the ESX only.
Introduced: Day one.
19. Problem: Compilation failed on kernel-3.0.x.
Change: Fix compat.h.
Introduced: Day one.
20. Problem: Improper RX ring configuration showed in some case via ethtool -g.
Change: Store current device configuration and pass to ethtool handler.
Introduced: 1.64.14.
21. Problem: Degradation in latency benchmarks noted (multiple TCP_RR). This was because driver configured FW to use the same state machine for rx and tx indices in status block.
Change: Use.seperate state machines for tx and rx.
Introduced: 1.60.00.
22. Problem: Forced half duplex link may not be supported.
Change: Clear full duplex bit in Warpcore when configuring forced link.
Introduced: Day 1.
Relevance: 578x0 + 84833, no exposure to 54616S/18SE PHY because it is configured as SGMII interface, not XFI.
23. Problem: CQ56846 - 84833 PHY has no traffic LED on 10G.
Change: Enable LED stretch on a different register offset for 84833.
Introduced: Day 1.
Relevance: 84833 PHY.
24. Problem: CQ56813 - 84833 PHY can't link up at forced 100M
Change: PHY FW requires setting auto-neg advertisement even at forced link mode.
Introduced: Day 1.
Relevance: 84833 PHY.
25. Problem: 84833 can't link up at 10G after the link went down from sub-10G.
Change: Re-enable 10G advertisement on every driver load instead of relying on hardware default.
Introduced: Day 1.
Relevance: 84833 PHY.
26. Problem: 84833 PHY FW command handler interface changed (needed for (auto-grEEEn and RJ45 pair swap).
Change: Made register offset adjustments to accommodate the new interface.
Relevance: 84833 PHY.
27. Problem: CQ58086 - on 578xx B0 ETS BW 0% is not allowed by driver.
Change: Provide alternative HW configuration for this case.
Introduced: 1.70.00.
Relevance: 578xx with DCB support.
28. Problem: Driver allowed DCBX queries on non-pmf interfaces.
Change: Disable the queries on non-pmf interfaces.
Introduced: 1.70.00.
Relevance: MF devices with DCB support.
29. Problem: Driver may get out of sync with FW when UNDI is present.
Change: Init fw_seq after undi_unload is done.
Introduced: Day one.
30. Problem: GRC-timeout message may may appear in syslog during driver load. Change: 1. Remove access to removed registers in 57712/578xx. 2. Do not allow device reset while reading IGU HW block info.
Introduced: 1.64.00.
Relevance: 57712/578xx.
31. Problem: CQ57969 - The iSCSI traffic completely stops when dual port FCoE & iSCSI RX/TX is run.
Change: Fix wrong HW configuration. HW eas configured to per mac guarantee mode instead of per class guarantee mode.
Introduced: 1.70.00.
32. Problem: Compilation failed when FCOE selected but FCOELIB is not in kernel config.
Change: Fix #if condition.
Introduced: 1.70.00.
Relevance: Specific kernel configuration.
33. Problem: IP and TCP ECN related TPA aggregation rules do not comply with LRO requirements. Firmware followed requirements for RSC which are incompatible with LRO requirements: 1. Allow TPA aggregation even if TCP ECE and CWR flags are set. 2. Allow TPA aggregation only if IP ECN CE and ECT bits are either 00 or 11.
Change: Fixed in FW 7.2.0. Firmware now allows TPA aggregation only if: 1. TCP ECE and CWR are both 0's. 2. IP ECN CE and ECT bits are other than 11.
Introduced: Firmware version 6.4.0.
34. Problem: CQ56960 (iscsi) - Arrival of un-solicited ASYNC message causes firmware to abort the connection with RST.
Change: Fixed in FW 7.2.0.
Introduced: Firmware version 4.6.
35. Problem: CQ55751 - Setting advertise speed in ethtool is not working, and displaying "Advertised pause frame use" was incorrect.
Change: Fix ethtool functionality.
Introduced: Day one.
36. Problem: Device may not send pause frames when configured to pause on exhausted rings. This is seen when configuration of the TX side to "pause disable" and the RX side to "pause on exhausted ring".
Change: Fixed in FW 7.2.1.
Introduced: Firmware version 6.0.8.
Relevance: BCM57711/BCM57712/BCM578xx.
37. Problem: Arrival of target-initiated NOP-IN during intense ISCSI traffic might lead to crash.
Change: Fixed in FW 7.2.1.
Introduced: Firmware version 6.0.0.
Relevance: iSCSI only.
Enhancements: ------------- 1. Request: Add remote fault link detection for 578xx based on LSS errors in the MAC layer.
Relevance: 578xx.
2. Request: Added 54616 PHY support.
Relevance: 54616 PHY.
3. Request: Enable FEC (Forward Error Correction) on 57810-KR.
4. Request: Support vlan trunk mode in NPAR-SD mode. If that mode is active, set FW to silently remove all vlan in ingress packets.
Relevance: NPAR-SD mode only.
5. Request: Initialized NIG LLH registers to disable ACPI packet recognition and configure the ACPI patterns.
6. Request: Configure NPAR-SD function parameters via function update ramrod.
7. Request: Allow changing network cos mode after chip initialization, via a new slow path command.
Version 1.70.21 (Jul 25, 2011) ============================== Internal FW 7.0.23
Fixes: ------ 1. Problem: Warning about the pending bit coming from the VLAN_MAC object if parity error happens under the rtnl_lock().
Change: Clear the internal VLAN_MAC object pending bit if bnx2x_config_vlan_mac() is called with RAMROD_DRV_ONLY flag.
Introduced: Day one.
2. Problem: bp->sp_state bits stayed set forever set if there was a parity error under rtnl_lock()
Change: Clear bp->sp_state after interrupts are disabled.
Introduced: Day one.
3. Problem: No flow-control on 578xx when link is up at 1G and below.
Change: Add pause functionality to UMAC
Introduced: 7.0.0.
Relevance: 578xx
4. Problem: CQ56991, CQ57007 - Networking traffic priority was mapped to the COS configured at startup which was 0 by default. If FCOE or ISCSI were configured by DCBX negotiation result to COS 0 the network traffic would cause drops on a dropless traffic class and could foul up ETS or PFC.
Change: When DCBX negotiation result occurs configure all priorities other than FCOE and ISCSI to the Networking COS.
Introduced: 1.70.15
Relevance: 57712/578xx with DCB support.
5. Problem: CQ57063 - tx checksum offload feature would not turn off when 'ethtool -K eth tx off' was used.
Change: Since at startup bnx2x declares support for ipv4 and ipv6 checksum offload, connect the ethtool ipv6 set checksum premade op to the set_tx_csum op which affects both ipv4 and ipv6 instead of the ipv4 op which affects only ipv4.
Introduced: 7.0.0.
6. Problem: CQ56294 - Incorrect Remote fault detection may lead to link down on 5771x fiber devices.
Change: Fix LSS fault mechanism to detect remote fault and transmit local fault through the BMAC. This change requires leaving the BMAC out of reset in case link of 10G goes down
Version 1.70.20 (Jul 19, 2011) ============================== Internal FW 7.0.23
Fixes: ------ 1. Problem: CQ56950 - When speed is set to 1G on SFP+ device, link may fail to come up and system may hang due to incorrect initialization of the XGXS mode in the NIG.
Change: Fix typo.
Introduced: 1.70.13.
Relevance: 57712+8727 and 57711+87x6.
2. Problem: Possible race between Queues UPDATE from the NIV_FUNCTION_UPDATE and from VLAN HW stripping configuration.
Change: Move Queues UPDATE in NIV_FUNCTION_UPDATE flow to be executed from inside bnx2x_sp_rtnl_task (under rtnl_lock()).
Introduced: 1.70.14.
Relevance: NIV only.
3. Problem: Link down when running iSCSI reboot test.
Change: Ensure that PHY_TX_ERROR_CHECK_FLAG is asserted before error checking.
Introduced: 7.0.8.
Relevance: 57712 with non-optic phys.
4. Problem: CQ57055 - ESX doesn't support LRO on top of IPv6.
Change: Separate TPA queue configuration: introduce BNX2X_Q_FLG_TPA_IPV6.
Introduced: Day one.
Relevance: ESX only.
5. Problem: CQ57125 - Missing configuration for the FIP MAC in single function mode and for WWN in multi function mode.
Change: Add the missing configuration.
Introduced: Day one.
Relevance: FCoE only.
6. Problem: CQ56784 - LED doesn't flash during LED test.
Change: Add the missing configuration.
Introduced: Day one.
Relevance: 578xx.
7. Problem: During error handling "FW failed to respond" message appears.
Change: Add missing command from driver to FW.
Introduced: 1.70.08.
8. Problem: CQ56687 - Traffic LED do not blink under multiple OSes and dim.
Change: Enable LED blink and set rate.
Introduced: 7.0.0.
Relevance: 57712 + 8727.
9. Problem: Parity attentions clearing code didn't cover ATC and PGLUE_B blocks for 57712.
Change: Add the ATC and PGLUE_B blocks to the parity mask registers data base.
Introduced: Day one.
Relevance: 57712 only.
10. Problem: Parity errors recovery flow for 578xx was broken.
Change: Fix the above flow: - Add a separate column for the 578xx in the parity mask registers DB. - Fix the bnx2x_process_kill_chip_reset() to handle the blocks newly introduced in the 578xx.
Introduced: Day one.
Relevance: 578xx only.
11. Problem CQ56870 - ethtool -d (register dump) causes bnx2x panic on E3 boards.
Change Add support for E3 A0 and E3 B0 in register dump.
Introduced: Day one.
Relevance 578xx only.
Enhancements ------------ 1. Request: Fix the direction of the dma_sync() to synchronize towards CPU as it's supposed to be.
2. Request: CQ56857 - Add support for AutoGrEEEn using nvram configuration as default with module parameter to force it to on or off.
3. Request: CQ56737 - Disable TX_DIS Signal when SFP+ module is plugged out to prevent current leakage.
Relevance: 578xx.
Version 1.70.19 (Jul 13, 2011) ============================== Internal FW 7.0.23
2. Problem: Possible no link when DAC is connected to 578xx device
Change: Restart WC microcode after module is plugged in and detected.
Introduced: Day one.
Relevance: 578x0 only.
Version 1.70.18 (Jul 12, 2011) ============================== Fixes: ------ 1. Problem: CQ56434 - System crash after running IO and pulling cable. Occurs since TX pipe is stalled due to missed XON indication (from MAC did to NIG).
Change: Force XON on NIG on link down/up.
Introduced: T7.0.
2. Problem: 84833 PHY link does not come up. The extra PHY write to the auto-neg register is bringing the PHY to auto-neg failure, resulting in constant retry.
Change: Remove the extra write to this register when auto-neg is enabled.
Introduced: Day one.
Relevance: 84833 PHY only.
3. Problem: CQ56462 - Unable to get link on both ports on several systems.
Change: Initialize warpcore twice in succession.
Introduced: 1.70.03
Relevance: 578xx.
4. Problem: 84833 link still comes up at 10G even when configured to be forced 100.
Change: Properly calculate TX queue for FCoE L2 traffic.
Introduced: 1.70.15.
Relevance: 57712/578xx with FCoE.
6. Problem: Kernel warning messages regarding the attempt to access the Tx queue with index more or equal to netdev->real_num_tx_queues.
Change: Align the initialization of the netdev with the Tx multi-CoS logic.
Introduced: 1.70.15.
7. Problem: CQ56790 - During the loading of the bnx2x module there is an error indicating that the symbol bnx2x_dbg_buf could not be found.
Change: Declare bnx2x_dbg_buf as a non-static variable.
Relevance: ESX only.
8. Problem: Setting Warpcore registers may be ignored due to missing cycle in MDC/MDIO.
Change: On 578xx-B0, set free running counter on EMAC before each cl45 access, and clear it at the end. This is not done globally, to prevent clock collisions between the four MDIO masters (One per EMAC).
Introduced: Not applicable.
Relevance: 578xx-B0.
Enhancements ------------ 1. Request: Use vmalloc for a zlib inflate buffer.
2. Request: Remove unnecessary read of PCI_CAP_ID_EXP The PCIE capability offset is saved during PCI bus walking. It will remove an unnecessary search in the PCI configuration space if this value is referenced instead of reacquiring it. Also, pci_is_pcie is a better way of determining if the device is PCIE or not (as it uses the same saved PCIE capability offset).
3. Request: CQ56790 - Pass the mf_mode to the CNIC so that CNIC can determine if it needs to call the DRV_CTL_START_NPAR_CMD/DRV_CTL_STOP_NPAR_CMD to setup the NIG when in NPAR mode.
Relevance: ESX only.
Version 1.70.17 (Jul 05, 2011) ============================== Internal FW: 7.0.23
Fixes: ------ 1. Problem: PFC is not configured for ports 1,3 on 4-port devices.
Change: Enable the configuration for every port.
Relevance: DCBX, 578xx 4-port devices.
2. Problem: Warning message: "MDC/MDIO access timeout" on the first driver load. This warning appears during the link reset sequence, but it has no significant meaning, since it occur prior to the first phy initialization command.
Change: Adjust AER and CL45 clock during link reset sequence.
Introduced: Day one.
Relevance: 57712+8727.
3. Problem: "Soft lockup" errors. Caused by race between bnx2x_sp_task() and local IRQ both calling for napi_schedule(), which adds elements to a local NAPI list.
Change: Disable local IRQs when calling for napi_schedule() from bnx2x_sp_task().
Introduced: 1.60.17.
Relevance: FCoE only.
4. Problem: (CQ56741, CQ56744, CQ56697, CQ56590) "Soft lockup". Caused by race between dcb negotiation update flow and nic unload flow. The dcb update flow, which is an element in the sp work queue waits for rtnl lock in order to call bnx2x_setup_tc while nic unload flow which takes the rtnl lock waits for the sp work queue to be flushed.
Change: The dcb negotiation update flow now schedules the call to the bnx2x_setup_tc on the rtnl_sp task.
5. Problem: Possible problems in using fcoe and iscsi concurrently. The same cid was assigned to both.
Change: Allocate each its own cid.
Introduced: 1.70.15.
6. Problem: Compilation failed on vanilla kernels below 2.6.33 when FCOE module is selected.
Change: Add appropriate #ifdef structure.
Introduced: 1.70.15.
Enhancements ------------ 1. Request: CQ56174 - Add AutogrEEEn support to 54618SE PHY.
Relevance: 578xx.
2. Request: Support sharing of PFC configuration between functions on the same port.
Relevance: MF devices with DCB support.
3. Request: CQ54245 - Add Operational DCB state to GET_DCBX_PARAMS structure.
Relevance: 57712/578xx with DCB support.
4. Request: Add ability to Enable/Disable DCB according to remote configuration/absence.
Relevance: 57712/578xx with DCB support.
5. Request: Add statistics ramrods to EQ resources accounting.
Version 1.70.16 (Jun 29, 2011) ============================== Internal FW: 7.0.23
Change: Change the ESX grcDump function to use the standard functions for disabling/clearing/enabling parity attentions.
Introduced: 1.70.15.
Relevance: ESX only.
2. Problem: CQ56438 - Tx timeout was hit when there was a parity error and offloaded drivers (bnx2i/bnx2fc) loaded. It takes too long for the offloaded drivers to close (CNIC_STOP) bnx2x disabled a carrier after the CNIC_STOP completed.
Change: Moved the bnx2x_tx_disable() call to be before the CNIC_STOP call.
Introduced: Day one.
3. Problem: When DAC (Direct Attached Cable) is used, there's not actual link down event on the far side since transmitter output is not disabled.
Change: Disable transmitter output when link is disabled. The same change in MFW (since v7.0.20) will cause link to stay down using earlier version of this software (CQ56652). This version and after fixes it.
Introduced: Day one.
Relevance: 57712+8727.
4. Problem: CQ53144 - Repeating "NOHZ: local_softirq_pending 08" messages in the syslog: NAPI softirq was scheduled on a local CPU but ksoftirqd wasn't invoked. This was caused by calling the napi_schedule() for the FCoE L2 ring from a workqueue and not from the ISR as it is supposed to, which caused the above phenomenon.
Change: Disable local softirqs before napi_schedule() call (local_bh_disable()) and then re-enable them (local_bh_enable()). This will invoke the ksoftirqd if needed.
Introduced: 1.60.17.
Relevance: FCoE only.
5. Problem: In MF mode, when DCBX enabled, ifconfig down of PMF function may cause stop traffic on other function.
Change: Use generic scheme when configuring HW and FW for DCBX; Protect function from going down during inappropriate state.
Relevance: MF, DCBX only.
6. Problem: CQ56292 - bnx2x assert dump when setting MTU to 9000. This was caused by an improper initialization of the fp->rx_buf_size for none-FCoE rings which led to improper initialization of BD buffer sizes for those rings.
Change: Fix the code that initializes the fp->rx_buf_size value.
Introduced: 1.70.08.
Relevance: FCoE on ESX only (CNA).
7. Problem: CQ56531 - Kernel crash due to page fault. Num of queues supplied to kernel erroneously included the iscsi queues which resulted with kernel choosing a transmission queue index beyond the boundary of the bxn2x's tx queues array.
Change: Supply the kernel with correct number of tx queues.
Introduced: 1.70.15.
Relevance: iSCSI OOO (since kernels 2.6.34 or Red Hat 6.0).
8. Problem: CQ56582 - BCM57810 may exhibit link down when connected to KR switch.
Change: Don't overwrite the value for other reg.
Introduced: 1.70.15.
Relevance: 578xx KR.
9. Problem: CQ56538 - DCBX: The PFC pause frames being sent have source MAC address of 00:00:00:00:00:00.
Change: Initialize source MAC address in the MAC
Introduced: Day one.
Relevance: 578xx.
10. Problem: CQ56507 - Panic Dump after DCBX negotiation completed.
Change: (FW) Fix TX queue allocation scheme and DCB related firmware flows.
Introduced: 1.70.15 (FW 7.0.19).
Relevance: 57712/57810A0/57840A0, when multiple-priorities is activated together with DCB.
11. Problem: CQ54938 - Driver asserts on CFC delete command, when running stress test against an Equalogic target, while issuing RESET_LUN commands.
Change: (FW iSCSI) Decrease activity counter in the cleanup flow, to compensate for later activity counter increase.
Introduced: 1.70.01 (FW 7.0.0).
Relevance: iSCSI.
12. Problem: Basic FCoE over NIV is not working when there is inner vlan on packet.
Change: (FW ETH) Fixed the flow in NIV mode to change a zero inner vlan vid to the NIV default vlan.
Introduced: 1.70.15 (FW 7.0.21).
Relevance: BCM57712/BCM578xx, only with NIV on packets with inner vlan.
13. Problem: CQ55328 - FCoE discovery does not work with ESX CNA device. The ESX stack would complain about the number of filters for the CNA NetQueue.
Change: Call netif_set_poll_cna() after the FCoE NAPI structure has been initialized.
Introduced: 1.70.08.
Relevance: ESX CNA only.
Enhancements ------------ 1. Request: Optimized the memory barriers usage in the slow path.
2. Request: Add AutogrEEEn support to 84833 PHY.
3. Request: Implement the netdev->ndo_fcoe_get_wwn().
Version 1.70.15 (Jun 22, 2011) ============================== Internal FW: 7.0.21
Fixes: ------ 1. Problem: Need to update references from 54616 PHY to 54618SE.
Change: Updated references from 54616 PHY to 54618SE.
Introduced: Day one
Relevance: No functional impact.
2. Problem: Need to update T0000G to enable AutogrEEEn by default.
Change: Updated T0000G to enable AutogrEEEn by default.
Introduced: Day one.
Relevance: T0000G boards.
3. Problem: Driver loading problems on 4 port device with active MF mode. Problem occurs due to wrong calculation of mailbox function.
Change: In 4 port mode, change calculation of BP_FW_MB_IDX to be: port_id + vnic_id*2.
Introduced: Day one.
Relevance: 4 port device (578xx) with active MF mode.
4. Problem: Wrong calculation of the available slow path elements. As a result possible false "ring is full" messages and failures of slow path commands.
Change: Fixed the above calculations.
Introduced: 1.70.12.
5. Problem: CQ56287 - STOP_ON_ERROR compilation was broken.
Change: Make the bnx2x_int_disable() function public.
Introduced: 1.70.13.
6. Problem: Compilation failed on 2.6.39 kernels.
Change: Fix compat for the kernels.
Introduced: 1.70.13.
7. Problem: CQ56325 - 57800 does not send LLDP frames.
Change: Enable DCBX for 4-port devices.
Introduced: 1.70.01.
Relevance: 578xx 4 port devices.
8. Problem: Storm clocks were not initialized properly in E3.
Change: (FW) Remove wrong clock initialization from init tool and move it to MCP.
Introduced: Version 1.70.13 (FW 7.0.20).
Relevance: BCM57800. Power-cycle of the device is needed in order to fix the Storm frequency, a regular driver update is not enough.
9. Problem: Possible race between writing event-ring element and updating the host-coalescing index.
Change: (FW) Fix the flow by sending host-coalescing index update only after the completion of the event-ring writing.
Introduced: Version 1.70.01 (FW 7.0.0).
10. Problem: Basic FCoE on NPAR-SD was not working.
Change: (FW-FCoE) Fixed the flow in NPAR-SD mode to add default vlan also when there is vlan with vid=0 on packet.
Relevance: BCM57712 and BCM578xx, only NPAR-SD mode.
Enhancements ------------ 1. Request: Propagate WWN info up to bnx2fc driver.
Relevance: FCoE only.
2. Request: CQ56040 - Enable DCBX on ESX5.0 and newer.
Relevance: ESX with DCB only.
3. Request: Honor BAM on KR NVRAM config for 578xx.
5. Request: Add fan failure detection for 578xx-SFI
Relevance: 578xx with fan mounted.
6. Request: Support multiple concurrent classes of service for network traffic. Support mapping of skb priority to traffic class and traffic class to transmission queue in kernel. Update said mapping according to multi class queue discipline and DCBX negotiaton.
Relevance: Kernel 2.6.39 or Red Hat 6.1.
Version 1.70.14 (Jun 14, 2011) ============================== Internal FW: 7.0.20
Fixes: ------ 1. Problem: Possible spurious cnic interrupt.
Change: Properly disable cnic sb.
Introduced: 1.60.00.
Relevance: (Theoretical) when CNIC is supported.
2. Problem: In NPAR-SD mode, VIF SET request for FCoE function takes more than 40 seconds to be completed and ACKed back to the MCP.
Change: Queue update ramrod sent to FCoE ring couldn't wait for completion in the same context. Therefore, don't wait for completion for this ramrod on FCoE ring.
Introduced: 1.70.00.
Relevance: FCoE in NPAR-SD mode.
3. Problem: In NPAR-SD mode, theoretically traffic can be dropped due to early VIF SET ACK sent back to the switch.
Change: Send VIF SET ACK from driver to MCP only after function update ramrod is completed + all queue updates ramrods are completed.
Introduced: 1.70.10 (when silent vlan removal was added).
Relevance: NPAR-SD mode.
Enhancements ------------ 1. Request: CQ53961 - Remove 10Mbps from 84833 PHY. Honor PHY speed attributes for 10/100. If the driver is set up to advertise only 10M, no speed capability will be advertised. And no link will be established.
Relevance: 84833 PHY based boards.
2. Request: Add definition for autogreen in eLink.
Relevance: 84833 PHY and 54618SE PHY based boards.
Version 1.70.13 (Jun 12, 2011) ============================== Internal FW: 7.0.20
Fixes: ------ 1. Problem: Driver might set NPAR-SD mf_mode even if that mode can't be set. Driver sets NPAR-SD according to value written to NVRAM, without considering error cases such as missing NVRAM images etc.
Change: Set mf_mode to NPAR-SD only if mac address in shmem is valid. If address in shmem is valid, then MFW performed all checks and found that mode as valid.
Introduced: Day one.
Relevance: NPAR-SD mode only.
2. Problem: Memory leak in during selftest. Driver mapped skb twice.
Change: Do it once.
Introduced: 1.70.09.
3. Problem: CQ55933 - ESX CNA enabled driver tries to configure Rx mode for an FCoE ETH queue for NICs that do not support an FCoE.
Change: Configure Rx mode for an FCoE ETH queue only for the NICs that support FCoE (57712 and newer).
4. Request: Added support for 2 queues on different CoSes in 57712 and 578xx A0.
5. Request: Performance improvements in order to resolve PCI bottleneck on short packet PPS test on multiple connections.
Version 1.70.12 (May 24, 2011) ============================== Fixes ----- 1. Problem: (CQ55655) WOL is not functional on functions 2-7.
Cause: Incorrect register configuration.
Change: Allow WOL via HW registers.
Impact: Introduced in 1.64.01.
2. Problem: Undefined device behaviour when bringing up more than 16 eth queues with CNIC enabled.
Cause: Resource management mechanism does not allow more than 16 queues without actual limiting the number.
Change: Limit number of eth queues to 16.
Impact: 57712 only.
3. Problem: Possible no link on 578xx SFP+.
Cause: Failed reading from SFP+ module EEPROM due to I2C register not returning acknowledge over successful operation.
Change: Add work-around of up to 3 retries in case of I2C failure.
Impact: 578xx SFI.
4. Problem: (CQ55748) Link loss during up/down test.
Cause: Race in driver code causes it to get out of sync.
Change: Fix assignment with the lock.
5. Problem: In NPAR-SD mode, iSCSI and FCoE MAC addresses for relevant functions are zero.
Cause: In NPAR-SD mode, iSCSI and FCoE MAC addresses were not taken from shmem for functions in which these protocols are enabled.
Change: If NPAR-SD mode is used and the function is iSCSI/FCoE enabled, read suitable MAC addresses from shmem.
6. Problem: In NPAR-SD mode, default vlan tag might not be silently removed by the FW.
Cause: default vlan value and mask sent to FW in function update ramrod (for NPAR-SD mode) includes 3 bits of priority.
Change: default vlan value and mask in function update ramrod will include only 12 bits of vlan id.
7. Problem: Parity recovery was broken.
Cause: Improper handling of starting and termination of the 'periodic_task'.
Change: Ensure that only a PMF is running a periodic task. Stop a periodic task when a function is shut down.
Impact: Introduced in 1.70.09.
8. Problem: Chip may crush under PF FLR.
Cause: Driver could get interrupt on a disabled function.
Change: (In FW 7.0.18) Fixed relevant firmware flow.
Impact: Introduced in 1.70.00 (FW 7.0.0)
9. Problem: Improper device behaviour on BE platform.
Cause: Use improper calculation for FW offsets.
Change: Use FW offsets instead.
Impact: Introduced in 1.64.01
Enhancements ------------ 1. Request: Add the ability to switch settings from one speed to another in the Warpcore without having to unload the driver.
Change: Add a routine to restore the Warpcore register settings back to default. The routine is called before configuring the Warpcore to the desired speed settings.
Impact: 578xx only.
2. Request: Separate the accounting of the context-less SP commands and those that complete on the FP Rx ring.
Change: As requested.
3. Request: Reduce loading time when not in hotplug flow.
Change: As requested.
4. Request: Updates the bnx2x_set_features() to handle loopback mode.
Change: When enabled, it sets internal-MAC loopback.
Impact: Backport from upstream.
5. Request: Add 20G supported display for ethtool.
Change: As requested.
6. Request: (CQ55781) Allow GDB script to poke at the hardware registers.
Change: As requested.
Impact: ESX only.
7. Request: Reduce number of pcie transactions in high PPS rate scenarios.
Change: (In FW 7.0.18) Changing Status block DMA to host to be read from RAM instead of 3 IMM DMA's. This reduces the number of transactions on PCI and resolves with faster replenishment of PCI credits, since we reduced the number of read modify write transaction on host cash lines.
8. Request: Use FW 7.0.18.
Change: As requested.
Version 1.70.11 (May 18, 2011) ============================== Fixes ----- 1. Problem: (CQ55251) "BAD MCP validity signature" shown when device hot-plugged.
Cause: Race between FW initialization and driver load.
Change: Let FW to complete initialization by adding msleep in driver.
2. Problem: TPA is not functional on platforms where CONFIG_NEED_DMA_MAP_STATE is not defined.
Cause: We used dma_unmap_addr_set() and dma_unmap_addr() macros for internal storing and for further retrieving of the DMA mappings which were then used for BDs configuration in the TPA Rx flow while dma_unmap_addr() will always return zero on the mentioned above platforms.
Change: Don't use the mentioned above macros in flows others than "map->unmap".
Impact: TPA only. Introduced in 1.70.09.
3. Problem: Compilation failed on SLES11 SP1 update 1.
Cause: Conflict on backported feature.
Change: Fix bnx2x_compat.h.
Impact: SLES11 SP1 update 1 only.
4. Problem: Wrong link LED when speed lower than 10G on 578xx devices.
Cause: Incorrect LED mode setting.
Change: Set correct LED mode setting.
Impact: 578xx devices only.
5. Problem: One queue is not selected for transmission in kernels below 2.6.38.
Cause: Incorrect mapping function.
Change: Fix compat to implement mapping similar to 2.6.38.
Impact: Kernels below 2.6.38 with multi queue support.
6. Problem: TCM, DMAE, PBF, TIMERS, XCM, DMAE parity errors were ignored, while still asserting the "close the gates" bit.
Cause: The appropriate bits were not checked when checking for parity errors.
Change: Added the missing bits handling to the parity recovery code.
7. Problem: Compilation failed on RHEL 5.7.
Cause: Conflict on backported feature.
Change: Fix in bnx2x_compat.h.
8. Problem: (CQ55312) DMAE timeout message shown in the syslog when loading the first function on the port.
Cause: BMAC was reset after the NIG-to-BRB channel was open and before the FW was initialized. This caused the parity error in TCM.
Change: Reset BMAC before opening NIG-to-BRB channel.
Impact: Introduced in 1.70.04.
Enhancements ------------ 1. Request: Optimize buffer mapping manipulations in the TPA flow.
Change: As requested.
2. Request: Don't use atomic bit operations unless needed.
Change: As requested.
3. Request: Propagate the CFC_DEL ramrod error code up to CNIC.
Change: As requested.
Version 1.70.10 (May 5, 2011) ============================== Fixes ----- 1. Problem: LRO failure in IPv6 case.
Cause: Erroneous calculation of lro_mss size for IPv6 case.
Change: Fix LRO MSS calculation in IPv6 case.
Impact: 57712 and newer IPv6 LRO only.
2. Request: Potential link issue.
Cause: Incorrect code alignment led to bad PHY struct initialization.
Change: Fix PHY struct initialization.
Impact: Introduced on 1.70.09.
3. Request: Potential inconsistent link state report towards OS.
Cause: Possible race between netdev->open() and link attention handling flows both reporting link state towards OS.
Change: Protect the link reporting code with the same locking scheme as used for the link state handling protection.
Enhancements ------------ 1. Request: Use FW 7.0.17.
Change: As requested.
2. Request: Employ silent vlan removal feature.
Change: Silent vlan removal use: 1. In NPAR-SD mode silently remove the default vlan. 2. In ESX Network Plug-in Architecture silently remove the NPA default vlan. 3. When DCB is enabled in kernels which don't treat vlan-0 as non-vlan use silent vlan removal to: a. Remove vlan 0 with priority 0 if non fcoe queue. b. Remove vlan 0 with any priority if fcoe queue.
3. Request: Do not add VLAN tag or modify the priority of an explicit vlan tag of packets with TC_PRIO_CONTROL value in the skb priority.
Change: As requested.
Version 1.70.09 (May 3, 2011) ============================== Fixes ----- 1. Problem: (CQ53629) System spontaneously reboots.
Cause: PCI/DMA address mapping error not properly handled by driver, which may cause chip to access improper addresses in host memory.
Change: Add proper handling for mapping errors.
2. Request: (CQ49132) Link seen as up when cable(mostly fiber) is not fully connected.
Cause : In this scenario, the physical link is up, while error are detected on the MAC layer.
Change: Add periodic check for LSS errors on the MAC layer, since they don't provide indication by interrupt.
Impact: Currently only 57712. Note that this fix will not discover a case where one of two wires of fiber cable is plugged out.
3. Problem: Storms get stuck shortly after a single-engine recovery.
Cause: Functions were not unloading against MCP in case of parity error thus later LOAD request was always returning a FUNCTION load code. This lead to improper HW/FW initialization.
Change: Added unloading against the MCP in case of parity error.
Impact: 57712 and newer only. Introduced in 1.70.06.
4. Problem: Kernel panic when handling egress UDP packet for which checksum offload has been requested.
Cause: The above case hasn't been properly handled in the code.
Change: Add a proper handling for the above case.
5. Problem: In case of VLAN removal of a first small packet in TPA aggregation, driver may access uninitialized address.
Cause: Firmware places a corrupted RX completion element in this case.
Change: (in FW 7.0.16) Fixed relevant firmware flow.
Change: (in FW 7.0.16) Fixed relevant firmware flow.
Impact: Introduced in 1.70.01 (FW 6.4.0). 578XX 4-port only.
8. Problem: (CQ53924) Ethtool Self Test fails loopback test.
Cause: Unmapping of dma memory was not performed before accessing it.
Change: Added unmap of the relevant memory.
9. Problem: MDC/MDIO access to Warpcore registers may fail with low probability.
Cause: Warpcore PCB controller may get stuck without having MDC free running in the system.
Change: Add work-around for 578xx-A0 by adding another write to the MDIO bus after each MDC access to the Warpcore. This will be fixed in HW for 578xx-B0.
Impact: 578xx.
10. Problem: (DCB)(CQ54899) PMF migration may cause DCB get out-of-sync.
Cause: Driver did not update port structure correctly.
Change: Fixed DCB update code.
Impact: Introduced in 1.70.06.
11. Problem: The following error is logged as soon as bnx2fcd service is started: "kernel: 8021q: device eth# has buggy VLAN hw accel".
Cause: Under Red Hat 6.1 the bnx2x was compiled assuming the netdev centralized handling of hardware acceleration exists in kernel.
Change: Changed the bnx2x to compile using the old scheme of handling of hardware acceleration in RH6.1.
Impact: RH6.1
12. Problem: (CQ53276) 578xx ethtool display and settings are not done per board type.
Cause: Missing distinctions between various Warpcore interfaces.
Change: Check Warpcore network interface during init stage, and update the supported network attributes accordingly.
Impact: 578xx
13. Problem: (CQ54552) System breaks once link is up after PMF migration when speed is 1G.
Cause: Missing synchronization flag between PMF and non-PMF which indicate the XGXS type, led to incorrect initialization once link is up after PMF migration.
Change: Initialize this flag during synchronization
14. Problem: ethtool will not show the correct media type after PMF migration and changing the SFP+ module type
Cause: Media type was not synchronized after it is changed
Change: Synchronize media type between PMF and non-PMF
Impact: SFP+ based boards. Introduce on 1.64.19
15. Problem: Over-current message displays with port0 instead of port1 on 57712 SFP+ devices.
Cause: 57712 port enumeration is per path.
Change: Set the correct port number of the over-current display message according to the device type.
Impact: 57712 with SFP+ boards.
16. Problem: Possible dead locks in slow path flows involving interface toggling.
Cause: vlan_mac object was using spin_lock() semantics instead of spin_lock_bh() semantics while it may be called under a spin lock with BHs disabled in the ndo_set_rx_mode() flow.
Change: Fixed the mentioned above code.
Impact: Introduced in 1.70.06.
17. Problem: A possible deadlock in flows involving the DMAE operations.
Cause: We protected the DMAE engine with mutex (suspends a task when lock can't be taken) in the bnx2x_issue_dmae_with_comp() function while it is also called under a spinlock in the ndo_set_rx_mode() flow.
Change: Protect the above DMAE engine with a spinlock instead of a mutex.
Impact: Introduced in 1.70.06. 57712 and newer in the NPAR mode only.
Enhancements ------------ 1. Request: Add preliminary support for E3+84833 to pass extlb_test. Caveat that both drivers must be loaded at this time to function correctly.
Change: As requested.
2. Request: Disable FCoE and DCB on unsupported platforms.
Change: Determine allowed platforms by kernel version.
Impact: FCoE/DCB.
3. Request: Add over-current check for 578xx
Change: As requested
Impact: 578xx
4. Request: Add default TX PMD settings (de-emphasis) for 578xx.
Change: Set the TX settings per PMD type (SFI/XFI/DXGXS/KR) according to DVT measurements to achieve optimal link.
Impact: 578xx.
5. Request: Use FW 7.0.16.
Change: As requested.
6. Request: Write driver version string to specified offset in scratchpad for NC-SI OEM commands.
Change: Read scratchpad offset from ncsi_oem_data_addr field of shmem2. Then, write driver version to appropriate offset.
7. Request: Remove zeroing of Ram0 from driver as it is performed by init tool.
Change: Removed relevant code and the defines.
Version 1.70.08 (Apr 11, 2011) ============================== Fixes ----- 1. Problem: Possible chip hang in case of parity error in QM.
Cause: QM was reset before PXP causing 'close the gates' to be de-activated shortly before resetting PXP, PSWRQ sends a write request to PGLUE, PXP is reset, PGLUE tries to read the payload data from PSWWR, but PSWWR does not respond. The write queue in PGLUE will be stuck, DMAE commands will not return.
Change: Change reset order of PXP and QM blocks so that PXP is reset before QM.
Impact: During error recovery flow of QM parity attention only. Introduced in 1.53.1.
2. Problem: Tx of a CNA netdev wasn't properly disabled.
Cause: Typo in a bnx2x_tx_disable().
Change: Fix the above typo.
Impact: ESX CNA only. Introduced in 1.64.13.
3. Problem: Fairness issue between functions 0, 1 and functions 2,3 on 57840 4x10G.
Change: Do not overwrites cnic_eth_dev->drv_state in bnx2x_register_cnic().
Impact: iSCSI and FCoE only.
5. Problem: Possible inconsistent rx_mode state for iSCSI L2 queue.
Cause: Both BNX2X_FILTER_ISCSI_ETH_START_SCHED and BNX2X_FILTER_ISCSI_ETH_STOP_SCHED bits might be set, which in line might cause the situation when the rx_mode that is finally configured is not the one that has been requested the last.
Change: Clear the already pending state when configuring the new one.
Impact: iSCSI L2 only.
6. Problem: (CQ51066) Link status in port mailbox indicates AUTONEG is disabled and no Serdes.
Cause: Link status was zeroed during link down state.
Change: Set AUTONEG and SERDES indications when needed.
7. Problem: Possible pending SP ramrod completion after FUNC_STOP ramrod is sent.
Cause: Missing protection when checking bits in bnx2x_wait_sp_comp().
Change: Added the protection with netif_addr_lock for the mentioned check.
Impact: Introduced in 1.64.00.
8. Problem: (CQ54422) Compilation Failed on RHEL 6.1.
Cause: Backported features complict.
Change: Adopt features in compat.
9. Problem: Potentioal race in NPAR-SD mode might cause sending of function update ramrod before function start ramrod is completed.
Cause: LOAD_DONE message to MCP is sent before function start ramrod. LOAD_DONE request starts VIF initialization process that ends with VIF_SET request from the switch that triggers function update ramrod.
Change: Perform function start ramrod before sending LOAD_DONE message to MCP.
2. Request: Integrate the upstream "Support for managing RX indirection table" patch by Tom Herbert implementing the support for ethtool -X/-x options.
Change: Integrated the mentioned patch taking into the account all remarks of the netdev people about this patch.
3. Request: Add 1G support for XFI serdes network interface type of Warpcore
Change: As requested
Impact: 578xx - XFI
Version 1.70.07 (Apr 04, 2011) ============================== Fixes ----- 1. Problem: TX fault LED doesn't work upon module validation.
Cause: Incorrect GPIO assignment.
Change: Fix GPIO setting that controls the TX fault LED.
Impact: 578xx - SFP+.
2. Problem: DAC may not link up.
Cause: Register read was missing after setting EDC mode.
Change: Read EDC register after setting it.
Impact: 578xx - DAC.
3. Problem: Parity errors prevent device from load on emulation environment.
Cause: Emulation environment limitation.
Change: Disable parity on emulation environment.
Impact: Emulation environment only.
4. Problem: Incorrect SFP+ module power setting.
Cause: Value was swapped.
Change: Reverse value to fit board scheme.
Impact: 578xx SFP+ when nvm cfg #160 is set.
5. Problem: When accept all TX packets is enabled (all TX packets are duplicated to both the physical and loopback ports), LSO traffic throughput is less than expected.
Cause: Firmware accounted duplicated LSO (and also some non-LSO) packets twice in the rate shaping algorithm, instead of only once.
Change: (In FW 7.0.15) Fixed relevant firmware rate shaping bytes calculation for duplicated TX packets.
Impact: Introduced in 1.64.01 (FW 6.4.0).
6. Problem: PF FLR while VFs are running may cause system to get stuck.
Cause: If VF FLR happens after PF is down, the VF may try to send an event message to the PF by mistake.
Change: (In FW 7.0.15) Fixed relevant firmware flow.
Impact: Introduced in 1.70.00 (FW 7.0.0).
7. Problem: When TPA is enable, tcp packets with erroneous length might add wrong bytes to packet.
Cause: Firmware didn't verify the packet length is equal Ethernet header + IP total length.
Change: (In FW 7.0.15) Added the required verification.
Impact: Introduced in 1.64.01 (FW 6.4.0).
8. Problem: (FCoE) FCoE on physical port 1 can't be enabled.
Cause: Wrong cos allocation.
Change: (In FW 7.0.15) Fixed relevant firmware flow.
Impact: 57810/57840 only. Introduced in 1.70.00 (FW 7.0.0).
9. Problem: (iSCSI) Chip hangs upon arrival of iSCSI packet with split digest.
Change: Add DCBX notification mechanism during PMF migration.
3. Problem: (DCB) Static configuration is not properly handled.
Cause: Static configuration flow does not handle HW interrupt, because of state where DCBX initialization performed.
Change: Move DCBX initialization to the end of nic_load.
Impact: DCBX involved flows.
4. Problem: (CQ53768) Kernel panic at bnx2x_cnic_reuse_ooo_pkt.
Cause: Wrong arithmetics on Tx HW consumer for a Forwarding ring.
Change: Fixed the above arithmetics.
Impact: iSCSI OOO only. Introduced in 1.64.00.
5. Problem: (CQ53347) Data does not validate reported while running Chariot for RH6.0 x64.
Cause: In case of VLAN removal of a first packet in TPA aggregation, firmware may add padding bytes in the middle of the packet.
Change: (in FW 7.0.14) Fixed relevant firmware flow.
Impact: Introduced in 1.70.00.
6. Problem: (CQ53523) System stuck during load/unload under traffic.
Cause: RX processor can get stuck in infinite loop when a set mac configuration is done during traffic.
Change: (in FW 7.0.14) Fixed relevant firmware flow.
Impact: Introduced in 1.70.00.
7. Problem: Link may not come up after SFP+ module plug in on BCM8726 based boards
Cause: Module detection was not triggered by module insertion, which may lead to incorrect setting of EDC mode
Change: Initialize AEU before collecting the group of signals in charge for generating interrupts
Impact: BCM8726 based boards Introduced in 1.52.50
8. Problem: (CQ54040) Unable to perform iSCSI login.
Cause: Missing iSCSI L2 and Netq MAC ramrods completion handling.
Change: Added a missing code.
Impact: iSCSI and ESX only.
9. Problem: bnx2x_func_state_change() and bnx2x_queue_state_change return a negative value while PENDING (1) value should be returned.
Cause: test_bit(nr, vec) returns all-F's if nr is a variable and the requested bit is set.
Change: Chaged test_bit(nr, vec) to !!test_bit(nr, vec) when nr is a variable.
Impact: Introduced in 1.64.08.
10. Problem: If MCP sends to driver second NPAR-SD event before first one handling is done, no NPAR-SD events will be handled since now on. Note that second event from MCP while first one is not done yet should not happen due to "one pending" mode, but it is good practice to handle both messages if such a scenario occures in some way.
Cause: drv_status field was checked to match exact value instead of bit masking the value to match various events.
Change: Check drv_status bits to know which NPAR-SD events should be handled.
Impact: NPAR-SD mode only.
11. Problem: (CQ52000 & CQ51697 Cont.) XAUI short detection mechanism only applies to 10G.
5. Request: Add a support for a parity errors recovery for 57712 and newer.
Change: As requested.
6. Request: Add MOD_ABS support for 578xx SFP+ modules
Change: As requested.
7. Request: Invert OPTRXLOS signal on SFP/XFP interface for 578xx
Change: As requested.
Version 1.70.05 (Mar 17, 2011) ============================== ***** This version does not support CNIC *****
1. Problem: (CQ53457) in MF mode actual TX max bandwidth differs from configured for the device.
Cause: non-pmf function has overwritten configuration according to 10G link speed in UP flow.
Change: Fix device load flow for non-pmf functions.
Impact: MF mode with link speed other than 10G.
2. Problem: (CQ5772) (NPAR) Some configuration of Bandwidth Weight and Maximum Bandwidth is not functional.
Cause: MAX algorithm timer was set to smaller value then MIN algorithm. In some cases this may cause under-run on the line.
Change: Increase MAX algorithm timeout from 100usec to 400usec.
Impact: Introduced in 1.64.09.
3. Problem: (CQ52834) (iSCSI) connection/login issues in DCBX environment.
Cause: Erroneous context override by firmware.
Change: (in FW 7.0.12) Fixed relevant firmware flow.
Impact: DCBX environment only.
4. Problem: (CQ53526) (NPAR) Driver asserts while running iSCSI/L2 traffic.
Cause: Forward channel configured for TX switching.
Change: Disable TX switching for FWD channel.
Impact: NPAR mode.
5. Problem: (CQ53414) bnx2x reports link down when loaded.
Cause: The code was set to report the link state on load time.
Change: Assume the link is down when loading and only report link up after loading.
6. Problem: (CQ53427) ethtool reports incorrect info for 10GE Passive Copper Cable connections
Cause: Cable type was not taken into consideration
Change: Determine port type using cable type information acquired from external SFP+ module if exists
Impact: SFP+ type
7. Problem: No fan failure notification when the fan failed and nvram option 83 is set to enabled.
Cause: The fan failure worked only for specific external PHYs and not according to option 83.
Change: Enable fan failure regardless of the PHY type if option 83 is set to enable.
Impact: No fan failure notification unless the PHY is SFX7101, BCM8073, BCM8481, BCM84823 or BCM84833 - other PHYs or designs without external PHY will not report fan failures (but the FW will stop the PHY).
8. Problem: Ethtool self test idle check tests erroneously for active connections.
Cause: 1. Input registers were confused. 2. Connection type bit offset has changed since 57712.
Change: Converted self test idle check to work with static record array Corrected register confusion and location of connection type.
Impact: Saved 18% off linux driver compilation time.
9. Problem: Rx and Tx coalescing timeout parameters are reversed.
Cause: Parameters passed erroneously between functions.
Change: Swapped parameters in function call.
Impact: Bug exists in all bnx2x versions supporting interrupt coalescing.
10. Problem: (CQ52887) Interrupt test using ethtool's self test fails.
Cause: The ramrod, RAMROD_CMD_ID_ETH_EMPTY, is used for both the interrupt test and NetQueue commands. When self test is ran, the NetQueue would always intercept this ramrod but not complete the command.
Change: Do not explicitly intercept the EMPTY ramrod in the netq code. Instead use the appropriate SP queue object to send the EMPTY ramrod.
Impact: ESX only.
11. Problem: ethtool shows the wrong port connected.
Cause: Dual media port presentation was swapped.
Change: Show the active port.
Impact: Dual media board.
12. Problem: (CQ53303, CQ52600) Firmware doesn't support FLR on both ports on the same path simultaneously on 578xx.
Cause: The Flr flow hold some variables only for the last port treated.
Change: (in FW 7.0.13) Added an array to hold separate variables for each port.
Impact: Only 578xx.
13. Problem: FCoE doesn't identify function in NPAR-SD mode.
Cause: FW use MAC classification.
Change: (in FW 7.0.13) Classify function according to ID.
Impact: Introduced in 1.70.01.
14. Problem: (iSCSI) Chip hangs upon arrival of iSCSI packet with FIN flag set.
Cause: Tstorm signals Ustorm to release same BRB block twice.
Change: (in FW 7.0.13) Fixed relevant firmware flow.
Impact: Introduced in 1.64.01.
Enhancements ------------ 1. Request: Add initial support for 1G over fiber.
Change: As requested.
Impact: 578xx fiber.
2. Request: (CQ50798) Add support for BCM8722.
Change: As requested.
3. Request: Allow set speed in NPAR mode when device still closed.
Change: As requested.
4. Request: Use FW 7.0.13.
Change: As requested.
5. Request: Use DCBNL app-list to store negotiated app tlvs.
Change: As requested.
6. Request: Add support for DCBNL peer information.
Change: As requested.
7. Request: Honor GPIO configuration values on Tx laser control, on top of existing EPIOs.
Change: As requested.
Impact: 578x0 SFP+ designs.
8. Request: Link support for Everest 57810 + 84833B0PHY.
Change: As requested.
Impact: Everest 57810 + 84833B0PHY combination can pass traffic for testing.
9. Request: Add SGMII support for a specific OEM design.
Change: Clear signal detect and configure internal PHY before BCM54618SE establishes link.
Impact: SGMII ports of 57800 only.
10. Request: (CQ52000 & CQ51697) Short on XAUI lanes on the MAC side of 8727 and 8706 PHYs needs to generate link down event.
Change: Tx fault detection has been added. In addition link qualification includes checking for Tx fault. The fault detection bit is read twice to clear any stale value.
Impact: 8727 and 8706 PHYs.
11. Request: Support added for E3 + 84833B0 PHY firmware upgrade.
Change: As requested.
Impact: E3 + 84833B0 PHY combinations.
12. Request: Disable Tx switching for 57712/578xx.
Change: As requested.
Impact: 57712/578xx in NPAR mode, ESX.
Version 1.70.04 (Mar 01, 2011) ============================== ***** This version does not support CNIC ***** Fixes ----- 1. Problem: (CQ53258) Ethtool self test fails loopback_test (offline) when run on the copper ports
Cause: Test was done over 10G rather than 1G, and test did not wait long enough for the link to come up
Change: When speed capability doesn't include 10G, then perform the self test using 1G. In addition, for PHY loopback test, wait for the link to come and not assuming it is already up.
Impact: 57800 copper ports
2. Problem: (CQ51134) NC-SI functionality dependant on Port initialization Sequence
Cause: During common init, the driver resets both BMACs such that if NCSI was enabled on the other port, it will stop working
Change: BMAC will be reset during port initialization only
Impact: 5771x with NCSI enabled
Version 1.70.03 (Feb 24, 2011) ============================== Fixes ----- 1. Problem: ethtool -t under heavy traffic may show idle_check error.
Cause: idle_check mistakenly reported error.
Change: Fix idle_check routine.
2. Problem: (CQ53143) Configuring a primary ETH MAC with ifconfig tool didn't clear the old MAC configuration.
Cause: Missing code that clears the old MAC configuration.
Change: Added a missing code.
Impact: Introduced in 1.64.00.
3. Problem: (CQ51593) Statistics are inaccurate on 578xx devices.
Cause: Improper handling data from MSTAT HW block.
Change: Fix data handling.
Impact: 578xx only.
4. Problem: "DMAE timeout" appears in syslog and chip halts.
Cause: Improper HW initialization sequence.
Change: (v2) Fixed relevant init sequence.
Impact: Introduced in 1.70.00.
Enhancements ------------ 1. Request: Translate 10G-Force KR and 1G-Force KR to autoneg with advertisement of 10G and 1G in accordance.
Change: As requested.
Impact: 578xx KR interface.
2. Request: Support NVRAM configuration of EPIO assignment on Tx laser control.
Change: As requested.
Impact: 578xx SFP+ interface, existing boards with this parameter unconfigured should still work using hardcoded default EPIO.
Version 1.70.02 (Feb 21, 2011) ============================== Fixes ----- 1. Problem: (CQ52452, CQ50960) VLAN stripping is not enabled for higher functions when function 0 is not up.
Cause: Function ID field was always set to zero in UPDATE ramrod data.
Change: Properly configure the above field in the ramrod data.
Impact: Multi-function only. Introduced in 1.64.00.
2. Problem: NULL pointer dereference in a flow of closing iSCSI L2 queue.
Cause: SW bug that caused cnic handler routine not to be called for CFC_DEL ramrod completion of iSCSI L2 queue.
Change: Fix the above SW bug.
Impact: iSCSI only. Introduced in 1.70.01.
3. Problem: (CQ52417), (CQ52845) Flow control doesn't work for 20G.
Cause: Flow control wasn't enabled for 20G.
Change: Set flow control on 20G according to settings.
Impact: 57840 20G.
4. Problem: (CQ52023) Driver asserts with HW attention.
Cause: Traffic type to priority/COS table was reset after link down by driver causing transmission on the wrong COS.
Change: (In FW 7.0.10) Removing the table in RAM from HSI section.
Impact: Introduced in 1.64.00 (FW 6.4.0).
5. Problem: System may crash when configuring some RX rings with TPA enabled and some with TPA disabled.
Cause: Firmware tries to do TPA also for the non-TPA clients.
Change: (In FW 7.0.10) Fixed relevant firmware flow.
Impact: Introduced in 1.64.9 (FW 6.4.15). BCM57710/57711/57711E only.
6. Problem: System crash under TCP traffic when driver is toggling TPA.
Cause: Firmware bug.
Change: (In FW 7.0.10) Fixed relevant firmware flow.
Impact: Introduced in 1.64.03 (FW 6.4.7).
7. Problem: Firmware aggregated packets with wrong checksum.
Cause: Firmware didn't check checksum as a requirement for aggregation.
Change: (In FW 7.0.10) Fixed relevant firmware flow.
Impact: Introduced in 1.64.0 (FW 6.4.0).
8. Problem: 10G-KR doesn't link up on an OEM design.
Cause: CL72 should not be disabled in KR environment.
Change: Removed codes that disables CL72.
Impact: 578xx 10G-KR.
9. Problem: Possible packet corruption when resetting the primary interface when there are VLAN interfaces configured for this interface.
Cause: VLAN HW acceleration (stripping) is configured after Rx packets are allowed at the end of netdev->open().
Change: Configure VLAN stripping in Client SETUP if there are VLAN interface already configured for this interface.
Impact: Kernels below 2.6.37. Introduced in 1.62.01.
10. Problem: System locks up after loading driver on 1Gb copper ports.
Cause: Incorrect interrupt acknowledge when link change occurs lead to interrupt storm.
Change: Acknowledge the interrupt correctly on 1G ports.
Impact: 578xx with 2x1G and 2x10 port. Introduced in 1.70.01.
11. Problem: When resetting/disabling link in 578xx boards output for TX PAUSE signal to the MAC is not disabled
Cause: Relevant register in the NIG is not cleared when link is disabled.
Change: Set value to 0 in that register if link is disabled.
Impact: 578xx.
12. Problem: BCM578xx may misconfigure the link on some OEM designs.
Cause: ELink determines 4-port mode strictly from the input pin, not from override register that MFW always configures.
Change: Changed to determine the 4-port mode by reading the override register.
Impact: 578xx.
13. Problem: Driver unload may halt under traffic fails.
Cause: Incorrect order of disabling XMAC.
Change: Close the XMAC RX path before issuing XMAC soft reset.
Impact: 578xx.
14. Problem: (CQ51417) ethtool -t may cause device to hang.
Cause: Race in interrupt handling during self test.
Change: Wait for SP completions in load flow to avoid the race.
Impact: Introduced in 1.64.01.
15. Problem: Drivers assert while transmitting packets.
Cause: Firmware lose packets synchronization during transmission (Xstorm Assert).
Change: (In FW 7.0.11) Fixed relevant firmware flow.
Impact: Introduced in 1.64.10. (FW 6.4.15). 57712/578xx only.
16. Problem: (CQ52536) Extra bytes might be added in the middle of the payload when a packet with padding after the TCP payload is received, while TPA is enabled.
Cause: Firmware wrongly places padding bytes on RX SGEs.
Change: (In FW 7.0.11) Fixed relevant firmware flow.
Impact: Exists in all previous versions. The problem will be exposed only in very rare case in which a device on the network pads the Ethernet packet to longer than 72 bytes.
17. Problem: "DMAE timeout" appears in syslog and chip halts.
Cause: Improper HW initialization sequence.
Change: Fixed relevant init sequence.
Impact: Introduced in 1.70.00.
18. Problem: ethtool -t fails on 578xx B0.
Cause: test accessed unexistent registers.
Change: remove improper access.
Impact: 578xx only.
Enhancements ------------ 1. Request: Remove support for 57710 emulation and FPGA.
Change: As requested.
2. Request: Add performance improvements to Ethernet TX flows in BCM57711.
Change: (In FW 7.0.10) Added optimizations in TX flow.
3. Request: Use FW 7.0.11.
Change: As requested.
4. Request: CQ52000 Short on XAUI lines between Everest 2 and 8727 PHY needs to generate link down event.
Change: Tx fault detection has been added. In addition link qualification includes checking for Tx fault.
5. Request: Collect FW TPA statistics: aggregations, bytes in aggregations and a number of aggregated network frames.
Change: As requested.
Version 1.70.01 (Feb 07, 2011) ============================== Fixes ----- 1. Problem: Potential wrong PHY initialization when loading the first function on a port, after another function from this port was unloaded.
Cause: In this case, the driver won't lock PHY access, which may cause MDC/MDIO collision.
Change: Initialize the lock flag on the probe stage, instead of the common and port init stage.
Impact: Multi-function mode.
2. Problem: CQ52212 8073PHY intermittently exhibits signs of disconnected devices upon loading/unloading.
Cause: Microcontroller and Driver both controlling Xaui Low Power Mode.
Change: Remove Driver control of Xaui Low Power Mode.
Impact: 8073PHY based boards.
3. Problem: CQ51624 PHY TXONOFF_PWRDN_DIS bit set to "1" instead of default 0 to prevent reset & power down of PHY.
Cause: When GPIO controls TX Laser on 8727 and 8706, turning off laser will put PHY in low power mode.
Change: Set TXONOFF_PWRDN_DIS accordingly.
Impact: 8727PHY and 8706PHY based boards with TX laser controlled by GPIO_0.
4. Problem: L2 TX LSO Packets with LLC-SNAP header and in-band VLAN header are corrupted (BCM57710/BCM57711/BCM57711E).
Cause: Firmware sends an illegal command, resulting with a corrupted header in such cases.
Change: (in FW 7.0.9) Fixed relevant firmware flow.
Impact: BCM57710, BCM57711 and BCM57711E only.
5. Problem: (iSCSI) Chip hangs when running iSCSI IOs bigger than 32KBs.
Cause: Firmware bug.
Change: (in FW 7.0.9) Fixed relevant firmware flow.
Impact: Introduced in 1.64.01 (FW 6.4.0).
6. Problem: 57710 constantly get a parity errors in PBF and TM blocks during TCP/UDP traffic.
Cause: False parity errors in the above blocks. PBF and TM blocks parity error attentions are not implemented in 57710.
Change: Don't enable parity attentions in the PBF and TM blocks on 57710.
Impact: 57710 only. Introduced in 1.70.00.04.
7. Problem: The atempt to configure iSCSI MAC address would cause a "NULL pointer dereference" error when CNIC module was loaded before L2 interface is opened.
Cause: iSCSI L2 MAC object was initialized before bp->slowpath memory was allocated (bp->slowpath was NULL at that stage). So, as long as the object used references to bp->slowpath memory, it caused the above error, when we tried to utilize it.
Change: Move iSCSI L2 MAC object initialization from bnx2x_cnic_probe() to the DRV_CTL_START_L2_CMD callback.
Impact: iSCSI L2 only. Introduced in 1.64.00.
8. Problem: iSCSI L2 queue wasn't receiving any packet.
Cause: Rx mode of this queue didn't have ACCEPT_ANY_VLAN option. Therefore FW filtered every packet by VLAN (assuming untagged frames having VLAN_ID 0) and as long as there were no HW VLAN acceleration configured, no frames were delivered to iSCSI L2 queue.
Change: Added ACCEPT_ANY_VLAN option to iSCSI L2 queue rx mode.
Impact: iSCSI UIO only. Introduced in firmware version 1.64.00.
9. Problem: (CQ52656) In NPAR mode "ethtool -t ethX" does not report error on some partitions while no link.
Cause: Link is not tested for non PMF partitions.
Change: Allow link testing for non PMF partitions.
Impact: NPAR mode only.
10. Problem: (CQ52402) In NPAR mode setting some speed via ethtool -s causes device to hang.
Cause: FW configured with illegal configuration.
Change: Limit allowed speed to range from 1%-100% of actual line speed.
Impact: NPAR mode only.
11. Problem: (CQ51417) Running ethtool -t causes the interface to hang.
Cause: Link test was checked according to 57711/2 scheme rather than 578xx.
Change: Test link according to the chip type.
Impact: BCM578xx.
12. Problem: Possible problems with buffers mapping in iSCSI OOO flow on kernels 2.6.34 and newer.
Cause: Improper mapping functions used (pci_xxx instead of dma_xxx).
Change: Use the proper mapping functions in the above flow.
Impact: iSCSI OOO only. Kernels 2.6.34 and newer. Introduced in 1.60.15.
Enhancements ------------ 1. Request: Add autoneg parallel detect and pause support for 578xx KR.
Change: As requested.
Impact: 578xx-KR.
2. Request: Use FW 7.0.9.
Change: As requested.
3. Request: Set default number of rx buffers to be divided equally between rx queues to decrease amount of pre-allocated buffers on systems with multiple CPUs.
Change: As requested.
4. Request: Configure a mini-jumbo (2500) MTU for FCoE L2 ring. Don't change it when NIC's MTU changes.
Change: As requested.
5. Request: Call for a cnic handler routine for CFC_DEL ramrod completion of iSCSI L2 queue.
Change: As requested.
Version 1.70.00.4 (Jan 19, 2011) ============================== Fixes ----- 1. Problem: VIF_LIST_GET request in NPAR-SD mode responded always with zero value.
Cause: drv mailbox param value was cleared after valid value was written, and therefore zero was read by the MCP and sent to the switch.
Change: Fix the logic.
Impact: NPAR-SD mode only.
2. Problem: Warpcore microcode wasn't loaded as image from nvram.
Cause: Non-clear loading sequence from the nvram forced loading microcode statically as temporary work-around.
Change: Warpcore microcode will be loaded solely from the nvram by the bootcode.
Impact: 578xx only; Requires bootcode 7.0.0.0/6.4.3 and above.
3. Problem: Statistics is not displayed correctly on 578xx.
Cause: Improper initialization.
Change: Fix initialization flow.
Impact: 578xx only.
4. Problem: NPAR-SD packets did not reach MCP after driver is loaded.
Cause: NIG registers initialization by the driver did not mark that NPAR-SD tag header can be included in rx packets, and overwrote value inserted by the MCP.
Change: Write correct value to that register in NPAR-SD mode.
Impact: NPAR-SD mode only.
5. Request: BCM8727 Link LED not functioning properly during BACS LED test.
Change: Not blinking correct link light.
Impact: BCM57712 + BCM8727 based boards.
6. Problem: (CQ51134) NC-SI functionality dependant on Port initialization Sequence.
Cause: When the driver loads the first port, some PHYs require reset and loading their microcode on both ports. In case NCSI was enabled on the other port, the traffic was stopped since PHY was reset.
Change: Load PHY microcode during common init, only if the PHY microcode wasn't loaded.
Impact: Requires bootcode 6.2.9 to resolve this problem PHY firmware upgrade will require reboot from now on.
7. Problem: (CQ51367) - BCM84823/84833 activity LED blinks at lower rate on 10G link.
Cause: The activity LED control registers are not configured right.
Change: Enabled activity LED stretch_en bit. Made activity LED blink on source.
Impact: BCM57712 + BCM84823/84833 based boards.
8. Problem: ESX - CNIC 'change MTU' would fail or result in a PSOD.
Cause: Mismatched module IDs for request/free IRQ.
Change: Masquerade as CNIC when cnic ops are called form bnx2x.
Impact: ESX only.
9. Problem: (NPAR, FCoE) FCoE MAC wasn't read in NPAR mode.
Cause: Missing code.
Change: Add the missing code.
Impact: FCoE in NPAR mode only.
10. Problem: (iSCSI) If iSCSI offload is requested in switch dependent MF mode zero MAC would be configured for iSCSI L2 queue.
Cause: Bug in a driver.
Change: Prevent the configuration of an illegal MAC.
Impact: iSCSI in switch dependent mode only.
11. Problem: (CQ51413) Driver crashed, when number of queues was set to a value smaller than a default one due to SAFC configuration.
Cause: Broken connection between an SAFC initialization and a memory allocation code.
Change: Fixed the above flaw.
Impact: SAFC only. Introduced in 1.62.06.
12. Problem: "Statistics sequence counter out of order" storm assert.
Cause: Race between the LINK_UP event handler and the timer which both are calling the bnx2x_storm_stats_post() thus sending consequent statistics ramrods without waiting for a completion of the first. Therefore FW will read the ramrod data of the second ramrod while handling the first one, which will cause the above assert.
Change: Prevent the above race.
13. Problem: Possible sending of a spurious MSI-X message after MSI-X is disabled.
Cause: MSI-X configuration wasn't properly cleared when MSI-X was disabled.
Change: Properly clear MSI-X configuration.
Impact: Introduced in 1.60.28.
14. Problem: Kernel panic when loading bnx2x with int_mode=1 and disable_iscsi_ooo=1.
Cause: INT#x ISR was scheduling iSCSI OOO ring's NAPI regardless NO_ISCSI_OOO flag.
Change: Consider NO_ISCSI_OOO flag before scheduling iSCSI OOO ring's NAPI.
Impact: Introduced in 1.64.07.
15. Problem: XSTORM assert due to wrong values in XSTORM RAM, occurring after turning up first interface on the other path (specifically traffic_type_to_priority_cos table was cleared in XSTORM RAM).
Cause: driver used to reset LCPLL in bnx2x_init_hw_common process, which is performed per each path. That configuration is not needed as it is done by the MCP, and is wrong because LCPLL is common and not per path.
Change: Remove that configuration from driver (it is done by MCP).
16. Problem: In NPAR-SD mode - DCBX configuration was not updated in FW.
Cause: Relevant implementation was removed as a workaround because of the side effects it caused. Those side effects were caused by two bugs resolved in this version (problem #12 and problem #15 above).
Change: Re-enable DCBX configuration implementation in NPAR-SD mode (remove workaround that prevented it).
Impact: NPAR-SD mode only.
17. Problem: 578xx B0 can't receive traffic in SD mode.
Cause: Inverted port configuration.
Change: Fix port configuration.
Impact: 578xx B0 only.
18. Problem: (FCoE) There was no licensing for FCoE.
Cause: Missing FCoE licensing handling code.
Change: Added the missing code.
Impact: FCoE only.
19. Problem: (NIV) VIF_SET ack was sent twice from driver to MCP and causing logic errors.
Cause: Wrong implementation that if bnx2x_func_state_change returns non zero value it is an error, while in fact only negative value is error.
Change: Assume error only if bnx2x_func_state_change returns negative value.
Impact: NPAR-SD only.
20. Problem: 57840: 4 port mode is not functional.
Cause: Incorrect initialization for this mode.
Change: Fix driver and FW (7.0.7) initialization.
Impact: 57840 only.
21. Problem: 57840: 4 port mode - Grc-timeout appears in syslog.
Cause: Statistics HW is not properly initialized.
Change: Init MSTAT1 correctly.
Impact: 57840 4 port mode only.
22. Problem: DMAE timeout after a few modprobe->ifup->rmmod iterations.
Cause: PGLUE_B was disabled before BMAC reset is completed.
Change: Fixed the relevant driver flow.
Impact: Introduced in 1.64.08.
23. Problem: a. rx error packets detailed in ethtool were increasing all the time while NPAR-SD session is up. b. rx error packets detailed in NPAR-SD protocol STATS_ARRAY_GET request were increasing all the time while NPAR-SD session is up (in UIF type request only).
Cause: all NPAR-SD messages reached host, but are destinated to vif_id of the MCP which is unknown to FW. Therefore, FW marks these packets as per port mf_tag_discard packets.
Yet, these per port statistics were also counted in PMF's per func statistics as rx error packets, and were also sent as rx error bytes in per port stats request of NPAR-SD protocol.
Change: a. Don't count per port mf_tag_discard/outer_vlan_discard packets as per func rx error packets of the PMF. b. Don't count per port mf_tag_discard/outer_vlan_discard packets as per port rx error packets sent in stats request of NPAR-SD protocol.
24. Problem: The module date was not updated since 2010/08/01.
Cause: The date was moved to another source file which did not updated it automatically on submission to the version control system.
Change: Update the file properties so the version control system will update the date automatically.
Impact: Introduced in 1.60.32.
25. Problem: 578xx unable to link after unload-load sequence.
Cause: Incomplete reset sequence.
Change: Fix reset sequence.
Impact: 578xx.
26. Problem: 578xx 4-port: load/unload test fails when compiled with CNIC.
Cause: Inappropriate client_id configuration for non eth clients.
Change: Fix initialization for 4-port mode.
Impact: 578xx 4port.
27. Problem: 57800 GPHY port (SGMII) LEDs don't work.
Cause: The LED setting routine is called only on 10G link.
Change: Call the LED setting routine even for non-10G link.
Impact: 578xx.
28. Problem: Unable to receive multicast frames on high functions in a multi-function mode.
Cause: approx_mcast_engine_id was not properly initialized in setup ramrod data.
Change: Fixed the relevant driver code.
Impact: Mutli-function mode only.
29. Problem: 578xx 4-port: load/unload test fails when compiled with CNIC.
Cause: Inappropriate client_id configuration for non eth clients.
Change: Fix initialization for 4-port mode.
Impact: 578xx 4port.
30. Problem: ifup returned error when device has illegal iSCSI mac.
Cause: FCoE/iSCSI features were enabled even with illegal mac.
Change: Disable the features if mac is illegal.
Impact: 57712 SF mode.
Enhancements ------------ 1. Request: CQ51710 - Disable CMS (common mode sense) feature in 84823 PHY, as this reduces power consumption and allows a better 10G link stability.
Change: Clear the CMS bit in PHY register in PHY configuration routine.
Impact: BCM84823B based boards.
2. Request: (CQ51889) Add Common Mode Sense (CMS) enable/disable functionality.
Change: Adding field 156 to nvm cfg, as well as support in eLink.
Impact: NVM config and Common Mode Sense capable PHYs.
3. Request: Increase RX ring size to 512 when using Jumbo Frames.
Change: As requested.
Impact: ESX only.
4. Request: Enable OOO by default and have the OOO ring match in size with a RX ring.
Change: As requested.
Impact: ESX only.
5. Request: Add statistics collection for NPAR-SD, and copy results to expected location in scratchpad if requested by the MCP due to request from the switch.
Change: Added NPAR-SD fields to qstats strcuture and collecting info for these fields each time stats are collected. When requested by the switch, writing relevant fields to exact location in scratchpad according to NPAR-SD protocol.
Impact: NPAR-SD enabled boards only.
6. Request: Support for 578XX B0.
Change: As requested.
7. Request: Use FW 7.0.8.
Change: As requested.
8. Request: Add dcbnl implementation supporting the FW DCBX engine.
Change: As requested.
Impact: 57712 only.
9. Request: Support SGMII with 54618SE GPHY for 57800.
Change: As requested.
Impact: Devices 3 and 4 of 57800 and small Warpcore changes only.
10. Request: Get all CNIC related info from shmem in the bnx2x.
Change: As requested.
Impact: iSCSI and FCoE only.
11. Request: Replace ethtool stats counter "rx_outer_vlan_discard" name with "rx_mf_tag_discard".
Change: As requested.
12. Request: Preserve temperature input setting for PCIE and Warpcore Serdes equalization logic.
Change: As requested, Warpcore initialization is now preserving that register value (no longer blindly overwrite it).
Impact: 578xx
13. Request: Support multi-function and DCBX in 4 ports mode (BCM578xx).
Change: (In FW 7.0.8) As requested.
Version 1.64.10 (Dec 7, 2010) ============================== Fixes ----- 1. Problem: (CQ50681) Device hangs on up/down test when PFC is enabled
Cause: If the device is going down while in PFC Xoff it will not set it to Xon and therefore, on the next load it will remain in constant Xoff
Change: Force PFC Xon when enabling the device
Impact: 57712 and 578xx
2. Problem: Tx packets are sent with wrong TCP checksum in case of TCP bi-directional scenarios
Cause: Firmware didn't update the L4/L3 checksum correctly in mixed traffic of packets with/without checksum offload
Change: Fixed the relevant firmware flow
Impact: Introduced in 1.64.08
3. Problem: A possible dead-lock situation between sch_direct_xmit() and bnx2x_run_loopback() (calling bnx2x_tx_int()) on netif_tx_lock()
Cause: Both functions above take a netif_tx_lock() but bnx2x_run_loopback() is called in a syscall context and takes a lock without disabling BHes on a local CPU, which may cause a dead lock as long as sch_direct_xmit() is called in a soft_irq() context
Change: Explicitly disable local BHes in bnx2x_run_loopback() to prevent a mentioned above dead-lock situation
Impact: Introduced in 1.60.25
4. Problem: (MF) ethtool -s speed has no effect in multi-function mode
Cause: Address calcutated using func_id instead of vn_id
Change: Fix address calculation
Impact: Introduced in 1.64.09, MF only
5. Problem: ethtool -t failed on sigle port boards and 57712 (nvram test)
Cause: Erroneous access to unexistent port info
Change: remove the access
6. Problem: All ingress packets were dropped by 57712 on Big Endian machines
Cause: Rx mode wasn't properly configured for 57712 on Big Endian machines
Change: Fix Rx mode configuration code for 57712
Impact: Introduced in 1.64.00, 57712 only
7. Problem: PCI bus error when trying to transmit LSO packets from 57712 on Big Endian machines
Cause: Parsing BD parsing_data field was malformed when running 57712 on Big Endian machines
Change: Fix the code handling the parsing_data field of a parsing BD for 57712
Impact: Introduced in 1.53.0a, 57712 only
8. Problem: Kernel panic when receiving in none-MSI-X interrupt mode
Cause: Indirection table was configured with none-existing queues when MSI-X was not attainable and RSS queues set was cut to a single queue. The reason for the above was an improper location of SAFC initialization code and usage of the SAFC parameters for the indirection table configuration despite the fact that an SAFC MF mode was not requested/not available
Change: Don't use SAFC parameters unless SAFC MF mode is requested
Impact: Introduced in 1.64.00
9. Problem: Single connection performance is much lower than expected in 57712
Cause: The firmware uses a malfunctioning bit in the HW for single connection optimization
Change: The firmware uses a different bit with similar functionality
Impact: Introduced in 1.64.00 when the optimization was implemented. Doesn't cause any penalty compare to older versions
10. Problem: (FCoE) An FCP_CONF frame was not transmitted when required
Cause: A confirmation indication was not handle properly if the task was from middle path type
Change: Fixed relevant firmware flow
Impact: FCoE only. Exist in all previous FCoE releases
11. Problem: CQ48350, CQ49176, CQ50911 and CQ51200. BCM57712 not linking up after wake on S4 and S5.
Cause: PHY firmware does not have enough time to download in 8073 and 8727 common init.
Change: Poll until firmware is downloaded, and then timeout at 300ms.
Impact: 8727 and 8073 PHY
12. Problem: Statistics were updated in wrong counters
Cause: The per-queue statistic address was miscalculated
Change: Fixed address calculation
Impact: Introduced in 1.64.00
13. Problem: Firmware assert will occur when LSO packets is duplicated in case Tx-switching is enabled and packet is sent without VLAN
Cause: Firmware looses synchronization with packet index which is enforced by firmware for debugging purposes
Change: Fixed relevant firmware flow
Impact: Introduced in 1.64.00
14. Problem: L2 packets which are duplicated in case Tx-switching is enabled may be counted twice in the Tx statistics
Cause: Firmware counts statistics each time a transmission command is sent to hardware, even if the duplicated packet was already sent
Change: Fixed relevant firmware flow
Impact: Introduced in 1.64.00
Enhancements ------------ 1. Request: Use FW 6.4.16
Change: As requested
2. Request: Integrate VLAN enhancements from the net-next
Change: As requested
3. Request: Use slow path function object mechanism to synchronize between function stop ramrod to NPAR-SD ramrods, instead of sleep work around in NPAR-SD mode used today
Change: As requested. Logic was added to function object
4. Request: Remove unrequired clearance of specific VIF from NIV VIF lists if that function is unloaded from host side (as anyway VIF_LIST_SET commands will be sent from switch).
Change: Don't call FW NIV_VIF_LISTS ramrod for the sub command of VIF_LIST_RULE_CLEAR_FUNC from the driver unload flow
5. Request: Use NIV_VIF_LISTS hsi new echo field to distinguish in ramrod completion flow for which sub command the respones is relevant, instead of using a bp dedicated field for that
Change: As requested (instead of using last_viflist_req_to_fw field).
6. Request: treat NPAR-SD driver_niv_support as a global shmem2 field, and write its value only in LOAD_COMMON flows
Change: As requested
7. Request: Add a support for TPA over IPv6 for 57712 and above
Change: As requested
Impact: Introduced in 1.64.10. 57712 and above only
8. Request: Support for forward connection traffic in NPAR-SD mode
Change: TX packets are sent with destination field, on NPAR-SD tag header, which is equal to the source VIF value
Impact: NPAR-SD mode is supported in BCM57712 only
9. Request: Enable Tx switching for 57712
Change: As requested
Impact: 57712 in NPAR mode only
Version 1.64.09 (Nov 18, 2010) ============================== Fixes ----- 1. Problem: CRC errors are seen with line-rate traffic on BCM578xx
Cause: Warpcore microcode was not loaded, and its clock wasn't synchronized well
Change: Load Warpcore microcode and apply clock compensation This change is a temporary work-around which will be embedded in the bootcode later on
Impact: 578xx Only
2. Problem: (CQ50748) MinBW not functioning as expected in certain NPAR configuration
Cause: MinBW algorithm coefficients were not calculated properly and cause the algorithm to not function well in extreme cases
Change: Re-calculate the algorithm coefficients to allow granularity of 1:100
Impact: Affects NPAR mode in which MAX bandwidth can be configured to over-subscription
3. Problem: Single Tx L2 connection enhancement feature is broken when FLR is sent on function which is under traffic
Cause: Tx firmware didn't release internal resources, which may be taken by connections that belong to FLRed functions
Change: (in FW 6.4.13) Fixed relevant firmware flow
Impact: Introduced in 1.64.01 (in FW 6.4.0)
4. Problem: Broadcast packets are received on a client which isn't configured to receive them
Cause: The firmware always passed broadcast packets to the leading client even when it wasn't configured to received them
Change: (in FW 6.4.13) Fixed relevant firmware flow
Impact: BCM57711 only, introduced in 1.64.05 (in FW 6.4.7)
5. Problem: TPA does not aggregate packet when RSS disable
Cause: Wrong initialization by firmware
Change: (in FW 6.4.13) Fixed firmware initialization
Impact: Introduced in 1.64.06 (in FW 6.4.9)
6. Problem: (iSCSI, CQ50672) Chip hangs when running iSCSI traffic on one function and toggling load/unload on the other function
Cause: Firmware initialized the CAM incorrectly, causing iSCSI out of order client to receive an unexpected packet
Change: (in FW 6.4.13) Fixed relevant firmware flow
Impact: BCM57710 only, introduced in 1.64.01 (in FW 6.0.0)
7. Problem: Compilation failed on RH5.6
Cause: Redefinition of backported function
Change: Remove the definition from bnx2x code for RH5.6
Enhancements ------------ 1. Request: Add NPAR-SD support
Change: As requested
2. Request: (CQ49959) Request to log event log in case the PHY does not come out of reset, and MDC/MDIO timeout
Change: As requested
3. Request: (CQ51065) NPAR mode: change Max BW from units of "intervals of [100Mbps]" to units of "% of physical link speed"
Change: As requested
Impact: NPAR mode only
4. Request: (FCoE) Synchronize all storms with ABTS operation before the transmission of ABTS packet, in order to avoid potential races
Change: As requested
Version 1.64.08 (Nov 08, 2010) ============================== Fixes ----- 1. Problem: 4-port MF/SF combined mode on 578xx is not functional
Cause: Improper HW initialization
Change: Common for both ports HW properly configured
Impact: 578xx only
2. Problem: Compilation failed on 2.6.36 kernels
Cause: Improper conditions in bnx2x_compat.h layer
Change: Fix condition for functions' definitions
3. Problem: (CQ50903) Driver prints some debug info when dcbx enabled
Cause: Debug info printed with error dbg level
Change: Remove the prints
4. Problem: Weighted fair queuing congestion management doesn't work on BCM57712
Cause: Firmware might send packet to wrong port in case weighted fair queuing is enabled
Change: (in FW 6.4.10) Fixed firmware flow
Impact: Introduced in 1.64.00
5. Problem: Firmware doesn't work correctly for 2 TCP connections with the same toeplitz hash result, when TPA is enabled
Cause: The firmware wrongly invalidated the aggregation for the first connection, when a packet from the second connection arrived
Change: (in FW 6.4.10) Fixed firmware flow
Impact: Introduced in 1.64.03
6. Problem: (CQ50722) When more than 16 TPA aggregations are open, aggregations might not close properly
Cause: The firmware miscalculated the TPA timer address
Cause: TCP window is closed and initiator cannot properly process incoming in-order packets
Change: (in FW 6.4.10) Fixed firmware flow
Impact: Introduced in 1.64.00
8. Problem: False bug-check when trying to set speed in NPAR mode when link is down
Cause: The FW should be configured only after the physical link is up
Change: Do not configure the FW while link is down with the new speed settings
Impact: 57712 NPAR mode only
9. Problem: (iSCSI) in NPAR mode devices have incorrect iSCSI mac address
Cause: Mac address is taken from port configuration
Change: Take the addreses from NPAR configuration
Impact: 57712 NPAR mode only
Enhancements ------------ 1. Request: Use FW 6.4.11.1
Change: As requested
Version 1.64.07 (Nov 03, 2010) ============================== Fixes ----- 1. Problem: No RSS in a multi-function mode
Cause: RSS engine ID was not initialized in Client SETUP ramrod data
Change: Set RSS engine ID in the SETUP ramrod data
Impact: Introduced in 1.64.00. 57711 and 57712 only
2. Problem: (CQ50624) Race between the netdev->open() and the last part of pci_dev->probe() that configures the interrupt mode and adds NAPIs causes kernel panic
Cause: Improper operations order: netdev_register() should be called after driver is completely configured
Change: Move all driver initializations before the netdev_register() call
Impact: Introduced in 1.60.28
Enhancements ------------ 1. Request: Unify the slow path flows for all types Client
Change: Handle iSCSI OOO slow path in a NAPI (interrupt driven instead of polling as it used to)
2. Request: Add support for 57800 HW
Change: As requested
3. Request: Add hw statistics support for 578xx
Change: As requested
4. Request: (CQ50053) Add "Dual Media Support" section to README/Man pages
Change: As requested
Version 1.64.06 (Oct 27, 2010) ============================== Fixes ----- 1. Problem: (CQ49515, CQ50024) Occasionally losing link on force 10/100 connections on BCM84823 based boads
Cause: Not waiting for GPHY to complete reset
Change: Add 50ms delay after 84823 PHY comes out of reset
Impact: BCM84823 based boards
2. Problem: (CQ50559) Build fails with RHEL6 kernel
Cause: Redefinition of backported function
Change: Remove the definition for RH kernels
Impact: Introduced in 1.64.05
3. Problem: (iSCSI OOO) When in MF mode, Hardware may get PCI error in case of iSCSI out-of-order flow
Cause: Firmware set the wrong PCI function ID
Change: Fixed firmware flow in FW 6.4.9
Impact: Introduced in 1.64.03, 57712 iSCSI OOO only
4. Problem: (CQ50483) Chip got stuck during stress test
Cause: Context was not initialized correctly by the Firmware
Change: Fix the initialization in FW 6.4.9
Impact: Introduced in 1.64.03, BCM57710/11/11E only
5. Problem: (FCoE) Trying to transmit from invalid host memory address
Cause: Receiving incorrect FCP_XFR_RDY second packet
Change: Rejecting the second FCP_XFR_RDY packet for the specific task
Impact: Introduced in 1.64.00. FCoE only
6. Problem: (FCoE) False timer REC_TOV expiration
Cause: Inappropriate advance of timer counter
Change: Fixed firmware flow in FW 6.4.9
Impact: Exists in all previous FCoE releases
7. Problem: (FCoE) Transmitting FCP_DATA frames with wrong OX_ID
Cause: Changing OX_ID once REC_TOV expiration is detected
Change: Fixed firmware flow in FW 6.4.9
Impact: Exists in all previous FCoE releases
Enhancements ------------ 1. Request: Use FW 6.4.9
Change: As requested
Version 1.64.05 (Oct 20, 2010) ============================== Fixes ----- 1. Problem: ESX Non LRO net-queues were still aggregating incoming TCP frames
Cause: net-queues not reserved for LRO were not internally marked as such (tpa not disabled)
Change: correctly disable tpa for such queues
Impact: ESX only
2. Problem: RX broken in MF SD mode
Cause: Improper hw configuration
Change: Write correct values to HW registers
Impact: Intoduced in 1.64.04
3. Problem: Link up event is not reported to the OS
Cause: Inconsistent link report state handling
Change: Change the link report state handling
4. Problem: (ESX, PR379952/PR405074) FW asserts on invalid value in a VLAN field in the start BD (xmit flow)
Cause: The first sg element might not contain all the headers
Change: Do a simple check and if this holds pull tail on the skb
Impact: ESX only. This may happen only when the VMs are using 3.0.x tools
5. Problem: Broadcast packets can be received on the wrong L2 client
Cause: Classification flow was using "unmatched unicast" flag also for broadcast packets
Change: Fixed firmware flow
Impact: 57710 only. Introduced in 1.64.03
6. Problem: When more than 16 TPA aggregations are open, aggregations are not closed properly
Cause: Firmware miscalculated the address for the TPA timers
Change: Fixed firmware flow
Impact: Introduced in 1.64.03
7. Problem: (FCoE) RRQ frame was not sent after abort operation
Cause: Corrupted ABTS ACC frame reported to the driver
Change: Firmware updates the correct R_CTL field in task context
Impact: Introduced in 1.64.00
8. Problem: (CQ49968) DMAE timeout on specific system during init
Cause: The DMAE can take up to 200ms to complete on some systems
Change: Update the DMAE timeout from 2ms to 200ms
9. Problem: Incorrect HW statistic on 578xx
Cause: Read stats from inexistent address
Change: Adopt statistics collection to avoid reading from the address
Impact: 578xx only
Enhancements ------------ 1. Request: (CQ49997) Implement Bandwidth allocation for Nic partitioning mode
Change: As requested
Impact: 57712 only
2. Request: Use FW 6.4.8
Change: As requested
3. Request: Properly calculate the LRO MSS value (needed for TCP delayed ACK handling)
Change: As requested
4. Request: Add support for BCM57810/57840 adapters
Change: As requested
Version 1.64.04 (Oct 14, 2010) ============================== Fixes ----- 1. Problem: (CQ49886) MC Assert on 57710 with more than 4 queues
Cause: ESX does not align physical memory to requested size. Thus ILT pages do not adhere to 57710 alignment requirements
Change: Allocate extra memory and manually align CDU ILT pages. Define ILT pages for all other clients to be 4K
Impact: ESX only
2. Problem: (CQ49827, CQ49844) pNic Link/Unlink test fails when the pNic eventually fails to load
Cause: During load skb allocation for L2 queues is stopped on the first failure. If this happens on the default queue before a minimal number of skbs were successfully allocated nic load fails
Change: Do not break upon first skb allocation failure. Fail only if after queues size allocation attempts not enough skbs were successfully allocated
Impact: ESX only
3. Problem: (CQ50208) ESX4.0/4.1 pNic statstics are not updated
Cause: Using a local statistics structure for ESX instead of the net_device statistics structure
Change: Use the correct statistics structure for ESX
Impact: ESX only
4. Problem: (CQ49826) Wrong skb queue mapping passed to hard_xmit
Cause: FCoE L2 queue is not disabled and is used by the stack
Change: Disable FCoE L2 queue for E1x in general and all devices in ESX
Impact: ESX only
5. Problem: ethtool -S shows all possible queues including disabled queues such as FCoE or queues with no stats such as iSCSI OOO queues
Cause: ethtool statistics call-backs iterate over all queues.
Change: Iterate only over L2 queues and FCoE queue if not disabled.
6. Problem: (ESX) packets received on a net queue may arrive after its filters are removed
Cause: filter removal completion is not syncronized with the net-queue fast-path completions
Change: Send a flush command for the net-queue after deleting the filter and before returning from the filter removal call-back
Impact: ESX only
7. Problem: (CQ50308) Compilation failure on RHEL6RC1
Cause: Definition of list_rotate_left in bnx2x_compat.h for all kernels from 2.6.34
Change: Remove the definitions for non IOV kernels
Version 1.64.03 (Oct 11, 2010) ============================== Fixes ----- 1. Problem: (ESX) MSI-X was disabled forever after NIC down/up sequence
Cause: MSI-X was explicitly disabled in the bnx2x_close() in ESX driver
Change: Cancel the explicit MSI-X disabling
Impact: ESX only
2. Problem: (CQ50033) Link remains down on the PMF despite the DCC "link up" indication
Cause: DCC event handler wasn't handling the event for the PMF
Cause: When multiple consecutive packets are sent on L2 forward connection, firmware might incorrectly manage internal transmission credit
Change: Fixed in FW 6.4.6
Impact: Introduced in 1.64.00 (FW 6.2.0)
4. Problem: LSO packets with large contiguous buffers may not be properly sent to the network
Cause: Firmware didn't calculate the number of segments to be sent to the network for LSO packet with large contiguous buffers correctly
Change: Fixed in FW 6.4.6
Impact: Introduced in 1.64.02 (FW 6.4.5)
5. Problem: (FCoE) FCP_XFR_RDY verification failure leads to the task abort
Cause: Error in a verification procedure in the second FCP_XFR_RDY packet on a single task
Change: Fixed in FW 6.4.6
Impact: Introduced in 1.64.00 (FW 6.4.0)
6. Problem: Malicious VF detection flow may cause memory corruption on TX processor
Cause: Bug in relevant firmware flow
Change: (Fixed in FW 6.4.7) Fixed firmware flow
Impact: Introduced in 1.64.00 (FW 6.4.0)
7. Problem: (FCoE)(CQ50211) InvalidCrcCount value after collecting statistics
Cause: Wrong statistics collection in firmware
Change: (Fixed in FW 6.4.7) Fixed firmware flow
Impact: Introduced in 1.64.00 (FW 6.4.0)
8. Problem: (FCoE)(CQ50267) ABTS sent with incorrect RX_ID value
Cause: Firmware reported incorrect task information when detecting the error
Change: (Fixed in FW 6.4.7) Fixed firmware flow
Impact: Introduced in 1.64.00 (FW 6.4.0)
Enhancements ------------ 1. Request: Use FW 6.4.7
Change: As requested
Version 1.64.02 (Sep 27, 2010) ============================== Fixes ----- 1. Problem: (FCoE) panic dump while opening FCoE connection
Cause: FCoE ramrods were counted on incorrect SPE pool
Change: Use L5 pool
Impact: Introduced in 1.64.00
2. Problem: Wrong statistic counter might be updated
Cause: (Fixed in FW 6.4.5) In client init the queue statistic address might be calculated wrongly
Change: Fixed the calculation in client init
Impact: Introduced in 1.64.00 (FW 6.2.1)
3. Problem: Congestion management doesn't work properly in case of a single L2 connection scenario on 57712
Cause: In case of a single connection L2 firmware didn't allow pausing transmission which is needed for the congestion management functionality
Change: (Fixed in FW 6.4.5) Firmware now considers congestion management decision to pause transmission
Impact: Introduced in 1.64.00 (FW 6.2.1)
4. Problem: The firmware returned the wrong error state for Ethernet ramrods
Cause: The code in Xstorm didn't save error state correctly
Change: (Fixed in FW 6.4.5) Fixed the relevant flow
Impact: Introduced in 1.64.00 (FW 6.2.0)
5. Problem: PF FLR could hang the chip
Cause: The firmware didn't return activity counter to CFC correctly
Change: (Fixed in FW 6.4.5) Fixed the relevant flow
Impact: Introduced in 1.64.00 (FW 6.2.0)
6. Problem: (CQ49299, PR57004) HW stuck after 8 hours of heavy LSO traffic
Cause: When driver send an LSO packet with total length longer than 64K, the firmware calculate the total SGL length in a uint16 variable which overlaps and causing an erroneous PBF command
Change: (Fixed in FW 6.4.5) Change the counter to be uint32
7. Problem: L2 traffic might be stopped in case of dcb updates COS value for some traffic types
Cause: The firmware didn't return activity counter to CFC correctly
Change: (Fixed in FW 6.4.5) Fixed the relevant flow
Impact: Exists in all previous releases that support dcb updates
Enhancements ------------ 1. Request: Port a new way L2 FW handles FCoE and FIP packets
Change: Starting from FW 6.4.4 L2 FW forwards FCoE and FIP frames to FCoE L2 client unconditionally. This means that there is no need to configure any MAC for an FCoE L2 client any more. So, all such code has been swept out
Impact: Introduced in 1.64.00 (FW 6.4.4)
2. Request: Use FW 6.4.5
Change: As requested
Version 1.64.01 (Sep 20, 2010) ============================== Fixes ----- 1. Problem: BMAC relays control packet to host and BRB is filled with unnecessary packets
Cause: BMAC is configured to relay control packets to host
Change: Configure BMAC not to relay control packets to host
2. Problem: Failed to load high functions in MF mode
Cause: bnx2x was trying to configure the HC for the default SB, which doesn't have it (during FCoE ETH ring configuration)
Change: Exclude HC configuration from FCoE ETH ring initialization
3. Problem: After "Fix 2" packets were silently dropped on the receive side in a SD MF mode
Cause: Tx OUTER VLAN was not properly configured
Change: Properly configure Tx OUTER VLAN in the function start ramrod
4. Problem: (CQ49795) Link loss on port after multiple iterations of load-unload
Cause: When link change occur, and at the same time the driver is unloaded, the NIG attention is left latched since it is used to be cleared only during link change event. This leads that following link change events are actually masked.
Change: Clear NIG latched attention during driver unload
Impact: BCM84823 based boards
5. Problem: False link up indication on boards with BCM84823 PHYs
Cause: Not waiting until PHY has come out of reset
Change: Poll on reset bit. Timeout after 1 second
Impact: BCM84823 based boards
6. Problem: iSCSI OOO didn't work over VLAN
Cause: Inconsistent Client configuration and fast path functions implementation for OOO Client in regard to HW VLAN acceleration
Change: Don't assume HW VLAN acceleration in fast path iSCSI OOO functions
Impact: iSCSI OOO only
Enhancements ------------ 1. Request: Add capability to build against SuSE source RPMs
Change: As requested
2. Request: Set drop threshold for receiver lossy COS to 90, when PFC is enabled
Change: As requested
Version 1.64.00 (Aug 31, 2010) ============================== Fixes ----- 1. Problem: (CQ47855) Link test fails under Linux using ethtool
Cause: In case a MAC test followed by link test, the NIG attention might be cleared while ISR was already triggered due to NIG attention. This led to declaring the MAC test as failed since there's actually no link in this case.
Change: In case NIG interrupt mask is cleared during interrupt handling, do not execute link status update routine.
2. Problem: (CQ48747) Dual media: fiber port does not link at 1gig speed
Cause: The link speed in the pass-through phy (84823) was set to 10G
Change: Set the pass-through speed to 1G as well when fiber is set to 1G
3. Problem: (CQ49143) Dual Media: First attempt to change from default TP to FIBRE using ethtool does not work.
Cause: When changing port type from TP to FIBRE the command failed since FIBRE doesn't support autoneg, yet the port type was changed.
Change: When ethtool command fail, do not change port type.
Impact: Dual-Media boards
4. Problem: Compilation error on kernels 2.6.34 and later
Cause: netdev_name() defined by both kernel and driver
Change: Fix compat.h for these kernels
5. Problem: 84823 PHY not showing correct Link LED's.
Cause: Incorrectly setting LED Masks
Change: Eliminated offending branch in code
Impact: Introduced in 1.60.24
6. Problem: (CQ49137) ethtool -t test fails in dual-media boards
Cause: Link wasn't tested correctly depending on the media configuration
Change: Test link according to media configuration
Impact: Dual-Media boards
7. Problem: (CQ49004) Dual Media: Switch show link on both media simultaneously.
Cause: Not disabling TX on non-active port.
Change: In case link is up in non SFP+, disable the SFP+ TX laser.
Impact: Dual-Media boards
8. Problem: On BCM8727 based boards, when link speed is changed from 1G to 10G, PCS may be halted
Cause: Restoring 10G link setting was done according to old PHY microcode
Change: Restore default 10G link setting according to new microcode
Impact: BCM8727 based boards
9. Problem: (ESX) Performance regression found by VmWare
Cause: Tx ring was configured to have a smaller length than it was in IOVP driver
Change: Configure Tx ring to have the same length as in IOVP driver
Impact: ESX only
10. Problem: (CQ48584) Intermitted link issue and unexpected behavior using boards with external PHYs
Cause: PHY lock indication was missing on second port, so there was no locking between the ports. When two ports tried to read/write from the PHY, they the instruction may collide.
Change: Set PHY lock indication of both ports
Impact: 57710/57711 on boards with external PHY. Introduced: T5.0
11. Problem: (CQ49219) Dual media: Copper link does not come up once 10gbaseT priority is set in driver property
Cause: Link indication from both Copper and Fiber
Change: Ignore link indication from Fiber in case Copper is selected
Impact: Dual-media boards Introduced: 1.60.32
12. Problem: (CQ49296) - Dual media: Copper link would not come up upon removal of fiber media when serdes priority and 1GB full is set
Cause: When Fiber link is set to 1G, its XAUI will not automaticity power down like it does in 10G. This cause the BCM84823 to detect false link from the BCM8727 even if Fiber is not connected. This ends up in not linking the copper side.
Change: When link is configured to 1G, power down the BCM8727 XAUI side, and when link comes up, power it up.
Impact: Dual Media boards.
13. Problem: (CQ49137) -Dual Media: Ethtool fail - Link_test (online) on TP every few iterations.
Cause: Link detection may take very long in case of copper, while the wait up time was limit to 10sec only.
Change: Increase link wait up time in link test to 14sec
Impact: Dual Media boards.
14. Problem: Dual Media PHY 84823 activity and front panel LED's not functioning correctly. Also Diagnostic Mode LED's not firing correctly
Cause: LED masks not set correctly
Change: Changed LED masks, and added LED mode for Diagnostics
Impact: Dual Media boards
15. Problem: CQ49197 - No link at 1Gb/2.5Gb on BCM8073 based boards
Cause: CL37 BAM was enabled on all boards while it should be configurable.
Change: Disable CL37 BAM by default.
Impact: BCM8073 based boards Introduced in 1.60.21
16. Problem: HW Statistics collection through the DMAE broken on 57712
Cause: For 57712 the DMAE command needs to include the destination function.
Change: Adjust the DMAE command to work on 57712
Impact: Introduced in 1.60.01
17. Problem: Possible inconsistency in parity recovery flow in case of bogus usage of bnx2x_trylock_hw_lock() function
Cause: Inconsistent error core returned (-EINVAL while function returns `bool')
Change: Return `false' in case of an error
Impact: 1.60.01
18. Problem: The firmware sends an assert when starting the first vf in a passthru mode
Cause: The firmware trys to send an event to the pf, but since the vf was never initialized, the firmware couldn't find which pf to use
Change: The firmware will only send an event in case the function was initialized before. Fixed in FW 6.4.4
Impact: Introduced in FW 6.2.1.1. ESX NPA only
19. Problem: (CQ48770) When working with rate-limiting in 57711/2 with jumbo frames, the rate is half of what configured
Cause: Firmware miscalculated the amount of bytes transmitted
Change: Fixed the calculation. Fixed in FW 6.4.4
Impact: Introduced in firmware version 6.0.20
20. Problem: PCI entity wasn't calculated before write event ring element in the initial cleanup and MaliciousVf handlers
Cause: Used wrong PCI entity in the handlers
Change: Calculate the PCI entity before using it. Fixed in FW 6.4.4
Impact: Introduced in FW 6.2.0
21. Problem: In FLR final cleanup flow - in some cases the IGU cleanup command was wrong
Cause: Used wrong parameters for calculation of the function id from Pf or Vf.
Change: Fixed the calculation. Fixed in FW 6.4.4
Impact: Introduced in FW 6.2.0
22. Problem: (ESX PR582737): TX switching along with LSO packet results with HW attention
Cause: LSO packet might be sent on a port which doesn't have sufficient QM credits
Change: LSO packets are sent only if credits were charged for the chosen port (physical vs. loopback). Fixed in FW 6.4.4
Impact: Introduced in first tx switching version 6.1.4
23. Problem: Possible race between dcb update and ethernet tx single connection optimizations
Cause: When Single Eth connection is present it may not allow updating the association of tx queues to COSes
Change: L2 firmware now considers DCB updates and may stop a single connection run to allow DCB configuration update Fixed in FW 6.4.4
Impact: Introduced in version 6.0.15
24. Problem: The firmware didn't support TX switching for MAC-VLAN-PAIR
Cause: The firmware didn't initialize the VFC correctly
Change: Fixed the VFC initialization. Fixed in FW 6.4.4
Impact: Introduced in FW 6.2.0
25. Problem: The error field in ramrod CQE was always sent as 0
Cause: Wrong initialization of the CQE
Change: Sending the right value. Fixed in FW 6.4.4
Impact: Introduced in FW 6.2.0.
26. Problem: The code entered the infinite loop in the Cstorm Common VfZone handler
Cause: Wrong calculation of a VF ID
Change: Fixed the VF ID calculation. Fixed in FW 6.4.4
Impact: Introduced in FW 6.2.0.
27. Problem: (CQ49649) Dual Media: No 1Gb fiber link after changing driver speed property, when cable is connected.
Cause: Link interrupt is generated from NIG attention common for both phys on dual media board. The NIG status was set for both PHYs while it should have been done for the copper attention only.
Change: Set NIG attention according to the active PHY
Impact: Dual media boards
Enhancements ------------ 1. Request: Use FW 6.2.1.1
Change: As requested
2. Request: Integrate T6.1 changes
Change: As requested
3. Request: Support HW Rx hash generation for a single queue configuration
Change: As requested
4. Request: Provide a way to know if there are pending ramrods' completions in multicast and rx_mode configuration flows
Change: Return a positive value from bnx2x_config_rx_mode() and bnx2x_config_mcast() if there are pending ramrods' completion
5. Request: Add "delete all" and "reconfigure" verbs to the VLAN_MAC object
Change: As requested
6. Request: Add "reconfigure" verb to the MCAST object
Change: As requested
Version 1.60.29 (Jul 21, 2010) ============================== Fixes ----- 1. Problem: (CQ48770) When working with rate-limiting in 57711/2 with jumbo frames, the rate is half of what configured
Cause: Firmware miscalculated the amount of bytes transmitted
Change: (In FW 6.0.30) Fixed the calculation
Impact: Introduced in 1.60.16 (FW 6.0.20)
2. Problem: FW XSTORM assert during server reboot test
Cause: There were two statistics ramrods sent with the same statistics counter. There was a race condition in the bnx2x driver that allowed this situation
Change: Protect statistics ramrod sending code and statistics counter update with the spin lock
Enhancements ------------ 1. Request: Use FW 6.0.30
Change: As requested
2. Request: Rearrange LLH memory organization
Change: Allow 16 MACs in the memory; do not set FCoE MACs in LLH
Impact: Switch-Independent mode only
Version 1.60.28 (Jul 14, 2010) ============================== Fixes ----- 1. Problem: Possible crash during load/unload of one function, if more functions are loaded.
Cause: Statistics ramrod of one function might override data of other functions
Change: (In FW 6.0.29) Fixed statistics ramrod
Impact: Introduced in 1.60.07 (FW 6.0.5)
2. Problem: Port detection feature(ethtool -p) for dual-media is not working
Cause: BCM8727 LED needs to be set via the PHY, and not the MAC
Change: Set BCM8727 LED via PHY
Impact: Dual-Media boards
3. Problem: ethtool -s ethX speed YYY does not work properly
Cause: Forcing port configuration every call to ethtool -s
Change: Do not change port configuration if not requested
Impact: Introduced in 1.60.27
4. Problem: Divide by 0 in driver code, after disabling coalescing via ethtool
Cause: Conversion from usec to interrupt per sec done without check for zero
Change: Check for zero in conversion
Impact: Introduced in 1.60.26
5. Problem: (CQ48787) ethtool -t fails in Switch-Independent mode after bringing up higher functions (4,5,6,7)
Cause: Improper mac placement in NIG block
Change: Fixed address calculation
Impact: Switch-Independent mode only
Enhancements ------------ 1. Request: Modify Dual-media look & feel such that ethtool gets and sets the configuration of the active PHY only. Active PHY is the PHY which linked up, or in case of link down, according to the port selection
Change: As requested
2. Request: Use FW 6.0.29
Change: As requested
3. Request: Don't call for pci_disable_msix() every time bnx2x_nic_unload() is called
Change: Move pci_enable_msi/msix() to pcidev->probe() callback
4. Request: (ESX) Call for netif_napi_add() before netdev->open()
Change: As requested. This change is relevant for all platforms
5. Request: Support for ethtool_cmd.speed_hi field
Change: As requested
Version 1.60.27 (Jul 07, 2010) ============================== Fixes ----- 1. Problem: (CQ48202) Under low memory condition, rx stop functioning during load/unload test
Cause: Some queue may be not fully populated, under low memory condition, which may cause FW to drop packets for this queue
Change: Change memory allocation scheme in order to avoid this situation
2. Problem: Link lost every other time when driver is brought up.
Cause: When the PHY swap parameter ('nvm cfg' option 124) is set, the PHY's swap everytime the link is brought up.
Change: Instead of storing the PHY order, we calculate it fresh everytime.
Impact: Dual-media boards.
Enhancements ------------ 1. Request: Return an error if bnx2x_set_flags() is called for unsupported flags
Change: As requested
2. Request: Don't collect statistics if requested so according to edebug-driver interface (edebug_driver_if field in shmem2 region)
Change: As requested
3. Request: Add support to bnx2x to extract Toeplitz hash out of the receive descriptor for use in skb->rxhash
Change: As requested
Impact: Kernel 2.6.35 and newer
4. Request: Add ethtool port selection for dual media
Change: As requested
Impact: Dual media boards
Version 1.60.26 (Jun 30, 2010) ============================== Fixes ----- 1. Problem: Incorrect LED behavior on dual-media platform
Cause: The LED settings are used to control GPIO in favor of over-current detection
Change: On NOC (No-OverCurrent) flavor, configure the GPIOs to reflect LED behavior rather than unnecessary over-current indication
Impact: BCM8727 based boards
2. Problem: Possible deadlock on bp->stat_sm_lock spinlock
Cause: Inappropriate locking function was used for protecting a resource accessed by workqueue and timer: used spin_lock()/spin_unlock() while should be spin_lock_bh()/spi_unlock_bh()
Change: Use an appropriate locking API: spin_lock_bh()/spin_unlokc_bh()
Impact: Introduced in 1.60.22
3. Problem: Possible crash loading cnic if iSCSI OOO has been disabled in a bnx2x
Cause: cnic was unaware of the fact that iSCSI OOO may be disabled in the bnx2x
Change: Add an appropriate bit in a cnic_eth_dev->drv_state and set it if iSCSI OOO is disabled in the bnx2x. This is done in a bnx2x_cnic_probe2()
Impact: CNIC only
4. Problem: Interrupt coalescing was disabled in the chip
Cause: Coalescing was erroneously disabled by bnx2x by default
Change: Properly configure coalescing
Impact: Introduced in 1.60.11
Enhancements ------------ 1. Request: Fit Dual media selection to the new scheme
Change: As requested
2. Request: Enable to set the GPIO which controls the external PHY reset (through nvm cfg 129)
Change: As requested
Impact: BCM8727 based boards
Version 1.60.25 (Jun 23, 2010) ============================== Fixes ----- 1. Problem: Link down when using specific DACs (Direct Attached Cables)
Cause: Some DAC's EEPROM do not respond at 400Khz speed
Change: Set 2-wire transfer rate of SFP+ module EEPROM to 100Khz
Impact: BCM8727 based boards
2. Problem: (FCoE) (CQ48021) RESET_LUN operation failed due to error detection
Cause: Detecting a protocol violation in response frame from target (target protocol violation)
Change: (In FW 6.0.28) Mask the error reporting
Impact: FCoE only
3. Problem: (FCoE) 10% performance degradation
Cause: Read queue used by firmware did not have enough credits
Change: (In FW 6.0.28) Change the read queue used by firmware
Impact: Introduced in 1.60.24 (FW 6.0.27)
4. Problem: (FCoE) (CQ48403) Target does not handle incoming FCP_DATA
Cause: Increasing SEQ_CNT is not supported by target
Change: (In FW 6.0.28) Reset the SEQ_CNT back to zero when transmitting new FCP_DATA frame
Impact: FCoE only
5. Problem: There was a "timeout waiting for queue[0]" message in a syslog when running self-test (ethtool -t ethX) on 57712
Cause: Unlike HC IGU won't generate an interrupt for status block updates that have been performed while interrupts disabled thus Tx work generated by loopback test will never be handled
Change: Call for bnx2x_tx_int() from inside the loopback test for chips with IGU (57712 and newer)
Impact: 57712 only
6. Problem: (CQ48284) up-down test on port 1 causes traffic to stop on port 0
Cause: Improper cleanup of HC and IGU blocks during function init
Change: Fix HC block cleanup, remove unnecessary IGU clean-up
Impact: Introduced in 1.60.15
Enhancements ------------ 1. Request: (CQ48374) Add a module parameter to disable iSCSI OOO
Change: As requested: added a disable_iscsi_ooo module parameter, which is present if BCM_CNIC is defined, otherwise iSCSI OOO is not enabled anyway
2. Request: (iSCSI) Add counters for iSCSI out-of-order events
Change: As requested (counters can be read from RAM through GRC) (In FW 6.0.28)
3. Request: Use FW 6.0.28
Change: As requested
Version 1.60.24 (Jun 16, 2010) ============================== Fixes ----- 1. Problem: (iSCSI) (CQ42399) Unable to run I/Os greater than 1500 bytes with initiator MTU set to 9000 and target MTU set to 1500
Cause: Timestamp option was not considered in MSS calculation
Change: (in FW 6.0.27) Fix mss calculation when timestamp option is present
2. Request: Mask protocol violations error detected by chip on HP targets
Change: Masking the specific checks (in FW 6.0.26)
3. Request: Dropping invalid packets which are received during the abort procedure
Change: As requested (in FW 6.0.27)
4. Request: Use FW 6.0.27
Change: As requested
Version 1.60.23 (Jun 10, 2010) ============================== Fixes ----- 1. Problem: Avahi daemon crashed after loading bnx2x.ko on kernels newer than 2.6.30
Cause: SAN MAC was added (dev_addr_add()) before netdev_register() call and call_netdevice_notifiers(NETDEV_CHANGEADDR, dev) has been called for a unregistered device
Change: Call dev_addr_add() after netdev_register()
Impact: Introduced in 1.60.21
2. Problem: Link status notification appeared each time when DCBX negotiation received
Cause: DCBX update handled as link update and notification printed
Change: Remove link notification from this flow
Impact: DCBX only
3. Problem: (CQ47700) Can't get Link when forcing speed on 10/100M
Cause: When link is not set to autoneg, MDIX wasn't enabled so link couldn't be established on direct cables
Change: Enable MDIX when autoneg is disabled
Impact: BCM84823 based board
4. Problem: (CQ47671) "ethtool -p ethx" has no effect on the port's LED
Cause: Specific PHY requires specific phy settings
Change: In case of copper phys, set LED registers directly in the PHY, rather than the NIG
Impact: Copper boards
5. Problem: (iSCSI OOO) Producer of OOO Rx CQ ring was updated twice than was expected
Cause: The mentioned producer was updated both in the bnx2x_cnic_get_ooo_cqe() and in the bnx2x_cnic_reuse_ooo_pkt() while is meant to be updated only in the bnx2x_cnic_reuse_ooo_pkt()
Change: Don't advance CQ ring producer in the bnx2x_cnic_get_ooo_cqe()
Impact: iSCSI OOO only
6. Problem: (iSCSI) UIO Client wasn't able to handle IPv6 traffic
Cause: UIO Client was not receiving multicast traffic because in non-promiscuous mode only one Client per function will receive multicast packets (leading RSS Client)
Change: Configure UIO Client's to accept all multicast packets
Impact: iSCSI only
7. Problem: bnx2x would not compile on kernel 2.6.34
Cause: Improper dependency in bnx2x_compat.h
Change: Switch on netdev_hw_addr_list_for_each during bnx2x_mc_addr() definition
8. Problem: (CQ47854) Driver crash during FCoE test
Cause: HW assert causes driver to halt
Change: Notify user with appropriate message without causing panic
9. Problem: Unable to bring up function 2-7 if MBA didn't configure MACs
Cause: Check for MAC for both multi-function modes
Change: Check for OV tag in Switch-Dependent mode
Impact: Introduced in 1.60.10
Enhancements ------------ 1. Request: Change PXP Write block initialization values in 57712 to help reduce latency
Change: As requested
Impact: 57712 only
Version 1.60.22 (Jun 02, 2010) ============================== Fixes ----- 1. Problem: (CQ47662) "stats updated by DMAE but no MAC active" message while up/down test
Cause: Race on update of statistics' state machine
Change: Use spinlock to protect the state machine
2. Problem: (CQ46918) Network bursts are larger than the configured connection on FLEX 10
Cause: Inaccurate bytes calculation at rate shaping mechanism
Change: Calculation was fixed in FW 6.0.25
3. Problem: (CQ47623,CQ46388,CQ47225,CQ47833) System hangs during iSCSI stress traffic
Cause: Incorrect packet trimming lead to HW internal error
Change: Fixed packet trimming on LB port in FW 6.0.25
Impact: Introduced in 1.60.10 (FW 6.0.11)
4. Problem: All BRB interrupts are masked
Cause: BRB interrupt mask is not initialized so reset value is used
Change: Initialize interrupt mask so only parser read length errors are masked
Impact: In scenarios where BRB interrupts occur, indicate appropriate error information
5. Problem: (CQ47834, CQ47795, CQ47980) On low memory condition, driver caused kernel panic in bnx2x_ilt_mem_op()
Cause: Unallocated memory access
Change: Validate non NULL pointers before access
6. Problem: (FCoE) FCoE traffic experiences a lot of drops
Enhancements ------------ 1. Request: Don't limit the pause advertisement for large MTU
Change: As requested
Impact: 57712 and above
2. Request: Forward setup ramrod should complete on event ring and not as a tx_bd_cons increment
Change: (in FW 6.0.25) as requested
3. Request: Use FW 6.0.25
Change: As requested
4. Request: Use terminate ramrod for non forwarding clients
Change: As requested
Version 1.60.21 (May 26, 2010) ============================== Fixes ----- 1. Problem: (iSCSI OOO) Kernel panicked in the skb_put() when called from bnx2x_cnic_reuse_ooo_pkt()
Cause: Wrong skb function has been used for resetting the data length in the skb: skb_put(skb, -skb_headlen(skb))
Change: Use the proper function: skb_trim(skb, 0)
Impact: iSCSI OOO only
2. Problem: 57710 - Load/unload stress test caused chip to hang
Cause: Disable of device in the middle of MSIX message caused deadlock in HC block
Change: Use PCI configuration space to avoid the deadlock
Impact: 57710 only
3. Problem: iSCSI is not functional in switch independent mode
Cause: iSCSI mac was not written into NIG memory
Change: Fix handling of MAC addreses in switch independent mode
Impact: switch independent mode only
4. Problem: Changing MTU when CNIC is loaded was causing CFC error
Cause: Setting CDU validation value for iSCSI L2 Client was done from bnx2x_register_cnic(), which is not called in change MTU flow
Change: Move setting of iSCSI L2 Client CDU validation value to bnx2x_cnic_sp_post() right before it sends iSCSI L2 Client SETUP ramrod
Impact: iSCSI only
5. Problem: 57710/57711/57711E: unable to load device on machine with 16 (and more) CPUs
Cause: Improper HC SB calculation
Change: Exclude none l2 contexts from HC SB calculation
Impact: 57710/57711/57711E only; introduced on 1.60.13
Enhancements ------------ 1. Request: (FCoE) Set SAN MAC before ifup event in order to allow the bnx2fc properly configure WWN
Change: Move the dev_addr_add() for a SAN MAC to pci_dev->probe() flow (bnx2x_init_one()) making it similar to networking MAC address configuration (it is configured in netdev at this stage as well). dev_addr_del() for a SAN MAC has been moved to bnx2x_remove_one() correspondingly
Impact: FCoE only
2. Request: Lower the bnx2x skb memory footprint on ESX
Change: Limit the OOO Rx ring to 40 BDs
Impact: ESX only
Version 1.60.20 (May 18, 2010) ============================== Fixes ----- 1. Problem: (iSCSI OOO) Call for bnx2x_cnic_reuse_ooo_pkt() was causing a kernel panic
Cause: There was a wrong fp picked in bnx2x_cnic_reuse_ooo_pkt() (fwd instead of ooo)
Change: Pick the right fp
Impact: iSCSI OOO only
2. Problem: (FCoE)(CQ47674) Chip hangs during destroy FCoE connection flow
Cause: FCoE reordering mechanism was corrupted during disable connection flow
Change: (Fixed in FW 6.0.24) Assure not to overrun relevant context for reordering operation
Impact: FCoE only
3. Problem: (FCoE)(CQ47644) Chip reporting an error instead of dropping the packet
Cause: Some errors were detected before verifying FCoE delimiters
Change: (Fixed in FW 6.0.24) Once an error detected, verify first the FCoE delimiters before reporting an error
Impact: FCoE only
4. Problem: (iSCSI OOO) Chip hangs during out-of-order traffic
Cause: Firmware internal synchronization issue between iSCSI and L2 flows
2. Request: Allow the RX rings to be initialize with a lower number of entries (at the source code level)
Change: As requested
3. Request: Use FW 6.0.24
Change: As requested
4. Request: Enable PFC statistics in MAC
Change: As requested
Version 1.60.19 (May 12, 2010) ============================== Fixes ----- 1. Problem: (iSCSI OOO): OOO packets were not indicated on the OOO Rx ring
Cause: There were missing OOO ring's CID and Client ID configuration in a TSTORM
Change: Properly configure OOO ring's CID and Client ID in the TSTORM memory
Impact: iSCSI OOO only
2. Problem: (iSCSI OOO): CNIC SB context in internal memory was zeroed after OOO and FWD rings' ramrods were completed
Cause: There was a call for bnx2x_init_sb() for CNIC SB in bnx2x_register_cnic()
Change: Remove the bnx2x_init_sb() call from bnx2x_register_cnic()
Impact: iSCSI OOO only
3. Problem: (CQ46146) "ethtool -t" fails when the speed is forced on cx4 NICs to 100/10Mb
Cause: Internal loopback test needs to conducted when speed is set to 10G force
Change: Set speed to 10G force during loopback test, and restore link speed afterwards.
Impact: ethtool -t test
4. Problem: Spelling error in module parameter
Cause: "Then" used instead of "Than"
Change: Fixed to "than"
5. Problem: (CQ47609) Link Level Pause causes link to pause after PFC has been negotiated
Cause: Wrong MAC registers configuration
Change: Fix configuration
Impact: 57712 only
6. Problem: Link change after PMF migration may halt the system
Cause: PHY attributes are provided to the initial PMF only
Change: Load PHY attributes for every new function regardless of being PMF or not.
Impact: Multi-function mode
7. Problem: (iSCSI OOO) OOO FW was not processing the incoming OOO packets
Cause: TSTORM internal RAM was not properly initialized
Change: Properly initialize OOO producer, CID and Client ID of OOO ring in a TSTORM internal memory
Impact: iSCSI OOO only
8. Problem: (iSCSI OOO) L2 FW was generating XSTORM x_eth_vlan_special_check assert when trying to post packets on a FWD ring
Cause: The running index that was posted on a VLAN field of the start BD was starting from 1, while FW was expecting it to start from 0
Change: Keep driver's packet producer and consumer running from 0 and decrement a FW packet consumer during completions handling instead
Impact: iSCSI OOO only
9. Problem: (CQ47445) The duplex mismatch does not work as expected
Cause: Duplex was set correctly in the phy, but wasn't passed to the driver. In addition, when setting 10/100 force speed, it actually advertised 10/100 with autoneg.
Change: Return the correct duplex result, and when speed is set to 10/ 100, set the speed actually for force 10/100
Impact: BCM84823 based boards
10. Problem: (CQ47383) It takes long time to re-establish link in when working against some switches in force 1G mode
Cause: PHY is unable to establish good link in this mode
Change: Enable CL37 BCM autoneg instead of working in force 1G
Impact: BCM8073 based boards
11. Problem: (CQ47436) FC setting not consistant
Cause: "ethtool -a" show flow-control autonegotiation as off when speed is not set to autonegotiate.
Change: Show the actual flow-control settings on "ethtool -a", but in case the speed setting is actually force speed, this setting will have no affect like with the BCM8727
Impact: ethtool -a
12. Problem: (CQ45632) NETDEV Watchdog message appeared and system hung
Cause: driver disables tx while carrier still on
Change: call to netif_carrier_off() after netif_tx_disable()
Enhancements ------------ 1. Request: Remove redundant LCPLL setting which is done already in the bootcode
Change: As requested
2. Request: (DCBX) Changing PFC RX configuration: In RX COS0 will always be configured to lossy and COS1 to lossless
Change: As requested
3. Request: Remove Outer Vlan configuration for Mac partitioning mode
Change: As requested
4. Request: Use FW 6.0.23
Change: As requested
5. Request: Allow driver compilation with different kernel location
Change: As requested
Version 1.60.18 (May 03, 2010) ============================== Fixes ----- 1. Problem: (CQ47451) iSCSI and FCoE broken and causes kernel panic
Cause: Wrong FW offsets used
Change: fix FW offsets defines
Impact: Introduced in 1.60.17
2. Problem: Loading driver on one port may cause link toggling on the other port
Cause: PLL was initialized for both ports instead of per chip
Change: Initialize PLL once during common init
Impact: 57712 only
3. Problem: Possible race between firmware threads when loading context to chip
Cause: Common firmware handler which loads context for slow path handler may override other handlers context load responses
Change: The common handler considers it's thread Id when waiting for the context load response
4. Problem: Loading driver on one port may cause link toggling on the other port
Cause: Firmware generates false data digest error on incoming PDU
Cause: Firmware caused connection activity-counter to drop to a negative value
Change: (Fixed in FW 6.0.22) Firmware fix
Impact: Introduced in 1.60.10 (FW 6.0.11)
Enhancements ------------ 1. Request: Remove the extra prefetch instructions from bnx2x_rx_int()
Change: As requested
2. Request: (DCBX) add ETS support
Change: As requested
3. Request: (DCBX) add DCB statistics information; add support for 4-bytes long remote chassis id
Change: As requested
4. Request: Set NIC_MODE when cnic driver does not exist in the system
Change: As requested
Impact: Revert of change introduced in 1.60.11
5. Request: Remove Modules.supported file
Change: As requested
6. Request: Use FW 6.0.22
Change: As requested
Version 1.60.17 (Apr 27, 2010) ============================== Fixes ----- 1. Problem: Kernel warning message from pci_enable_msix() in case of parity error
Cause: Improper handling of MSI-X enable/disable flow in parity error case
Change: Disable interrupts, disconnect from IRQs and disable MSI-X in OS level in bnx2x_nic_unload() both in parity error case
2. Problem: FIP packets won't arrive to the FCoE L2 ring
Cause: Current FW still doesn't support the FIP packets filtering according to the ETH type
Change: Revert the previous enhancement that removed setting the "FIP MAC" to the FCoE L2 Client
Impact: Introduced in 1.60.16
3. Problem: PCI speed is always reported as 5G (Gen2) on 57712
Cause: Wrong decoding of the PCI speed
Change: Fixed the speed decoding
Impact: Only 57712
4. Problem: There was a possibility that packets might be transmitted on the queue of the FCoE L2 Client before its SETUP ramrod is completed
Cause: bp->state was set to OPEN after FUNCTION_START ramrod (before SETUP ramrod(s) are sent)
Change: Set bp->state=OPEN only after all Clients' SETUP ramrods complete
Change: bnx2x didn't send an ACK to IGU after establishing OOO and FWD clients
Impact: CNIC only
2. Problem: (CQ47020) Kernel panic during cnic load
Cause: Initializing of iSCSI L2 context validation values was done from bnx2x_cnic_probe() function, which is called both for devices that are down and their memories are still not allocated (including contexts)
Change: Initialize iSCSI L2 context from bnx2x_register_cnic() which may be called only for interfaces that are up
Impact: CNIC only
3. Problem: CFC error when FCoE INIT ramrod is sent
Cause: FCoE Init CID was not initialized
Change: Initialize fcoe_init_cid to the correct value in bnx2x_cnic_probe()
Impact: FCoE only
4. Problem: (CQ47100) When the force KR enabler is set correctly, traffic does not work on 8073 based boards
Cause: Polarity swap was not set correctly in case link is set to 1G
Change: Initialize polarity swap correctly when enabled.
Impact: BCM8073 based boards only
5. Problem: DCB change during FLR might cause chip hang
Cause: Firmware skipped DCB update when encountered a PCI error
Change: (Fixed in FW 6.0.19) Firmware flow changed to first update DCB version and only then to proceed to handle PCI error
Impact: Introduced in 1.60.11 (FW 6.0.15)
6. Problem: (FCoE) Chip hangs after trying to access inappropriate host memory address
Cause: Firmware instructed corrupted SGEs in PBF command due to corrupted Xstorm context
Change: (Fixed in FW 6.0.19) Save entire Xstorm context during disable connection procedure
Impact: Exists in all previous FCoE releases
7. Problem: (FCoE) (CQ47022) Disabling/Enabling the adapter from Host side without IO, causes device manager to hang
Cause: Firmware did not update task properly in host memory after detecting illegal CONF request
Change: (Fixed in FW 6.0.19) Save task context only after all verification has been completed
Impact: Introduced in 1.60.01
8. Problem: (iSCSI) Connection close does not complete
Cause: Final ACK from target is discarded by firmware
Change: (Fixed in FW 6.0.19) Firmware fix
Impact: Introduced in 1.60.10 (FW 6.0.11)
9. Problem: (CQ47034) MIN/MAX is not accurate for small packets
Cause: The firmware didn't count inter-packet gap and preamble in bandwidth allocation.
Change: (Fixed in FW 6.0.19) Fixed L2 calculation
Impact: Introduced in 1.45.xx. Doesn't include fix for iSCSI and FCoE
10. Problem: (CQ46501) DCBX IOTCL config_dcbx_params.admin_dcbx_version shows incorrect value
Cause: Variable initialized to incorrect value of 2
Change: Fixed to appropriate 0 (CEE)
11. Problem: Link down when upgrading BCM84823 phy firmware to 2.24/2.25
Cause: Changes in the firmware initialization required setting different values
Change: Set the require phy register to achieve link and led in all speeds
Impact: BCM84823 based boards
Enhancements ------------ 1. Request: Add support for iSCSI OOO flow in L2 driver
Change: As requested
Impact: iSCSI only
2. Request: Don't call for NAPI related functions from non-NAPI context
Change: Handle cleanup ramrods in an interrupt driven mode and not in a polling mode as it was
3. Request: (FCoE) Reset the entire KCQE before start initializing it
Change: As requested
4. Request: (FCoE) Change firmware assert to error notification to driver when receiving MP frame with unknown R_CTL.function mode
Change: As requested
5. Request: Use FW 6.0.19
Change: As requested
6. Request: Don't disable TPA on XEN enabled kernels
Change: As requested
Version 1.60.14 (Apr 08, 2010) ==============================
Fixes ----- 1. Problem: Driver failed to pass TCP traffic in non-TPA mode on 57712
Cause: SGE buffer size was not configured to zero in non-TPA mode
Change: Properly set TPA-related section in Client Init ramrod data
Impact: 57712 only
2. Problem: Link LED for 10M/100M/1000M is not functional on BCM84823 based boards
Cause: LED functionality was controlled by 10G core all the time
Change: When link speed is up in 10M/100M/1000M, set led control to 1G core.
Impact: BCM84823/BCM8481 based boards
3. Problem: Link doesn't come up when changed from 1G to 10G with BCM84823 based boards.
Cause: Phy wasn't initialized in this case so some parameters were not cleared
Change: Reset phy when any parameter is changed
Impact: Seen on BCM84823 based board, but may relate to others
4. Problem: (CQ46902) Unable to load driver on some systems
Cause: Old BIOS behaviour is not compliant with newest PCIE spec according to number of tags supported by the system
Change: Driver validates the capability
Impact: 57712 only
Version 1.60.13 (Apr 4, 2010) ============================== **** This release doesn't support non-TPA mode on 57712 devices ****
Cause: Variable initialized to incorrect value of 2
Change: Fixed to appropriate 0 (CEE)
2. Problem: FC behavior is changed so that setting FC to auto when speed is force has no influence of to flow-control
Cause: Although this configuration is not so logic, many boards have their configuration build this way so need to restore this behavior
Change: Change back to old behavior
Impact: Optic devices. Introduced in 1.60.11
3. Problem: When RX-polarity swap is set, traffic in 1G link doesn't pass.
Cause: RX-polarity was set on the PMA/PMD side instead of the XGXS side
Change: Set RX polarity on the XGXS side of the 8073
Impact: KR (BCM8073)
4. Problem: Autoneg flow-control is not seen using "ethtool -a"
Cause: Duplicating the link parameters configuration for dual-media platform
Change: Return the correct FC status
Impact: Introduced in 1.60.11
5. Problem: Self-test was reporting errors in an IGU block when driver was configured to use INT#x
Cause: Driver was reading interrupt status register when IGU was still disabled for the current PF
Change: Connect to IRQs after HW initializing
6. Problem: Self-test was reporting errors in an IGU block when driver was configured to use INT#x
Cause: Driver was reading interrupt status register when IGU was still not configured to Single ISR mode
Change: Set IGU_PF_CONF_SINGLE_ISR_EN bit together with IGU_PF_CONF_FUNC_EN when driver is configured to Single ISR mode (MSI or INT#x) and do not turn it off unless the driver is configured to use MSI-X interrupt mode
Impact: 57712 only
7. Problem: When link speed is set to 1G, link comes up in 10G when connected to device which advertise 10G.
Cause: BCM84823 always advertises 10G speed.
Change: When speed capability doesn't include 10G, or force speed is not set to 10G, disable 10G advertisement
Impact: BCM84823, BCM8481
8. Problem: (CQ46844, CQ46842) Driver did not work properly on machines with large number of CPUs.
Cause: Driver was managing more resources then available in FW
Change: Taking into account max available L2 contexts
Impact: 57712 only
8. Problem: Potential link issue with force 1G on 8073
Cause: Setting one of the registers in the force 1G sequence incorrectly
Change: Fix 1G force sequence
Impact: 57712 + KR only
9. Problem: Terminate ramrod called host coalescing on Tx segment
Cause: Wrong logic while sending host coalescing on Tx
Change: (Fixed in FW 6.0.17) The ramrod no longer send host coalescing
Impact: Introduced in 1.60.6 (FW 6.0.3)
10. Problem: Firmware asserted when TPA is disable
Cause: Wrong logic in the assert Conditions
Change: (Fixed in FW 6.0.17) The assert may occur only when TPA is enabled
Impact: Introduced in 1.60.12 (FW 6.0.15)
11. Problem: VF: system crashed when VF reads client init data
Cause: Reading client init from VF memory and not from PF memory
Change: (Fixed in FW 6.0.17) VF read the client init from PF memory
Impact: Introduced in 1.60.12 (FW 6.0.15)
12. Problem: Pause on exhausted ring broken
Cause: Internal pause data structure was initialized improperly
Change: (Fixed in FW 6.0.17) Fix internal ram offset calculation
Impact: Introduced in 1.60.12 (FW 6.0.15)
13. Problem: (FCoE) Timer expiration doesn't read DCB info
Cause: DCB update is done only for transmission flows
Change: (Fixed in FW 6.0.17) Read DCB info for timer expiration
Impact: Introduced in 1.60.12 (FW 6.0.15)
14. Problem: Return credit in termination handler without executing DCB update
Cause: Firmware bug
Change: (Fixed in FW 6.0.18) Update DCB in the beginning of the terminate handler
Impact: Introduced in 1.60.10 (FW 6.0.11)
Enhancements ------------ 1. Request: When link speed is set to force on copper devices, set link to autoneg with specific link speed advertisement since force speed is not copper compliant
Change: As requested
Impact: BCM84823/BCM8481 based devices
2. Request: Add PFC/DCBX support for E2
Change: As requested
3. Request: Make driver to be compiled, by default, with FCoE support
Change: As requested. FCoE support comes by default with CNIC support
4. Request: Don't allocate SGEs when TPA is not enabled for a specific ring
Change: As requested
5. Request: Use FW 6.0.18
Change: As requested
Version 1.60.12 (Mar 23, 2010) ============================== 1. Problem: Flow control is not set on optic devices
Cause: When flow-control was set to force on optic devices, configuration was not permeate to the MACs
Change: Set the FC configuration on optic devices according to user settings
Impact: Optic devices
Version 1.60.11 (Mar 22, 2010) ============================== Fixes ----- 1. Problem: Driver didn't work on big endian setups
Cause: There were endianness bugs both in HSI and in driver
Change: Properly handle endianness in EQ related code
Impact: Introduced in 1.60.10
2. Problem: Potential link issue with BCM8727
Cause: In BCM8727, the firmware in second port must be loaded before the first port.
Change: Download the second port to 8727 first during initialization
Impact: 57712 only and SFP+ only
3. Problem: Driver didn't work with KVM SR-IOV
Cause: Final client delete (CFCdelete ) was not communicated to the SR-IOV management code.
Change: Passing the delete completion notifications to the SR-IOV management.
Impact: Introduced in 1.60.10
4. Problem: (CQ46455) Load-unload test failed in Multi-Function mode
Cause: Improper initialization and cleanup of IGU block
Enhancements ------------ 1. Request: (CQ45126) Change NIC_MODE to impove latency if no offloaded connection is present
Change: As requested
2. Request: Support dual-media configuration with swapped phy configuration
Change: As requested.
Impact: Dual media board
3. Request: Split speed and duplex parameters into two media
Change: As requested
4. Request: Support powering down the BCM84823 copper core when phy configuration is set to second_port
Change: As requested
Impact: BCM84823 dual-media
5. Request: Add support for 4-port mode device
Change: As requested
Impact: 57712
6. Request: Add support for force 1G for KR triggered by new nvm cfg option 127: "Force KR enabler"
Change: As requested
Impact: KR(BCM8073)
7. Request: Add support for Client Setup ramrod
Change: Use FW 6.0.15
8. Request: Cleanup VLAN related code
Change: As requested
9. Request: Add TCP Out-Of-Order support in iSCSI Firmware
Change: As requested (in FW 6.0.14)
10.Request: Increase L2 clients from 26 clients to 28 in order to support iSCSI Out of Order in multi function mode
Change: As requested (in FW 6.0.15)
11.Request: Added client_init_ramrod_data struct, in order to decouple between driver and firmware client-related structures
Change: As requested (in FW 6.0.15)
12.Request: Support changing COS and vlan priority updates according to DCB in L2 TX firmware
Change: As requested (in FW 6.0.15)
13.Request: (FCoE) Support stop traffic\start traffic flow control ramrods
Change: As requested (in FW 6.0.15)
Version 1.60.10 (Mar 8, 2010) ============================== **** This release doesn't support big-endian architecture **** Fixes ----- 1. Problem: CFC HW attention was popping up on 57710 and 57711 when interface was closed
Cause: bnx2x_pf_disable() was called for all types of chips
Change: Call bnx2x_pf_disable() for 57712 only
Impact: Introduced in 1.60.08; applies for 57711 and 57710 only
2. Problem: (FCoE) PFC didn't function properly
Cause: Bad values of LLFC watermarks
Change: Set LLFC watermarks to proper values
Impact: 57712 PFC only
3. Problem: Limiting the number of queues with the num_queues module parameter to a number smaller then the number of CPUs renders the driver inoperable.
Cause: The RX RSS indirection table is initialized with bad values.
Change: Fixed the indirection table initialization
Impact: Introduced in 1.60.01
4. Problem: VF load for VFs with id greater then 3 crashes the host driver.
Cause: The host driver failed to allocate the HW-context for such VFs.
Change: Fixed the host driver VF HW-context allocation for VFs.
Impact: 57712 IOV only
5. Problem: (CQ45880, CQ46008) On 57712 incorrect statistic information is displayed for ethtool/ifconfig
Cause: Reading the information from incorrect memory region
Change: Fixed region and registers addresses
Impact: 57712 only
6. Problem: (CQ46197) Compilation error on system with undefined value of CONFIG_PCI_MSI
Cause: Code was not compiled due to undefined value
Change: Removed dependency on this value
Impact: Introduced in 1.60.06
7. Problem: BCM84823 Copper link doesn't come up
Cause: Starting from firmware 2.20, BCM84823 enforces the XGXS to link first with the BCM84823 before it triggers LASI.
Change: Set the appropriate flag for the 84823 which enforce XGXS initialization before external link is up
Impact: BCM84823(copper)
8. Problem: CQ45718: Driver crash after driver load
Cause: Driver was sending a relatively new command to a bootcode which doesn't support it. This command in unfamiliar with this bootcode, and should only be sent to bootcode which support it.
Change: Send this command only to bootcode which support it.
Impact: SFP+ only
9. Problem: Some error statistics weren't counted correctly
Cause: The statistics address was miscalculated
Change: Fixed address calculation (in FW 6.0.11)
Impact: Introduced in 1.60.06 (FW 6.0.3)
10. Problem: iSCSI firmware broken
Cause: TCP layer interface was changed
Change: Applied new TCP interface to iSCSI firmware (in FW 6.0.11)
Impact: Introduced in 1.60.07 (FW 6.0.4)
11. Problem: Possible permanent locking of Tx queue
Cause: There was a memory barrier missing after tx_cons update
Change: Added a missing barrier
12. Problem: Possible "queue is alive while ring is full" situation
Cause: bnx2x_start_xmit() may have run and locked the queue while bnx2x_tx_int() has decided that it may unlock it
Change: Take tx_lock while deciding to unlock the queue
Enhancements ------------ 1. Request: Add clarification for int_mode driver parameter
2. Request: Support MAC partitioning mode (Multi function based on MAC classification)
Change: As requested
Impact: 57712 only (when set to MAC partitioning mode)
3. Request: Use FW 6.0.12
Change: As requested
4. Request: Use the upstream printouts and mcast iterators semantics
Change: As requested
Version 1.60.09 (Feb 22, 2010) ============================== Fixes ----- 1. Problem: (CQ46006) NIG test A36 failed if the driver was loaded before
Cause: Configuration of PGLUE_B register with wrong value, while reset value is good
Change: Remove erroneous configuration
Impact: 57712 only
2. Problem: (CQ45648) driver asserts while trying to unload/load iSCSI/FCoE
Cause: internal firmware resources were not cleaned properly by driver upon unload
Change: (Fixed in FW 6.0.8) offset was generated for slow path sync line index
Impact: 57712 only
3. Problem: (FCoE) Terminate handler will not complete
Cause: Race between timer expiration and terminate handler invocation
Change: (Fixed in FW 6.0.8)
Impact: 57712 only
4. Problem: (CQ46052) Compilation warning on older kernels ("warning: assignment discards qualifiers from pointer target type")
Cause: The compilation condition regarding the kernel version was mistakenly changed
Change: Change the kernel version condition
Impact: Introduced in 1.60.08
5. Problem: (FCoE) (CQ45915): Second CNIC interrupt was never arriving when working with port 1
Cause: Wrong SB ID was used in CNIC functions sending ACK to IGU
Change: Added IGU_SB_ID to CNIC interface, fixed CNIC functions sending ACK to IGU to use the new index
Impact: Has been introduced in T6.0
Enhancements ------------ 1. Request: For 57712 add support for switch-independent mode
Change: As requested
2. Request: Add per-path licensing support
Change: (In FW 6.0.9) Support BCM57712 address scheme
Impact: 57712 only
3. Request: Minimize DMA transaction to improve PCIE latency
Change: (In FW 6.0.9) Packet placement is done in single DMA command instead of two
4. Request: Constant pause avoidance
Change: (In FW 6.0.9) Timeout for pause sending was added. Un-pause message will be sent upon timeout expiration. (Timeout default is 1 minute, can be set up to 5 minutes by the driver)
Impact: 57711/57711E/57712 only
5. Request: Use FW 6.0.9
Change: As requested
Impact: iSCSI is not functional in this version
Version 1.60.08 (Feb 18, 2010) ============================== **** iSCSI is not functional in this version **** Fixes ----- 1. Problem: (CQ45963,CQ45962) DCBX IOCTL shows unusual values for admin_configuration_ets_pg, admin_pfc_bitmap
Cause: Admin section was initialized with incorrect values
3. Problem: (CQ45763, CQ45799) On 57712 a request can be sent on a disabled function
Cause: Request sent from timers block that scans function 6/7 when function 2/3 scan off is set
Change: Workaround in the driver that assures that if the timers starts scanning for function 6/7 nothing fatal will occur
Impact: 57712 only
4. Problem: (CQ45973) On 57712 bringing up interface caused DMAE timeout
Cause: Initialization of function not performed properly
Change: Enable function in PGLUE_B module before accessing DMAE
Impact: 57712 only
5. Problem: In KR board type, when loading the first port first, it causes the other port's link not to come up.
Cause: BCM8073 requires that the second port's firmware will be loaded first.
Change: Always load the first phy port's firmware
Impact: 57712 only and KR only
Enhancements ------------ 1. Request: Replace references to cnic_drv.h with cnic_if.h
Change: As requested
2. Request: Add DRV_CTL_{START,STOP}_L2_CMD capabilities to drv_ctl()
Change: As requested
3. Request: Update cnic driver with SP_SB information
Change: As requested
4. Request: Add handling for iscsi mac addresses during registrer_cnic() unregister_cnic() and chip_cleanup()
Change: As requested
Version 1.60.07 (Feb 11, 2010) ============================== **** iSCSI is not functional in this version **** Fixes ----- 1. Problem: (CQ45674) Warning message was displayed when modprobe bnx2x "bnx2x_get_hwinfo ..."
Cause: Inappropriate printing level for the message used
Change: Set correct level
2. Problem: BCM8073 wasn't initialized during common init
Cause: In 57712, the second port is actually port0 of the second path, and it wasn't treated like that.
Change: Initialize port0 of both paths of BCM8073 during common init
Impact: 57712 only and KR only
3. Problem: PCIE-X link speed is not displayed correctly for 57712
Cause: Misinterpretation of link speed encoded value
Change: Fixed for 57712
Impact: 57712 only
4. Problem: Performance drop on high-PPS scenarios with new HC code
Cause: New HC flow was overloading a HW buffer and caused back pressure on on-chip processors
Change: (In FW 6.0.6) Remove some of the HW buffer uses
Impact: introduced in 1.60.01 (FW 5.3.19)
5. Problem: (CQ45499) HW attention at BCM57710 stress test
Cause: New HC flow could cause HW bug by using illegal timers command
Change: (In FW 6.0.6) Remove the use of timers command, instead use aggregated interrupts
Impact: introduced in 1.60.01 (FW 5.3.19) BCM57710/BCM57711 only
6. Problem: Change MTU causes L4 traffic to stop
Cause: Status Block of cnic driver was not updated during nic_load
Change: Add cnic SB update
Impact: Introduced in 1.60.01
Enhancements ------------ 1. Request: Use FW 6.0.7
Change: As requested
Impact: iSCSI is not functional in this version
Version 1.60.06 (Feb 4, 2010) ============================== **** This version requires bootcode 6.0.6 or above for BCM57712 ****
Fixes ----- 1. Problem: FCoE wasn't receiving mcast packets, including FIP packets sent to ALL_ENODE_MACS address
Cause: There was DROP_ALL_MCAST flag set to FCoE L2 client
Change: Set ACCEPT_MCAST flag to FCoE L2 client that will make it receive only matched mcast packets
2. Problem: Path1 shared memory data run over Path0 configuration
Cause: The register that marks the beginning of the shared memory is global rather than split per path
Change: Use different registers to mark the beginning of the shared memory per path.
Impact: 57712 only
3. Problem: bnx2x stopped receiving on the VLAN after MTU change
Cause: VLAN removal flag was not configured after reloading FW during change MTU flow
Change: Configure VLAN removal flag if needed after MTU change
4. Problem: drivers enter infinite loop during crash dump
Cause: lack of parentheses in loop expression
Change: add parentheses
5. Problem: (iSCSI)(CQ45150) OIS Assert occurred after attempting to login to iSCSI target
Cause: Firmware bug
Change: Fixed in FW 6.0.2
6. Problem: (FCoE)(CQ44937) Data corruption after forcing FC-CRC error
Cause: Hardware bug when detecting CRC error on FCoE data placement
Change: (Fixed in FW 6.0.3) Firmware workaround - Send 64 DMA dummy write commands in order to prevent the false error from appearing
7. Problem: 57712 4-port mode doesn't link up
Cause: XGXS wasn't actually configured in this mode since the current MD_DEVAD used didn't work.
Change: Use different MD_DEVAD when working with the E2 XGXS
Impact: 57712 only
8. Problem: 57712 4-port D2 nic test(internal loopback test) fail
Cause: Loopback was set as 10G instead of 1G loopback
Change: When speed selection is 1G, set 1G loopback, otherwise set 10G loopback.
Impact: 57712 only
Enhancements ----------- 1. Request: Add support for KVM SR-IOV (BCM57712 and onwards)
Change: As requested
2. Request: Add support for VF devices
Change: As requested
3. Request: Update README.TXT and manpages with GRO dependency on 8021q module
Change: As requested
4. Request: Use FW 6.0.3
Change: As requested
Version 1.60.04 (Jan 26, 2010) ==============================
Fixes ----- 1. Problem: (CQ43831) Driver error reports while loading/unloading under DCC traffic
Cause: A race condition between disabling the incoming traffic when unloading and DCC enabling the link
Change: Changed DCC enable/disable commands to use a different register setting that will not interfere with normal unload sequence
2. Problem: Driver load under DCC traffic might fail
Cause: Lack of lock between driver load command and DCC ack command
Change: Add mutex to protect the FW mailbox
3. Problem: ifconfig up reported error while using bootcode 6.0.1
Cause: Lack of lock between DCBX init command and response handling
Change: Add mutex to protect the FW mailbox
4. Problem: FW asserts while unloading/loading under DCC enable/disable commands
Cause: DCC disable command changed the driver internal state and might overrun state changes which are initiated by the load/unload sequence. This caused the driver to be out of sync with the FW
Change: DCC disable/enable command uses different flag and not the driver state
5. Problem: Error message is printed when failing to obtain MSI-X vectors
Cause: When trying to work in multi-mode and not getting enough MSI-X vectors, the driver printed an error message indicating that it will use a single queue
Change: Since this is a valid condition, the print is allowed under specific messages level only
6. Problem: port 1 of 57712 can't initialize correctly
Cause: driver accessed incorrect shmem addresses
Change: fixed
Impact: 57712/57712E only
7. Problem: 57712 link is not up
Cause: There's difference in AER strapping between 57711 and 57712
Change: Set the XGXS AER to the appropriate value according to the new XGXS model
Impact: 57712 only
Version 1.60.03 (Jan 20, 2010) ==============================
Fixes ----- 1. Problem: Unresolved symbols during compilation on 32bit platforms
Cause: Improper initialization of variable with FP symbol
Change: Using integer constant instead
Impact: Introduced in 1.60.01
2. Problem: MF dead in the water for 57711
Cause: Improper initialization of the FW caused it to hang
Change: Fixed initialization
Impact: Introduced in 1.60.01
3. Problem: HC not enabled for port 1
Cause: Improper initialization the HC in the FW
Change: Fixed initialization
Impact: Introduced in 1.60.01
4. Problem: (iSCSI) Unexpected chip behavior when padding is splitted into 2 or 3 parts
Cause: Firmware bug when aligning split padding
Change: Firmware was fixed
Impact: Problem exists in all previous releases
5. Problem: (iSCSI) False data digest error when data digest is splitted into 3 parts
Change: Remove access to EMAC register in case of emulation
2. Problem: In dual-media, only the SFP+ module on the first phy is checked
Cause: Insufficient support in SFP+ module checking
Change: Modify SFP+ module API verification to include parameter indicating the exact phy.
Impact: Whenever driver send command to the bootcode, it will now also send parameter. Bootcode will treat this parameter only when it is relevant
3. Problem: (FCoE) Chip hangs while running normal rd/wr operations
Cause: RX Doorbell was not handled properly
Change: (Fixed in FW 5.3.18) Handling the case where receiving false RX doorbell
4. Problem: (FCoE) (CQ44936, CQ44937) Data corruption during read/write/compare test
Cause: Error was not detected by FW since it was short FCP_RSP packets
Change: (Fixed in FW 5.3.20) Checking if received the amount of data when receiving this format of FCP_RSP
5. Problem: (FCoE) (CQ44936, CQ44937) Data corruption during read/write/compare test
Cause: When packet with invalid CRC detected, task context isn't reverted to previous valid state
Change: (Fixed in FW 5.3.20) on detection of packet with invalid CRC, task cached context isn't write back to memory
6. Problem: (iSCSI) Chip hangs when running iSCSI read traffic
Cause: Miscalculation of HW commands when SGEs are not 64-bytes aligned
Change: (Fixed in FW 5.3.20) Fixing FW calculation of SGE alignment and fields in HW command
7. Problem: (FCoE) Upper layer didn't know which MAC to use during DCBX negotiation.
Cause: Proper MAC (SAN) was not set in the netdev.
Change: Call dev_addr_add() with the proper MAC and SAN type.
8. Problem: (FCoE) FIP packets were not ruled by the PFC FC.
Cause: FIP packets were arriving on a regular L2 client.
Change: Set a different MAC to the FCoE L2 client.
Enhancement ----------- 1. Request: Changed the doorbell size (the stride between consecutive doorbells' addresses) from 4K to 128
Change: As requested
2. Request: Add support for dual-media board type
Change: Redesign the CLC to be able to handle multi-phy boards. Rename clc/CLC to elink/ELINK. Driver is required to probe the phys on board before initializing the link. Specific phy access will be done using "phy" structure. Common access will go over all phys on board and execute the command on them.
Impact: From now on, high level driver will not be familiar with the phys on-board. For every phy access, it is required to use the elink API, or add new one.
3. Request: Having the ability to pass data from the Tstorm to the driver over the SGL in fast_path_cqe (required for iSCSI Out-Of-Order)
Change: As requested (in FW 5.3.20)
4. Request: Use FW 5.3.20
Change: As requested
5. Request: Add DCBX support for 57711
Change: As requested
6. Request: Remove #ifdef CONFIG_PCI_MSI sections from code
Change: Removed #ifdef CONFIG_PCI_MSI sections. Left the code that was compiled when this (CONFIG_PCI_MSI) macro has been defined.
Version 1.53.14 (Dec 7, 2009) ==============================
Enhancement ----------- 1. Request: (CQ41760) Use more generic log message in case of fan failure
Change: As requested
2. Request: (CQ43089) Add VPD-R V0 entry to displayed firmware revision in ETHTOOL
Change: As requested
3. Request: Use FW 5.3.17
Change: As requested
4. Request: Enable parity errors recognition and recovery.
Change: First implementation of parity error recovery flow. Currently only "process kill" is supported. Parity errors are currently disabled for E1 until the proper changes are done to init tool.
Version 1.53.13 (Nov 17, 2009) ==============================
Fixes ----- 1. Problem: Improper initialization of MF/SF causes driver to stall
Cause: Using uninitialized values of fpid
Change: Using fpid moved to later stages after its initialization
Impact: None
Version 1.53.12 (Nov 16, 2009) ==============================
Fixes ----- 1. Problem: CQ41232: Management gets incorrect AN and FC bit values.
Cause: FC wasn't updated correctly during link up event
Change: Extract all status_link information correctly
Impact: None
2. Problem: CQ36401: Excessive link down messages when driver is unloaded
Cause: Link event is reported for every link event, even when link is not changed
Change: Do not report link change unless there's actually link link change
Impact: None
3. Problem: BCM8481 doesn't negotiate FC capabilities
Cause: FC capabilities weren't advertised during phy initialization
Change: Set BCM8481 FC capabilities during init stage
Impact: None
4. Problem: (FCoE) Completions are not arrived on open tasks
Cause: Connection does not register to QM since SQ producer/consumer
Change: Fixed in FW 5.3.14: Set BCM8481 FC capabilities during init stage
Impact: None
Enhancement ----------- 1. Request: Support bootcode on 57712
Change: As requested
Impact: 577712 Only
2. Request: Allocate available MSI-X vectors in normal mode
Change: As requested
Impact: None
3. Request: Use multi cpu rx when using msix in kernels without new napi
Change: As requested
Impact: None
4. Request: support correct number of iSCSI and FCoE sessions in the HW initializations
Change: As requested
Impact: None
5. Request: support any number of L2 queues in the HW initializations
Change: As requested
Impact: None
6. Request: Hanlde both Tx and Rx in NAPI
Change: As requested
Impact: None
7. Request: Support 4-port mode for 57712
Change: As requested
Impact: None
8. Request: Use FW 5.3.14
Change: As requested
Impact: None
Version 1.53.11 (Nov 11, 2009) ============================== Fixes ----- 1. Problem: When iptable_nat module is installed on RH4, traffic halts
Cause: iptable_nat on RH4 requests for GSO without asking for csum offload
Change: When configuring the HW/FW to GSO, always configure csum offload as well
2. Problem: (FCoE) Chip hanged during data placement
Cause: Thread started placing data before verifying the task type
Change: Fixed in FW 5.3.13: verify task type is match to read in FCP_DATA before placement
Impact: None
3. Problem: (CQ44328) (FCoE) Chip hanged after error was detected
Cause: Thread was waiting for CRC result instead of releasing the packet
Change: Fixed in FW 5.3.13: Release the packet if an error occurred during data placement
Impact: None
Enhancement ----------- 1. Request: Use FW 5.3.13
Change: As requested
Impact: None
Version 1.53.10 (Nov 08, 2009) ==============================
Enhancement ----------- 1. Request: Use FW 5.3.12
Change: As requested
Impact: None
Version 1.53.9 (Oct 27, 2009) ==============================
Fixes ----- 1. Problem: ethtool -t ethX FAILED
Cause: test_registers() accessed registers without mask
Change: Added mask for write access
Impact: None
Version 1.53.8 (Oct 26, 2009) ==============================
Enhancement ----------- 1. Request: Use FW 5.3.10
Change: As requested
Impact: None
Version 1.53.xx (Oct xx, 2009) ==============================
Enhancement ----------- 1. Request: Improve times for ifconfig up/down (slow 57712 chip revision)
Change: As requested
Impact: None
Version 1.53.xx (Oct xx, 2009) ==============================
Enhancement ----------- 1. Request: Add support for EMAC loopback for FPGA
Change: As requested
Impact: None
Version 1.53.7 (Oct 22, 2009) ==============================
Enhancement ----------- 1. Request: Use FW 5.3.9
Change: As requested
Impact: None
2. Request: Remove compilation flag for BCM57712/BCM57712E/BCM57713/BCM57713E
Change: As requested
Impact: None
Version 1.53.6 (Oct 21, 2009) ==============================
Enhancement ----------- 1. Request: 57712 multifunction support
Change: As requested
Impact: None
Version 1.53.5 (Oct XX, 2009) ==============================
Fixes ----- 1. Problem: Failed to build bnx2x in chroot build environment
Cause: The Makefile attempted to run with -j flag to utilize all CPU in the system and in chroot environment it resulted with "-j 0"
Change: The Makefile should not force the -j option. Removed this feature
Impact: Without explicitly providing the -j flag when compiling the driver, the compilation will consume more time
Version 1.53.4 (Oct 11, 2009) ==============================
Fixes ----- 1. Problem: Priority Flow Control on BCM57711 showed low performance
Cause: Transmitted Xon PFC packet was malformed. PriorityEnableVector field in PFC packet was set to zero instead of the relevant priorities. This caused to remote peer to wait longer until timers expired to Xon again
Change: Fixed in FW 5.3.8: set properly PriorityEnableVector in Xon PFC packet
Impact: None
2. Problem: (CQ43517) SLES11u0 iSCSI: SUT hangs when unexpected FIN packet was received under traffic
Cause: FW erroneously increased activity counter
Change: Fixed in FW 5.3.8: condition for activity counter increment fixed
Impact: None
3. Problem: (CQ43517) SLES11u0 iSCSI: SUT hangs when unexpected SYN packet was received under traffic
Cause: TCP reset initiated by FW caused endless wake ups for FW
Change: Fixed in FW 5.3.8: changed setting of FW internal flags
Impact: None
4. Problem: iSCSI offload: Memory sanity of thread check fail during Query ramrod
Cause: During Query ramrod, when FW prepared the context for upload on the scratchpad, it exceeds the thread scratchpad boundary
Change: Fixed in FW 5.3.8: use the scratchpad within the thread boundary only
Impact: None
5. Problem: iSCSI offload: TCP Close failed
Cause: Bug in byte credit update during termination
Change: Fixed in FW 5.3.8
Impact: None
6. Problem: FCoE INIT ramrod was never completed
Cause: Reading from inappropriate VQ in Tstorm
Change: Fixed in FW 5.3.8: reading from to the correct VQ
Impact: None
Enhancement ----------- 1. Request: BCM577xx support for FW 5.3.8
Change: As requested
Impact: None
2. Request: Adding support broadcast and multicast received packets in L2 switch independant mode
Change: In FW 5.3.8 as requested
Impact: None
Version 1.53.3 (Oct xx, 2009) ==============================
Fixes ----- 1. Problem: Only Tx queue 0 was used in default configuration on kernel 2.6.30 and above
Cause: bnx2x_select_queue() was returning 0 by default
Change: Make bnx2x_select_queue() return stack tx_hash() by default
Impact: None
Enhancement ----------- 1. Request: Add a separate L2 ring for FCoE L2 traffic
Change: As requested
Impact: None
Version 1.53.2 (Oct 8, 2009) ==============================
Fixes ----- 1. Problem: 57712 failed to receive data from network
Cause: Incorrect MAC type selected during initialization
Change: MAC initializaton fixed
Impact: None
2. Problem: 57712 failed to bring up interface
Cause: Unhandled attention interrupt caused processor to stall
Change: Added handling for new attentions
Impact: None
Version 1.53.1 (Oct 5, 2009) ==============================
Enhancement ----------- 1. Request: 57712 support for FW 5.3.7
Change: As requested
Impact: None
Version 1.53.xx (Sep xx, 2009) ==============================
Enhancement ----------- 1. Request: When PFC is enabled, set BigMAC to relay control packets to the system as well, and enable BigMAC to react on received Pause packets
Change: As requested
Impact: None
Version 1.53.0a (Oct 1, 2009) ==============================
Enhancements ------------ 1. Request: Use FW 5.3.7
Change: As requested
Impact: None
2. Request: Add support for BCM57712 (by compilation flag)
Change: As requested
Impact: None
Version 1.51.0a (Sep 14, 2009) ==============================
Fixes ----- 1. Problem: Enabling fairness algorithm in the middle of the run causes the function to stop transmitting.
Cause: The fairness credit is not initialized in this case.
Change: Change the fairness credit init value.
Impact: None.
2. Problem: (CQ42873) No traffic when number of receive buffers is configured to 50 (the minimum) in the advanced properties page.
Cause: Firmware is always saving a CQE for each TPA aggregation. So in case less then 75 CQEs are on the ring, the firmware starts dropping packets.
Change: Check if TPA is enabled before deciding if to drop packet. If TPA is disabled save only 11 CQEs instead of 75.
Impact: None.
Enhancements ------------ 1. Request: Use FW 5.3.4
Change: As requested
Impact: None
Version 1.51.x (Aug xx, 2009) =============================
Fixes ----- 1. Problem: Link is down with BCM8481 when connected to 1G device after it was connected to 100M device
Cause: When link type changes from SGMII to GMII/XGMII, the SGMII configuration wasn't removed
Change: Remove SGMII configuration in non-SGMII link type
Impact: None
2. Problem: BCM8481 link is not able to link up after cable plug out/in
Cause: New BCM8481 image required new configurtion of the LED4 signal which generate the interrupt
Change: Detect link down using the LED4 signal rathen than the BCM8481 registers
Impact: None
3. Problem: Link is down with BCM8481 when connected to 1G device after it was connected to 100M device
Cause: When link type changes from SGMII to GMII/XGMII, the SGMII configuration wasn't removed
Change: Remove SGMII configuration in non-SGMII link type
Impact: None
4. Problem: BCM8481 link is not able to link up after cable plug out/in
Cause: New BCM8481 image required new configuration of the LED4 signal which generate the interrupt
Change: Detect link down using the LED4 signal rather than the BCM8481 registers
Impact: None
5. Problem: Driver might read corrupted data from shared memory in case bootcode is missing
Cause: Some pieces of code are not protected in case bootcode is missing
Change: Add additional protection in case bootcode is missing
Impact: None
Enhancements ------------ 1. Request: When PFC enabled, pass pause frames towards the NIG
Change: As requested
Impact: None
2. Request: Improve FP performance
Change: Remove writing ACK to USTORM from Tx flow and to CSTORM from Rx
Impact: None
3. Request: Handle fan failure for BCM8481 PHY
Change: As requested
Impact: None
4. Request: Once PFC is selected along with emac, it is required to set BIT 3, KEEP_MAC_CONTROL, at emac register rx_mode. Setting this bit causes MAC control frames (except for pause frames) to be passed on for processing. This setting has no affect on the operation of the pause frames. This bit affects all packets regardless of RX Parser packet sorting logic.
Change: As requested
Impact: None
5. Request: Use FW 5.1.23.1
Change: As requested
Impact: None
6. Request: Support kernel 2.6.31 (RC2)
Change: Use DMA_MAP macros and .ndo_select_queue
Impact: None
7. Request: (CQ41112) - PHY LED Programming for BCM8481 on BlackBird (BCM957711A1100G) Production Board
Change: As requested
Impact: None
8. Request: Increase DMAE max write size for 57711/57711E
Change: As requested
Impact: None
9. Request: Not handling statistics in panic condition
Change: As requested
Impact: None
10. Request: Enhance bnx2x_panic_dump() - print SB data
Change: As requested
Impact: None
Version 1.52.2 (Aug 18, 2009) ============================= Fixes ----- 1. Problem: (CQ42998) 57711E PF on OS linked even after unassigning network in VC
Cause: ethtool reports the physical link status instead of PF OS link status
Change: bnx2x_get_link() returns no link if driver is not in open state
Impact: None
2. Problem: ethtool displays 57711E PF link speed as 0 in certain scenario
Cause: VC assigned network and max bandwidth were not refreshed during driver load
Change: Refresh the VC assigned network and max bandwidth during driver load
Impact: None
3. Problem: syslog and kernel logs always report 57711E PF speed as 10000 Mbps
Cause: bnx2x_link_report() reports the actual physical link speed instead of the max bandwidth assigned to the PF
Change: Report the max bandwidth assigned to the PF
Impact: None
4. Problem: In some cases FW does not respond in time to driver requests and thus driver load fails
Cause: For certain PHYs, FW might need some more time before responding to driver request
Change: Increase the timeout up to 5 sec
Impact: None
Enhancements ------------ 1. Request: Set interrupt coalescing granularity to 4us instead of 12us
Change: As requested
Impact: None
2. Request: Change default interrupt coalescing numbers to supported numbers
Change: Since the interrupt coalescing granularity is 4us, a value of 25 is actually configured as 24 to the HW
Impact: None
3. Request: Fix bnx2x_fw_dump() to compute trace start address based on shmem offset
Change: As requested
Impact: None
Version 1.52.1 (Aug 12, 2009) ============================= -- Upstream Version -- Fixes ----- 1. Problem: Link is down with BCM8481 when connected to 1G device after it was connected to 100M device
Cause: When link type changes from SGMII to GMII/XGMII, the SGMII configuration wasn't removed
Change: Remove SGMII configuration in non-SGMII link type
Impact: None
2. Problem: BCM8481 link is down after cable plug out/in
Cause: New BCM8481 image required new configuration of the LED4 signal which generate the interrupt
Change: Detect link down using the LED4 signal rather than the BCM8481 registers
Impact: None
3. Problem: (CQ35477) Incorrect display of External Phy Firmware Version for Everest XFP board.
Cause: External Phy Firmware Version for BCM8705 PHY used to display 0000:0000
Change: Change not to display PHY FW version
Impact: None
4. Problem: In BCM8727, spirom was loaded first on slave port, rather than on the master port. This may lead to xaui pll issue.
Cause: Port-Swap wasn't considered when loading spirom to the BCM8727, hence first the slave port was loaded with the spirom.
Change: First load the SPIROM to the master port.
Impact: None
5. Problem: Possible FW assert in driver unload/load test case
Cause: Possible race on statistics state machine state change
Change: Added a write barrier to ensure that the state change is committed
Impact: None
Enhancements ------------ 1. Request: In promiscuous mode, pass management traffic to the host
Change: As Requested
Impact: None
2. Request: PCI drivers that implement the struct pci_error_handlers' error_detected callback should return PCI_ERS_RESULT_DISCONNECT if the state passed in is pci_channel_io_perm_failure
Change: As Requested
Impact: None
3. Request: (CQ41112) PHY LED Programming for BCM8481 PHY
Change: As requested
Impact: None
4. Request: (CQ41067) Add support for CL73 on XAUI
Change: As requested
Impact: None
Version 1.52.0 (Jul 28, 2009) =============================
Fixes ----- 1. Problem: Redundant settings of vlan_features at set_tso
Cause: There is no need to change vlan_features at set_tso since this field is a capability field and not current settings
Change: Remove redundant code
Impact: None
2. Problem: (CQ42550) No host traffic when NCSI is enabled on some systems
Cause: The driver did not set the required filtering flags and received only traffic which was not intended for the BMC - on some systems, this is not enough and the driver should enable its own masking
Change: Setup the driver mask to receive traffic even when NCSI is enabled
Impact: None
Version 1.50.13 (Jul 22, 2009) ==============================
Enhancements ------------ 1. Request: Update to FW 5.0.21
Change: As requested
Impact: None
Version 1.50.12 (Jul 16, 2009) ==============================
Fixes ----- 1. Problem: In some TPA aggregation cases, might go into TCP slow-start instead of fast-retransmit
Cause: When TPA is used, pure ACK on open aggregation was aggregated
Change: (FW 5.0.20) Do not aggregate pure ACK packets in TPA
Impact: None
Version 1.50.11 (Jul 7, 2009) =============================
Fixes ----- 1. Problem: Setting rx-usecs to the value less than 12 causes the traffic to stop
Cause: Did not disable HC coalescing when set the coalescing timeout to zero (coalescing timeouts are multiples of 12us)
Change: Disable HC coalescing, when timeout is set to the zero
Impact: None
2. Problem: Packet descriptors in NIG might get out of sync if management egress traffic is pass through during self test
Cause: During loopback test management egress traffic might be routed to the host and will not be cleared when exiting the diag mode
Change: Disable management egress traffic when driver is in diag mode
Impact: None
Version 1.50.10 (Jul 1, 2009) =============================
Fixes ----- 1. Problem: (CQ42298) Management traffic does not resume after self test
Cause: Writing to the egress management FIFO during the memory test interpreted as a start of a management packet and cause the FIFO not to be empty
Change: Remove the write to the egress management FIFO from the self test
Impact: None
2. Problem: Link up time takes too long with BCM8727 based NICs
Cause: EDC mode is not set automatically
Change: Set EDC mode manually according to the SFP+ module type detected (Passive DAC / Active DAC / LC-LRM / LC-SR / LC-LR)
Impact: None
3. Problem: (CQ41567) In BCM8727 based NICs, when SFP+ module is not plugged, there is continuous messages of Link Down
Cause: The EDC tries to process the Rx data/noise because its OPRXLOS input signal is false (low), indicating an Rx signal is present.
Change: Perform 'Or' of the Active Module Absent Level with the Active Laser Loss of Light Level. This way we tell the EDC not process Rx data/noise when the module is not present.
Impact: None
Version 1.50.9 (Jun 25, 2009) =============================
Fixes ----- 1. Problem: Low throughput when using VLAN on kernel 2.6.26 or above
Cause: New VLAN_features field in struct net_device was not initialized hence no offload capabilities were available with VLAN
Change: Initialize VLAN_features field in struct net_device
Impact: None
2. Problem: No event log in case fan failure occured prior to loading the driver
Cause: The event was not detected since it was already set when the driver was loaded
Change: Check for the event on load time
Impact: None
3. Problem: Loopback test in self test might fail in case NCSI is enabled
Cause: NCSI egress traffic is received instead of the loopback test packets
Change: Disable NCSI egress traffic during loopback test
Impact: None
4. Problem: ethtool reports link up when the device is down
Cause: Bug in ethtool_op_get_link()
Change: Use bnx2x_get_link() instead
Impact: None
5. Problem: 57711E WoL does not work if only one function per port was active prior to shutdown
Cause: WoL is configured to work in SF mode
Change: Set the chip back to SF mode (so WoL will work) even if only one function was loaded per port in MF mode
Impact: None
Version 1.50.8 (Jun 8, 2009) ============================
Fixes ----- 1. Problem: When running many TCP connections (>200) on both ports, some connections hangs
Cause: When all TPA aggregations are occupied, FW can override the RX CQE consumer of the other port
Change: Fix in FW 5.0.18: reload the RX CQE consumer from RAM after TPA handler breaks to sleep
Impact: None
2. Problem: CL73 enhancement causes link down
Cause: Unknown
Change: Revert CL73 enhancement until problem resolved
Impact: None
Version 1.50.7 (Jun 4, 2009) ============================
Fixes ----- 1. Problem: (CQ41533) Unapproved modules behavior is not enforced according to nvram configuration
Cause: In case the module was not approved, the function quit before enabling the Tx laser - so even when set to warning, there was no link. When set to power off the module, there was continues false indication of over current when the module was extracted
Change: When set to warning - enable the module. Validate that the module is present before checking for over current indication
Impact: None
2. Problem: The coalescing timeout value displayed by `ethtool' is different for the one used by the FW
Cause: The limitation for coalescing timeout values in driver's `ethtool -C' callback was wrong
Change: Fix the limitation for coalescing timeout in `ethtool -C' callback
Impact: None
Enhancements ------------ 1. Request: Reduce the number of cache misses in a fast path
Change: Avoid extra cache miss by updating `trans_start' from inside start_xmit() as long as it's done by the core network layer starting from kernel 2.6.31
Impact: None
2. Request: (CQ41067) Add 5771x CL73 support
Change: As requested
Impact: Everest is now able to link with devices which operate in CL73 alone / CL37 alone / or both
3. Request: Make 8727 over-current behavior code more efficient
Change: As requested
Impact: None
Version 1.50.6 (Jun 1, 2009) ============================
Fixes ----- 1. Problem: In 8727, after power-fault occurred and the driver is unloaded and then reloaded, the interrupt is not cleared
Cause: In this scenario, the mod_abs mode remain in "wait for module plugged in", so interrupt was not cleared
Change: Set module_absent to wait for module absent scenario
Impact: None
2. Problem: There is no need to read the warning string for un approved modules from the FW/nvram
Cause: This is over design that cause unnecessary overhead - a constant string can be used
Change: Use constant warning string instead of receiving it from FW/nvram
Impact: Warning message is not to be used in the modules nvram file
3. Problem: High CPU usage in bnx2x_free_tx_pkt()
Cause: prefetch(skb_shinfo(skb)) implied immediate cache miss when NET_SKBUFF_DATA_USES_OFFSET is enabled
Change: Replaced prefetch(skb_shinfo(skb)) by prefetch(&skb->end). This would prefetch only the first one from two cache misses needed for reading of skb_shinfo(skb)->nr_frags, which is needed by dev_kfree_skb(skb), but it will do it in a background avoiding an immediate CPU stall
Impact: None
Enhancements ------------ 1. Request: Add support for BCM8727 without over current detection (BCM8727_NOC)
Change: As requested
Impact: None
Version 1.50.5 (May 26, 2009) =============================
Fixes ----- 1. Problem: (CQ38975) Failed to setup leading connection after a lot of iterations of "down-up" test. Workaround for CQ37893 (Use INTx mode when MSI-X fails due to memory allocation failure) was broken
Cause: bnx2x_set_int_mode() wasn't returning a status, thus there was no way to catch a mentioned above memory allocation failure
Change: Return a status from bnx2x_set_int_mode()
Impact: None
2. Problem: (CQ41349) Linux panic when disabling RX chksum and running RX traffic
Cause: TPA enabled option was not controlled per function/queue level
Change: FW fix in version 5.0.16: TPA enabled is now controlled per function/queue level
Impact: None
3. Problem: (CQ41434) ethtool -S was printing junk on kernels with RSS support
Cause: There was a bug in function returning number of lines in device statistics bnx2x_get_stats_count - it was returning more than there actually were)
Change: Make bnx2x_get_stats_count return the correct number
Impact: None
Enhancements ------------ 1. Request: Support approved module list and warn if the module is not on the list
Change: This feature requires bootcode 5.0.6 or later and a valid optic modules image on the nvram. The feature is controlled by nvram option 81
Impact: None
2. Request: Allow enabling and disabling the fan failure mechanism for different PHY types
Change: Determine if fan failure enforcement is required according to nvram configuration. The configuration can be auto enforcement according to the PHY type, disabled or enabled
Impact: None
3. Request: Support firmware flow control when consuming SGEs
Change: FW change in FW 5.0.16: Added check for Flow control when consuming SGEs from host
Impact: None
4. Request: Advertise driver DCC capabilities
Change: As requested
Impact: None
Version 1.50.4 (May 18, 2009) =============================
Cause: LSO packets with BDs that point to buffers that are less than MSS size caused the firmware to send illegal bytes within the same LSO packet
Change: FW fix in version 5.0.14
Impact: Regression introduced in v1.50.2
2. Problem: (CQ41198) modprobe generate error on RH4.6 or 4.7 which will cause kernel panic
Cause: pci_register_driver() returns count and not errno
Change: Ignore the return code from pci_register_driver() in kernels below 2.6.10
Impact: None
3. Problem: (CQ38975,CQ38925) Failed to setup leading connection after a lot of iterations of "down-up" test
Cause: There were a few memory barriers missing
Change: Add missing memory barriers
Impact: None
Enhancements ------------ 1. Request: Reduce the time spent in skb_release_data()
Change: Add prefetch(&skb->end) before calling dev_kfree_skb in order to bring in the cache line that skb_release_data() will eventually need (based on the bnx2 patch proposed by Eric Dumazet)
Impact: None
2. Request: (CQ33228) Add required IOCTLs to support PHY FW upgrade
Change: Add 3 magic numbers to the ethtool -E (eeprom) command to support PHY FW upgrade init, PHY FW upgrade complete, and PHY re-init after upgrade Add CL45 MDIO IOCTL support
Impact: None
3. Request: Add support for BCM8481 SPI-ROM upgrade
Change: As requested
Impact: None
Version 1.50.3 (May 14, 2009) =============================
Fixes ----- 1. Problem: (CQ40848,CQ40835) System breaks due to a firmware assert
Cause: Firmware asserted when PCI read latency for RX BD ring was longer then 20usec
Change: FW fix in version 5.0.12: Replace the workaround by a flow which polls on the RX BD ring every 4usec
Impact: None
2. Problem: (CQ36705) Performance on 57711/57711E is lower when flow control is enabled than when flow control is disabled
Cause: L2 firmware flow control was enabled for 57711/57711E and caused performance decrease
Change: Disable L2 firmware flow control by default (add new module parameter to enable it)
Impact: None
3. Problem: Workqueue might not be freed if driver fail to register
Cause: Workqueue is not freed if driver fail to register
Change: Free workqueue when driver fail to register
Impact: None
4. Problem: Negative number of received packages might be returned in STOP_ON_ERROR debug mode
Cause: Negative errno is returned in STOP_ON_ERROR debug mode
Change: Do not return negative number of received packages
Impact: None
5. Problem: Fan failure on BCM8727 was not supported on port 1
Cause: The fan failure assertion was tied only to port 0
Change: The fan failure assertion is tied to port 1 also
Impact: None
6. Problem: BCM8727 shows link up while RX is disabled
Cause: When module-compliance enforcement is enabled, and non-compliant module is detected, then the driver disables the TX-Laser for the phy, yet the link keeps showing link up.
Change: When link is changing, in case the TX-laser is off, indicate that the link is down although the phy detects RX link up.
Impact: None
7. Problem: (CQ41000) Could miss link up event in BCM8727 right after optic module insertion
Cause: At the time that SFP+ module plugged-in was triggered, driver enabled the module while ignoring link change
Change: Check for link changes during module plugged in/out
Impact: None
8. Problem: BCM8727 doesn't link in 10G after changing from 1G
Cause: 10G default configuration was overwritten after setting 1G configuration. Since the phy is not reset, the configuration for 10G doesn't go back to default after link speed change
Change: When setting 10G, enforce 10G configuration, and not relay on the default configuration.
Cause: BCM57710 was unable to receive multicast packets. This BUG was introduced with transition to the new Rx HSI. It's unlikely that this failure is SuSE 11 specific
Change: Fix BCM57710 specific multicast configuration code
Impact: None
Enhancements ------------ 1. Request: Add dropless_fc module parameter to send pause frames in case where one of the host buffers (when in RSS mode) are exhausted
Change: As requested
Impact: None
Version 1.50.2 (May 05, 2009) =============================
Fixes ----- 1. Problem: (CQ40300) XFP adapter shows link up in network properties with no cable
Cause: Link status register was updated long after interrupt was triggered
Change: Check that RX PMD Loss of Sync bit is cleared and RX PMD Sync Acquired bit is set to detect link
Impact: None
2. Problem: When Over-Current state is established, LASI interrupts are not cleared
Cause: In this scenario, the module is powered-off so OPTXFLT/OPRXLOS indications are set. This cause a fixed RX_ALARM indication which cannot be turned off
Change: When Over-current condition is detected, set RX_ALARM to detect only module-absent events, so when a new module is plugged in, it will be detected and then RX_ALARM will be set to detect link as well
Change: From now on bnx2x_main.c doesn't include huge X_init_values.h files. Instead X_init_values.h were transformed to X_init_values.c, which also include internal pointers initialization function for the appropriate chip revision
Impact: None
3. Request: Add additional support for BCM8727
Change: Add support module detection, over-current detection and SFP+ EEPROM access
Impact: None
4. Request: Add fan-failure check for BCM8727
Change: As requested
Impact: None
Version 1.50.1 (April 27, 2009) ===============================
Fixes ----- 1. Problem: (CQ39681) Dtape test fails on Dell TL2000 media changer device
Cause: Misalignment between driver and firmware
Change: FW fix in version 5.0.8
Impact: None
2. Problem: When several protocols work together, interrupt rate is the sum of all protocol rates, instead of the maximum between them
Cause: State machines in host coalescing code were independent and generated interrupts on their will
Change: FW fix in version 5.0.8: Add dependency between the states machine - when an interrupt is generated then all state machines of this status block are handled as expired, resulting with lower interrupt rate
Impact: None
3. Problem: Bootcode unable to set phy configuration
Cause: When driver is loaded, it sets Serdes to work in CL45 while the bootcode is using CL22 for phy access, so when driver is unloaded, bootcode unable to access the phy.
Change: When driver is loaded set Serdes mode to CL22 only when 1G-switch is set. This shall solve the issue for older bootcodes, and will be fixed in newer bootcodes
Impact: None
4. Problem: BCM8481 is not able to link up in legacy speeds
Change: Removed taking tx_lock in Tx interrupt flow. This also voided a need for tx_xon_tasklet - Tx is moved to XON state directly from bnx2x_tx_int
Impact: None
2. Request: Add support for new BMAC HW block for new chip types
Change: When accessing the new BMAC, use the new registers. No need to initialize the PBF HW block credits since flow-control is always enable in that block.
Impact: None
3. Request: Enable support for other chips in more general way.
Change: Split init values and FW into 2 different files. Work against pointers in bnx2x struct instead of global arrays.
Impact: None
4. Request: Add initial support for BCM8727
Change: Add support for the new dual-port SFP+ phy
Impact: None
5. Request: In BigMac2, when PFC enabled, pass pause frames towards the NIG
Change: Set the appropriate bit in the bigmac control register
Impact: None
6. Request: Improve Rx packet rate
Change: FW 5.0.8
Impact: None
Version 1.50.0 (April 02, 2009) ===============================
Fixes ----- 1. Problem: Rx was getting stuck on ia64 platform when system page size was configured to be 64KB on the kernels 2.6.27 and later
Cause: The implementation on PAGE_ALIGN macro has been changed, which caused downcast in some places in the code and as a result improper HW configuration
Change: Add a proper casting for the argument of SGE_PAGE_ALIGN macro
Impact: None
2. Problem: (CQ39552) Link LED is turned OFF while running external loopback test
Cause: When using phy loopback, the link doesn't actually comes up since there's no link partner
Change: Set link led up on loopback test
3. Problem: BCM8481 is not able to link up in 10/100/1000 Mbps
Cause: No 10/100/1000 link signal is connected from the BCM8481 to the Everest
Change: BCM8481 will connect LED4 signal to the Everest LASI signal. The Everest will use the NIG latching mechanism which allows to catch a link event even if the link toggles fast
4. Problem: SFP+ (BCM8726) boards do not use flow-control
Cause: Flow control wasn't set for BCM8726
Change: Set flow control according to configuration in BCM8726
Impact: None
5. Problem: Flow-control in MF mode should behave like in SF mode
Cause: Old restriction which is not necessary
Change: Remove special flow-control configuration in MF mode
Impact: None
6. Problem: CNIC sanity tests fails
Cause: When changing to new dynamic HC code, no RAM line was allocated to default SB so there was a memory corruption
Change: FW fix in version 5.0.3: Add RAM line for default SB to dynamic HC array
Impact: None
7. Problem: (CQ39503) Transmission stops for 5 second
Cause: Confusion in scaling of the receive window of the remote. Sometimes it is taken "as is" as a number of bytes, without scaling
Change: FW fix in version 5.0.3: Scaling added in 3 places in the code
Impact: None
8. Problem: Low performance on Tx side in UDP test with small packets
Change: HC coalescing has been moved from USTORM to CSTORM. TSTORM performance has been improved. FW 5.0.3
Impact: None
2. Request: Add support for DCC
Change: As requested
Impact: None
3. Request: Improve performance
Change: Connect Tx and Rx to different interrupt vectors
Impact: None
4. Request: Add module parameter controlling number of Rx and Tx queues
Change: As requested. Number of Tx queues must be not more than number of Rx queues
Impact: None
5. Request: Add "per function" statistics support for NCSI management
Change: As requested
Impact: None
Version 1.48.106 (Mar 04, 2009) ===============================
Fixes ----- 1. Problem: (CQ38925) Unload/Load with netperf TCP traffic test eventually caused a SETUP ramrod failure
Cause: ISR discarded a SP interrupt due to weak synchronization of atomic variable that disables interrupt handling (intr_sem)
Change: Add write memory barriers where intr_sem is updated
Impact: None
2. Problem: Possible problem in pram initialization
Cause: There was a bug in init code generation script
Change: Fix the pram initialization
Impact: None
Version 1.48.105 (Mar 02, 2009) =============================== -- Upstream Version -- Fixes ----- 1. Problem: Unload/Load test under traffic caused kernel panic in skb allocation/freeing functions
Cause: Previously added patch (enhancement 6 in release 1.48.100) broke proper usage of net_device object
Change: Remove the mentioned patch
Impact: None
Version 1.48.104 (Mar 01, 2009) ===============================
Fixes ----- 1. Problem: New phy version (P14) of the BCM8726 unable to link up
Cause: The new phy version doesn't behave exactly like its previous version (P13), hence requires some adjustments
Change: 1. Microcode download requires write of another register 2. Read from "Limiting/LRM mode" register before setting Limiting mode
Cause: Tx wasn't properly disabled in the 'close' flow
Change: Properly disable Tx during 'close' flow
Impact: None
Enhancements ------------ 1. Request: Use DMAE to zero the FW internal memory before loading the FW
Change: As Requested
Impact: None
2. Request: Remove "budgeting" in bnx2x_tx_int
Change: As Requested
Impact: None
3. Request: By default, multi_mode is disabled for old NAPI kernels (up to 2.6.24)
Change: As Requested
Impact: None
Version 1.48.102 (Feb 12, 2009) =============================== -- Upstream Version -- Fixes ----- 1. Problem: FW stats counters might not be updated when running heavy stress test
Cause: Sending FW stats ramrod query depends on stats_pending flag. This flag might not be cleared by sp_task() under heavy stress. Thus, next FW stats ramrod query will not be send
Change: Clear stats_pending flag at the end of storm_stats_update()
Impact: None
Version 1.48.101 (Feb 09, 2009) ===============================
Fixes ----- 1. Problem: Compilation is broken on kernels >= 2.6.24
Cause: FW constant rename was not updated in latest drop
Change: Fix constant name
Impact: None
Version 1.48.100 (Feb 09, 2009) ===============================
Fixes ----- 1. Problem: "ext_phy_fw version" command for BCM8706 sometimes shows invalid version number
Cause: The version number is read during init phase. Reading the BCM8706 version during init phase is done premature
Change: During init phase of the BCM8706, wait until the firmware is loaded completely before reading the version number
Impact: None
2. Problem: When setting pre-emphasis values for external phys, the XGXS is also set
Cause: In external-phy boards, when pre-emphasis values were set in the nvram, both the external phy and the XGXS pre-emphasis values were set, while the values fit the external phy only
Change: Set pre-emphasis values in XGXS only for direct type boards
Impact: None
3. Problem: (CQ37809) loopback test failure
Cause: The link was initialized for real work mode and then re-init to loopback mode. During that time, incoming packets might be queued in the rx ring in front of the loopback packet
Change: Always initialize the link to loopback mode if load_mode is LOAD_DIAG
Impact: None
4. Problem: Possible false error in the idle check section of the self test regarding the CFC_REG_ACTIVITY_COUNTER register
Cause: The test was designed to check halted system (after fatal error) and thus assumed that the chip is idle
Change: Change the test to "info" debug print
Impact: None
5. Problem: (CQ39439) mf_cfg function disabled error message displayed
Cause: Putting the driver into disabled mode was considered an error
Change: Change the printed message from error to a notification
Impact: None
6. Problem: (CQ38925, CQ37645) ifconfig ethX down up may cause a wrong MSI configuration, which will prevent MSI interrupts to arrive
Cause: Chip reset function cleared "MSI reconfigure enable" bit
Change: Don't clear the "MSI reconfigure enable" bit
Impact: None
7. Problem: Uninitialized HW blocks
Cause: XCM and BRB1 port init part were missing
Change: Add XCM and BRB1 port init part
Impact: None
8. Problem: Constant pause is sent to the network if pause is enabled and TPA is disabled
Cause: Wrong thresholds were configured
Change: Set the thresholds to 0 if TPA is disabled
Impact: None
9. Problem: Unloading UNDI by the driver in E1HMF mode might disable interrupts of the wrong function
Cause: HC regs are splited by 4
Change: Pritend to write as function 0 when writing to HC regs
Impact: None
10. Problem: BCM8726 MDIO access is not locked as it should be
Cause: MDC/MDIO access to BCM8726 is done via single EMAC, hence all MDC/MDIO access to this phy needs to be locked, like BCM8072 and BCM8073
Change: Lock the hardware using MDIO_RESOURCE when accessing the BCM8726 phy via MDIO
Impact: None
Enhancements ------------ 1. Request: Set default WoL state according to nvram settings
Change: As Requested
Impact: None
2. Request: WRR between different COS queues at TX side
Change: Added in driver and in FW 4.8.53
Impact: None
3. Request: Add ability to change BCM8726 TX PreEmphasis using nvram configuration
Change: When nvram config "Override pre-emphasis configuration" (75) is set, use Tx pre-emphasis nvram configuration (47), lane0 value to set the Main Tap and lane1 to enable TX-PreEmphasis in BCM8726
Impact: None
4. Request: Add basic support for BCM8481
Change: As Requested
Impact: None
5. Request: Limit Tx queue number to one for kernels 2.6.24 - 2.6.26 (non-TSS kernels with new NAPI)
Change: As Requested
Impact: None
6. Request: Add RSS support for old NAPI kernels (up to 2.6.24) that support MSI-X
Change: As Requested
Impact: multi_mode = 1 is now the default for all kernels
Version 1.48.51 (Jan 26, 2009) ==============================
Fixes ----- 1. Problem: Load balancing didn't work
Cause: Driver assumed that there was Tx work as long as driver packets producer and consumer were not equal
Change: Changed driver's Tx work amount evaluation logic
Impact: None
Version 1.48.50 (Jan 22, 2009) ==============================
Fixes ----- 1. Problem: (CQ38862) modprobe fails to load driver on SuSE 11
Cause: SuSE 11 does not allow 3rd party modules to be loaded without toggling a flag in /etc/modprobe.d/unsupported-modules
Change: Toggle the bit during make install
Impact: None
2. Problem: Accessing nvram while the driver is down caused PCI error
Cause: The driver attempted to access the nvram while the device was in D3 since it was disabled
Change: Prevent nvram access when the device is down
Impact: None
3. Problem: FW assert while running multi_mode=2 with tx MULTI_QUEUE enabled
Cause: start_xmit() selected different tx queue than the tx_lock was taken
Change: Implement dev->select_queue() callback so start_xmit() selects the correct tx queue
Impact: None
4. Problem: Compilation problem with kernel 2.6.29
Cause: netif_rx_schedule and netif_rx_complete do not require the device parameter anymore
Change: Do not pass the device paramter for those functions for kernels above 2.6.29
Impact: None
5. Problem: Invalid presentation of BCM8726 fw version
Cause: The register that holds the fw version is used for other functionality as well, and it is run over after firmware is loaded
Change: Save the firmware version of all external phys in shared memory, after firmware is loaded
Impact: None
6. Problem: BCM8726 may start tx laser before module detection occurs
Cause: Module detection used to be done during link update, which probably would be after tx was enabled
Change: From now on use interrupt driven event using GPIO3, to detect module plugged in/out, and execute module detection then
Impact: None
7. Problem: 1G switch configuration (using the 5th lane) doesn't work
Cause: Support for Serdes (5th lane) was not maintained since no production design used it and when switching to CL45 it stopped working
Change: In order for control the Serdes over Clause45, (and not Clause22), it requires first one time register setting in Clause22
Impact: None
8. Problem: Softlock during remove_one()
Cause: NAPI context was not released before unloading
Change: Release NAPI context before unloading
Impact: None
9. Problem: False self-test failures due to MC_ASSERT
Cause: iSCSI FW sometimes report run-time warnings which are acceptable and do not cause any harm
Change: Do not check for MC_ASSERT. A real FW error will cause the interrupt test to fail
Impact: None
10. Problem: Possible miss of FW response on unload
Cause: Missing memory barrier while waiting for FW response
Change: Add read memory barrier
Impact: None
11. Problem: (CQ37809) loopback test failure
Cause: A link change interrupt might be queued and activated after the loopback was set
Change: Lock all PHY activities while running loopback test
Impact: None
12. Problem: (CQ39057) Everest, 57710 Error message: bnx2x_start_xmit: BUG Tx ring full when queue awake
Cause: In kernels 2.6.24 - 2.6.26 (non-TSS kernels with new NAPI) there can be a possibility that NAPI instance (fp instance) other than the one moved Tx to XOFF state will wake the Tx So, this is highly possible that start_xmit is called while the ring is still full In any other kernel this state is an obvious bug
Change: Remove an error message in the code for the mentioned kernels
Impact: None
Enhancements ------------ 1. Request: Use FW 4.8.50
Change: As Requested
Impact: None
2. Request: BCM8726 should be able to link up at 1G
Change: Add support for 1G for BCM8726
Impact: When requested speed is 1G force, it will try to link in 1G force. When the speed requested is autoneg, and the speed mask capabilities contain 1G, it will try to autoneg in 1G as well as in 10G
3. Request: (CQ39048) Add ability to change 8706 XAUI RX Equalizer using nvram configuration
Change: When nvram config "Override pre-emphasis configuration" (75) is set, use the 3LSB bits of RX_equalizer nvram configuration (48) to set the BCM8706 XAUI RX Equalizer registers for each lane
Impact: None
4. Request: Verify external phy image before ROM upgrade
Change: New headers will be added to the images of external phys to be upgraded. Currently this list includes BCM8073, BCM8726 and SFX7101. The headers will be checked against fixed magic number and specific phy type
Impact: From now on, external phy images MUST include image header
Version 1.48.11 (Jan 13, 2009) ==============================
Fixes ----- 1. Problem: Possible memory overrun on platforms with page size more than 8K
Cause: "linearization" should take into an account system page size and run or not run accordingly
Change: Fixed the compilation condition
Impact: None
2. Problem: Compilation problem with kernel 2.6.28
Cause: struct net_device_ops was postponed to next release
Change: Remove struct net_device_ops from compilation
Impact: None
Enhancements ------------ 1. Request: Limit multi_mode to support only regular mode
Change: As requested
Impact: None
Version 1.48.10 (Jan 07, 2009) ==============================
Fixes ----- 1. Problem: (CQ39129) driver assert while logging out during iSCSI max sessions test
Cause: QM initialization was wrong
Change: Fix QM initialization
Impact: None
Version 1.48.9 (Jan 05, 2009) =============================
Fixes -----
1. Problem: (CQ38909) on IA-64 with TPA enabled, kernel memory was sometimes smeared (depending on the MTU size)
Cause: The max TPA fragments assumed 4KB pages and that system had 16KB pages
Change: Fix the SGE (TPA fragment) size to be system page size
Impact: Improved performance on systems with page size > 4KB like PPC and IA-64
Version 1.48.8 (Dec 31, 2008) =============================
Fixes -----
1. Problem: (CQ38992) on IA-64 Driver crash when transmitting on all 8 functions in chariot IPv6 with tx checksum disabled scenario
Cause: FW read the buffer descriptor (BD) producer and after that the BD itself before the BD content was updated. This is possible on IA-64 due to weak ordered memory module
Change: Add write barrier after updating the BD data and before updating the BD producer
Impact: None
Version 1.48.7 (Dec 30, 2008) =============================
Fixes -----
1. Problem: (CQ38985) Port swap is not working for BCM8726
Cause: BCM8726 is driven by MDC/MDIO through single EMAC. In case of port swap, the EMAC access was left with EMAC0
Change: In case port-swap is enabled in the NIG, access MDC/MDIO via EMAC1
Impact: None
2. Problem: BCM8726 was not reset when driver was unloaded
Cause: This phy hardware reset affects both ports and thus wasn't used
Change: When link needs to be reset, reboot the micro-controller of the BCM8726
Impact: None
3. Problem: BCM8726 was not reset during init
Cause: This phy is connected using static port-swap, hence the reset should have been triggered through the opposite port from the spec
Change: Set gpio1 during common init from port1 instead of port0
Impact: None
4. Problem: (CQ38991) In E1HMF mode some interfaces occasionally misreport link speed
Cause: Races between interfaces during init cause an interrupt event to be ignored
Change: Flag the device as "ready for interrupts" prior to enabling the interrupts
Impact: None
5. Problem: (CQ39057) Everest, 57710 Error message : bnx2x_start_xmit: BUG Tx ring full when queue awake.
Cause: Tx BD producer update may not be "seen" by bnx2x_tx_int function running on different CPU, thereby bnx2x_tx_int may erroneously conclude that it may wake Tx.
Change: Add smp_mb() after update of Tx producer before putting Tx to XOFF state.
Impact: None
6. Problem: In E1HMF mode with multi queue, functions 2..7 cannot receive data
Cause: Incorrect initialization of indirection table
Change: Initialize correctly the indirection table
Impact: None
7. Problem: The driver debug crash dump does not handle cyclic rings correctly
Cause: The debug prints were simply from start to end and did not print anything in case start < end (cyclic rings)
Change: Enhance the debug prints with cyclic logic
Impact: None
8. Problem: Packets dropped due to lack of host buffers were counted twice - in good and bad statistics
Cause: Firmware does not maintain separate counters for unicast/broadcast/multicast drops, therefore driver cannot subtract these values from the good packet/byte counters
Change: Fixed in FW 4.8.9
Impact: None
9. Problem: iSCSI FW: High non-paged host memory consumption
Cause: Unnecessary optimization of chipset<->memory bandwidth in expense of memory consumption
Change: Fixed in FW 4.8.9
Impact: None
Version 1.48.6 (Dec 18, 2008) =============================
Fixes ----- 1. Problem: System hangs when running ifconfig on an 8 CPUs system
Cause: A loop variable was used again in an inner loop. That caused an endless loop
Change: Use another variable for the inner loop
Impact: None
2. Problem: Some stats names are not displayed but their values were displayed in other stats
Cause: Incorrect condition caused to skip stats names but not their values
Change: Correct the condition
Impact: None
3. Problem: iSCSI FW: During connection establishment on-chip (option2), in case we receive SYN/ACK with incorrect dst_mac the chip gets stuck
Cause: This scenario led to accessing invalid PRAM address which made the chip halt
Change: Fixed in FW 4.8.8
Impact: None
4. Problem: NAPI poll mode was stopped (netif_rx_complete called) and HW interrupts reenabled even if the whole device quota had been consumed.
Cause: There was a bug in NAPI poll-mode canceling logic.
Change: Fix the logic in NAPI poll method.
Impact: None
Version 1.48.5 (Dec 11, 2008) =============================
Fixes ----- 1. Problem: TCP packets with VLAN weren't handled properly, when received in non-accelerated VLAN traffic mode (when VLAN tag is not stripped by the FW)
Cause: Driver didn't support receiving VLAN packets in non-accelerated mode. for TPA packets, there was a wrong IP header offset calculation and, as a result, writing IP checksum to the wrong offset. Non-TPA packets weren't handled right as well: driver always used vlan_hwaccel_receive_skb to pass an skb with VLAN to the stack, while it should use netif_receive_skb in non-accelerated case
Change: Fixed IP header offset calculation for TPA packets. Fixed VLAN skb handling logic.
Impact: None
2. Problem: (CQ38698, CQ37931) No link when using direct attached copper cable with BRCM8726 PHY
Cause: Passive copper cables should always operate in LRM mode rather than in Limiting mode
Change: In case of passive copper cables, link up in LRM mode
Impact: None
3. Problem: (CQ38815) iSCSI failure during hotplug
Cause: Not everything is setup before calling register_netdev(). pci_set_drvdata() and bnx2x_init_bp() were called after register_netdev(). This potentially can also affect L2 because bnx2x_open() can potentially be called before those 2 calls have successfully completed
Change: Call register_netdev only at the end of successful setup
Impact: None
4. Problem: (CQ38862) modprobe fails to load driver on SUSE11
Cause: SuSE does not allow 3rd party modules to be loaded without toggling a flag in /etc/modprobe.d/unsupported-modules
Change: Toggle the bit through the packaging script
Impact: None
5. Problem: iSCSI FW: In non-aligned PDUs with data-digest enabled, the data-digest is calculated to a wrong value
Cause: The CRC machine was not reset correctly in non-aligned PDUs
Change: Fixed in FW 4.8.6
Impact: None
6. Problem: iSCSI FW: Connection wasn't initialized with the right parameters for the TX in E1HMF mode
Cause: Initialization was done using SF mode
Change: Fixed in FW 4.8.6
Impact: None
7. Problem: (CQ38886, CQ38888) iSCSI FW: Double-vlan was not supported for iSCSI. The packet was transmitted with bogus IP length and no inner-vlan
Cause: The vlan flag and the header builder command size weren't set correctly
Change: Fixed in FW 4.8.6
Impact: None
8. Problem: Byte counters statistics did not count the 4 FCS bytes
Cause: The FCS bytes were not counted
Change: Fixed in FW 4.8.7
Impact: None
Enhancements ------------ 1. Request: SFP+ optical module (MSA) vendor verification should be optional when using BCM8726 PHY
Change: Verify the optical module vendor according to nvram configuration option #81: "Optic Module Vendor Enforcement"
Impact: The new nvram bit is visible using ediag version 4.8.3 or later
2. Request: In multi queue mode, separate FW stats per queue
Change: As requested
Impact: None
3. Request: Change some stats names: pause_frames_received is now rx_pause_frames pause_frames_sent is now tx_pause_frames timer_max_events is now rx_constant_pause_events
Change: As requested
Impact: None
4. Request: Align with RMON MIB (rfc 1757): net_device_stats.rx_bytes is total_bytes_received net_device_stats.multicast is total_multicast_packets_received
Change: As requested
Impact: None
5. Request: Use static singlethread_workqueue shared for all bnx2x interfaces
Change: As requested
Impact: None
Version 1.48.4 (Nov 26, 2008) =============================
Fixes ----- 1. Problem: CNIC driver is failing on higher functions of 57711E
Cause: The status block ID for the CNIC was not assigned correctly for higher functions
Change: Assign the status block ID according to the function ID
Impact: None
Version 1.48.3 (Nov 20, 2008) =============================
Fixes ----- 1. Problem: Intermittent MDC/MDIO failures on 8726 PHY
Cause: MDIO register access is sometimes broken since PHY is not hard reset
Change: Pull GPIO1 low for 1 ms after power-on. Note that the hard reset is a shared resource on the PHY
Impact: None
2. Problem: gso_type indication was not set for TPA packets
Cause: gso_type wasn not set
Change: Set gso_type accordingly
Impact: None
3. Problem: Possible false parity indication
Cause: When using 5 tuple hash (not used today) the searcher might falsely indicate parity error
Change: Mask bit 6 of the searcher parity errors
Impact: None
4. Problem: (CQ37809) Intermittent failures in ethtool diagnostic (CQ36771) Calltrace and interface locks up when up/down interface
Cause: If sp_task() is queued in the shared work queue after the linkwatch, it will be starved and will not update the link status until ethtool diagnostic ends and frees rtnl that linkwatch is waiting for
Cause: Inefficient implementation of ring management in firmware
Change: Fixed in FW 4.8.4
Impact: None
6. Problem: (CQ38424) SAFC iperf drop result is 5 times higher than previous build
Cause: Mis-configuration of the SAFC timeout
Change: The new SAFC timeout will be 200usec
Impact: None
Version 1.48.2 (Nov 10, 2008) =============================
Fixes ----- 1. Problem: SAFC packets were not generated periodically by NIG
Cause: A HW architecture bug
Change: Fixed in FW 4.8.3
Impact: None
Enhancements ------------ 1. Request: Support iSCSI MAC and VLAN per function in 57711E
Change: Added in FW 4.8.3
Impact: None
Version 1.48.1 (Nov 06, 2008) =============================
Fixes ----- 1. Problem: Possible race between init_one() and open() with calling to netif_carrier_off()
Cause: After register_netdev(), open() can be called at any time and the interrupt handler can be called after that. If you get a link change interrupt, the netif_carrier_* call from IRQ or NAPI poll can race with netif_carrier_off() call in probe.
Change: Move netif_carrier_off() to open()
Impact: None
2. Problem: Possible access to illegal addresses inside the chip during self test
Cause: Loop size was given in bytes and not in number of entries
Change: Fix the loop size
Impact: None
Enhancements ------------ 1. Request: Fewer dropped packets when flow control is enabled on 57711/57711E
Change: As requested
Impact: None
Version 1.48.0 (Nov 03, 2008) =============================
Fixes ----- 1. Problem: Failures on RH5 when using enabling and disabling the functions one by one on 57711E
Cause: Unloaded driver tries to access the PHY to get its FW version since RH calls "ethtool -i" periodically
Change: Clear the PMF indication when the driver is unloaded
Impact: The PHY FW is inaccessible when the driver is unloaded
2. Problem: Searcher block initialization for 57711E is wrong
Cause: The searcher registers are split (same address for all functions)
Change: Use the port offset and not the function offset
Impact: None
3. Problem: Kernel panic when failing to load the driver
Cause: netif_carrier_off was called before making sure that the driver can be loaded
Change: Call netif_carrier_off as last action in the probe
Impact: None
Enhancements ------------ 1. Request: Add iSCSI for 57711E
Change: FW 4.8.2 supports iSCSI for 57711E
Impact: None
2. Request: Add transmit multi queue support
Change: As requested
Impact: This fetaure is available on 2.6.27 kernel when using MSI-X
Version 1.46.12 (Oct 29, 2008) ==============================
Fixes ----- 1. Problem: (CQ37832) System crash when running TCP connections on 57711
Cause: Access to unsupported address in FW PRAM due to increased FW size
Change: Fixed in FW 4.6.21: Moved all operational FW code to legal PRAM addresses
Impact: None
2. Problem: After some cases of driver failure, driver cannot be re-loaded
Cause: The driver took the HW out of reset without making sure that it was indeed in reset state
Change: Reset the HW before taking it out of reset
Impact: None
3. Problem: (CQ37893) Driver failure when installed on RHEL4.5 from PXE Server
Cause: MSI-X fails due to memory allocation failure and though MSI registration succeeded interrupts are not received in MSI mode
Change: Use INTx mode when MSI-X fails due to memory allocation failure
Impact: None
Enhancements ------------ 1. Request: Add debug module parameter to force MRRS value
Change: As requested
Impact: None
Version 1.46.11 (Oct 23, 2008) ==============================
Fixes ----- 1. Problem: (CQ37915) On 57710, if self-test is run on port 1, port 0 stops transmitting/receiving traffic unless in promiscuous mode
Cause: Primary MAC address of port 0 is lost after the self-test on port 1
Change: Changed self-test to fix the problem
Impact: None
2. Problem: (CQ37087) iSCSI FW: Data digest error event found in event viewer
Cause: Wrong UPB command in non-aligned data that is adjacent to iSCSI header in the TCP segment from the target
Change: Fixed in FW 4.6.17
Impact: None
3. Problem: (CQ38061) iSCSI FW: Invalid iSCSI PDU seen while running OEM diagnostic to Equallogic target
Cause: Misinterpretation of the 3720 RFC regarding data-in sequences definition
Change: Fixed in FW 4.6.17
Impact: None
4. Problem: (CQ37861) iSCSI FW: BSOD occurred while running iLab's TOE automated tests and iSCSI traffic
Cause: Failed to identify task cleanup during processing of a data-in PDU that belong to the same task
6. Problem: Possible false warning (not a failure) in the idle check section of the self test regarding the BRB1_PRTY_STS register
Cause: The condition was not masked properly
Change: Fixed the condition check for that register
Impact: None
Enhancements ------------ 1. Request: Add support for BCM8726 (Dual port phy SFP+ ) including MSA module recognition and verification
Change: As Requested
Impact: None
Version 1.46.5 (Sep 17, 2008) =============================
Fixes ----- 1. Problem: (CQ36478) MSI fails on Big-Endian systems
Cause: The IGU was configured to swap the data over the PCI
Change: Config IGU not to swap the data and add swap in the driver where it is necessary
Impact: None
2. Problem: (CQ37309) Can not compile on some old kernels
Cause: Call to pci_disable_msi() was not under appropriate #ifdef
Change: Add the appropriate #ifdef
Impact: None
3. Problem: Self test sometimes indicates on a failure
Cause: A test result was declared as an error instead of a warning
Change: Declare the test result as a warning
Impact: None
Version 1.46.4 (Sep 16, 2008) =============================
Enhancements ------------ 1. Request: CNIC enabled in default compilation
Change: As Requested
Impact: None
Version 1.46.3 (Sep 11, 2008) =============================
Fixes ----- 1. Problem: (CQ34165) High number of pause frames
Cause: The thresholds in the receive buffer needed some tuning
Change: Tuned the thresholds in the receive buffer
Impact: None
2. Problem: (CQ36559, CQ36989) System crash when working on PPC with 64KB page
Cause: The allocated buffer was bigger than the PCI mapped buffer, and in the 64KB configuration the buffer is aligned only to 128 bytes and so the packet can overstep the PCI mapped area and cause a fatal error
Change: Map the same size as the allocated buffer size
Impact: None
3. Problem: (CQ36479) EEH recovery causes system crash
Cause: When EEH detects an i/o error it resets the device thus it cannot be accessed. In this case the driver needs to unload its interface only with OS, kernel and network stack but not with the device.
Change: Add a special unload function for EEH recovery that does not access the device
Impact: None
4. Problem: Option2 RST did not complete
Cause: Missing context initialization in FW
Change: Fixed in FW 4.6.10
Impact: None
5. Problem: (CQ37090) Placement of RQ data to wrong address
Cause: ASM problem
Change: Fixed in FW 4.6.10
Impact: None
6. Problem: (CQ36912) BSOD when destroying erroneous connections
Cause: Activity count leak
Change: Fixed in FW 4.6.10
Impact: None
7. Problem: (CQ 36987) Unable to perform media changer/tape functions
2. Request: Add stats counter for NIG timer max events
Change: As Requested
Impact: None
3. Request: Enable timer scan for CNIC
Change: As Requested
Impact: None
4. Request: Add support for using MSI interrupt mode
Change: As Requested
Impact: None
5. Request: (CQ36758) Firmware now enforces iSCSI licensing and fails the offload if no iSCSI initiator license exists
Change: Added in FW 4.6.10
Impact: None
Version 1.46.2 (Aug 25, 2008) =============================
Fixes ----- 1. Problem: (CQ36510, CQ36583) Link LED does not turn off when 1G link is lost when external PHY is present
Cause: The current code manually turned off the 10G LED but did not handle other speeds which are controlled by HW. Since the HW detect link with the external PHY, the link LED stayed on
Change: Turn off the LED for all speeds manually when link goes down
Impact: None
2. Problem: Packets with bad TCP/UDP checksum error are dropped
Cause: Actively dropping packets with bad TCP/UDP checksum in the driver
Change: Do not drop packets with bad TCP/UDP checksum - let the stack decide what to do with them
Impact: None
3. Problem: Some packets are dropped without showing on any statistics counter
Cause: The driver assumed that packets which were identified as bad are counted by the FW, but the FW does not count those when configured to pass them
Change: Add counters in the driver
Impact: None
4. Problem: (CQ36153) Flow control doesn't work against non KR switches
Cause: Missing support for clause-37 auto negotiation
Change: Add support for clause-37 auto negotiation
Impact: 0.5 seconds delay during autoneg
5. Problem: Link dangling during init
Cause: no delay after initial link change interrupt
Change: Add 30ms before allowing link update indications
Impact: Additional 30ms during init phase
6. Problem: Unable to load driver after iSCSI boot under incoming traffic
Causes: The reset function after iSCSI boot did not handle closing incoming traffic
Change: Close the port to prevent Rx traffic and clear all buffers
Impact: None
7. Problem: (CQ36408) Failed driver disk installation with SuSE10 and RH4
Cause: The CRC module is not part of the Kernel in those distributions
Change: Special driver disk compilation mode to include the CRC routine in the driver though it is an external module in normal installation with those distributions
Impact: The driver in the driver disk is less efficient due to the CRC algorithmic implementation and not static tables as in the CRC module which is used when loading the driver normally under SuSE10 and RH4
8. Problem: (CQ34921) Possible memory leak
Cause: rx_page_ring was not freed
Change: free rx_page_ring
Impact: None
9. Problem: (CQ36242) brb_truncate statistics increments to very high numbers
Cause: brb_truncate_discard is a 4 bytes variable but 8 bytes were copied to ethtool
Change: use brb_truncate from NIG and extend it to 8 bytes
Impact: None
10. Problem: Tx Pause were not send on 1G link
Cause: Missing initialization to the EMAC TX_MODE
Change: Set FLOW_EN bit in the TX_MODE in addition to the EXT_PAUSE_EN
Impact: None
11. Problem: (CQ36361) Changing speed to 1G on KR switch side results in no link in OS
Cause: When Serdes is configured to 1G, it should remove setting MDIO_SERDES_DIGITAL_MISC1_FORCE_SPEED_SEL bit in MDIO_REG_BANK_SERDES_DIGITAL
Change: Unset MDIO_SERDES_DIGITAL_MISC1_FORCE_SPEED_SEL bit for every link change
Impact: None
12. Problem: Possible loss of attentions
Cause: Attention mask register was manipulated without a proper lock
Change: Protect attention mask register using hw lock, use read modify write on this register
Impact: None
13. Problem: HW lock was sometimes not taken
Cause: HW lock was not taken per function
Change: use lock control per function
Impact: None
14. Problem: (CQ36089) RX counter on all functions are incorrect
Cause: tstorm_client.statistics_counter_id was 0 for all functions
Change: set tstorm_client.statistics_counter_id to the cl_id of the function
Impact: None
15. Problem: (CQ36090) down/up of the interface during traffic on the other interface caused traffic to stop
Cause: Aggregation context must be initialized only at COMMON init block
Change: Change initialization code and init-tool output
Impact: None
16. Problem: (CQ35672) Doorbell was arriving after halt and before start ramrod
Cause: XON/XOFF flow control should be disabled in NIC close flow
Change: Fixed XON/XOFF code
Impact: None
17. Problem: (CQ34555) MSI-x PCI spec aberration
Cause: PBA table starts from the middle of a page
Change: Use GRC access instead of BAR access
Impact: None
18. Problem: Lost link indication in BCM8073.
Cause: During link establishment LASI latched signal wasn't reset and stopped link change indication
Change: Fixed flow to clean latched LASI signal
Impact: None
19. Problem: Declaring bootcode timeout too soon
Cause: The bootcode can take a while to set a link when a link is needed (for example, WoL is enabled). The driver should allow adaptive scheme to wait for the bootcode
Change: Waiting up to 2 seconds in 10ms intervals
Impact: In some cases, the driver unload process will take up to 2 seconds
20. Problem: Wrong WoL capability report
Cause: The WoL capability was read from the nvram which was not always updated
Change: Determine the WoL capability from the PCI configuration space
Impact: None
21. Problem: (CQ36644, CQ366697, CQ36928, CQ36983) On some cases with low traffic, the computer was irresponsive up to the point of soft-lockup and even hard lockup. Ping-pong latency tests always hit this problem and so get very low result
Cause: If the FW was at the end of the Rx page, the driver will already be at the beginning of the next page. In this case the condition of having the driver and the FW on the same pointer was never true and so the driver kept polling until timeout or another packet came in. On driver unload (including intermediate driver unload like in MTU change or self-test) the lockup was fatal
Change: Change the check for "now work" to handle end of page as well
Impact: None
22. Problem: (CQ36697 CQ36771) Interface locks up when up/down interface
Cause: In nic_unload(), call to netif_poll_disable() cause to set __LINK_STATE_RX_SCHED flag that is checked in dev_close() in a loop forever. This flag is cleared by netif_rx_complete() called by bnx2x_poll() which is not called if !netif_running()
Change: Reorder nic_unload() - first close interrupts, then only if netif_running() call netif_poll_disable()
Impact: None
23. Problem: (CQ36795) driver fails to load after iSCSI boot
Cause: Unloading UNDI by the driver is protected by a HW lock. With a KR (8073) interface, unloading the UNDI takes more than 1 sec. Taking the lock by another driver times out after 1 sec then the driver tries also to unload UNDI.
Change: Clear UNDI signature and release the lock. Only the driver who saw UNDI signature will continue to unload UNDI.
Impact: None
24. Problem: Allocate skbs for unused aggregation queues in 57710
Cause: Allocate skbs for 64 aggregation queues but 57710 has only 32
Change: Allocate skbs for max_agg_queues according to chip id
Impact: None
25. Problem: Wrong cleanup on exit from nic_load() in case of a failure
Cause: Upon some failure nic_load() exits without disabling and freeing the interrupts
Change: Fix to disable and free the interrupts in that case
Impact: None
26. Problem: Potential link problem when loading two ports with 8073 PHY
Cause: Initializing the 8073 PHY takes more than 1 seconds and the HW lock might expire since it is only trying for 1 second
Change: Increase the HW lock timeout to 5 seconds
Impact: None
27. Problem: XAUI link on port0 goes down and then up, when the link on port1 is changed
Cause: When master port (port1) is down, it will also cause the blade side down. In turn, PLL will change speed from 10G to 1G. It will cause XAUI clock to both ports down and then up again
Change: Set bit in the BCM8073 that enables the fix
Impact: None
28. Problem: (CQ36772) KR with 8073 PHY sometimes does not establish link
Cause: A missing delay between initializing the PHY SPI ROM and inserting the PHY back to low power mode
Change: Add 15ms delay after loading the SPI PHY ROM which is before entering low power mode
Impact: None
29. Problem: Sometimes when unloading the driver a message will appear: "sp_running (j 1)"
Cause: Wrong condition, the message should appear only if the counter (j) is greater than 1000. This is a false alarm
Change: Fix the print condition
Impact: None
30. Problem: When upgrading 8073 SPI ROM PHY to version 0103 the link will not come up
Cause: Register 0x8370 is no longer required in the new version and writing to it cause the link not to come up
Change: Remove the write to address 0x8370
Impact: None
31. Problem: On some KR boards when loading driver on port0, and port1 is not loaded, sometimes the XAUI link is not coming up
Cause: The 8073 PHY has two ports that share a single clock. This clock is routed to a port deemed to be the master (port 1), and then a PLL at the master sets the clock frequency and routes the buffered clock to both the master XAUI interface as well as the slave (port 0) XAUI interface. If port 0 is loaded while the 8073 PHY SPI ROM is not loaded, the PLL for port 0 is not guaranteed to lock
Change: First driver to be loaded reset and download SPI ROM on both ports of the 8073 PHY during one-time initialization
Impact: The 8073 PHY is only reset when both ports are brought down
32. Problem: On some KR boards when unloading driver on port1 port 0 might loose link
Cause: The 8073 PHY has two ports that share a single clock. This clock is routed to a port deemed to be the master (port 1), and then a PLL at the master sets the clock frequency and routes the buffered clock to both the master XAUI interface as well as the slave (port 0) XAUI interface. If port 1 is unloaded while port 0 is in use, the port 0 PLL might loose lock
Change: Do not reset the PHY if either driver is still up
Impact: The 8073 PHY is only reset when both ports are brought down
33. Problem: When loading driver after it was loaded before, packets are getting into the chip before the MAC addresses are configured (but not into the host)
Cause: The HW filters are not cleared when the driver is unloaded so previous driver configuration is still present
Change: Clear HW filters so no packet will come in when driver is unloaded
Impact: None
34. Problem: Driver does not pass the last version of checkpatch.pl
Cause: Some updates to the script found some coding standard violations in the code
Change: Fixed all reported errors and spelling mistakes
Impact: None
35. Problem: (CQ36492) rx_csum_offload_errors increments for any none TCP/UDP packet
Cause: Parsing CQE flags incorrectly
Change: Parse CQE flags according to CQE status bits
Impact: None
36. Problem: Packets with IP checksum error are dropped
Cause: Dropping packets with IP checksum error
Change: Pass packets with IP checksum error to the stack. Drop only packets with L2 errors
Impact: None
37. Problem: (CQ46480) The nomcp module parameter is causing kernel panic
Cause: This debug parameter was not needed and not maintained
Change: Remove this debug parameter. The driver can detect if the FW is missing and act accordingly
Impact: None
38. Problem: Per function statistics are not cleared on driver load unload
Cause: The FW statistics area was not cleared on driver load
Change: Clear FW statistics area when loading the driver
Cause: Did not apply the right mask on the HW report caused some false positives
Change: Use mask to check only the memory errors report
Impact: None
40. Problem: (CQ36497) Self-test idle_check part is failing
Cause: Did not apply the right mask on the HW report caused some false positives
Change: Use mask to check only the memory errors report
Impact: None
41. Problem: (CQ36514) Failed to load the driver after iSCSI boot on SuSE10 SP2
Cause: The built-in driver from the SuSE10 SP2 (1.42.3) was loaded after the iSCSI-boot
Change: Added update.post file to SuSE10 SP2 dd.iso
Impact: None
42. Problem: (CQ36382) Low 1G UDP performance with one connection with flow control disabled
Cause: The credits in the transmitter HW caused too much gap between UDP packets in case the flow control was disabled
Change: Use the same HW credit as if the flow-control is enabled when the line speed is 2.5G or less
Impact: None
43. Problem: (CQ35662) NVRAM pre-emphasis support does not take effect
Cause: Current nvm values didn't actually affect the phy
Change: To keep backward compatibility, only in case the "Override pre-emphasis configuration" nvm option is enables, it sets the the tx preemphasis and rx equalizer values for the 4 lanes according to the "XGXS backplane Tx pre-emphasis matrix coef." and "XGXS backplane Rx equalizer matrix coef." respectively
Impact: None
44. Problem: Prevent possible glitch due to speed change without link down in the middle
Cause: Currently the NIG goes into drain mode only after link down. If the only the speed was changed from 1G to 100Mb, for example, without link-down indication then the FIFO isn't cleaned and glitch due to clk change may occur
Change: On speed change set the NIG into drain mode
Impact: Several packets may be dropped, but it's ok, since we assume that anyhow several packets were dropped due to the link down
45. Problem: Fix EMAC initialization setting
Change: Currently it is configured inside the enable emac before configuring the EMAC mode. Changed to be after that and should be disabled (with the drain mode setting) at the entrance of the link_update function. In addition, in link down, after putting the nig into drain mode this register should also be disabled.
After configuring the mode and before opening the nig_emac#_en, reset the EMAC_REG_EMAC_RX_MODE and EMAC_REG_EMAC_TX_MODE
Impact: None
Enhancements ------------ 1. Request: Error messages might be displayed in unload
Change: Check work only on the tx fast path and call bnx2x_tx_int() to handle it. Rx work is handled during halt ramrod
Impact: None
2. Request: Indicate that there is no WoL support for functions higher than 1 (only 0 and 1 should support WoL)
Change: As Requested
Impact: None
3. Request: Pause in 57711E mode always advertise both Rx and Tx regardless of frame size
Change: As Requested
Impact: None
4. Request: Skb's marked as CHECKSUM_UNNECESSARY (TPA'ed) were passed to the net stack even if user disabled checksum offloading.
Change: Disable TPA if Rx checksum offloading is disabled.
Impact: There is no way to enabling TPA in kernels older than 2.6.26 except unloading and loading the driver
5. Request: Do not display internal FW version and enhance readability of the bootcode version
Change: As requested
Impact: None
6. Request: Optimize link setup and support 2.5G
Change: Link will be configured on the external PHY before setting up the internal PHY. When needed, only the external PHY will be configured to autoneg. The internal PHY will be set to the obtained speed
Impact: None
7. Request: Skb's marked as CHECKSUM_UNNECESSARY (TPA'ed) were passed to the net stack even if user disabled checksum offloading.
Change: Disable TPA if Rx checksum offloading is disabled.
Impact: None
8. Request: Incorporated latest firmware 4.6.7 - Add support for priority-based ETH TX queues and enable SAFC pausing per queue
Change: As requested
Impact: None
Version 1.46.1 (June 25, 2008) ==============================
Enhancements ------------ 1. Request: Use FW version 4.6.2
Change: As Requested
Impact: None
Version 1.45.6 (June 23, 2008) ==============================
Fixes ----- 1. Problem: (CQ35672, CQ35818) Changing MTU under traffic causes driver hang
Cause: A rare case of LSO packet alignment, relatively to MSS, caused a HW debug checking for end of packet to fail
Change: In computing the end of packet flag, the calculation of the total packet length was modified
Impact: None
2. Problem: Possible memory corruption on kernels with 64K page size
Cause: Inconsistency in using page macros
Change: Use only BCM page macros
Impact: None
Enhancements ------------ 1. Request: Add support for TPA (LRO) setting via ethtool
Change: As Requested
Impact: Kernels after 2.6.26 use this interface to turn off TPA when forwarding enabled due to the limitation of no forwarding (bridging) and TPA together
Version 1.45.5 (June 17, 2008) ==============================
Fixes ----- 1. Problem: (CQ35691) Undefined symbol __udivdi3 when compiled on 32-bit platforms.
Cause: There was 64-bit division
Change: Reordered the arithmetic expression in order to eliminate the 64-bit division
Impact: None.
2. Problem: (CQ35644) Tx mulicast counter does not increment
Cause: start_xmit sets the unicast flag for all packet types
Change: Remove the broadcast and mulicast counters
Impact: None
3. Problem: (CQ35836) Ethtool reports wrong speed when set via CLP
Cause: get_settings returns always the max BW set via CLP without considering the actual link speed
Change: Return the min between the max BW set via CLP and the actual link speed
Impact: None
4. Problem: (CQ35859) Ethtool -S reports many jumbo tx packets with MTU set to 1500
Cause: There is a different in tx histogram statistics between EMAC and BigMAC
Change: Use NIG stats counters instead
Impact: None
5. Problem: (CQ35114) Self test failure on some systems
Cause: pcie_rst_b test can be set and should not be categorized as ERROR
Change: Change pcie_rst_b test priority from ERROR to WARNING
Impact: None
Enhancements ------------ 1. Request: Remove non-coherent stats in 57711E
Change: As Requested
Impact: None
2. Request: Remove xSEM_REG_INT_TABLE from memory test
Change: As Requested
Impact: None
Version 1.45.4 (June 10, 2008) ==============================
Fixes ----- 1. Problem: (CQ34905) load/unload causes link detect failure
Cause: Handling of link events during load wasn't protected
Change: Add synchronization in handling of link events during driver load
Version 1.45.1 (May 26, 2008) =============================
Fixes ----- 1. Problem: (CQ34964) ethtool -a/A is broken
Cause: The autoneg define changed to value of zero and broke the code
Change: Use comparison instead of bit-wise logical and
Impact: None
2. Problem: (CQ35123) Support for 32bit Kernels is broken
Cause: The TPA code had a 64 bit address that broke the 32bits support
Change: Fixed the upper 32bits of the address to zero in 32bit Kernel
Impact: None
3. Problem: (CQ35123) Support for Big-endian is broken
Cause: The TPA and SGE code was not big-endian compliant
Change: The necessary le_to_cpu were added
Impact: None
4. Problem: Failed to work on emulation with MCP
Cause: The time interval between the pulses towards the MCP was the same for ASIC and emulation
Change: Increased the time interval between MCP pulses for emulation/FPGA
Impact: None
5. Problem: (CQ34313) Compilation error on SuSE
Cause: Broken in last drops
Change: Fix the errors
Impact: None
6. Problem: (CQ35124) Kernel panic when unloading NIC with shared INTA
Cause: The interrupts were masked when unloading, but the handler was still present. In case of shared INTA line, the handler was called after freeing the resources due to other device interrupt
Change: Free the interrupt handler when masking all interrupts on unload. Clear old interrupt before registering the IRQ on load.
Impact: None
7. Problem: Failed to re-load the driver (after unload) on the upstream kernel
Cause: The fast path structures which are used by NAPI where released on unload and re-allocated on load
Change: Use static allocation for the fast-path structures
Impact: None
Enhancements ------------ 1. Request: (CQ34895) Change Linux Driver Disk Images from Floppy to ISO Format
Change: As Requested
Impact: None
2. Request: (CQ34931, CQ34976) Replace RH4.5 binaries with RH4.6
Change: As Requested
Impact: None
3. Request: Link down indication should be at error level and not information
Change: As Requested
Impact: None
4. Request: BCM57711E Support MIN/MAX bandwidth control
Change: As Requested
Impact: None
5. Request: Support BCM8073A1 external PHY
Change: As Requested
Impact: None
6. Request: Support Transparent Packet Aggregation (TPA) for 57711E
Change: As Requested
Impact: None
7. Request: Support WoL
Change: As Requested. This feature requires bootcode 4.4.7 or later
Impact: None
8. Request: Not allowing any ethtool link change (speed and flow control) in 57711E
Change: As Requested
Impact: None
9. Request: Reporting the function max speed as the current speed (and not the port speed) for 57711E
Change: As Requested
Impact: None
10. Request: Only the port master driver can run the link test (part of the self-test)
Change: As Requested
Impact: None
Version 1.46.0 (May 01, 2008) ============================= **** This version should have been named 1.45.0 (and not 1.46.0) ****
Fixes ----- 1. Problem: Possible bug on DMAE reads (write from the chip to the host)
Cause: HW limitation that was not obeyed
Change: DMAE reads (write from the chip to the host) is limited to 128 DWORDS
Impact: None
Enhancements ------------ 1. Request: Support approximate match for multicast MACs
Change: As Requested
Impact: New module dependency for bnx2x driver Run 'modprobe crc32c' before 'insmode bnx2x.ko'
2. Request: Support statistics on 57711
Change: As Requested
Impact: None
Version 1.44.12 (April 21, 2008) ================================
Fixes ----- 1. Problem: (CQ34845) Autoneg flow-control is broken
Cause: Broken in last drops - wrong check of the autoneg result
Change: Fixed the autoneg result check
Impact: None
2. Problem: (CQ34313) Compilation error on SuSE10
Cause: Broken in last drops
Change: Fix the errors
Impact: None
Version 1.44.11 (April 16, 2008) ================================
Fixes ----- 1. Problem: PHY loopback was not performed as part of the self-test
Cause: The PHY loopback did not wait for the link to be established
Change: Wait for loopback to establish link before starting the test
Impact: None
2. Problem: (CQ34313) Compilation error on SuSE9 SP3
Cause: Broken in last drops
Change: Fix the errors
Impact: None
Version 1.44.10 (April 15, 2008) ================================
Fixes ----- 1. Problem: Occasional failures in the self-test
Cause: Few registers should not have been included in the registers test. The PHY loopback test fails on some systems
Change: Removed some of the registers that should not have been included in the first place from the registers test. Removed the PHY loopback test - only the MAC loopback test is executed
Impact: None
Version 1.44.9 (April 14, 2008) ===============================
Fixes ----- 1. Problem: Kernel panic after stressing bi-directional data over night
Cause: A bug in the none-TSO fragmented Tx packets
Change: Fix the Aggregation rule of none-TSO packets
Impact: None
2. Problem: Possible bug when unloading and reloading the driver: we are not guarantee to allocate all IRQs
Cause: The allocation is not guaranteed
Change: Force every nic_unload to release the IRQs
Impact: None
3. Problem: Possible bug on low memory systems
Cause: Number of BDs must be at least equal to number of CQEs
Change: Force the rule on init
Impact: None
4. Problem: Failures on rmmod
Cause: Sleep in timer context
Change: No sleep on timer context - simply wait for next tick
Impact: None
5. Problem: DMAE timeout problem on 57711
Cause: DMAE needs to be configured differently
Change: Reduce the MPS of the DMAE client
Impact: None
6. Problem: No link on some functions on 57711
Cause: A link report call was missing after link update
Change: Added link report after link update
Impact: None
Enhancements ------------ 1. Request: Adding internal PHY and MAC loopback tests to ethtool -t (no external PHY and no cable PHY loopback)
Change: As Requested
Impact: None
2. Request: Update idle_check in self test
Change: As Requested
Impact: None
Version 1.44.8 (April 09, 2008) =============================== **** Starting from this version, there are 2 C files ****
Fixes ----- 1. Problem: (CQ34604) Kernel panic after stressing Tx Data over night
Cause: The driver did not handle fragmented Tx packets
Change: Aggregating packets which are too fragmented for the FW
Impact: None
2. Problem: (CQ34586) Warning message after configuring eth port
Cause: Did not synchronized the DMAE of the statistics with load/unload operations
Change: Changed the statistics mechanism to a state machine which is aware of the device state and DMAE state
Impact: None
3. Problem: (CQ34313) Compilation error on SuSE9 SP3 x86-64
Cause: Compatibility issue
Change: Fixed
Impact: None
4. Problem: (CQ34067) Debug prints are displayed when using the use_multi compilation flag
Cause: The debug level of the prints was high
Change: Reduced the prints debug level so they will not be displayed by default
Impact: None
Enhancements ------------ 1. Request: (CQ33897) Support BCM8073 PHY
Change: As Requested
Impact: This is still an initial HW revision of the BCM8073 PHY so changes might be needed as the PHY HW or FW evolve
2. Request: (CQ33845) Turn off link LED when link is not active
Change: As Requested
Impact: None
3. Request: Displaying PHY FW (when applicable) at ethtool -i
Change: As Requested
Impact: None
4. Request: Upgrading the SFG10 FW from ethtool -E
Change: As Requested
Impact: None
5. Request: Adding Registers test to ethtool -t
Change: As Requested
Impact: None
6. Request: Adding Memory test to ethtool -t
Change: As Requested
Impact: None
Version 1.44.7 (March 31, 2008) ===============================
Fixes ----- 1. Problem: (CQ34445) Interface got stuck when stress with UDP and TCP simultaneously
Cause: Wrong CQE size initialization
Change: Fixed CQE ring initialization
Impact: None
2. Problem: No traffic on higher functions on 57711
Cause: Need to send the client ID in messages to FW
Change: Add client ID to the required messages
Impact: None
3. Problem: Wrong link indication on 57711
Cause: The link was not updated correctly on 57711
Change: Update the link indication mechanism in 57711
Impact: None
4. Problem: Update coalescing is not working
Cause: Wrong parameter was used
Change: Changed to the required parameter
Impact: None
Version 1.44.6 (March 26, 2008) ===============================
Fixes ----- 1. Problem: (CQ34445) Interface got stuck when stress with UDP and TCP simultaneously
Cause: The BD producer that was passed to the FW was wrapped according to the size of the BD ring and not 16 bits range as expected
Change: Wrap the BD producer according to 16 bits range
Impact: None
Enhancements ------------ 1. Request: full TPA support
Change: TPA is now fully supported with the expected performance
Impact: None
Version 1.44.5 (March 24, 2008) ===============================
Enhancements ------------ 1. Request: Initial support for TPA
Change: TPA is now supported, but the throughput is still lower than in the DEMO_TPA version - a new version with enhanced throughput is being constructed
Impact: None
2. Request: (CQ34011) Add module parameter to disable TPA
Change: As requested. For now, TPA is always disabled on 57711
Impact: None
3. Request: CNIC Support
Change: As requested. By default, CNIC support is not part of the bnx2x - BCM_CNIC should be defined to enable it.
Impact: None
Version 1.44.4 (March 20, 2008) ===============================
Fixes ----- 1. Problem: DEMO_TPA was broken on 0.44.3
Cause: Compilation problem due to MACRO rename
Change: Rename the MACRO for DEMO_TPA as well
Impact: None
2. Problem: (CQ43424) Cannot link SFP module at 1G with Dell PowerConnect 6224
Cause: The Dell switch supports only autoneg and not forced 1G
Change: Changed the 1G implementation to autoneg with only 1G advertisement
Impact: When choosing 1G speed, the speed is achieved via autoneg and not forced
Enhancements ------------ 1. Request: Support Emulation, FPGA and ASIC in a single module file
Change: Changed the init values and the init routine to support all the compilation of 57710/57711 ASIC/CHIP/EMUL
Impact: The size of the binary and the source code is bigger mainly due to having two ASM images
2. Request: Add link update support for 57711
Change: Added
Impact: None
3. Request: Add HW statistics for 57711
Change: Added
Impact: Only HW (errors) statistics will be displayed since the feature is not yet supported by FW
4. Request: Add nvram test
Change: Added
Impact: None
5. Request: Add link test
Change: Added
Impact: None
6. Request: Add interrupt test
Change: Added
Impact: None
Version 0.44.3 (March 12, 2008) =============================== *** TPA is not functional on this release ***
Fixes ----- 1. Problem: (CQ #34103) DKMS driver diskette update.tar.gz do not have smp directory
Cause: DKMS driver diskette was created only for the default SuSE kernels
Change: Add all supported SUSE kernels into the DKMS driver diskette Note: The size of the DKMS driver diskette for the SUSE distributions is 14400 kb. This size is appropriate for USB or CD devices
Impact: None
Enhancements ------------ 1. Request: Add support for 57711
Change: Added preliminary support
Impact: None
2. Request: Remove module param 57711E
Change: Move to bp and initialized from analyzing CLP information
Impact: None
3. Request: Add fw_dump() to panic_dump()
Change: Call fw_dump() before idle_chk()
Impact: None
4. Request: Separate bp information to fast-path/common/port/ function
Change: Divide bp structure into common/port/function structures Divide get_hwinfo() into common/port/ function. Initialize outer VLAN and MAC from CLP information in 57711E mode Note: CLP FUNC_DISABLED is not handled correctly
Impact: None
5. Request: Set link_status according to link_up status
Change: link_status was set according to phy_link_up status
Impact: None
6. Request: Add is_pmf flag
Change: is_pmf flag is initialized from MCP load_code and by general attention from MCP
Impact: None
7. Request: Fix attentions in 57711
Change: Init MISC_REG_AEU_MASK_ATTN according to 57711E status Handle attention bits in IGU per function
Impact: None
8. Request: Clear HW blocks attentions
Change: Clear HW blocks attentions and call panic()
Impact: None
9. Request: Call fw_dump() on MCP assert
Change: Call fw_dump() instaed of mc_assert() on MCP assert
Impact: None
10. Request: Do not send STAT_QUERY ramrod if previous stat ramrod didn't return
Change: Do not send STAT_QUERY ramrod if previous stat ramrod didn't return Call panic() if stats didn't updated for 3 times
Impact: None
11. Request: Separate init_board() into init_dev() and init_bp()
Change: Divide init_board() into init_dev() and init_bp()
Impact: None
12. Request: Fix directory name for SuSE
Change: Add sles9 and sles10 to the names
Impact: None
Version 1.42.3 (February 28, 2008) ==================================
Fixes ----- 1. Problem: Changing the link speed to "autoneg on" the A1022G will cause driver failure
Cause: This board is using TP for the 10G interface, but the command was interpreted as a request to move to the 1G interface which is inactive on this board
Change: Do not support switching interfaces since no production board has this feature
Impact: A user will not be able to switch between the two valid interfaces of the T1001 test board without changing the nvram configuration
Version 1.42.2 (February 20, 2008) ==================================
Fixes ----- 1. Problem: TSO is not working against some none Linux clients
Cause: TCP flags were not transmitted correctly on TSO packets
Change: Corrected bit extraction in tcp_flag_word()
Impact: None
Version 0.42.1 (February 14, 2008) ==================================
5. Problem: (CQ #33305) Changing MTU to 9000 was jamming TCP traffic
Cause: LSO wasn't properly enabled on some Kernels
Change: Fixed LSO enabling code for all kernels
Impact: None
Enhancements ------------ 1. Feature: Wait for completion for ramrods sent during nic unload was only by polling and not by an interrupt.
Change: stop multi and stop leading are using poll if netif is not running and interrupt otherwise.
Impact: None
2. Request: Add workaround for bug in PXP that causes PXP attention on stress scenarios due to under run situation between PXP and USDM
Change: The workaround was added
Impact: None
Version 0.40.18 (January 03, 2008) ==================================
Fixes ----- 1. Problem: (CQ #33148) After "make install" command 'modprobe bnx2x' displays "Module bnx2x not found".
Cause: Linux Makefile runs depmod automatically only if System.map exists.
Change: Run depmod after modules_install.
Impact: None
2. Problem: (CQ #33054) Link is not detected after configuring BCM57710 port with Suse 10Sp1.
Cause: HW fails to use INTA after using MSI-X.
Change: Set MSI_MSIX_INT_EN bit in HC_CONFIG REG to use INTA after MSI-X.
Impact: None
3. Problem: (CQ #33190) ifconfig command showed errors received. But ethtool -S ethx did not show any errors.
Cause: Some error counters did not have a bin to be printed by ethtool -S command.
Change: Add appropriate bins for the missed counters.
Impact: None
4. Problem: BSOD on T1002 boards.
Cause: A new code was added that manipulate GPIO 1 for external phy reset. On T1002 board this GPIO control the PERST_L_BYPASS.
Change: Do not manipulate GPIO 1 on T1002 boards
Impact: None
Enhancements ------------ 1. Feature: Add support for IPv6 checksum and IPv6 TSO.
Change: The support was added
Impact: None
2. Feature: Add fan failure detection and external PHY power down for the A1022G
Change: When a fan failure is detected (indicated by SPIO5) on the A1022G, the driver will shutdown the PHY (reset and low power mode, using GPIO1+2) and issue a warning message
Impact: When fan failure occurs the link will go down until server reset
Version 0.40.17 (December 17, 2007) ===================================
Fixes ----- 1. Problem: (CQ #33023) Pause RX is on when driver is loaded with MTU > 4500.
Cause: Pause mode was computed from the requested flow control parameter in NVRAM without considering the MTU size.
Change: Resolve the pause mode only before advertising the flow control.
Impact: None
2. Problem: Pause autoneg can be set on for XFP cards.
Cause: Pause autoneg mode was always accepted from user.
Change: Pause autoneg is not supported if speed autoneg is not supported (e.g. XFP cards).
Impact: None
3. Problem: (CQ #33044) make install fail.
Cause: No make install target in Makefile.
Change: Add make install target to Makefile.
Impact: None
4. Problem: (CQ #33057) No README.TXT in driver release folder.
Cause: No README.TXT in driver project.
Change: Add README.TXT in driver release folder.
Impact: None
5. Problem: (CQ #32541) No README.TXT in driver tarball.
Cause: No README.TXT in driver project.
Change: Add README.TXT to driver tarball and change the directory name.
Impact: None
Enhancements ------------ 1. Request: Add parity and assert regs for idle check.
Change: The check was added
Impact: None
2. Request: Add workaround for threshold mechanism for usdm-dp
Change: The workaround was added
Impact: None
3. Request: Add workaround for full Tetris buffer bug.
Change: The workaround was added
Impact: None
4. Request: Add support for the SFG10 PHY
Change: The support was added
Impact: None
5. Request: Add support for the BCM8072 PHY
Change: The support was added. The code is still not 100% functional
Impact: None
6. Request: Change the MDC/MDIO CL45 scheme
Change: The functions are more generic: - Supports different MDC/MDIO controller - Reduce the clock to 2.5MHz - Less PIO writes (writing all the required information at one attempt)
Impact: All external PHY access are using a slower (standard) MDC/MDIO clock
7. Request: Hard reset external PHYs
Change: The external PHYs are now reset via GPIO. Before working with an external PHY, a reset pulse of 1ms is generated, and when the driver is down, the external PHY is kept in reset
Impact: Link partner should always see link down when the link is down
Version 0.40.16 (November 29, 2007) ==================================
Cause: vlan_kill_vid() removed in newer versions is needed by older kernels to allow loading.
Change: Re added function.
Impact: None
2. Problem: (CQ #29543) System panicked if receiving UDP data while load and unload
Cause: sp_task work was not synchronized with int_disable_sync()
Change: move sp_task to work_queue element
Impact: None
3. Problem: (CQ #32430) XFP port showed link lights on and link detected = yes when configured port up with no cable attached
Cause: Link_up was declared by local phy (XGXS) link up without the external phy (8705) link status
Change: Link up is now the combination of local phy (XGXS) link up and external phy (8705) link up
Impact: None
Enhancements ------------ 1. Request: Print PCI link properties upon load.
Change: The print was added
Impact: None
Version 0.40.15 (November 15, 2007) ==================================
Fixes ----- 1. Problem: On heavy traffic scenarios, the machine halted due to PCI problem
Cause: A HW change in A1 boards requires some registers that controls the PCI credit to be changed as well
Change: Updating the PXP credit registers
Impact: None
2. Problem: (CQ #31120) The traffic LED was not active for lower speeds
Cause: A new bootcode is required to set the traffic LED when the speed is less then 10G (using the emac and not the bmac)
Change: The set LED routine was updated and bootcode 4.0.10 or above is required to have the LED functional
Impact: None
3. Problem: Found a bug when doing ifconfig down/up during traffic. In this case FW can assert
Cause: A packet that was received before unloading driver stayed in Pbuff, and was processed after loading the driver again
Change: Added the reordering mechanism to slow path handlers
Impact: Implementation of all L2 slow-path commands was modified
4. Problem: (CQ #30160) Removed false positives from the self test (ethtool -t)
Cause: Many tests in the self test were designed to check halted system (after fatal error) and the test assumed that the chip is idle
Change: Any test that can happen while the chip is operational was changed to "info" debug print and is not counted as warning or error
Impact: The self test is more reliable
Enhancements ------------ 1. Request: Forward preparation in the code for 57711
Change: Using only two DMAE clients per port. Using "port" instead of "function".
Impact: Not visible to the user
2. Request: Block RX Pause if Auto-pause was selected and the MTU > 4500 to prevent performance retrogression when using PAUSE with big packets
Change: The auto-pause resolution will be only TX pause if the MTU is larger than 4500. Force pause mode will be obeyed as requested
Impact: Jumbo frames with auto-pause will achieve higher throughput
3. Request: Report HW errors
Change: Parity and blocks errors attentions code was added to the driver. Not all indications are enabled.
Impact: In case of an assert in the chip, the user will get an error notification
4. Request: Added the ability to support multi interrupt queues from kernel 2.6.24 and above
Change: Allow ISR and NAPI (the stack processing) to run on several CPUs. The new feature is disabled by default
Impact: Can reduce latency in some cases
5. Request: Move slow-path to work-queue to allow sleeps
Change: The slow-path is now implemented as work queue
Impact: Better fairness to other host drivers
6. Request: Changes with statistics requirements due to performance enhancement and preparation for next features.
Change: a. Removed rcv_error_bytes b. Replaced errors_discard stat by: mac_discard stat, checksum_discard stat and packet_too_big_discard stat c. Removed statistics histogram
Impact: The displayed statistics format was changed
7. Request Remove FW interrupts that are not needed
Change: FW no longer interrupts the driver for reading a new slow-path element (it updates driver only when completing processing it)
Impact: None
8. Request: Support easier SuSE compilation
Change: In previous version, a flag in bnx2x.c was required in order to compile under SUSE. In the new implementation the make file can be used in the following way: SLES9 command: make EXTRA_CFLAGS+=-DBNX2X_SLES_9 SLES10 command: make EXTRA_CFLAGS+=-DBNX2X_SLES_10
Impact: SLES compilation procedure is different now
Version 0.40.14 (November 06, 2007) ==================================
Enhancements ------------ 1. Naming the TCP performance improvement feature TPA (still for demos only)
Version 0.40.13 (November 05, 2007) ==================================
Enhancements ------------ 1. Added support for L2 Rx TCP performance improvements in a special mode (implementation for demos only). This support is disabled by default and requires a change of compilation flag to enable. 2. Added support for vanilla kernel 2.6.18.5, SLES9, and RHES4
Version 0.40.12 (October 29, 2007) ==================================
Fixes ----- 1. Problem: A fragmented Tcp/Udp packet might have been wrongly dropped
Cause: parser doesn't checks tcp/udp checksum for fragmented packets
Change: FW will report to driver the tcp/udp checksum wasn't Validated if the packet was fragmented
2. Problem: ethtool -S|r|t eth[x] on un-configured port causes errors/panic
Cause: When port is un-configured memory is not allocated and blocks in chip can be in reset
Change: Check driver state in nway_reset() and self_test() and check memory pointer in get_ethtool_stats()
Enhancements ------------ 1. Supporting the upstream Kernel including new NAPI approach 2. Open source coding standard modifications throughout the code, including new init code, new HSI header files, new registers definitions, SPARSE fixes and checkpatch.pl fixes 3. Replaced patches mechanism with #ifdefs 4. Supporting big-endian machines 5. Supporting nVidia chipsets with MCP55 6. Support checksum offload for A1 boards (modification with some flag in PBF command)
Version 0.40.10 (August 27, 2007) =================================
Bug fix version, no new features
Version 4.0.9 (August 10, 2007) ===============================
New features: -------------
1. Updated to firmware version 4.0.7.
2. Added support for ethtool EEPROM options.
Version 4.0.7 (July 23, 2007) =============================
New features: -------------
1. Added support for flow control.
2. Added patch for Kernel 2.6.22.x.
Version 4.0.6 (July 11, 2007) =============================
New features: -------------
1. Added support for new bootcode 4.0.2.
Version 4.0.5 (June 29, 2007) =============================
Fixes: ------
1. Problem: Linux stack rechecked the RX checksum.
Cause: In most cases, the indication of RX checksum was wrong causing the Linux stack to recheck.
Fix: Indication mistake was fixed.
2. Problem: NFS UDP test failed writing to server.
Cause: Incorrect HW init values.
Fix: HW init values were corrected in the driver.
3. Problem: MTU change cause system to assert.
Cause: Memory leak in the ifconfig up/down sequence.
Fix: Memory leak fixed in driver.
Version 4.0.1 (June 15, 2007) =============================
New features: -------------
1. Added Power management is support.
2. Added WoL is support.
3. Auto-negotiation and speed & duplex is supported.
4. Updated firmware version to v4.0.2.
5. Support for Ethtool.
6. Changing MTU can be done when link is up.
Version 0.30.1 (June 4, 2007) ============================
New features: -------------
1. Updated firmware version to v0.30.0.
Version 0.29.1 (May 21, 2007) ============================
New features: -------------
1. Updated firmware version to v0.29.0.
Version 0.27.5 (May 7, 2007) ============================
New features: -------------
1. Interrupt coalescing values have been optimized.
2. Updated to Linux Kernel 2.6.20.7.
Fixes: ------
1. Problem: High performance scenarios involving many threads could have caused tx ring overrun.
Cause: SNP concurrency driver bug.
Fix: Driver related code was fixed.
Version 0.27.1 (Apr 23, 2007) ============================
New features: -------------
1. Added speed and activity support for LEDs.
Fixes: ------
1. Problem: Low performance when running Netperf TCP_RR.
Cause: Driver bug caused a the driver to enter a busy loop in certain cases when there was no RX processing queued.
Fix: The logic used to decide if there is pending RX work was corrected.
2. Problem: XFP link detection problem - intermittent issue.
Cause: Driver would not get link change interrupt.
Fix: Corrected the setting of the link change interrupt.
C. ============================ R E L E A S E N O T E S ============================
Broadcom NetXtreme II iSCSI Driver For Linux
Copyright (c) 2006-2012 Broadcom Corporation All rights reserved.
Version 2.7.2.1k (Mar 06, 2012) =============================== Fixes ===== 1. Problem: Cont00061985 - fails to build on RHEL5.7x32 Cause: The /usr/src/kernels/- linux src path was never included in the Makefile Change: Updated the Makefile to include this Impact: All
Version 2.7.2.1j (Mar 02, 2012) =============================== Fixes ===== 1. Problem: Cont00061911 - version incorrect Cause: The previous version did not get updated Change: Version is now updated to 2.7.2.1j Impact: All
Version 2.7.2.1i (Feb 28, 2012) =============================== Enhancements ============ 1. Added definition for ISCSI_KCQE_COMPLETION_STATUS_PARITY_ERR
Version 2.7.2.1f (Jan 31, 2012) =============================== Fixes ===== 1. Problem: Cont00061303 - error_mask1 and error_mask2 module parameters do not work Cause: The error_mask overriding mechanism has a bug which didn't allow it to work properly. Change: Fixed the bug and also changed the error_mask1/2 type attribute from int to uint so the MSB of the parameters can be set Impact: All
Version 2.7.2.1e (Jan 12, 2012) =============================== Enhancements ============ 1. Fixed compilation for RHEL5.8
Version 2.7.2.1d (Jan 04, 2012) =============================== Enhancements ============ 1. Minor optimization to the iSCSI statistics collection code 2. Adapted to use the newly introduced bnx2x_mfw_req.h header 3. Updated Copyright year 4. Fixed the proper notification to the iscsi daemon to handle conn failure when NETDEV_GOING_DOWN event arrives first
Version 2.7.2.1c (Dec 21, 2011) =============================== Enhancements ============ 1. Minor optimization to the iSCSI statistics collection code 2. Added UPDATE_CONN failure detection to prevent from entering FFP
Version 2.7.2.1b (Dec 01, 2011) =============================== Enhancements ============ 1. Added support for iSCSI statistics collection 2. Fixed kthread freezing bug for RHEL5.X and SLES11SP1 distros
Version 2.7.0.4i (Nov 01, 2011) =============================== Enhancements ============ 1. Fixed compilation for SLES11sp2 beta8+
Version 2.7.0.4h (Sep 15, 2011) =============================== Fixes ===== 1. Problem: Cont00056438 - Driver panic running Super Stress w/ Error Recovery Cause: The kernel panic was caused by a race condition between the connection establishment retrival of the ISCSI_PARAM_CONN_ADDRESS parameter and ep_disconnect. Change: Fixed the race condition by employing the bnx2i_resc_lock to lock the bnx2i_conn and bnx2i_ep association. Impact: RHEL6.1/SLES11SP1 and older
Version 2.7.0.4g (Aug 22, 2011) =============================== Fixes ===== 1. Problem: Cont00057987 - Can't compile under RHEL6.2 Cause: The param_mask and host_param_mask has been moved to use the attr_is_visible routine Change: Made the proper modification Impact: All
Version 2.7.0.4f (Aug 13, 2011) =============================== Fixes ===== 1. Problem: Cont00057829 - iscsi ping timeout and session flapping connected to nx4 target Cause: Every once in a while, this target would send an async NOP-in packet requesting a NOP-out response (TTT != 0xFFFFFFFF). There's a bug in the NOP-out send code where big endian was forced upon the TTT param instead cpu specific. Change: Added a be32_to_cpu conversion in the TTT setting. Impact: All
Version 2.7.0.4e (Jul 27, 2011) =============================== Fixes ===== 1. Problem: kernel panic observed when performing ifup/down with I/O under SLES11SP2 beta1 Cause: The newer kernel requires a bnx2i patch which handles the newly defined get_ep_param instead of using the get_conn_param directly Change: Ported over the get_ep_param patch from upstream. This will be employed for newer kernels/distros (RHELS6.2+/SLES11SP2+/Linux kernel 2.6.38+) Impact: All
Enhancements ============ 1. Added bnx2i_compat.h to hide all backwards compatibility code.
Version 2.7.0.4d (Jul 19, 2011) ===============================
Enhancements ============ 1. From linux-iscsi, a problem was found in the rq_affinity code which prevented HT cpu cores from being scheduled for block I/O processing. This severely hampers iSCSI performance if we use the sc->request->cpu for kthread scheduling. The sc->request->cpu will no longer be employed in the kthread scheduling until further notice.
2. Restored the vlan_id from indicate_netevent in accordance to the same change in CNIC.
Version 2.7.0.4c (Jul 13, 2011) ===============================
Enhancements ============ 1. Removed the vlan_id from indicate_netevent in accordance to the same change in CNIC.
Version 2.7.0.4b (Jul 12, 2011) ===============================
Enhancements ============ 1. Fixed the illegal use of sc->request->cpu as ported from upstream code. 2. Added support for kernel 3.0.xx compilation.
Version 2.7.0.3c (Jun 20, 2011) ===============================
Enhancements ============ 1. Modified the init procedure to skip the registration to CNIC if iSCSI is not supported. 2. Augmented the SCSI host template parameters can_queue and cmds_per_lun for performance optimization. 3. Synchronized with several minor fixes from the upstream code.
Version 2.7.0.3b (Jun 02, 2011) ===============================
Fixes ===== 1. Problem: Cont00051898 - iSCSI Read throughput dips at 512KB with higher qdepths Cont00051896 - iSCSI Read throughput under performs at lower request sizes with higher qdepths Cause: Both problems are caused by a certain deficiency in the existing iSCSI fast path completion code under higher qdepth operations. Change: The iSCSI fast path completion code has been completely retuned to include optimization such as using kthreads and a new event coalesce formula. Impact: All
Enhancements ============ 1. Removed 57713 and added 57800/57810/57840_MF/VF support.
Version 2.7.0.2b (May 03, 2011) ===============================
Fixes ===== 1. Problem: Cont00054496 - Session continuously drops and reconnects with sq_size = 16 against EQL target Cause: The ccell setup in the chip was not at 1/2 of the outstanding task setup. This causes the fw to reuse a ccell which wasn't available. Change: The ccell setup will now be reinitialized accordingly after the sq_size adjustment. Impact: All
2. Problem: Can't compile against upstream server Cause: The parsing of the kernel version string requires a '-' or a '.' as the delimiter which is missing when running any upstream kernel Change: Modified the kernel version parsing string in the Makefile to accommodate for this Impact: All
Enhancements ============ 1. Removed obsolete installation instructions from the README.
Version 2.7.0.1b (Mar 29, 2011) ===============================
Enhancements ============ 1. Added support for E3 (57800, 57810, and 57840)
Version 2.6.4.1e (Mar 22, 2011) ===============================
Fixes ===== 1. Problem: CQ53773 - bnx2i -WARN CONN_DISCON timeout after setting sq_size to 16 Cause: The chip's sq memory was being overdriven where as there is no mechanism in the code to flow off the SCSI layer from sending more commands down Change: Added a guard to flow off the SCSI layer from queuing more than the chip's sq limit Impact: All
Enhancements ============ 1. Added support for XenServer 2.6.32 kernel.
Version 2.6.4.1d (Mar 15, 2011) ===============================
Fixes ===== 1. Problem: bnx2x panic was observed under various recovery PQA tests Cause: The size of the RQ doorbell was changed from 16 to 64 Change: Fixed the RQ doorbell size in the driver Impact: 5771X
Version 2.6.4.1c (Feb 28, 2011) ===============================
Enhancements ============ 1. Optimized the iSCSI fast path arming procedure; CQE rescan and skip the 0xFFFF check.
2. Modified the Makefile to filter out unsupported distro compilation
Version 2.6.4.1b (Feb 02, 2011) ===============================
Enhancements ============ 1. Restored the vlan_id handling for the indicate_netevent call
Version 2.6.2.4c (Feb 01, 2011) ===============================
Fixes ===== 1. Problem: Cont00052673 - iLab failed test6_14 - delayed iSCSI response Cause: A bug was found in the ep_disconnect routine where the session variable did not get initialized correctly. This bug will cause TCP abortive disconnect to be requested unconditionally. Change: Fixed the initialization bug Impact: All
Version 2.6.2.4b (Jan 14, 2011) ===============================
Fixes ===== 1. Problem: Cont00052132 - iSCSI has poor write IOPS at 1K block size Cause: A soft lockup for 10s was observed with this and various different I/O size test where as soon as the bh is released, the scsi_next_command routine will trigger and the queue lock will get stuck. Change: - Restored all CQE processing back to the cnic tasklet bh and modified the session lock granularity - Modified the event coalesce algorithm to include the cmd_cmpl_per_work module param Impact: All
2. Problem: Cont00052131 - Cannot establish solid offload connection to Dell MD3220i target from SLES11sp1 (RHELS is okay) Cause: The problem was caused by the deferred CQE processing to workqueue scheme which caused nop timeouts during logouts. Change: The new CQE processing scheme no longer uses workqueue. Impact: All
3. Problem: Cont00051479 - bnx2 unable to compile under RH5.6ss3 Cause: The bnx2i makefile did not accommodate for native RHELS5.6 installations either. Change: Modified the bnx2i Makefile which will now examine the ...kernel.../linux/include/version.h file for the corresponding RHEL version that it is compiling against. Impact: All
Enhancements ============ 1. Updated README for Cont00052157 to update the open-iscsi util
Version 2.6.2.3g (Jan 04, 2011) ===============================
Fixes ===== 1. Problem: Cont00051896 - iSCSI Read throughput underperforms at lower request sizes with higher qdepths for 5771X Cause: The new workqueue CQE processing mechanism was not tuned for this scenario Change: Various modification has been included for performance optimization Impact: All
Enhancements ============ 1. Feature: Removed the scsi_flush_workqueue call and use a hba workqueue array instead. This eliminates the potential libiscsi softlock that one connection is performing scsi cleanup while the other is undergoing scsi_flush_workqueue. Impact: All
Version 2.6.2.3f (Dec 20, 2010) ===============================
Fixes ===== 1. Problem: Cont00051815 - kernel BUG - logging into EMC NX4 Cause: This target uncover a timing bug in the CQE processing call in the mtask transmission. The nopin response got processed before the nopout request was returned to the stack. This causes the nopout request to timeout all the time as the nopin responses would never get processed. Change: Removed the CQE processing in mtask requests. This is not necessary. Impact: All
Version 2.6.2.3e (Dec 17, 2010) ===============================
Fixes ===== 1. Problem: Cont00051647 - Unable to logout of Dell MD3220i target for RHELS6.0 Cause: Upon logout or shutdown, a scsi sync cache cmd will get transmitted while the scsi worker is being blocked. Since this is a fastpath cmd, the response was queued to the scsi scsi workqueue which resulted in a lost response. When this happens, the sync cache logic in the kernel will block forever. Change: Upon receiving a scsi sync cache cmd, the cqe processing will switch to direct processing instead of deferring to the wq Impact: All
Enhancements ============ 1. Feature: No longer have to flush the entire shost workqueue for every connection termination. In RHELS6.0, the cancel_work_sync function will remove the connection's single entry to the shost's workqueue. Impact: All
2. Feature: Added retry logic in the send nl mesg routine for robustness Impact: All
Version 2.6.2.3d (Dec 15, 2010) ===============================
Fixes ===== 1. Problem: Cont00051625 - call trace while ifdown with traffic bnx2i_conn_worker Cause: Under certain ifdown cases, the bnx2i_ep and the bnx2i_conn are not associated when going through chip_cleanup. The previous fix did not take this into consideration Change: Moved the disabling of the workqueue to hw_ep_disconnect under bnx2i_conn validation check Impact: All
Version 2.6.2.3c (Dec 14, 2010) ===============================
Fixes ===== 1. Problem: Cont00051625 - call trace while ifdown with traffic bnx2i_conn_worker Cause: During ifdown, the bnx2i_stop code will clean up all active connections from the chip. However, because of the new workqueue data processing architecture, the workqueues for the already cleaned connections were still being called. This has created a window of opportunity for the libiscsi2 layer to get into a continuous locking/unlocking via the task_xmit path. Change: Added the disabling of the workqueue for every active iSCSI conn before chip cleanup. Impact: All
2. Problem: Cont00051647 - Unable to logout of Dell MD3220i target Cause: The scsi_flush_work call in the ep_disconnect was waiting indefinitely for outstanding nopout cmd which was never sent during the SCSI sync cache phase Change: Removed the scsi_flush_work call until conn_destroy to align with internal scsi state. Note that all outstanding scsi work must be flushed before the bnx2i_conn gets destroyed. Impact: All
Version 2.6.2.3b (Dec 07, 2010) ===============================
Fixes ===== 1. Problem: Cont00051499 - Call trace seen with bnx2i_process_new_cqes Cause: For targets which employs ip redirect, a remote abort/close event would occur. However, these were not being handled correctly under the new cqe processing architecture Change: Added session recovery workqueue to defer all remote abort/close requests Impact: All
Version 2.6.2.3a (Dec 06, 2010) ===============================
Fixes ===== 1. Problem: Cont00050655 - Low read/write IOPS on linux configuration 57711 Cause: The chip was being underutilized due to the mutual starvation in the bottomhalf tasklet between the fastpath's EQ->CQE handling and the SCSI ML's queue command requests Change: Alleviate the processing time of the EQ->CQE by creating a workqueue and also added processing of such in the queuecommand's bh. Impact: All
2. Problem: Cont00051427 - Session recovery seen after stopping I/O traffic on Lefthand P4300 target Cause: The nopout's reserved field was not being initialized to zero before being reused. Change: Zero out the entire nopout wqe before sending to fw. Impact: All
Enhancements ============ 1. Feature: Updated the README to remove the jumbo MTU limitation caveat Impact: All
Version 2.6.2.2b (Nov 09, 2010) ===============================
Fixes ===== 1. Problem: Cont00050725 - RH6.0:iSCSI HBA Linux: bnx2i WARN-CONN_DISCON timed out message observed when restarting iSCSI service Cause: A chip panic was observed as CFC delete was initiated without SRC delete being executed first. Change: There's a path where if the connect response exceeded the connection timeout, CFC delete will occur without first executing SRC delete. Impact: 5771X
Enhancements ============ 1. Feature: Added jumbo MTU support for iSCSI offload connections Change: For cases where the shost is not provided, jumbo MTU is not supported. Impact: All
Version 2.6.2.2a (Oct 28, 2010) ===============================
Enhancements ============ 1. Added send text pdu support for iSCSI send-target discovery via the offload path
2. Added compilation support for RHELS5.6-alpha
3. Reduce the hard-coded 20s delay wait time to 1s for NETDEV_GOING_DOWN operations
4. Changed the ulp_ops->iscsi_nl_send_msg() to prevent a circular lock dependency issue
Version 2.6.2.1a (Oct 11, 2010) ===============================
Fixes ===== 1. Problem: Cont00044011 - Linux iSCSI: Cannot obtain max number of sess when changing sq_size to 16 (5708) Cause: - Task allocation unit were not correctly allocated - Offloaded PG were being leaked - 5706/08 firmware's context allocation were not correct Change: Fixed all 3 desribed issues above. This also requires an update of the 5706/08 firmware which contains this fix. Impact: 570X
2. Problem: Cont00049584 - System panic with this message "mutex_lock" Cause: The single threaded iSCSI daemon has prevented the NETDEV_UNREG path to invalidate the host when it is too busy trying to perform session recovery. Change: The fix is separated in both the open-iscsi utility and bnx2i. The fix in bnx2i is to combat netlink messages from being lost. The fix in the open-iscsi utility is to fix the single threaded scheduler which flushed the INVALID_HOST path. The patch has already been submitted to RHELS for the next release of 5.6/6.0. Impact: 5771X
3. Problem: Cont00049609 - Running iLab automated iSCSI test 6.1 on RHELS6.0 intermittently caused kernel panic Cause: A bug in the TMF LUN reset command generation code in bnx2i has corrupted the LUN number which the target will reject the request. This has led to libiscsi to dereference an incomplete TMF scsi_cmd; hence the kernel panic. Change: Fixed the TMF LUN reset generation in bnx2i. Impact: All
Version 2.1.3a (Sep 15, 2010) =============================
Fixes ===== 1. Problem: Cont00049899 - RHELS5.5 iSCSI boot thru offload path fails in IPv6 mode Cause: The local IPv6 address being transferred to the iSCSI daemon is corrupted Change: Fixed the proper formatting of the ipv6 address for the HOST_PARAM_IPADDRESS retrieval Impact: All (RHELS5.4/5.5 and IPv6 only)
Version 2.1.2z (Sep 07, 2010) =============================
Fixes ===== 1. Problem: Cont00049798 - System unresponsiveness during cable pull test Cause: This is newly introduced by the previous code. The root cause of the problem relates to how libiscsi immediately initiates another nopout request when the previous one fails to queue Change: Allow nopout requests to return success as normal. The associated task will get freed upon nopout timeout. Impact: All
Version 2.1.2y (Sept 02, 2010) ==============================
Fixes ===== 1. Problem: Cont00049634 - Linux iSCSI: MC assert on idle port while running ifup/down with 128 sessions 2. Problem: Cont00049667 - Linux iSCSI: bnx2x_panic_dump while running adapter selftest with active sessions connected ([bnx2x_stats_update:1070(eth6)]storm stats were not updated for 3 times) 3. Problem: Cont00049477 - Linux iSCSI: bnx2x_panic_dump while running adapter selftest with active sessions connected (bnx2x_cnic_handle_cfc_del:4443) 4. Problem: Cont00049584 - LinuxiSCSI: System panic with this message "mutex_lock+0x2b/0x50" Cause: Several issue in connection cleanup and bnx2i_stop() code and bnx2i was not uploading connection if it does not receives TCP CONN_DISCON completion. also bnx2i_ep_connect() was not handling certain error cases well which was resulting resource leak and also messing up cid and l5_cid handling mapping Change: * Moved 'hba->adapter_state' flags bit clear to after connection cleanup wait is over. This allows ep_disconnect() code to run normally and upload the connection properly * Added code to wait for pending connection offload and upload requests to complete before proceeding to chip clean-up. iscsid and libiscsi will not cleanup these ep's when session_drop() is called because these ep's are not yet bound to any iscsi sessions * Forcefully terminate all in progress connection recovery at the earliest, either in bind(), send_pdu(LOGIN), or conn_start(). This will avoid iscsid waiting for 10-15-sec waiting for login response and then proceeding with connection cleanup. This fix enables iscsid to start connection cleanup process immediately * There are known certain target TCP stack behavior which could lead to missing CONN_DISCONNECT request timeout eventhough firmware has terminated the tcp connection properly. Firmware team has confirmed it is safe to terminate and CFC_DEL these connections * Fixed several issues in error handling code in bnx2i_ep_connect() which could lead to resource leak and cid and iscsi cid mangling
Impact: 5771X
Enhancements ============ None
Version 2.1.2x (Aug 26, 2010) ==============================
Fixes ===== 1. Problem: Cont00049634 - MC assert on idle port while running ifup/down Cause: The chip panic was caused by performing a CFC deletion operation to a connection that is not idle. The tx/rx pipe in the driver were still trying to access the chip. Change: The tx/rx pipe is now suspended before attempting the chip cleanup Impact: 5771X
Version 2.1.2w (Aug 25, 2010) ==============================
Fixes ===== 1. Problem: Cont00049584 - System panic with this message "mutex_lock" Cause: The single threaded iSCSI daemon has prevented the NETDEV_UNREG path to invalidate the host when it is too busy trying to perform session recovery. Change: Instead of changing the iSCSI initiator code, the NETDEV msg handling path was modified to prevent the iSCSI daemon from entering session recovery in the NETDEV_UNREG path. Impact: 5771X
2. Problem: Cont00049477 - bnx2x_panic_dump while running adapter selftest Cause: Another CFC delete chip panic was observed when CONN_DISCONN timeout (option2 disconnect timed out) happens. The driver should not allow the associated l5_cid from being freed which will prevent l5_cid reuse. Change: Block the freeing of the associated l5_cid Impact: ALL
Version 2.1.2v (Aug 18, 2010) ==============================
Fixes ===== 1. Problem: Cont00049477 - bnx2x_panic_dump while running adapter selftest Cause: Its a cleanup issue exposed by uIP taking too long to recover the session. This has led to the driver initiating the chip cleanup process while the iSCSI daemon is staggering its connect/disconnect request. Change: Disallow ep_connect request while performing chip cleanup Impact: ALL
Version 2.1.2u (Aug 11, 2010) ==============================
Fixes ===== 1. Problem: Cont00049283 - cannot login thru offload path with vlan Cause: The hardware net device identifier should be used instead of the vlan identifier Change: Since this is the intended behavior, only the README has been updated with this info Impact: ALL
Enhancements ============ 1. Ignore all netevents associated with VLAN. Only process netevents from the non-VLAN net device
Version 2.1.2t (Aug 08, 2010) ==============================
Fixes ===== 1. Problem: Cont00049208 - Error when compile bnx2i under IA64 Cause: The IA64 architecture does not support cflags of -mhard-float Change: Since bnx2i does not use any floating point components, it has been decided to remove both -ffast-math and -mhard-float from the Makefile Impact: ALL
2. Problem: Cont00049245 - Session recovery timeout kernel panic Cause: iscsi_conn was destroyed asychronously after long selftest Change: Added guard against pointer dereferencing for CONN_DISCONN conditions Impact: ALL
3. Problem: Cont00049247 - Kernel panic seen after selftest a few times Cause: cnic csk was nullified upon chip cleanup from bnx2i stop. At the same time, a new instance of iscsid tries to disconnect the same bnx2i endpoint but now with the cnic csk being NULL. Change: Added guard against double calling of hw_ep_disconnect via ep->state being EP_STATE_IDLE Impact: ALL
4. Problem: Cont00049182 - IPv6 redirection does not work on Equalogic target Cause: With the new ipv6 enabled uIP, it uncovered a bug in the ep_poll routine where bnx2i is providing an erroneous timeout error to the iSCSI daemon. Change: Fixed the bug in the ep_poll routine Impact: ALL
Version 2.1.2s (Aug 03, 2010) ==============================
Fixes ===== 1. Problem: Cont00049161 - Kernel panic occurs running iLAB test6_1 Cause: The kernel panic was caused by an synchronization issue in the iSCSI stack when a fail TMF lun reset request was introduced by a bug in our driver. Change: Fix the lun reset TMF request endian bug where the lun field was not correct Impact: ALL
Version 2.1.2r (Aug 02, 2010) ==============================
Fixes ===== 1. Problem: Cont00049047 - EP disconnect timeout - chip panic Cause: Chip panic occurred while trying to force CFC delete upon cm_abort/close (CONN_DISCONN) timeout Change: It is adviced to not separate the conn destroy procedure of SRC_DELETE, terminate offload and CFC_DELETE. So upon a CONN_DISCONN timeout situation, no CFC_DELETE will be issued. Impact: 5771X
Enhancements ============ 1. Added temporary workaround for the HOST_IPADDRESS parameter for ipv6
Version 2.1.2q (Jul 30, 2010) ==============================
Fixes ===== 1. Problem: Cont00048941 - iscsi2_conn_failure kernel panic due to target restart Cause: Kernel panic occurred in iscsi2_conn_failure dereferencing a NULL iscsi_conn pointer. The asynchronous tcp FIN/RST that gets received might have been blocked while the iscsi_conn is being nullified. Change: Added check against iscsi_conn/sess dereferencing for asynchronous response such as remote abort/close scenarios Impact: All
2. Problem: Cont00049068 - Sessions drop and recovery against Lefthand Networks P4300 target Cause: The session recovery was caused by the LUN reset timeouts. Only abort_task TMF is supported. Change: Added support for other TMF modes like LUN reset. Added protocol violation fix for NOP-Out responses to unsolicited NOP-Ins Impact: All
Version 2.1.2p (Jul 29, 2010) ==============================
Fixes ===== 1. Problem: Cont00049013 - bnx2i_tear_down_conn kernel panic Cause: Chip panic occurred due to CID reuse without being initialized Change: Added chip cleanup procedure in the bnx2i module unloading code path Impact: 5771X
Version 2.1.2o (Jul 28, 2010) ==============================
Fixes ===== 1. Problem: Cont00049044 - bnx2i driver version is not correct Cause: Version didn't get bumped Change: Updated version string Impact: ALL
2. Problem: Cont00049047 - EP disconnect timeout Cause: CONN_DISCONN was causing a double CFC delete request which ultimately caused the chip to panic Change: Fixed the double CFC delete request handling Impact: 5771X
3. Problem: Cont00049857 - System lock up when connect to lefthand target Cause: Two sess spinlocks were being requested in the NOP-Out local completion path Change: Fixed the spinlock request in the handling routine Impact: All
Version 2.1.2n (Jul 24, 2010) ==============================
Fixes ===== 1. Problem: Cont00048998 - Compilation error found with sles11sp1x86 Cause: The ARCH variable during the compilation was overwritten with i686 which failed recordmcount.pl Change: Removed the ARCH variable in the Makefile as it is not used Impact: ALL
2. Problem: Cont00047900 - bnx2x panic observed after booting via iSCSI boot Cause: The previous fix had a bug where the IP ADDRESS was wrong Change: Fixed the IP ADDRESS bug in the HOST_PARAM Impact: ALL
Version 2.1.2m (Jul 20, 2010) ==============================
Fixes ===== 1. Problem: Cont00047900 - bnx2x panic observed after booting via iSCSI boot Cause: The RQEs were not being freed for unsolicited NOP-Ins Change: Fixed 2 bugs in the NOP-In handling. Modified the conn_bind routine to detect and perform a chip cleanup on the stale endpoints. Added temporary workaround for the HOST_IPADDRESS parameter Impact: ALL
Version 2.1.2l (Jul 15, 2010) ==============================
Fixes ===== 1. Problem: Cont00041327 - Need Ability to Identify Adapter iSCSI Offload Capabilities Cause: This CQ was resolved in t5.2 but did not work on distro that uses a single transport name such as SLES11 Change: Modified the driver to examine the iSCSI offload license upon bnx2i_start. This will prevent the adapter from appearing in the /sys/class/iscsi_host/hostN entry. Impact: ALL
Enhancements ============ 1. Fixed potential kernel panic caused by stale pointer dereferencing from elements in the ofld_list whenever cnic fails the ofld request
2. Modified ep_connect/ep_disconnect to guard against asynchronous calls from the iSCSI daemon during NETDEV_GOING_DOWN->NETDEV_DOWN
Version 2.1.2k (Jun 30, 2010) ==============================
Enhancements ============ 1. Added ep_active_list to replace active_sess code 2. Optimized the HOST_PARAM_IP_ADDRESS retrieval code to use ep_active_list 3. Added module param ooo_enable to enable the TCP out-of-order feature for iSCSI offload (default = 1) 4. Restored the disconnect timeout for 5771X back to 20s as CONN_DISCON timeouts were observed
Version 2.1.2j (Jun 18, 2010) ==============================
Fixes ===== 1. Problem: Cont00046648 - CID Leakage occurs while running iLab test 5.12 (connection closure scenarios) rework Cause: The new bnx2x driver 1.60.24 has changed the max FIN disconnect timeout down to 6s instead Change: Modified the disconnect timeout for 5771X back to 10s Also modified the clean up procedure for the case where the iSCSI daemon is slow or not operational for bnx2i_stop Impact: ALL
2. Problem: Cont00044011 - Cannot obtain max number of sessions when changing sq_size to 16 for 5708 Cause: The driver has capped the number of max commands to sq_size/2 unnecessary Change: Restored the cmds_max = sq_size instead of num_ccells Impact: ALL
Version 2.1.2i (Jun 10, 2010) ==============================
Fixes ===== 1. Problem: Cont00046648 - CID Leakage occurs while running iLab test 5.12 (connection closure scenarios) Cause: Still occurred with the piggybacked FIN on logout responses Change: Extended the disconnect timeout for 5771X to 20s to accommodate for the worse case firmware disconnect timeout of 16s Impact: 5771X
Enhancements ============ 1. Correspondingly extended the per connection clean up timeout to 20s
Version 2.1.2h (Jun 04, 2010) ==============================
Fixes ===== 1. Problem: Cont00047973 - 57711E: Kernel panic when running iLab automated test 6.14 (iProt's delayed logout response) Cause: The open-iscsi stack's 15s logout timeout has expired and a disconnect request was forced prior to the delayed logout response is received. This has created a stale pointer deferencing in the libiscsi stack Change: Modified the disconnect path to handle logout req/resp accordingly. Also suspend the rx endpoint for disconnect timeout conditions to prevent stale pointer dereferencing in libiscsi Impact: 5771X
2. Problem: Cont00046648 - CID Leakage occurs while running iLab test 5.12 (connection closure scenarios) Cause: Reset completion was received instead of close complete kcqe while the driver is engaged in connection close request Change: Modified various graceful/abortive local/remote connection termination code path for both 1g/10g This works in conjunction to the new cnic changes Impact: All
Enhancements ============ 1. Added HOST_IP_ADDRESS in sysfs
Version 2.1.2g (May 26, 2010) ==============================
Fixes ===== 1. Problem: Cont00047794 - Linux-iscsi: Everest always terminates the iSCSI connection (logout) with a reset packet Cause: The code to decide to perform a graceful vs abortive termination did not take into account this situation where a remote close indication happened prior to the locally initiated termination sequence Change: Modified the code which decides to perform a graceful vs abortive termination to account for this scenario Impact: All
2. Problem: TCP timestamp module param option was removed Cause: This option was added from T5.2 and have not been submitted to upstream bnx2i Change: The option has been added Impact: All
Enhancements ============ 1. Updated README
2. Added tcp_buf_size module param to control TCP Window size setting
Version 2.1.2f (May 24, 2010) ==============================
Fixes ===== 1. Problem: Cont00047901 - Linux-iscsi: Unable to initiate iSCSI connection with 57712 Cause: There was a bug in the 57712 identifier code Change: Added fix in the 57712 identifier code Impact: 57712, 57712E
Version 2.1.2e (May 21, 2010) ==============================
Fixes ===== 1. Problem: Cont00047527 - Linux-iscsi: Kernel panic after manually killing iscsid process and removing bnx2i/cnic modules Cause: The problem was caused by a race condition where the iscsid daemon tries to access the sysfs host entries while bnx2i is undergoing rmmod. Change: Return a length of 0 if the bnx2i hba has been freed or when it has already been unregistered from cnic Impact: all chipsets
2. Problem: Cont00047734 - Linux-iscsi: Kernel panic after rebooting with active iSCSI sessions Cause: The problem was caused by the stop code where the adapter state was set to down before the iSCSI daemon has a chance to perform the cleanup. Change: Added proper cleanup code in the stop routine Impact: all chipsets
Enhancements ============ 1. Added sysfs entry last_active_tcp_port to display the source TCP port info of the last iSCSI offload connection used. This is a request from iLab to test OOO.
Version 2.1.2d (May 03, 2010) ==============================
Enhancements ============ 1. Added support for 57712
Version 2.1.2c (Apr 30, 2010) ==============================
Enhancements ============ 1. Added the feature to return -EBUSY if the offload connection failure was due to the 2s CFC WAIT for iscsid.
Version 2.1.2b (Apr 22, 2010) =============================
Enhancements ============ 1. Migrated to use the new uIO method for iSCSI offload connections. 2. Removed the obsolete install_usr option (for bnx2id)
Version 1.8.13d (Apr 12, 2010) =============================
Fixes ===== 1. Problem: Cont00047101 - Linux-iscsi: Switching from offload to non-offload with OOB iscsi solution on Red hat 5.5 requires extra steps Cause: same root cause as CQ44503, makefile defines macro to use which forces driver to use scsi_transport_iscsi2 for RHEL5.4 only. Change: Update makefile to define __RHEL54_DUAL_ISCSI_STACK__ for both RHEL5.4 and RHEL5.5 Impact: Only RHEL5.5 distro, all chipsets
Enhancements ============ None
Version 1.8.13c (Mar 19, 2010) =============================
Fixes ===== 1. Problem: Cont00046658 - CID leakage occurs (submit GRC dump message from bnx2i driver) while running iLab automated test 1.1 (login/logout) Cause: 5770x firmware design is changed not to process and complete TCP_CLOSE RAMROD request after any TCP event (FIN/RST received, TCP protocol error detected, etc') occured on the connection Change: This is a big change and we feel there is a finite time delay (big enough) between iscsi logout w/o piggybacked FIN received and by the time iscsid issue ep_disconnect() during which target TCP stack can issue FIN or the RST. By design bnx2i driver issues TCP_CLOSE on a gracefully terminated iscsi session (using iscsi logout process) and for all error conditions it will issue TCP_ABORT request. So the current firmware change cause a big challenge which cannot be mitigated in the driver. Only way bnx2i driver can handle is to issue TCP_ABORT for all connection termination process whether it is graceful or abortive cleanup. This release is just a partial shutdown which will sucessfully handle iscsi logout pdu with piggybacked FIN. Further analysis and discussions is on going with the firmware team. Impact: 5771x chipset. Please refer to 'Change' section for further limitation and follow-up issues to be addressed with the firmware team.
2. Problem: Cont00046691 - Linuxiscsi: SUT became unstable and ask to run grcdump after login/logout Cause: Duplicate of Cont00046658 Change: Please refer to Cont00046658 for details Impact: 5771x chipset
Enhancements ============ None
Version 1.8.13b (Feb 04, 2010) =============================
Fixes ===== 1. Problem: 5771x doorbell page size reduced from 4096B to 128B causing iSCSI offload to break Cause: iSCSI doorbell calculation has to be fixed to accomodate this HSI change Change: Changed doorbell mapping code to match the HSI Impact: 5771x chipset
Enhancements ============ Add 57712 PCI ID support
Version 1.8.13a (Jan 20, 2010) =============================
Fixes ===== 1. Problem: 5771x doorbell page size reduced from 4096B to 128B causing iSCSI offload to break Cause: iSCSI doorbell calculation has to be fixed to accomodate this HSI change Change: Changed doorbell mapping code to match the HSI Impact: 5771x chipset
Enhancements ============ None
Version 1.8.12f (Jan 19, 2010) =============================
Fixes ===== 1. Problem: Cont00044986 - LinuxiSCSI:Unable to get more than a few disks when i login to Netapp setup with maxlun disks Cause: In certain configurations kernel is assigning 'shost->max_lun' a value of '8'. In most configurations is correctly assigned '512' Change: Explicitly initialized shost->max_lun to '512' when a new scsi host is allocated and initialized Impact: All chips, RHEL5.4 Linux distro
Enhancements ============ None
Version 1.8.12e (Dec 11, 2009) =============================
Fixes ===== None
Enhancements ============ Per OEM request made system log entry more administrator friendly e.g. Changed "bnx2i: hba ffff810089abdcef does not support iscsi" to "bnx2i: dev eth0 does not support iscsi"
README.TXT was updated to reflect this change.
Version 1.8.12d (Dec 09, 2009) =============================
Fixes ===== 1. Problem: Cont00044503: RHEL 5.4 x86_64 with Multiple iSCSI Errors Booting the Kernel Cause: out-of-tree bnx2i was including references to symbols in scsi_transport_iscsi1 where as iscsi_tcp was referencing the ones in scsi_transport_iscsi2. This conflict caused software and offload iscsi not to coexist Change: Modified bnx2i driver to work with scsi_transport_iscsi2. Update session/connection/endpoint setup/teardown code path to account for new data structure objects created in libiscsi2 which were not present in libiscsi1 Impact: All chips, RHEL5.4 Linux distro
Enhancements ============ None
Version 1.8.12c (Dec 01, 2009) =============================
Fixes ===== 1. Problem: Cont00041327: Linux: Need Ability to Identify Adapter iSCSI Offload Capabilities Cause: OEM's requested this feature because the driver was registering all NX2 devices with the iscsi transport layer. Change: Modified bnx2i to register only the licensed devices with iscsi transport layer. This will avoid the need for mechanism to identify licensed and unlicensed NX2 devices as only the licensed devices will appear in '/sys/class/iscsi_transport' directory. Impact: All chips, All Linux distro
Enhancements ============ None
Version 1.8.12b (Nov 09, 2009) =============================
Fixes ===== 1. Problem: Async logout with Equallogic target results in "CONN_DISCON" and "CONN_CLEANUP" timeout messages Cause: This issue was initially reported by Vmware against ESX4.5 iSCSI inbox driver. This same issue was reproduced in Linux as well. Driver was returning DID_NO_CONNECT when the session is being logging out which caused a ton of debug log from SCSI-ML. While running heavy I/O on 12 session per port and simultaneously issue async message to logout these sessions caused a huge log spew which caused 570x device interrupt to be delayed in order of 10x seconds. Change: Return DID_HOST_BUSY while session is being logged out and till either session recovers or recovery times out. Once session recovery timeout is hit driver will return DID_NO_CONNECT Impact: All chips, All Linux distro
Enhancements ============ None
Version 1.8.12a (Oct 22, 2009) =============================
Fixes ===== None
Enhancements ============ Repacking 1.8.9u as baseline for T5.2 release
Version 1.8.9u (Oct 16, 2009) =============================
Fixes ===== 1. Problem: Cont00044141 - Linux iSCSI: Kernel panic while performing cable pull test with MPIO on RHEL5.4 (swiotlb_map_sg+0x2f/0x14a) Cause: swiotlb_map_sg() crash was caused because SCSI-ML queued a command with sg_length = 0, sg_count = 1 and sg table != NULL. Driver was only looking at last 2 parameters to call pci_map_sg() or not. Follow on issue was cause by open-iscsi daemon changes, ep_disconnect() was called without calling stop_conn(). Change: Fixed driver to consider 'sg_length' before mapping SG buffers & also shost workqueue is flushed in ep_disconnect() if it is not already done so. Impact: All chips on RHEL5.4
Enhancements ============ None
Version 1.8.9t (Oct 08, 2009) =============================
Fixes ===== None
Enhancements ============ Special sections were added to list know issues and workarounds related to out-of-tree bnx2i and software iscsi coexistence issue in RHEL5.4
Version 1.8.9s (Sept 30, 2009) =============================
Fixes ===== 1. Problem: Cont00043901 - Linux iSCSI: RHEL5.4 OOB - Kernel panic during logout with iscsi-initiator-utils-6.2.0.871-0.10c Cause: Latest open-iscsi changed graceful session tear down sequence. ep_disconnect() is called before stop_conn() and this caused NULL pointer access while dereferencing conn->ep Change: check for 'conn->ep' validity before dereferencing Impact: All chipsets, RHEL5.4 only
2. Problem: Cont00043896 - Linux iSCSI: System crash with iscsi-initiator-utils-6.2.0.871-0.10c Cause: Duplicate of CQ43901. Please check CQ43901 for root cause Change: Same as CQ43901 Impact: All chipsets, RHEL5.4 only
Enhancements ============ 1. Problem: Cont00041327 - Linux: Need Ability to Identify Adapter iSCSI Offload Capabilities Cause: Refined fix which caused unlicensed device not to be unregister with iscsi transport. This is a partial fix and needs interface to be up before bnx2i loads. Complete fix will be delivered in T5.2 Change: Check for cnic_dev->mac_iscsi_conn while the device is registered as this value will be cleared during unregister_device() call Impact: All chipsets, Linux
Version 1.8.9r (Sept 27, 2009) =============================
Fixes ===== 1. Problem: Cont00041327 - Linux: Need Ability to Identify Adapter iSCSI Offload Capabilities Cause: bnx2i cannot determine license information unless the device is registered with cnic and the network port is initialized by the user (ifup). Because of limitation, driver was registering transport name for all enumerated NX2 devices Change: Driver will continue to register all devices at init time and unregister the transport name when license information is available and found the device is not licensed for iSCSI. This eliminates the need for a separate means to identify if device support iSCSI or not. Impact: All chipsets, Linux
Enhancements ============ None
Version 1.8.9q (Aug 31, 2009) =============================
Fixes ===== 1. Problem: Cont00043282 - linux:iscsi_offload:can not modporbe bnx2i after installation of linux-nx2 v5.2.6 on RH 5.4 Cause: RHEL5.4 has 2 sets of scsi_transport_iscsi and libiscsi modules, second modules added specifically to support inbox bnx2i. With the current service load order, scsi_transport_iscsi2 gets loaded before bnx2id service is started. Initially bnx2id was chosen to be loaded after network service is started because of dependency of bnx2/bnx2x. Now that cnic driver implements weak symbol linking with bnx2/bnx2x, we can load cnic, bnx2i modules (start bnx2id service) much before network service Change: start bnx2id service before iscsi/iscsid services Impact: All chipsets, Linux
Enhancements ============ None
Version 1.8.9p (Aug 17, 2009) =============================
Fixes ===== None
Enhancements ============ Updated README.TXT to reflect new combined packaging. nextreme2- and ported a bug fix related to doorbell register mapping in IA64 architecture
Version 1.8.9o (Jul 25, 2009) =============================
Fixes ===== 1. Problem: Cont00042502 - Linux iSCSI HBA: SUT kernel panics after test I/O is started Cause: MPP driver failed to honor bnx2i's 'sg_tablesize' and 'max_sectors' parameter causing bnx2i to overstep BD table memory. Change: Workaround is to allocate 4KB of memory for each BD table, i.e. 255 entries per table which is sufficient to handle a maximum IO size of 512KB issued by MPP Impact: All chipsets, Linux
Enhancements ============ Above change will cause bnx2i to consume little more memory than previous drivers
Version 1.8.9n (Jul 22, 2009) =============================
Fixes ===== 1. Problem: Cont00042555 - Kernel panic occurs while running iLab iSCSI automated test 6.4 (data digest error) Cause: Some tests used to hang because session recovery code never returned from wait due to sess->recovery_state mis-match Change: Fixed wait state variable to check for sess->recovery_state = 0, which is cleared when session is re-logged in Impact: All chipsets, Linux, ESX
Enhancements ============ None
Version 1.8.9m (Jul 01, 2009) =============================
Fixes ===== None
Enhancements ============ Updated Makefile in order to package bnx2i, bnx2, bnx2x and cnic together
Version 1.8.9l (June 30, 2009) =============================
Fixes =====
1. Problem: DMA memory leak and eventualy run out of memory during overnight test Cause: wrong 'size' parameter is sent to pci_free_consistent() Change: pass 'dma->size' instead of PAGE_SIZE as 2nd argument to pci_free_consistent() Impact: All chipsets, Linux, ESX
2. Problem: Linux iSCSI: Soft lockup seen while continuously restarting iscsid service overnight with persistent targets attached (bnx2i_conn_stop+0xc8/0x109) Cause: login resources allocation failure was not handled correctly in create_conn() which caused timer_del_sync() to be called on an uninitialized timer in destroy_conn() path. Change: fixed code to handle return value of bnx2i_conn_alloc_login_resources() and also added a flags to track if conn->poll_timer is initialized or not. Impact: All chipsets, Linux, ESX
3. Problem: Everest1.0:Linux iSCSI:CX4 - kernel panic while running IPv6 login/logout maxsessions stress(bnx2i_cm_remote_abort+0x23/0x41) Cause: open-iscsi does conn_stop()/conn_destoy()/ep_disconnect()/ sess_destroy() in the same order. So if remote RST/FIN is received after conn_destoy() will cause panic because driver will try to access ep->conn->worker_enabled and ep->conn is already set to NULL in conn_destoy(). We found the same issue on another test bed last evening Change: Check ep->conn in cnic upcalls for remote RST/FIN and do not start session recovery if 'ep->conn' is NULL. Also take sess->lock to synchronize remote RST/FIN and conn_destroy() accessing ep->conn Impact: All chipsets
Enhancements ============ None
Version 1.8.9k (June 02, 2009) =============================
Fixes =====
1. Problem: Cont00041700 - iSCSI Linux Offload:Everest: rmmod bnx2x or bnx2 causes system to hang Cause: hba_poll_timer is only valid for ESX Change: ifdef code valid only for ESX Impact: All chipsets, Linux
Enhancements ============ None
Version 1.8.9j (May 30, 2009) =============================
Fixes =====
1. Problem: Cont00041556 - Linux iSCSI: Kernel panic during target logout Cause: ESX change caused this issue. Method to get session pointer from iscsi_transport layer sess pointer is different for Linux and ESX, With recent changes Linux code was trying to get the sess pointer the ESX way Change: Fix the above logic Impact: All chipsets, Linux, ESX
Enhancements ============ None
Version 1.8.9i (May 26, 2009) =============================
Fixes =====
1. Problem: Cont00039906 - Linux iSCSI: Soft lockup seen when performing adapter selftest with more than 10+ sessions connected Cause: bnx2i was taking spinlock before calling cnic->register_device() and cnic would call bnx2i_start() in the same context which actually will sleep waiting for ISCSI_INIT response Change: Fix is not to hold spinlock for the duration of register_device() Impact: All chipsets, Linux, ESX
2. Problem: Cont00041210 - Everest1.0:Linux iSCSI:CX4 - kernel panic while running heavy disk traffic with bnx2i v1.8.7 (bnx2i_conn_main_worker+0x10b/0x70a) Cause: There were several bug fixes to workqueue/tasklet in last week and this panic dump is addressed by it Change: Changes made to support tasklet implementation for ESX broke some of the logic. Cleaned up a bunch of issues related to this Impact: All chipsets, Linux, ESX
Enhancements ============ More stable ESX code with tasklet implementation and enhanced task management code. Build 00005 is based on this code. Some of the tasklet and workqueue bug fixes are applicable to both ESX and Linux
Version 1.8.7 (May 13, 2009) =============================
Fixes ===== 1. Problem: Various driver crashes in error recovery path Cause: tasklet/workqueue are scheduled when connection is in stopped state. Change: Not to accept any commands if conn_stop() is called on the connection and this will eliminate any tasklet/workqueue scheduling. This was initially reported and more often seen in ESX, but same problem exhists in Linux as well Impact: All chipsets, Linux, ESX
Enhancements ============ Further enhancements to tasklet/workqueue code
Version 1.8.6 (May 11, 2009) =============================
Fixes ===== 1. Problem: Cont00040971 - iSCSI Boot Linux Offload:NX2: compile error with bnx2i v1.8.5 on SuSE 10 SP2 Cause: In order to support older kernel iscsi_compat.h defines some functions which should have been defined 'static' but are not. This creates trouble when scsi_transport_iscsi.h is included in multiple *.c files. Change: worked around iscsi_compat.h header file issues Impact: All chipsets, SLES10 SP2
2. Problem: Cont00040921 - ESX4.0 build 4.0.0-00000_x86_64 w/ bnx2i - iscsi_cmd_win_closed Cause: not conforming to rfc1982 Change: Fixed serial arithmetic logic as per rfc1982 Impact: ALL chipsets, Linux, ESX
3. Problem: Cont00040512 - ESX4.0 build 4.0.0-00000_x86_64 w/ bnx2i - Disks disappear after overnight stress tests Cause: tasklet was being scheduled without being enabled when connections goes into recovery mode Change: Tasklet is disabled in stop_conn() and enabled in bind_conn() Impact: All chips + ESX40U1
4. Problem: Cont00040920 - ESX4.0 build 4.0.0-00001_x86_64 w/ bnx2i - bnx2i_process_new_cqes+0x7b Cause: This issues is seen only in workqueue implementation for ESX as scsi_host workqueue was not flushed fearing it would affect other connections. But would cause work to be scheduled after connection is torn down or in middle of recovery process Change: per connection tasklet implementation will not exhibit this failure as tasklet is disable in conn_stop() and re-enabled in conn_bind() Impact: All chipsets, ESX40U1
5. Problem: Cont00040918 - ESX4.0 betabuild 4.0.0-00001_x86_64 w/ bnx2i Cause: Duplidate of Cont00040920, please refer to Cont00040920 for more details Change: Duplidate of Cont00040920, please refer to Cont00040920 for more details Impact: All chipsets, ESX40U1
Enhancements ============ ESX40U1 driver changes to use tasklet instead of workqueue for command transmission and CQE processing.
Version 1.8.5 (Apr 29, 2009) =============================
Fixes ===== None
Enhancements ============ ESX40U1 driver changes to match the updated iscsi_net API's
Version 1.8.4 (Apr 29, 2009) =============================
Fixes ===== 1. Problem: Connection setup problems with 570x Cause: Changes to 570X_SQE_DEFAULT macro caused alternate connections to fail Change: reverted back 570X_SQE_DEFAULT to 128 Impact: 5706/5708/5709
Version 1.8.1 (Apr 25, 2009) =============================
Fixes ===== 1. Problem: Cont00040099 - Linux iSCSI T4.6+ 57710 performance bottleneck at 80K IOps (L2 and Offload) Cause: CQE processing in softIRQ context was becoming bottleneck because 5771x has only on MSI-X vector for iSCSI completion notification. This caused 1 core to be pegged 100% processing completions. Change: Implemented a per connection workqueue to process both command request and completion. This spreads work load to across available cores and boosted IOPS numbers to nearly at par with what should be Impact: 57710/5771/57711E
Version 1.8.0 (Apr 22, 2009) ============================
Fixes ===== 1. Problem: Cont00040267: Linux iSCSI: Kernel panic during cable pull with one iSCSI over native TCP connection + iSCSI offloaded connection Cause: iscsi daemon is calling iscsi_transport->ep_poll() with ep_handle=0xffffffff eventhough driver failed ep_connect() request. This causes ep_poll() to access invalid memory and cause the crash Change: Add additional check to ignore both ep_handle = 0xffffffff and null pointer Impact: 5706/5708/5709/57710/5771/57711E
Enhancements ============ changed pci dma memory management code to be more stream lined
Version 1.7.0 (Mar 17, 2009) ============================
Fixes ===== 1. Problem: Cont00039999 - Linux iSCSI: Usages count increases for bnx2x when iSCSI sessions are connected via Teton/Xinan devices Cause: Before looking up the route to target IP, there is a requirement that bnx2i has to register with cnic all active devices. cnic won't identify the device if the device is not registered. So when the first connection is offloaded, bnx2/bnx2x module usage count will be incremented once for every corresponding NX2 device in the system even though connection is offloaded on only one. This usage counts will be later decrement to zero when the last connection is torn down. Change: Fix is the unregister all idle devices before returning from ep_connect() Impact: 5706/5708/5709/57710/5771/57711E
2. Problem: Cont00040037 - Linux iSCSI: Need jumbo frame support for Linux iSCSI offload in T5.0 Cause: bnx2i was checking and not allowing connection offload is device's MTU is set to > 1500 Change: changed maximum MTU limit to 9000B Impact: 5706/5708/5709/57710/5771/57711E
3. Problem: Cont00039906 - Linux iSCSI: Soft lockup seen when performing adapter selftest with more than 10+ sessions connected Cause: Multiple problem caused this issue - big connection teardown/ cleanup timeout in bnx2i and bnx2 was swutching off interrupts before propogating stop() call to ULPs Change: bnx2 driver code was reordered to keep interrupts enabled during ULP's stop() call and bnx2i driver timeouts are tuned based on device type Impact: 5706/5708/5709
4. Problem: Cont00039648 - Linux iSCSI: Please add line in README.TXT that states ipv6.ko is a requirement for cnic to load Cause: Documentation enhancement request Change: updated README.TXT to reflect the dependency requirements Impact: 5706/5708/5709
Enhancements ============ None
Version 1.6.2 (Mar 10, 2009) ============================
Fixes ===== 1. Problem: Cont00039912 - Linux iSCSI accel - unable to offload on NC532i, says iSCSI not supported Cause: mismatch in PCI Id definition between system include and driver source Change: fixed the mismatch Impact: 57711/57711E
Enhancements ============ None
Version 1.6.1 (Feb 23, 2009) ============================
Fixes ===== 1. Problem: Performance on 5606/5708 is sluggish & session keeps recovering Cause: 5706/5708 firmware can only handle 172 CQ entries and Everest requirements of SQ/CQ to be integral number of pages was causing this issue and 570x family has no such requirements Change: Execute SQ/CQ size massaging code for 5771X device type only Impact: 5706/5708
Enhancements ============ None
Version 1.6.0 (Jan 14, 2009) ============================
Fixes ===== 1. Problem: Cont00038728 - Linux iSCSI:Everest:A1: iscsiadm becomes unresponsive if wrong transport name is used Cause: There was a list corruption in open-iscsi daemon code caused when list element is blindly initialized when it is actually a node in the pend_list. Also conn->link was not initialized when bind_conn() failed which caused crash in destroy_conn() code path. Change: Fixed both open-iscsi user daemon and driver issues Impact: 57710/57711E
Enhancements ============ Updated copyright information
Version 1.4.9 (Jan 03, 2009) ============================
Fixes ===== 1. Problem: CQ38744 - Everest1.5:Linux iSCSI:CX4 - Unable to connect to more than ~450 sessions, out of host memory Cause: Linux kernel can only address 1G memory which includes all kernel code and data structures. This limitation would not allow us to offload 1024 iscsi connections Change: Limit number of outstanding tasks (SQ size) per connections to 64 Impact: 57711E
Enhancements ============ None
Version 1.4.8 (Dec 31, 2008) ============================
Fixes ===== 1. Problem: CQ38744 - Everest1.5:Linux iSCSI:CX4 - Unable to connect to more than ~450 sessions, out of host memory Note: This is 1 of 3 fixes made to support 1024 connections. Refer to bnx2i-1.4.7 & netxtreme2-1.8.2c_1.48.7 release notes for other changes Cause: 992 connections limitation was due to limit on max numbers of file descriptors 'bnx2id' application was allowed to open. Default value is 1024, so bnx2id was able to allocate 1023 socket structures and last 31 were not even delivered because the daemon was unable to open char device to issue ioctl. So driver ended up with only 992 tcp ports. Change: Modified application to change RLIMIT_NOFILE parameter to 1056. With this change we were able to successfully open 1024 connections using 57711E device on a x86_64 system Impact: 57711E
Enhancements ============ Updated rc script to create '/dev/bnx2i' node during startup
Version 1.4.7 (Dec 29, 2008) ============================
Fixes ===== 1. Problem: Unable to allocate endpoint structure for 513th connection Cause: Driver was allocating a total of 512 endpoint structures due to a macro definition Change: defined ISCSI_MAX_ADAPTERS to 8 Impact: 57711E
Enhancements ============ None
Version 1.4.6 (Dec 22, 2008) ============================
Fixes ===== 1. Problem: Cont00038965 - Everest1.5:Linux iSCSI:CX4 MF- bnx2i cid TCP errors while running iSCSI + netperf stress traffic Cause: queuecommand() would report device offine when sess->lead_conn->ep is NULL. But actually this value will be NULL between the time existing endpoint (EP) is cleaned and a new endpoint is bound in bind_conn() call. This is a valid transient state during connection recovery and driver is suppose to report BUSY and not NO_CONNECT Change: reverted back to old scheme Impact: 5706/5708/5709/57710/57711
Enhancements ============ None
Version 1.4.5 (Dec 17, 2008) ============================
Fixes ===== 1. Problem: Driver crash when interface IP address is changed while there are actice connection Cause: spinlock contention Change: fixed spinlock contention Impact: 5706/5708/5709/57710/57711
Enhancements ============ None
Version 1.4.4 (Dec 11, 2008) ============================
Fixes ===== 1. Problem: Cont00038936 - LinuxiSCSI: bnx2x Firmware crash dump when loging out of EMC target Cause: Incorrect handling of TCP CONNECT failure caused iscsid to behave improperly with follow on connections, ep_disconnect() was getting called just 1-sec after ep_connect(). According to implementation it should wait 15-secs before timing out, while firmware times out in 9-secs (3 attempts at 3-sec interval). So driver doesn't expect ep_disconnect() to be called before 10-secs after ep_connect() returns Change: Fixed handling of TCP CONNECT failure in driver which avoids 'iscsid' to get into weird state. Also even though ep_disconnect() is called immediately, driver will wait for firmware to complete TCP_CONNECT request with either good or failed status before going ahead with connection cleanup Impact: 5706/5708/5709/57710/57711
2. Problem: Cont00038965 - Everest1.5:Linux iSCSI:CX4 MF- bnx2i cid TCP errors while running iSCSI + netperf stress traffic Cause: Recently changed queuecommand() to report device office if session is not in FFP stage. Actually we have to report device offline only after session recovery timeout (120-secs) is reached Change: reverted back to old scheme Impact: 5706/5708/5709/57710/57711
Enhancements ============ None
Version 1.4.3 (Dec 09, 2008) ============================
Fixes ===== 1. Problem: Cont00038871 - Everest1.5:Linux iSCSI:CX4 MF- CONN_DISCON timeout + bnx2x driver assert during cable pull test Cause: Due to open-iscsi interface change, NOOP OUT was not working as expected. open-iscsi user stack added following connection params to determine if NOOP is supported in user daemon or the kernel driver - 1. ISCSI_PARAM_PING_TMO 2. ISCSI_PARAM_RECV_TMO As bnx2i depends on iscsid to implement this feature, it should return -ENOSYS to set_param() call to update above said parameters. Change: After implementing this change, iSCSI NOOP OUT started to behave as expected. Impact: 5706/5708/5709/57710/57711
2. Problem: Cont00038797 - LinuxiSCSI:Segmentation fault when running ifup/down and passing traffic Cause: Partly caused by NOOP OUT issue explained above (Cont00038871) and other issue was not guarding 'active_sess' list while traversing in bnx2i_start_hba_shutdown() routine & not properly handling in-recovery state in TMF code path Change: Fixed above said conditions Impact: 5706/5708/5709/57710/57711
Enhancements ============ None
Version 1.4.2 (Dec 03, 2008) ============================
Fixes ===== 1. Problem: Everest1.5:Linux iSCSI:CX4 - bnx2x driver assert while changing MTU size with targets connected Cause: Issue was cause by mutex lock deadlock condition in cnic when unregister_device() is called while bnx2i is still in cnic_stop() function call processing. Change: This issue is worked around in bnx2i by deferring inactive device unregistering till all the connections are torn down Impact: 57711
Enhancements ============ None
Version 1.4.1 (Nov 17, 2008) ============================
Fixes ===== 1. Problem: Cont00038537 - Everest 1.5E MF-Linux iSCSI: Unable to iSCSI login to target Cause: bnx2i was requesting a large number of TCP ports than bnx2id can allocate. Change: bnx2i is changed to request 32 TCP ports at a time. Eventually bnx2id will be fixed to handle socket()/bind() call failure Impact: 57711
Enhancements ============ Added support for 57711
Version 1.4.0 (Nov 14, 2008) ============================
Fixes ===== None
Enhancements ============ Added support for 57711
Version 1.3.11 (Nov 12, 2008) =============================
Fixes ===== 1. Problem: Cont00038195 - LinuxiSCSI:Bnx2x kernel panic when running read/write test or when the target became unaccessible Cause: There was a possibilty driver will unregister with cnic before all the connections are cleaned up. For such connection only driver resources are freed in ep_disconnect(). Driver assumes chip will be reset when ifdown request is completed and this is true for 5706/5708/5709. However in case of 57710 certain blocks such as CFC/SEARCHER will not be reset if second port is up. Change: So driver will have to wait for all connections to cleanup before returning from NETDEV_GOING_DOWN notification. Also driver will block scsi host before entering clean mode to avoid any futher scsi command being queued with the driver Impact: 57710
2. Problem: Cont00038030 - LinuxiSCSI: Data corruption writing to iscsi target Cause: In Couple of scenarios driver was accessing memory immediately after freeing. Also in wrong memory was cleared because of wrong array index (control bits of ITT was not cleared in case of aborted commands. This would cause when a write command is aborted) Change: Rearranged memory resources freeing and cleaned ITT table indexing code Impact: 57710
Enhancements ============ Enforce max SQ size of 128 for 5706/5708/5709 devices and also adjust to power of 2.
Version 1.3.10 (Oct 28, 2008) =============================
Fixes ===== None
Enhancements ============ Update RPM dependency in bnx2i.spec file from NetXtremeII to netxtrem2
Version 1.3.9 (Oct 28, 2008) =============================
Fixes ===== None
Enhancements ============ Fixed a race condition causing kernel dump when a netdev/inet event is received while session is being torn down. Durning iscsi session tear down process, open-iscsi stack will execute tasks in following order - 1) iscsi logout 2) destroy iscsi connection 3) tear down endpoint (TCP connection) 4. destroy iscsi session
This issue will manifest when a netdev/inet event is received b/w #2 and #4
Version 1.3.8 (Oct 26, 2008) =============================
Fixes ===== None
Enhancements ============ Updated RPM spec file to reflect module dependency to NetXtemeII instead of bnx2/bnx2x
Version 1.3.6 (Oct 16, 2008) =============================
Fixes ===== 1. Problem: Cont00037814 - Linux iSCSI:Everest:A1: Kernel panic when running dt during max sessions test (cnic:cnic_get_bnx2x_ctx+0x59/0x6e) Cause: Couple of issues attributed to this issue, 1. bug in ep structure handling code in bnx2i driver 2. memory corruption due to boundary over stepping in bnx2x driver (fixed in 1.46.9) Change: revamped endpoints offload / destroy list handling code Impact: 57710
2. Problem: Cont00037858 - Linux iSCSI:Everest:A1: bnx2i: ofld_timer: CONN_DISCON timeouts when running login/logout continuously to max number of sessions Cause: bug in ep offload / destroy list handling code in bnx2i driver Change: revamped endpoints offload / destroy list handling code Impact: 57710
3. Problem: Cont00037701 - LinuxiSCSI:EverestA1: Kernel Panic whe running traffic on both ports Cause: same as Cont00037814 Change: see Cont00037814 above Impact: 57710
Enhancements ============ Updated driver logs section in README.TXT
Version 1.3.5 (Oct 06, 2008) =============================
Fixes ===== 1. Problem: Cont00037576 - Linux iSCSI:Everest:A1: Unable to connect to more than 64 sessions per port Cause: With 8 pages limit driver was able to allocate only 72 endpoint structures. Change: Doubled number of pages used for endpoint structures to 16 Impact: 57710
2. Problem: Test 5.9 failure with kernel panic Cause: Incorrect handling in error path was causing SCSI-ML to free device resources while some commands are still active. Thus causing kernel panic when driver tried to unmap SG list at a later point in time Change: cleaned up session recovery path and cleanup active command list in case host_reset() failed. Impact: 57710
Enhancements ============ Increased TCP CLOSE timeout to 20-secs from 10 -secs to be in sync with firmware limits
Version 1.3.4 (Sept 26, 2008) =============================
Fixes ===== 1. Problem: Cont00037386 - Linux iSCSI: Installing drivers via source tarball will not create a bnx2id startup script Cause: Previous release was partially fixed and user still need to run 'chkconfig' to get it to work Change: Added 'chkconfig' to fix the issue properly Impact: 5706/5708/5709/57710
2. Problem: Cont00037576 - Linux iSCSI:Everest:A1: Unable to connect to more than 64 sessions per port Cause: It was hardcoded in header file Change: Fixed code to limit 64 simultaneous iscsi connection on 5706/5708/5709 and 128 connection on 57710 Impact: 57710
Enhancements ============ Increased num outstanding tasks (SQ size) to 256 for 57710. 570x still has SQ size of 128
Version 1.3.3 (Sept 22, 2008) =============================
Fixes ===== 1. Problem: Cont00037386 - Linux iSCSI: Installing drivers via source tarball will not create a bnx2id startup script Cause: In previous release only carried partial fix by installing only the binary, 'bnx2id' and not the init script Change: updated makefile to copy init script along with 'bnx2id' binary when 'install_usr' build target is issued. This was initially fixed in 1.2.12 and got omitted in later releases Impact: 5706/5708/5709/57710
Enhancements ============ Added debug prints in ep_connect() and ep_disconnect() code path to easily identify option-2 related issues
Version 1.3.2 (Sept 14, 2008) =============================
Fixes ===== None
Enhancements ============ 1) Inserted BUG_ON() to trap TCP disconnect timeout 2) Turned off TCP timestamp and fixed receive window to 256K 3) Added code to replenish RQ buffers before issuing any iscsi requests
Version 1.3.1 (Aug 07, 2008) =============================
Fixes ===== 1. Problem: Cont00035910 - LinuxiSCSI:Kernel panic when running login/logout with 64 sessions Cause: iop mapped memory for connection doorbells was not unmapped and also a small piece of memory was not freed. This caused a slow memory leak and eventually system would run out of memory Change: Fixed memory leak issue Impact: 5706/5708/5709
Enhancements ============ Updates README.TXT file to add 'iface' usage with examples. Fixed a critical corruption issue caused by memset() while clearing SQ/RQ/CQ page table for 57710 devices, failed to adjust actual size of page table which starts at an offset of DB structure size from the base address.
Version 1.2.14 (June 20, 2008) =============================
Fixes ===== None
Enhancements ============ Updates README.TXT file to clarify Broadcom iSCSI Offload software suite loading process. Fixed init rc script to manually unload bnx2i and cnic driver when bnx2id service is stopped. Earlier we would do 'modprobe -r' which could potentially unload bnx2 module and even bring the network interface down. 'service bnx2id stop' is only intended to unload iscsi(storage) modules, keeping networking components intact.
Version 1.2.13 (June 19, 2008) =============================
Fixes ===== 1. Problem: Cont00035285 - DF216309: Open iSCSI Initiators Not Provided for RHEL5.2 and SLES10.2 Cause: This was caused by interface change resulted in changes in iscsi transport. This caused a data structure to be referenced after being freed. Change: Fixed session teardown code take care of this interface change Impact: SLES10 SP2 and 5706/5708/5709
Enhancements ============ Removed all references to 57710 in README.TXT file and going forward Broadcom will release single iscsi-initiator package for Redhat EL 5.0, 5.1 and 5.2
Version 1.3.0 (June 02, 2008) =============================
Fixes ===== None
Enhancements ============ Complete support for 57710 added
Version 1.2.12 (May 23, 2008) =============================
Fixes ===== 1. Problem: Cont00035452 - Linux iSCSI: Installing drivers via source tarball will not create a bnx2id startup script Cause: In previous release only carried partial fix by installing only the binary, 'bnx2id' and not the init script Change: updated makefile to copy init script along with 'bnx2id' binary when 'install_usr' build target is issued Impact: 5706/5708/5709
Enhancements ============ None
Version 1.2.11 (May 22, 2008) =============================
Fixes ===== 1. Problem: Cont00035451 - Linux iSCSI: Typo in line 29 of bnx2id startup script Cause: typo Change: fixed the comment line in code Impact: 5706/5708/5709
2. Problem: Cont00035292 - Unnecessary Set Group ID Permission in bnx2i Source Cause: file permissions got changed unintentionally Change: set correct file permissions for source code files Impact: 5706/5708/5709
3. Problem: Cont00035452 - Linux iSCSI: Installing drivers via source tarball will not create a bnx2id startup script Cause: not implemented Change: added 'install_usr' command to Makefile and document the required steps in README text Impact: 5706/5708/5709
Enhancements ============ None
Version 1.2.10 (May 14, 2008) =============================
Fixes ===== 1. Problem: Cont00035222 - DF215961: Cannot Compile bxn2i-1.2.8 on SLES10sp2 Cause: SLES10SP2 back ported create_session() to include 2 additional arguments and thus causing minor compilation warning. Also it would create problems when use attempts to establish an iscsi connection Change: Modified makefile to detect number of argument to create_session by looking at function prototype in header file, include/scsi/scsi_transport_iscsi.h Impact: 5706/5708/5709, uses 'awk' to parse the header file efficiently
Enhancements ============ None
Version 1.2.9 (May 08, 2008) ============================
Fixes ===== 1. Problem: Cont00035222 - DF215961: Cannot Compile bxn2i-1.2.8 on SLES10sp2 Cause: Similar to Cont00035035, but SLES10 update 2 back ported scsi_set_resid & scsi_get_resid and placed them in include/scsi/iscsi_compat.h whereas RHEL 5.2 put them in include/scsi/scsi_cmnd.h Change: Modified makefile to accommodate these differences Impact: 5706/5708/5709
2. Problem: Cont00034621 - Linux iSCSI Xinan: Multiple iSCSI sessions occasionally do not recover after cable pull Cause: Sending TCP_RESET KWQE on a connection for which option-2 connect was not initiated (TCP_CONNECT 1/3) caused neighboring iscsi connection context memory to corrupt Change: bnx2i will not issue cm_abort() if option-2 connect was not successful, it will directly send request to destroy the context Impact: 5709
3. Problem: Cont00034872 - Linux iSCSI Xinan: Target does not recover when running MPIO over both Xinan ports Cause: duplicate of Cont00034621 Change: See Cont00034621 for details Impact: 5709
Enhancements ============ None
Version 1.2.8 (May 02, 2008) ============================
Fixes ===== 1. Problem: Cont00034848 - Linux iSCSI Xinan: No network activity (possible chip lockup) after running pqa script (test 6.1-- Errors from initiator to target) in a loop using IPv6. Cause: wrong ITT was posted with login request causing 5709 firmware to hang. This was caused because upper 2-bits weren't clearing before putting aborted SCSI WRITE command's ITT to free list. Same issue won't happen if aborted command was a SCSI READ, because command type field is '0' for read commands. Also normal scsi completion won't suffer the same as driver clears this field before starting completion processing Change: Driver clears command type fields whenever freeing an ITT value Impact: 5709
2. Problem: Cont00035035 - DF214119: bnx2i-1.2.7 Fails to Compile on RHEL5.2-snapshot6 Cause: Newer Linux api functions, scsi_set_resid() and scsi_get_resid() were back ported to 2.6.18-88 kernel in RHEL5.2 resulting in compilation errors because of duplicate definitions Change: worked around in make file. This is a tricky issue caused by distro's backporting newer features back to older kernels. This causes following scenario - 1. RHEL 5.1 kernel 2.6.18-53 does not define these functions 2. RHEL 5.2 kernel 2.6.18-88 does define these functions 3. kernels 2.6.19.x to 2.6.22.x does not define it 4. kernel 2.6.23.x+ is part of kernel by default This makes it hard as it can't be determined whether to define ourselves or use kernel api's based on linux version as LINUX_VERSION takes into account only first 3 bytes out of 2.6.x-y. We counter this by greping for function prototypes in the include directory and based on grep result define macros which facilitates either local definition or references the kernel api's Impact: 5709
3. Problem: Cont00034274 - Linux iSCSI: Running heavy stress on multiple sessions causes connection resets and other errors Cause: duplicate of Cont00034848 Change: duplicate of Cont00034848 Impact: 5709
4. Problem: Cont00034977 - B57DELLCDT447 Contains Two Different Open iSCSI Packages for RHEL5 Cause: Two open-iscsi packages are for RHEL5.0 and RHEL5.1 Change: updates README text file to reflect the importance of two RHEL related open-iscsi packages Impact: NA
5. Problem: Cont00035034 - DF213523: Offload Driver (bnx2i) not getting installed on RHEL5.2 Cause: Duplicate of Cont00035035, package manager was not able to install the driver because non was built due to compilation error Change: Duplicate of Cont00035035, package manager was not able to install the driver because non was built due to compilation error Impact: NA
Enhancements ============ User will be able to compile and install bnx2i on RHEL5.2, but would like to remind users/OEMs that RHEL5.2 does not feature in supported distributions list for this release and only minimal validation is achieved.
Version 1.2.7 (Apr 10, 2008) ============================
Fixes ===== 1. Problem: Cont00034704 - Linux iSCSI Xinan: Target occasionally does not recover when running ifup/down Cause: This is an expected behavior based on the very nature of the test script and environment. Test script continously toggles the interface up & down with a time difference of 1-sec. Also the interface is configured to aquire IP address via' dhcp, which actually takes upto several seconds. So iSCSI stack will hardly get a chance to reconnect to target lun and after 120-secs SCSI disk will be taken offline Change: Not applicable (not a bug) Impact: 5709
2. Problem: Cont00034705 - Linux iSCSI: Errors seen when running ifup/down with multiple targets attached Cause: logic issue where a loop variable is not reset for each session processing causing 2nd and subsequent sessions to be retried for infinitely long time. Change: fixed the logic Impact: 5709
Enhancements ============ None
Version 1.2.6 (Apr 07, 2008) ============================
Fixes ===== 1. Problem: Cont00034260 - Linux iSCSI: Kernel panic while performing ifup/down with target connected Cause: Shutdown thread was waiting for 10-secs for iscsi driver to cleanup all active session whereas ep_disconnect() thread also has 10-sec timeout for TCP connection shutdown. This was causing shutdown thread to return before connection context destruction Change: TCP connection termination timeout is set to a lower value Impact: 5709
Enhancements ============ None
Version 1.2.5 (Apr 03, 2008) ============================
Fixes ===== 1. Problem: Cont00034315 - Linux iSCSI Xinan: Scanning disks during max sessions test causes connection problems Cause: CID range allocated by cnic driver was not in sync with firmware expectation causing firmware to allocate CID range for which memory is not allocated by the driver Change: sync'ed driver range with the firmware range Impact: fixes host memory corruption caused by this mis-match
2. Problem: Cont00034260 - Linux iSCSI: Kernel panic while performing ifup/down with target connected Cause: Timing issue caused cnic driver to free resources & stop hardware while bnx2i is still registered. This resulted in cnic driver crash when bnx2i calls cm_destroy() api call to free 'cnic_sock' Change: During repetitive shutdown process driver avoids async events such as connection completion notifications, teardown and connection destroy taks and relies on top level session freeze to keep sanity Impact: Fixes system crash
3. Problem: Cont00031780 - LinuxiSCSI:Unable to load bnx2id from iscsiBoot on suse X86-64 Cause: RPM package was only install 32-bit version of 'bnx2id' and relied of COMPAT feature in kernel module for interoperability. However bnx2i source package did included a 64-bit version of the binary and user was expected to install manually by hand Change: RPM install script is modified to install 'bnx2id' binary based on system architecture Impact: Manual installed required to get iSCSI boot for 64-bit architecture is no more required
4. Problem: Cont00033922 - Linux iSCSI Xinan: Kernel oops when doing "service network restart" Cause: duplicate of Cont00034260 Change: refer to Cont00034260 for more details Impact: refer to Cont00034260 for more details
5. Problem: Cont00031404 - Linux iSCSI: A successful login occurs eventhough initiator receives login response with T-bit and C-bit set to 1 Cause: open-iscsi user daemon wasn't validating (C-bit && T-bit) on received login response Change: updated open-iscsi code to accomodate this in 6.2.0.742-0.6c (RHEL5.0), 6.2.0.865-0.8b (RHEL 5.1) Impact: minimal
6. Problem: Cont00034385 - DF205266: DKMS RPM for bnx2i will not install with bnx2 and bnx2x present Cause: install script was running 'rpm -qa | grep "bnx2.*rpm"' to determine multiple instances of bnx2 RPM is installed. But 57710 dkms rpm is named "bnx2x-*" which also matches the previous expression misleading script to believe multiple instance of same driver. Change: Modified the search pattern to avoid pitfall Impact: DKMS
7. Problem: Cont00034316 - LinuxiSCSI: When installing bnx2i rpm package on Linux-64, it does not install bnx2id64, iscsiboot needs bnx2id64 Cause: RPM package was only install 32-bit version of 'bnx2id' and relied of COMPAT feature in kernel module for interoperability. However bnx2i source package did included a 64-bit version of the binary and user was expected to install manually by hand Change: RPM install script is modified to install 'bnx2id' binary based on system architecture Impact: Manual installed required to get iSCSI boot for 64-bit architecture is no more required
Enhancements ============ None
Version 1.2.4 (Mar 17, 2008) ============================
Fixes ===== Couple of issues related to PTE setup and queue size adjustments for 57710 are fixed. Also resolved issues with 'sysfs' entry being read during driver load which used to crash the system because it was triggering context stage buffer and PCI bar register access which are suppose to be initialized during iscsi conn offload process. Driver now checks and returns error if the context stage buffer or the pci bar mapping is not present
Enhancements ============ None
Version 1.2.3 (Mar 10, 2008) ============================
Fixes ===== 1. Problem: Cont00034202 - linuxiSCSI:bnx2i failed to compile on SLES10SP1 X86-64 Cause: missing pci definition due to older kernel Change: changed code to include 'resource_size_t' only if running Linux kernel >= 2.6.18 Impact: SLES 10u1 testing
Enhancements ============ None
Version 1.2.2 (Mar 10, 2008) ============================
Fixes ===== None
Enhancements ============ Modified code to rearrange additional 'iscsi_kwqe_conn_offload3' to include first RQ PTE followed by first CQ PTE [1 - 7]. As we don't intend to include multiple CQ per connection in initial release, bnx2i will only send '1' additional 'iscsi_kwqe_conn_offload3'
Version 1.2.1 (Feb 27, 2008) ============================
Fixes ===== None
Enhancements ============ Added docbook style function & structure definition header and defined new kwqe 'iscsi_kwqe_conn_offload3' required for offload support on 57710
Version 1.2.0 (Feb 21, 2008) ============================
Fixes ===== None
Enhancements ============ Added initial code to support 57710 device
Version 1.1.8 (Feb 20, 2008) ============================
Fixes ===== 1. Problem: Cont00033893 - Linux iSCSI: bnx2id does not automatically get loaded with v1.1.5 Cause: init scripts, bnx2id.redhat & bnx2id.suse included in v1.1.5 was in DOS file format, for that reason it was not executed during system boot Change: Converted init scripts to UNIX format Impact: 5708/5709 iscsi testing
Enhancements ============ None
Version 1.1.7 (Feb 20, 2008) ============================
Fixes ===== 1. Problem: Cont00033898 - Linux iSCSI: kernel panic when connecting to targets with bnx2i v1.1.5 Cause: Timing issue caused by new interface change b/w bnx2i/cnic/bnx2 Earlier 'pcidev' was available when NX2 device is presented to bnx2i and recently CNIC was modified to expose 'pcidev' only after bnx2i registers the device. But it could happen interrupt is processed in register device context causing kernel panic Change: bnx2i HBA adapter and pci_dev binding is determined in bnx2i_start() instead of waiting for register_device() compl. It is gauranteed bnx2i_start() is called before CNIC interrupts are enabled on the device. Impact: 5708/5709 iscsi testing
Enhancements ============ None
Version 1.1.6 (Feb 19, 2008) =============================
Fixes ===== 1. Problem: Cont00033899 - Linux iSCSI: RPM build errors on SLES10 SP1 with bnx2i v1.1.5 Cause: missing PCI id macro for 5709 in pci_ids.h header file Change: If not defined driver will define the macro to support older kernel such as 2.6.16 carried by SUSE 10SP1 Impact: 5709 testing on SUSE10 SP1
Enhancements ============ None
Version 1.1.5 (Feb 13, 2008) =============================
Fixes ===== None
Enhancements ============ bnx2i module is completely de-linked from bnx2 driver. Also bnx2i is modified to adhere to new cnic driver interface specification
Version 1.1.4 (Jan 25, 2008) ============================
Fixes ===== None
Enhancements ============ IPv6 support added.
Version 1.1.2 (Dec 06, 2007) =============================
Fixes ===== 1. Problem: Cont00031780 - LinuxiSCSI:Unable to load bnx2id from iscsiBoot on suse X86-64 Cause: missing 32-bit compat libraries Change: use 64-bit binary distributed in the package Impact: Use 64-bit 'bnx2id' binary in iSCSI boot environment
2. Problem: Cont00032801 - bnx2i: Add 64 bit bnx2id to the release Cause: NA Change: source package includes 64-bit binary under 'bnx2i-1.x.y/bin/bnx2id64' (need to rename as 'bnx2id') Impact: Enables user to build initrd image for 64-bit system
3. Problem: Cont00032141 - Linux iSCSI: Update README for MPIO behavior in Section 5 Cause: default values got changed in the latest open-iscsi package Change: Documentation changes Impact: None
4. Problem: Cont00032671 - Linux iSCSI: Interface up/down stress causes kernel softlockup with 5706S Cause: race condition and also hba shutdown thread was un-necessarily waiting on an event which is mutually exclusive ending up in timeout every single time. This wait cluase speeds hba shutdown process resulted because of 'ifdown' command Change: fixed spin_lock issues and removed unnecessary wait event mentioned above Impact: None
Enhancements ============ None
Version 1.1.1 (Dec 05, 2007) ============================
Fixes ===== None
Enhancements ============ Added init scripts to automatically load driver and the daemon during boot.
Version 1.1.0 (Nov 15, 2007) ============================= FIRMWARE - 4.4.0 ========
Fixes ===== None
Enhancements ============ NX2 5709 support added
Version 1.0.32 (Oct 18, 2007) ============================= FIRMWARE - 3.7.19 ========
Fixes ===== 1. Problem: Cont00031905 - Linux iSCSI: login/logout stress against wintarget with multiple luns causes kernel panic Cause: This was an issue caused by Win Targets wierd behavior of holding on to SCSI INQUIRY response till TMF is sent. Other issue was a race condition when logging off iSCSI session while TMF request is pending. this would clear out all commands while TCM timer was still active. When TMF timer expires, it tries to operate on a command already freed when session logged out. Change: if TMF is active while trying to logout, driver will wait for TMF request to either complete or timeout. Only them it will send iSCSI logout pdu. Impact: iSCSI TMF and iSCSI Logout rocessing
2. Problem: Cont00031884 - Linux iSCSI: Kernel panic with ifdown/up when logged into target with 5708s Cause: This issue was caused by a race condition depending on when GOING_DOWN message is received by the driver. Once this message is received, driver will start cleaning up all active sessions and any session already in recovery mode won't be bothered. But when this bug is hit, GOING_DOWN was received when session was in login in phase (recovery mode) and driver let it continue and return to user. Once bnx2i returns to cnic, cnic driver would release all resources including cnic_sock structures. One of the cnic_sock structure belonged to iscsi session which was going through login phase. This connection will stay alive and will be cleaned up during next iteration of interface bring down and CNIC driver won't find refence to this cnic_sock as it was already freed. Change: When HBA is shuting down, driver will wait for recovering sessions to complete iSCSI, then tear active sessions down before returing to user Impact: HBA shutdown code
Enhancements ============ None
Version 1.0.31 (Oct 10, 2007) ============================= FIRMWARE - 3.7.16 ========
Fixes ===== 1. Problem: Cont00031787 - Linux iSCSI: Red Hat system becomes unresponsive after cable pull test Cause: SCSI-ML issue which got in 2.6.19 kernel. Run same test on 2.6.23 kernel and it did not exhibit this issue. For more details refer to following URL's https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/118833 http://lists.parisc-linux.org/pipermail/parisc-linux-cvs/2006-September/037006.html Change: To avoid crossing the recursion limit of 19, driver sets 'cmd_per_lun' parameter n scsi_host_template to 16 Impact: Could lower iops when measured on a single iSCSI connection
Enhancements ============ None
Version 1.0.30 (Oct 05, 2007) ============================= FIRMWARE - 3.7.16 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== 1. Problem: Cont00031668 - Linux iSCSI Offload Licensing not enforced Cause: Dupicate of CQ31577, FW identifies the card as HP NIC instead of HP LOM, FW was checking for entire register instead of a specific bit Change: change the checking to refer to only a specific bit in MCP's scratchpad and not the entire register Impact: Licensing should work as expected on oem systems
2. Problem: Cont00031671 - Linux iSCSI: unable to connect to maximum number of sessions (64), on an x86_64 system Cause: Driver was allocating only 40 endpoint structures on 64-bit systems. Driver has a logic of allocating a maximum of #n pages of memory for each control structures (endpoint, connection, session, etc') and #n is set to 4. On a 32-bit system size of endpoint structure is 256B whereas on a 64bit system it is ~400B. So driver was able to allocate 40 endpoint structures Change: increaded number of pages per control structure to '8' Impact: None
3. Problem: Cont00031655 - Linux iSCSI: bnx2i: Error message - cmd not allocated w/ v1.0.29 Cause: one command structure was getting leaked when session goes into recovery due to nop-out timeout Change: NOPOUT requests are also queued in active command queue and freed when session is cleaned up Impact: None
4. Problem: Cont00031662 - Linux iSCSI: Kernel Oops running disktest with maximum sessions test Cause: driver was hard coding "sht->can_queue' parameter to 128 (max outstanding commands issued by SCS-ML). Where as the QP size was decreased using 'sysfs'. It get more complicated as 'can_queue' parameter is advertised when iscsi transport is registered which happens even before 'sysfs' setup. So will have to remove 'sysfs' support for changing SQ/RQ/CQ size and instead provide module parameters to choose these parameters based on requirements for number of the iSCSI connection Change: Removed 'sysfs' support for changing SQ/RQ/CQ size and instead module parameters are included to change these parameters. Also 4 command structures are reserved for slow path (TMF ABORT, NOP-OUT, etc) commands. Impact: None
Enhancements ============ Broadcom user daemon is renamed to 'bnx2id' and ioctl support added instead of 'sysfs'
Version 1.0.28 (Sep 29, 2007) ============================= FIRMWARE - 3.7.15 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== None
Enhancements ============ All software components are bundled as RPM packages
Version 1.0.27 (Sep 28, 2007) ============================= FIRMWARE - 3.7.15 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== None
Enhancements ============ Includes updated Firmware and CNIC driver
Version 1.0.26 (Sep 26, 2007) ============================= FIRMWARE - 3.7.14 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== None
Enhancements ============ None
Version 1.0.25 (Sep 26, 2007) ============================= FIRMWARE - 3.7.14 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== 1. Problem: Cont00031537 - Linux iSCSI: Cable pull broken in v1.0.22 Cause: iscsi driver was not destroying the connection context whenu cm_connect() returns failure, it just cleand up driver data structures. This is uncovered because of recent changes to ARP handling in the cnic driver Change: iscsi driver properly destroys iSCSI connection context when cm_connect() returns with failure Impact: None
Enhancements ============ None
Version 1.0.24 (Sep 25, 2007) ============================= FIRMWARE - 3.7.14 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== 1. Problem: Cont00031513 - Linux iSCSI: Cannot log in to target if the number of pending tasks have changed from the previous login/logout sessions Cause: bug in ISCSI_INIT message processing code in TXP/TPAT Change: Fix the initialization of the iSCSI number of pending tasks for TXP and TPAT Impact: None
2. Problem: Cont00031509 - LinuxiSCSI:iSCSIBoot failed to to successfully login to EMC ratget Cause: Unusual behavior of kernel call neigh_event_send() Change: neigh_event_send() returns error after sending the first ARP entry. This error must be ignored and we should only rely on subsequent NETEVENT_NEIGH_UPDATE for proper neighbour status. Impact: None
3. Problem: Cont00031517 - LinuxiSCSIBoot: Connection is not restored when disconnecting Primary HSRP router Cause: 2.6.16 kernel does not support NETEVENT_NEIGH_UPDATE Change: 2.6.16 kernel does not support NETEVENT_NEIGH_UPDATE, so router failover with gratuitous ARP will be unknown to the driver. To fix this issue, a timer was added to check the ARP entries periodically to detect ARP changes on 2.6.16 kernels. Impact: None
Enhancements ============ Includes new CNIC driver, V1.1.19
Version 1.0.23 (Sep 24, 2007) ============================= FIRMWARE - 3.7.13 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== 1. Problem: Cont00031529 - Linux iSCSI: EMC CX3 target errors out while running Bonnie++ w/ v1.0.22 Cause: programming error - when target returned "UnderFlow' condition and residual_length = Total expected data length, driver used to mistakenly report DDI_BAD_TARGET error. This was because one conditonal check was coded as "<" instead of "<=" Change: Changed the conditional check to "<=" Impact: None
Enhancements ============ None
Version 1.0.22 (Sep 21, 2007) ============================= FIRMWARE - 3.7.13 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== 1. Problem: Cont00031469 - Linux iSCSI: Kernel oops while logging out during maximum sessions test Cause: The warning and stack dump were caused by excessive calls to neigh_release(). This was caused by the work queue being called in a re-entrant way Change: Driver was changed to use tasklet instead of work queues to fix the problem. Tasklet are guaranteed to be single-threaded and runs at a higher priority than work queues. Impact: None
Enhancements ============ None
Version 1.0.21 (Sep 19, 2007) ============================= FIRMWARE - 3.7.13 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== 1. Problem: Cont00031421 - Linux iSCSI: Hotplug feature - Does not reconnect to target if nic is removed and put back in if there is already an iSCSI session established Cause: Offload driver cannot support this and driver will cleanup all activer iSCSI session/connections which also includes all outstanding commands and even releases the adapter structure as part of hot remove. When the adapter is added there won't be enough state information to restore the session. It is is a good idea to orderly shutdown all iSCSI sessions before removing the device Change: Will not be addressed Impact: None
2. Problem: Cont00031193 - LinuxiSCSI:iSCSIBoot continously drops and then recover iscsi connection Cause: This issue happens when 'iscsid' daemon is killed and restarted while one or more iSCSI session are active. When the daemon is restarted, it does not have reference to old TCP connection but it knows iSCSI session and connection information. So iscsid blindly stops the iSCSI connection, establishes a new TCP connection and tries to bind it to iSCSI connection. This results in a resource conflict situation as there is already a TCP conn bound to iSCSI connection causing a bad state with broken link between EP and CONN structures Change: When driver detects this condition old TCP connection is shutdown and cleaned up before binding the new TCP connection to iSCSI connection Impact: None
3. Problem: Cont00031205 - iscsid does not get the established session info after restarting Cause: This issue happens when 'iscsid' daemon is killed and restarted while one or more iSCSI session are active. When the daemon is restarted, it does not have reference to old TCP connection but it knows iSCSI session and connection information. So iscsid blindly stops the iSCSI connection, establishes a new TCP connection and tries to bind it to iSCSI connection. This results in a resource conflict situation as there is already a TCP conn bound to iSCSI connection causing a bad state with broken link between EP and CONN structures Change: When driver detects this condition old TCP connection is shutdown and cleaned up before binding the new TCP connection to iSCSI connection Impact: None
Enhancements ============ None
Version 1.0.20 (Sep 17, 2007) ============================= FIRMWARE - 3.7.13 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== None
Enhancements ============ Event coalescing is disabled
Version 1.0.19 (Sep 17, 2007) ============================= FIRMWARE - 3.7.12 + COM (Event Coalescing) ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== 1. Problem: Cont00031304 - Linux iSCSI: Does not see all the disks after LUN has been remove and then re-added on the target Cause: bug in SCSI sense data handling code - driver was copying entire RQ buffer as is, actually first 2 bytes (length field) should be omitted when copying to SCSI command sense buffer Change: Only actual sense data is copied to sense buffer Impact: None
2. Problem: Cont00031238 - Linux iSCSI: Kernel panic after running disktest (w/various io) to Cisco target overnight Cause: this is caused by race condition when command is completed while TMF request is pending. 'cmd->scsi_cmd' will be set to NULL ptr after completing the command to SCSI-ML and system paniced dereferencing cmd->scsi_cmd when TMF completes waking up the waiting thread. Change: driver checks if the cmd completed while waiting for iSCSI TMF Impact: none
3. Problem: Cont00031131 - LinuxiSCSI:Using HP target iscsi session drops after nop-out timedout after 15 seconds on RH5 Cause: some targets do not explicitly respond to NOPOUTs when there are active commands. These iSCSI targets expect initiator to update sequence numbers from SCSI CMD RESPONSE pdus Change: bnx2i driver will not send nopout on wire when following conditions are met - 1. there are active SCSI commands 2. one or more SCSI commands where sent between this and previous nopout request
Instead driver will itself respond to nopout. Infact we can even change iscsid to keep track of 'cmdsn' and send down nopout request only if connect is truely idle. We will evaluate changes to iscsid and work to community to incorporate the change. Impact: Initiator's proactive NOPOUTs are not seen on wire when the iSCSI connection is not truely idle
4. Problem: Cont00031121 - Linux iSCSI: Kernel panic when running ifdown/up test + disktest Cause: In interface going down notification, iSCSI connection context was destroyed without tearing down the TCP connection. Another issue was option-2 s/w was not handling 'SYN - ACK - RST' condition properly. Change: Code is fixed to attempt TCP connection shutdown (FIN/RST) before destroying connection context. Impact: none
5. Problem: Cont00031024 - Linux iSCSI: Keyboard locks up when running traffic to Sanrad w/ Suse10 SP1 Cause: There were a bunch of issue uncovered by this test - 1. race condition in cleanup code 2. error while assigning LUN value during TMF request wqe 3. issue related to RQ producer index posting, from the second wraparound, indices posted was in the range 0x0 - 0x10, 0x8000 - 0x8010. Correct RQ producer index range is 0x1 - 0x10, 0x8001 - 0x8010 (this example considers total of 16 RQ buffers) 4. RQ producer suppose to be increment by driver on every unsolicited PDU that generated a CQE(even without iSCSI data) Change: code changes to take care of all above said issues Impact: none
6. Problem: Cont00031221 - Linux iSCSI: Bonnie++ reports drastic I/O error when running to EMC AX100SCi target Cause: combination of Cont00031304 and Cont00031024 (issue #4) Change: combination of Cont00031304 and Cont00031024 (issue #4) Impact: none
7. Problem: Cont00031203 - Linux iSCSI: LUN rescan does not complete after cable pull when connected to multiple targets Cause: couple of issues attributed to this issue - 1. order of conditional checks - link down check was before session recovery state. Actually order should be reversed 2. old recovery state should be a per session attribute but instead was kept as static variable in bnx2i_queuecommand(). When there were multiple sessions this broke state transition Change: Fixed both the issues Impact: None
8. Problem: Cont00031194 - Linux iSCSI: traffic does not resume on standby nic when cable pulled during MPIO testing Cause: couple of issues attributed to this issue - 1. order of conditional checks - link down check was before session recovery state. Actually order should be reversed 2. old recovery state should be a per session attribute but instead was kept as static variable in bnx2i_queuecommand(). When there were multiple sessions this broke state transition Change: Fixed both the issues Impact: none
9. Problem: Cont00031383 - LinuxiSCSI:iSCSIBoot encounters connection failure during iscsiBoot Cause: Related to option-2 issue of not handling 'SYN - ACK - RST' condition properly. Change: Instead of sending Reset on bad ack sequence segment when expecting syn/ack, just redirect to L2 in order for it to send the reset (for the sake of simplicity) Impact: Second SYN request should succeed in establish the 3-way handshake
Enhancements ============ Event coalescing is implemented
Version 1.0.18 (Aug 30, 2007) ============================= FIRMWARE - 3.7.11 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== 1. Problem: Cont00031121 - Linux iSCSI: Kernel panic when running ifdown/up test + disktest Cause: Driver was not tearing down the connection when interface was brought down. This was causing TCP connection to be active on the target side and won't let initiator to reuse the port. Driver is fixed to attemp TCP connection teardown but firmware needs to fixed as well to either indicate error status to driver or return sending SYN packet when first 3-way handshake fails Change: Driver initiates TCP connection teardown process before cleaning up iSCSI state Note: Need firmware fix to resolve SYN - ACK - RST issue as same issue will resurface when 'ifdown' command is issued when cable is disconnected Impact: none
Enhancements ============ None
Version 1.0.17 (Aug 29, 2007) ============================= FIRMWARE - 3.7.11 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== 1. Problem: Cont00031063 - Linux iSCSI: Kernal panic when attempting target login (w/o authentication) with certain login parameters Cause: this is an iET target implementation issue. Target is not setting 'F' bit in the last datain pdu of a sequence. In this test scenario, MBL = MRDSL (initiator) = 2K and the command was a scsi read \ with exp data length = 4K. Target sends 2 datain's - 1. datasn=0, data segment len = 2K, F=0, S=0 2. datasn=1, data segment len = 2K, F=1, S=1
In first DATAIN pdu, 'F' should have been set to '1'. MIPS firmware correclty detects the error & notifies the driver. Driver actually starts the recovery phase, but every single connection will end up in same fate as the 1st. As this happens in SCSI discovery phase right after the iSCSI login, user shell will never return and iscsid will keep retrying. Change: Fixed driver crash issue and made code changes to iET software to be more 3720 compliant. SWE will publish the code changes to iET development community Impact: none
Enhancements ============ Made some performance improvements change in CNIC driver which should avoid some spurious interrupts under heavy I/O
Version 1.0.16 (Aug 23, 2007) ============================= FIRMWARE - 3.7.11 ========
NOTICE - iSCSI License enforcement is turned on. ======
Fixes ===== 1. Problem: Cont00030122 - Linux iSCSI: Disk does not reappear after cable pull on Sanrad target Cause: link change events was not handled in iscsi driver Change: Link change events are handled in driver correctly and bnx2i driver will not issue new scsi commands / scsi tmf requests to chip if the link is down Impact: none
2. Problem: Cont00031024 - Linux iSCSI: Keyboard locks up when running traffic to Sanrad w/ Suse10 SP1 Cause: This issue uncovered few bugs - 1. race condition in cleanup code 2. there was a coding error while assigning LUN value during TMF request wqe formation 3. logic error in RQ producer index posting - from second RQ index wrap around, producer index posted was (0x0 - RQ_Size) and (0x8000 - (0x8000 + RQ_Size)). Correct indices range is (0x1 - RQ_Size) and (0x8001 - (0x8001 + RQ_Size)) Change: All above said issues were resolved Impact: none
Enhancements ============ None
Version 1.0.15 (Aug 22, 2007) ============================= FIRMWARE - 3.7.11 ========
NOTICE - iSCSI License enforcement is turned off. ======
Fixes =====
1. Problem: Cont00030809 - Linux iSCSI: Able to log in to target when FirstBurstLength > MaxBurstLength Note : Check more accurate description of issue at hand when this issue was first resolved Cause: To be in sync with SW open-iscsi implementation, offload driver will not allow FBL > MBL when either immediate data or unsolicited data is enabled, irrespective of target advertised MRDSL Change: Not to allow FBL > MBL when either immediate data or unsolicited data is enabled Impact: None
Enhancements ============ None
Version 1.0.14 (Aug 21, 2007) ============================= FIRMWARE - 3.7.11 ========
NOTICE - ====== iSCSI License enforcement is turned off. Also TCP port binder utility is bundled in this release, user has to start 'portbind' daemon before attempting to establish iSCSI sessions
Fixes ===== 1. Problem: Cont00030892 - Linux iSCSI: Enhancement Request - Print out appropriate message when session cannot be established due to restriction in iSCSI licenses Cause: MIPS firmware was returning single failure error code Change: MIPS firmware returns newly defined error code if unable to allocate iSCSI context space Impact: None
2. Problem: Cont00030042 - Linux ISCSI - Session freezes running ISCSI initiator at 10Mb/s-Hd Cause: iscsi_discovery script under open-iscsi/utils folder was used to discover and connect to targets. This scripts was using iSER to connect to target, so in effect 2 simulaneous connections were made to target Change: not to use iscsi_discovery Impact: None
3. Problem: Cont00031024 - Linux iSCSI: Keyboard locks up when running traffic to Sanrad w/ Suse10 SP1 Cause: race condition in cleanup code and also there was a coding error while assigning LUN value during TMF request wqe formation Change: cleaned up error path to hammer out few remaining bugs Impact: More stable error recovery code
4. Problem: Cont00031040 - Linux iSCSI: Kernel oops occurs between long transmit timout and recovery. Cause: Same as Cont00031024 Change: Same as Cont00031024 Impact: Same as Cont00031024
5. Problem: Cont00029844 - Linux ISCSI - Bonnie++ fails while testing against Linux Target Cause: Same as Cont00031024 Change: Same as Cont00031024 Impact: Same as Cont00031024
6. Problem: Cont00030809 - Linux iSCSI: Able to log in to target when FirstBurstLength > MaxBurstLength Cause: This is a iSCSI target implementation issue - during login reponse following parameters were agreed b/w target and the initiator - 1. MaxBurstLength (MBL) - 32768 2. FirstBurstLength (FBL) - 65536 3. MaxReceiveDataSegmentLength Initiator - 131072 (advertised) 4. MaxReceiveDataSegmentLength Target - 8192 (not advertised, spec defaults) 5. ImmediateData=Yes 6. InitialR2T=Yes
When all these parameters are put together Initiator can only send 8192B of immediate data and no unsolicited data. So any negotiated FBL value greater than 8192 is a waste and target might be ignoring it. Change: Third party issue Impact: Won't be addressed
Enhancements ============ Fixed one issue related to iSCSI R2T statistic counter update code. Also 'portbind' utility is bundled with this release and the user has to start the daemon before attempting to establish iSCSI sessions
Version 1.0.13 (Aug 07, 2007) ============================= FIRMWARE - 3.7.10_b0 ========
NOTICE - iSCSI License is required to use iSCSI Offload ======
Fixes ===== Check CQ resolution information in 1.0.12 (open community release) 1. Cont00030950 2. Cont00030948 3. Cont00030903 4. Cont00029670 5. Cont00030227 6. Cont00030817
Enhancements ============ None
Version 1.0.12 (Aug 06, 2007) ============================= FIRMWARE - 3.7.10_b0 ========
NOTICE - iSCSI License is required to use iSCSI Offload ======
Fixes ===== 1. Problem: Cont00030950 - Linux iSCSI: FIN packet is NOT sent out from initiator after each target logout. Cause: Driver was using a single flag to mark FIN received and RST received. Driver used to skip cm_close() path when this flag is set and directly initiate connection context destroy Change: Now this flag is separated into 2 different flag bits and driver will take following action based on state machine - 1. FIN received - initiated an option-2 request to send FIN if remote socket layer sent us FIN either with logout respons PDU or standalone TCP segment with FIN flags set 2. RST received - will skip cm_close() path and directly proceeds to destroy connection context Impact: should also resolve occational "4 - encountered connection failure" error condition when attempting to create a new iSCSI connection
2. Problem: Cont00030948 - Linux iSCSI: Kernel Oops occurs after 3-way handshake (for target login) failed. Cause: In ep_disconnection thread driver tried to dereference a null pointer, ep->sess. this structure element is assigned correct value in conn_bind() routine and this routine is not called when ep_connect() fails because of 3-way handshake failure Change: Check validity of ep->sess pointer before de-referencing Impact: None
3. Problem: Cont00030903 - Linux iSCSI: Cannot log in to target after unloading/loading iSCSI offload drivers if iscsid is not restarted Cause: Everytime is driver is unloaded and reloaded, it is not guarenteed the same 64-bit handle is allocated to iSCSI transport name. 'iscsid', open-iscsi user daemon will cache transport attributes/properties only when the transport name is first discovered. This will result in 'iscsid' trying to use the stale transport handle which is not recoqnized by kernel iscsi tranport module Change: 'iscsid' is changed to check for changed transport handles of existing transport names while scanning iscsi transports directory for updates Impact: Need to co-ordinate with Mike Christie to push this change upstream
4. Problem: Cont00029670 - Linux ISCSI - encounter error (4 - encountered connection failure) when loging to the target Cause: related to Cont00030948, as initiator did not send FIN - ACK, socket was alive at the other end. This causes target to ignore SYN packet when tuple matches with exisiting active connection and send an ACK segment instead Change: Driver code is modified to gracefully shutdown the connection with a FIN/ACK TCP segment before destroying the iSCSI connection context. This ensure ordely shutdown of TCP socket at the other end. Impact: None
5. Problem: Cont00030227 - Linux iSCSI: Login/logout and traffic stress test causes kernel panic Cause: KCQ context was not properly re-initialize when driver tries to stop KCQ and re-init KWQ/KCQ Change: driver and mips firmware was fixed to correctly re-initialize KCQ context when KWQ/KCQ is re-initilaized by the driver Impact: None
6. Problem: Cont00030817 - Linux iSCSI: Login/logout stress causes iscsid process to disappear Cause: related to Cont00030227 Change: refer to Cont00030227 entry above Impact: None
Enhancements ============ Driver code was modified as per review comments / suggestions from Arlando Carvalho de Melo
Version 1.0.11 (Aug 02, 2007) ============================= FIRMWARE - 3.7.10_a0 ========
Fixes ===== None
Enhancements ============ changed a couple of print messages for initial Linux community
Version 1.0.10 (Aug 02, 2007) ============================= FIRMWARE - 3.7.10_a0 ========
Fixes ===== 1. Problem: Cont00029443 - Linux iSCSI: iSCSI licenses in xDiag not enforced Cause: not implemented as licensing scheme was finalized very recently Change: Licensing code is implemented in MIPS firmware Impact: iSCSI Offload won't work on engineering boards / servers LOMs which does not carry proper licensing
2. Problem: Cont00030863 - Linux iSCSI: Transport name for 5706 devices is titled bcm5708-xxxxxx w/ v1.0.07 and above Cause: PCI device ID field was cleared by mistake which cased driver to choose the default device type, '5708' Change: fixed in code Impact: transport name format for 5706 devices will be 'bcm5706-xxxxxx'
Enhancements ============ None
Version 1.0.09 (July 31, 2007) ============================= FIRMWARE - 3.7.9_a1 ========
Fixes ===== 1. Problem: Cont00030788 - Linux iSCSI: CHAP is broken in v1.0.07 Cause: Bug in connection state machine prevented driver from sending multiple iSCSI login requests to firmware Change: connection state machine changed to take care of this issue Impact: none
Enhancements ============ None
Version 1.0.08 (July 30, 2007) ============================= FIRMWARE - 3.7.9_a1 ========
Fixes ===== 1. Problem: Cont00030302 - Linux iSCSI: Session disconnect and kernel panic when formatting EMC target w/ NOP Out interval set to 10 Cause: there were a few repeated iSCSI protocol warning messages Change: Driver changed to display each warning once for each session Impact: none
2. Problem: Cont00029546 - Linux iSCSI: Requires upgrade to 2.6.19 kernel on Suse10 Cause: SLES10 update 1 had older open-iSCSI components Change: SLES10 SP1 has a newer open-iSCSI and we don't need kernel upgrade Impact: none
3. Problem: Cont00030820 - Linux iSCSI: Error messages seen on Cisco MDS 9216 target w/ v1.0.07 Cause: FW generates iSCSI Error KCQE for each iSCSI protocol violation whether is configured to be treated as warning or error. So driver will priting message for each indication, this caused a flury of messages and slowing down the system. Now driver is changed to print each type of warning only once. Change: Driver prints message only once for each iSCSI protocol violation which is configured to be treated as WARNING and not an ERROR Impact: none
4. Problem: Cont00029689 - Linux iSCSI: Maximum of 16 iSCSI sessions supported Cause: Driver was limiting max offloaded connections to 32 Change: driver and FW are equipped to support upto 64 iSCSI connections Impact: none
5. Problem: Cont00030805 - Linux iSCSI: iSCSI Rx Statistics not incrementing w/ v1.0.07 Cause: issue was introduced in v1.0.07 when code was revamped to meet Linux coding standards. A stale structure element was being check to determine whether the completion is for READ or WRITE command. 'Cuz of constant value of this absolete structure member, same code path was take all the time. Change: Correct structure member is referenced to determine whether the command is SCSI READ or WRITE IMP: currently couple of counter are not correctly implemented in FW and should be taken care in next release. Other than these (R2T/DATAOUT pdu count) everything else look to be fine. Impact: none
Enhancements ============ This release is tested on SUSE Enterprise Linux Server 10 (Service Pack 1). Open-iSCSI packaged with SLES 10 SP1 works with offload iSCSI driver and we do not require kernel update on SLES
Version 1.0.7 (July 25, 2007) ============================= FIRMWARE - 3.7.7 ========
Fixes ===== 1. Problem: Cont00030060 - Linux iSCSI: Hotplug using fakephp driver w/ iSCSI drivers loaded does not work Cause: Hotplug feature was incomplete Change: This is implemented correctly in cnic as well bnx2i driver in version 1.0.7 release Impact: Hotplug feature is fully supported
2. Problem: Cont00030302 - Linux iSCSI: Session disconnect and kernel panic when formatting EMC target w/ NOP Out interval set to 10 Cause: couple of issue attirbuted to this - 1. race condition in driver caused by not properly guarding critical sections 2. EMC target has issues handling nop-out requests when link is not idle, i.e. if a SCSI command follows the nop-out, it will not respond with nop-in. This caused system crash as the driver was not properly recovering from this failure. Change: System crash is fixed and the initiator reconnects to target after tearing down the connection Impact: None
3. Problem: Cont00030013 - Linux iSCSI: Running disktest read/write with NOP Out interval set to 10 causes system lockup Cause: there was a bug in 'cmdsn' assignment code Change: fixed 'cmdsn" assignement code Impact: None
4. Problem: Cont00030066 - ISCSI Linux - System hangs when issue a couple of ifdown/ifup command Cause: There were few bugs in iscsi driver not properly synchronizing events such as connection setup and interface reset happening simultaneosuly. During ifdown, the cnic will shutdown and a number of bugs were triggered. The L4 connection code did not unregister, and so during subsequent ifup, it could not be registered again. There was also a lock imbalance when L4 connection code tried to register again, and this caused the soft lockup. Change: Now it's all taken care and also driver tracks age of the adapter (number of times it's reset) which allows iscsi driver to detect if the network interface is reset between 2 events from iscsi daemon, e.g. connect establishment and login pdu send Impact: None
4. Problem: Cont00029719 - Linux iSCSI: Enhancement Request - MTU size > 1500 should not be allowed for bnx2 driver Cause: bnx2i driver was not checking MTU Change: bnx2i driver will disallow any iSCSI connection offload if network device's MTU is > 1500B Impact:
Enhancements ============ Source code was revamped to meet Linux coding standards
Version 1.0.6 (July 10, 2007) ============================= FIRMWARE - 3.7.6_A0 ========
Fixes ===== 1. Problem: Cont00030435 - Linux iSCSI: Cannot log into certain targets w/ driver package v1.0.05 Cause: Linux iSCSI package version 1.0.5 contained firmware version 3.7.4 and it seems the firmware has this issue. This issue not seen with firmware 3.7.6_a0 Change: new firmware image Impact: none
Enhancements ============ None
Version 1.0.5 (July 06, 2007) ============================= Fixes ===== 1. Problem: Cont00030060 - Linux iSCSI: Hotplug using fakephp driver w/ iSCSI drivers loaded does not work Cause: Hotplug was not implemented properly Change: Support was added in bnx2i driver and also bnx2i-cnic driver interface was upgraded to support hotplug Impact: all of login - logout, driver load - unload test cases need to be re-run to thoroughly validate the interface change
Enhancements ============ 1. This release includes iSCSI context dump utility and the required driver hooks is included in this release 2. bnx2i and cnic driver interface changed quite a bit while adding hotplug support
Version 1.0.04 (May 30, 2007) ============================= Fixes ===== None
Enhancements ============ Added print statement to display network interface and iSCSI transport names for each NX2 device enumerated by the driver. Other enhancements include cosmetic changes to README_iSCSI.txt file and the bnx2 driver includes latest mips firmware.
Version 1.0.03 (May 29, 2007) ============================= Fixes ===== 1. Problem: Cont00029452 - Linux iSCSI: Error messages seen during login/logout on Equallogic target with v1.0.01 Cause: iSCSI driver was attempting to do session recovery every time it received a TCP FIN or RST from the remote peer. Actually session recovery has to attempted only if the sess is in FFP state. Change: checks are put in place to avoid any un-necessary recovery attempts Impact: none
2. Problem: Cont00029655 - Linux ISCSI - Seeing error in the /var/log/messages when connecting to Linux target Cause: duplicate of Cont00029452 Change: see notes for Cont00029452 Impact: none
3. Problem: Cont00029662 - Linux iSCSI: Problem formatting EMC target Cause: protocol violation (invalid LUN field in R2T PDU) by the target Change: removed couple of strict protocol checking in MIPS firmware Impact: might affect iSCSI protocol validation certifications, will reinstate the checks once we have this fixed in the target end.
4. Problem: Cont00029690 - Linux iSCSI: Login attempt to 17th session causes the 16th session to be dropped Cause: 'cid_free_cnt' was not decremented after allocating a 'iscsi_cid' from the free list. This caused false queue full condition even when all the entries are allocated. Change: 'cid_free_cnt' is properly updated while allocating iscsi_cid from the free pool Impact: driver will gracefully turn down request to open 17th connection
5. Problem: Cont00029535 - Linux iSCSI: iSCSI session drops and fails to recover Cause: There was a diconnect between BD table allocation and what is advertised to the SCSI layer. Driver was allocating BD table with max 32 entries for each command and what was registered with SCSI-ML was a bigger value. Change: Driver now allocates BD table of size equal to 'sg_tablesize' value specified in scsi_host_template structure Impact: None
6. Problem: Cont00029432 - Linux iSCSI: Does not automatically reconnect to target after cable pull test Cause: 'fdisk -l' will result in couple of read commands and these gets queued up in the TX pipeline (retransmission queue) and firmware will not complete CMD_CLEANUP requests for commands that have some entries in the retransmission queue. Unless the number of CMD_CLEANUP requests issued and responses that got completed match, driver will assume connection can't be shutdown properly. Change: Driver will teardown connection without cleaning up the commands when needed and it is the right thing to do. Impact: None
Bug fixes in other modules : -------------------------- a) Cont00029590 - Linux iSCSI: Unable to connect to iSCSI target on a tagged vlan using offload iSCSI Fixed in cnic driver - vlan was not supported by the option-2 component of cnic driver. Code was added to support vlan tagging and checking if the route to desitination is over a vlan interface. cnic driver will set correct VLAN id while sending down option-2 connect request. b) Cont00029579 - Linux iSCSI: Running ethtool -t with target connected causes kernel panic Fixed in bnx2 driver - Asynchronous reset during self-test causes the cnic driver to crash. The fix is to disallow offline selftest when cnic driver is loaded.
Version 1.0.02 (May 22, 2007) ============================= Fixes ===== 1. Problem: Cont00029425 - Linux iSCSI: Issue when connecting to 16+ LUNs Cause: RQ buffers replenish code was commented out. By default iSCSI QP is created with 16 RQ buffers, so were we allowed to discover 16 SCSI LUNs. For the 17th LUN firmware did not have RQ buffer to place sense data. Change: cleaned up RQ buffer replenish code Impact: can connect to > 16 LUNs and run I/Os
2. Problem: Cont00029532 - Linux iSCSI: Running more than 64 outstanding I/Os on multiple LUNs w/ disktest has issues Cause: iSCSI initiator was not properly honoring the iSCSI Session Command window presented by the target. Netapp is actually only providing command window of 64 and once violated would drop the connection via' REJECT and ASYNC messages. Change: iSCSI driver is taking care of iSCSI command window correctly
3. Issues fixed in other modules - a) Cont00029404 - Linux iSCSI: Unable to login to Cisco MDS 9216 Fixed in chip software (MIPS firmware) - Wrong KCQE opcode was due an error in error reporting mechanism. New FW version 3.7.1.A0 fixes this.
b) Cont00029415 - Linux iSCSI: HP target rejects NOP Out from our driver Fixed in chip software (MIPS firmware) - The correct opcode is sent to the wire now. Fixed in ver 3.7.1.A1
c) Cont00029542 - Linux iSCSI: Problem formatting Stringbean target with ext3 file system Fixed in chip software (MIPS firmware) - The problem was present due to wrong error reporting mechanism in FW. This mechanism is fixed in new FW version 3.7.1.A0
d) Cont00029571 - Linux iSCSI: Adding new session causes previous session to be dropped on Equallogic Fixed in chip software (MIPS firmware) - Wrong cam index handling caused the wrong connection to be flushed away from cam while removing other coonnection
e) Cont00029579 - Linux iSCSI: Running ethtool -t with target connected causes kernel panic Fixed in bnx2 driver - Asynchronous reset during self-test causes the cnic driver to crash. The fix is to disallow offline selftest when cnic driver is loaded.
f) Cont00029634 - Linux iSCSI: Changing MTU size w/ drivers loaded causes kernel panic Fixed in bnx2 driver - For now, the bnx2 driver will not permit MTU changes after CNIC is loaded. To change the MTU, you need to do so before loading the cnic driver. A better method will be available in future versions.
g) Cont00029366 - Linux iSCSI: Unable to connect to EMC AX100SCi Fixed in chip software (MIPS firmware) - The bug is due to target TCP protocol vioaltion (not our bug actually). Now once we support window scale option - this issue is resolved.
Enhancements ============ Implemented bnx2i driver maintained iSCSI statistics (Cont00029583). Some of the statistics counters are to be implemented by MIPS firmware and the interface specification. Once those are in place Cont00029583 will be resolved. Also default value of HC_COMP_PROD_TRIP is changed from 0x00020004 to 0x00020008 to boost 2 port performance
Version 1.0.01 (May 08, 2007) ============================= Fixes ===== 1. Problem: Cont00029362 - Linux iSCSI: Proactive NOP Out not handled by the driver Cause: 'CmdSN' was not specified in nopout SQ WQE and was always accompanied with cmdsn value of 0x0000000. Also NOPIN received in response to Initiator's proactive NOPOUT was not propogated to open-iscsi user daemon. Change: correct 'cmdsn' is used while posting NOPOUT request to ship and also code was added to send nopout pdu header to user daemon Impact: NA
2. Problem: Cont00029416 - Linux iSCSI: Login/logout stress causes kernel panic Cause: System crashed because of an issue in KCQ processing code in the CNIC driver Change: Refer to CNIC driver's release notes for further information
Enhancements ============ None.
Version 1.0.00 (April 27, 2007) ===============================
Initial release to QA team.
This release will support most iSCSI full feature operations including 1. SCSI CMD, TMF, NOPIN, NOPOUT, ASYNC and LOGOUT 2. REJECT is currently not supported 3. All IO size from 512B to 512KB
Driver unload and reload is also supported. This driver will work on Linux Kernel 2.6.18 and 2.6.19 and open-iscsi software 2.0-724 or later is required to make connections to iSCSI targets. iSCSI target discovery using 'SendTargets' is the only one tested so far, but it should matter to bnx2i as complete discovery is handled by the open-iscsi user code.
Following targets were used during initial debugging stages and should be fully supported - 1. Equallogic PeerStorage PS100E 2. Netapp Target - FAS250, FAS270 3. Linux Software Target - iET 4. Microsoft's StringBean target, minimal validation by developers
Fixes & Features ================ Export fcoe_capabilities to cnic Fix Cont00061013: Kernel panic when adding/removing targets from zone Upstream merges Support fcoe create on non-vlan interface
Fixes & Features ================ Fix Cont00060537:MLTT reports data corruption when running smaller IO Fix Cont00060456: Fix compilation when trace is enabled Handle error cases during create on a system that has 2 CPUs or less
Fixes & Features ================ Fix Cont00060008: IO miscompares seen on writing 512b sized packets Fix Cont00060041: Physical/NPIV ports go offline when interface is toggled.
Version 2.1.9 (Nov 15, 2011): ============================= Internal Release: RHEL Kernel : RHEL 6.1 SLES Kernel : SLES 11 SP1 Firmware Version : 7.0.29 bnx2x Version : 1.70.34 cnic : 2.5.7g
Fixes & Features ================ Fix soft lockup issue for SLES 11 SP2 kernel
Fixes & Features ================ Fix Cont00058540: Kernel panic when creating NPIV port on Brocade fabric Fix Cont00057834: DMA: Out of SW-IOMMU space
Fixes & Features ================ Fix Cont00057693 - Cannot reboot with IO Fix Cont00057894 - MCassert with RSCN stress Reset max recv frame size during link up
Fixes & Features ================ Support SLES 11 SP1 Errata kernel Support 1024 sessions
Version 2.0.9 (Jul 26, 2011): ============================= Internal Release: RHEL Kernel : RHEL 6.1 Firmware Version : 7.0.23 bnx2x Version : 1.70.21 cnic : 2.5.7c
Fixes & Features ================ Clear DESTROY_CMPL flag after FW destroy Do not re-use FCoE connection id immediately Code cleanup in bnx2fc_offload_session Fix Cont00057104 - README to include about adminStatus in lldpad.conf
Version 2.0.8 (Jul 19, 2011): ============================= Internal Release: RHEL Kernel : RHEL 6.1 Firmware Version : 7.0.23 bnx2x Version : 1.70.20 cnic : 2.5.7b
Fixes & Features ================ Obtain WWNN/WWPN from the shared memory Handle NETDEV_UNREGISTER for vlan devices Fix Cont00057047 - Not sending FIP LOGO after recovering FCP2 IO error and destroy a FCoE interface Support bsg_requests Drop unsolicited ABTS requests
Version 2.0.7 (Jul 13, 2011): ============================= Internal Release: RHEL Kernel : RHEL 6.1 Firmware Version : 7.0.23 bnx2x Version : 1.70.19 cnic : 2.5.6d
Fixes & Features ================ Remove vlan_id argument from indicate_netevent compilation fix for upstream kernel
Version 2.0.6 (Jul 12, 2011): ============================= Internal Release: RHEL Kernel : RHEL 6.1 Firmware Version : 7.0.23 bnx2x Version : 1.70.18 cnic : 2.5.6c
Fixes & Features ================ Enable compiling T7.0 driver on upstream kernel
Version 2.0.5 (Jul 08, 2011): ============================= Internal Release: RHEL Kernel : RHEL 6.1 Firmware Version : 7.0.23 bnx2x Version : 1.70.17 cnic : 2.5.6b
Fixes & Features ================ Fix Cont00056859 - Send discovery solicitation instead of waiting for DA from the switch
Version 2.0.4 (Jun 29, 2011): ============================= Internal Release: RHEL Kernel : RHEL 6.1 Firmware Version : 7.0.23 bnx2x Version : 1.70.16 cnic : 2.5.4b
Fixes & Features ================ Fix Cont00056618 - does not repond to modified max advertised receive frame size Merge upstream fixes
Version 2.0.3 (Jun 21, 2011): ============================= Internal Release: RHEL Kernel : RHEL 6.1 Firmware Version : 7.0.20 bnx2x Version : 1.70.14 cnic : 2.5.4b
Fixes & Features ================ Do not arm CQ when there are no CQEs Tx BD cache in write tasks Fix data protection fault in bnx2fc_unsol_els_work
Version 2.0.2 (Jun 10, 2011): ============================= Internal Release: RHEL Kernel : RHEL 6.1 Firmware Version : 7.0.20 bnx2x Version : 1.70.12 cnic : 2.5.4b
Fixes & Features ================ Integrate upstream changes to main branch - Uses inbox libfc/libfcoe - redesigned to work with fcoeutils - integrated T7.0 FW check for duplicate NPIV ports Fix panic in fc_vport_terminate() Fix Cont00055260 - System crashes after rapd link flap test with NPIV ports
Version 2.0.1 (May 03, 2011): ============================= Internal Release: RHEL Kernel : RHEL 6.0 SUSE Kernel : SLES 11u1 Firmware Version : 7.0.16 bnx2x Version : 1.70.09 cnic : 2.5.2b
Fixes & Features ================ Enable E3 device
Version 0.9.2 (Apr 29, 2011): ============================== Internal Release: RHEL Kernel : RHEL 6.0 SUSE Kernel : SLES 11u1 Firmware Version : 6.4.34 bnx2x Version : 1.64.26 cnic : 2.4.3b
Fixes & Features ================ Fix Cont00054734 - MC assert when destroying 255 NPIV ports.
Fixes & Features ================ Fix Cont00054500: Handle CVL with no VN_Port descriptor Fix Cont00054551: bnx2fcd does not start when restarting service Updated README.txt
Fixes & Features ================ 1. Makefile check for distro/kernel version compatibility. 2. thread_should_stop check fixes. 3. Lock related fixes - work lock release before wake up, tgt lock before return_rqe, cq lock.
Fixes & Features ================ Fix Cont00052932 - kernel panic when receiving REC LS_ACC after getting delayed FC4DATA Fix Cont00052926 - Send smaller size of FC4DATA size than advertised max frame data size
Fixes & Features ================ Fix Cont00052714 - system hang during bnx2x load/unload tests Fix Cont00052602 - README should include about changing SLES11 'unsupported-module' parameter Fix Cont00052347 - No FLOGI when host contains more than 8 ports
Fixes & Features ================ Ensure that CONF bit is set to 1 during offload FCP_CMND lost case, check for reason code "Unable to perform command request" also Eliminate percpu threads for L2 traffic Introduce percpu thread for IO completions FCoE license check in ulp_init and ulp_start
Fixes & Features ================ FCP-2 Tape Support for Sequence level error recovery Fix Cont00050816: workaround for cisco rejecting FLOGIs Fix Cont00051261/51262: Host/switch go out of sync
Version 0.7.8 (Nov 17, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.36-rc3-fcoe-next2+ (RHEL 6) SUSE Kernel : SLES 11u1 Firmware Version : 6.4.11 Bootcode : 6.2.1 bnx2x Version : 1.64.08 cnic : 2.3.2c
Fixes & Features ================ Fix Cont00050712: Kernel panic when dropping random frame
Version 0.7.7 (Nov 09, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.36-rc3-fcoe-next2+ (RHEL 6) SUSE Kernel : SLES 11u1 Firmware Version : 6.4.11 Bootcode : 6.2.1 bnx2x Version : 1.64.08 cnic : 2.3.2c
Fixes & Features ================ Fix Cont00050713: bnx2fc fails to iniailize a board after hotplug Fix Cont00050500: Kernel panic while unloading bnx2fc Fix Cont00050797: kernel panic with RSCN stress Print bnx2fc version string in syslog Enable session caching in FW
Version 0.7.6 (Oct 28, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.36-rc3-fcoe-next2+ (RHEL 6) SUSE Kernel : SLES 11u1 Firmware Version : 6.4.9 Bootcode : 6.2.1 bnx2x Version : 1.64.06 cnic : 2.3.2c
Fixes & Features ================ Fix Cont00050631: unloading bnx2fc driver does not send LOGO to the devices Fix Cont00050486: System hangs after rapid cable pull
Version 0.7.5 (Oct 21, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.36-rc3-fcoe-next2+ (RHEL 6) SUSE Kernel : SLES 11u1 Firmware Version : 6.4.7 Bootcode : 6.2.1 bnx2x Version : 1.64.04 cnic : 2.3.2b
Fixes & Features ================ Fix Cont00050470: host fails to login to fabric after reboot Fix Cont00050556: ifconfig up/down causes stack trace Fix Cont00050327: Driver upgrade option not supported Fix Cont00049876: Install from tar README instructions not correct Fix Cont00050197: Cannot login to Cisco NPV switch
Version 0.7.4 (Oct 14, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.36-rc3-fcoe-next2+ (RHEL 6) SUSE Kernel : SLES 11u1 Firmware Version : 6.4.7 Bootcode : 6.2.1 bnx2x Version : 1.64.04 cnic : 2.3.2b
Fixes & Features ================
Fix Cont00049880: Host doesnt boot with upstream kernel Fix Cont00050308: Cannot compile sources on RHEL6 RC1
Version 0.7.3 (Oct 12, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.4.7 Bootcode : 6.2.1 bnx2x Version : 1.64.03 cnic : 2.3.2b
Fixes & Features ================ Fix Cont00050344 - enode, npiv nodes fail to log back after vlan change Fix Cont00050226 - sysclass maxframe_size is updated only when hostX directory is created Fix Cont00050316 - IO error with 128K transfer size Fix Cont00050331 - sysclass 'speed' of NPIV port is Unknown Fix Cont00050328 - sysclass supported_speeds is "Unknown"
Version 0.7.2 (Oct 04, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.4.5 Bootcode : 6.0.35 bnx2x Version : 1.64.02 cnic : 2.3.1b
Fixes & Features ================ Fix Cont00050136: MFS not updated even if MTU is 2300 Fix Cont00050137: syslog shows "Unknown ABTS response" when recovering IO Fix Cont00050173: System hangs discovering > 128 targets Fix Cont00050514: Cannot login to Brocade 8000 switch
Version 0.7.1 (Sep 28, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.4.5 Bootcode : 6.0.35 bnx2x Version : 1.64.02 cnic : 2.3.1b
Fixes & Features ================ 6.4.5 FW integration with HSI changes
Version 0.7.0 (Sep 01, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.0.31 Bootcode : 6.0.28 bnx2x Version : 1.60.38 cnic : 2.2.5l
Fixes & Features ================ Fix Cont00049681: Target reset causes warning stack trace Fix Cont00049627: Host loses targets during rapid login/logout Export FCP stats to apps. Do not issue FLOGI if FCF is not selected
Version 0.6.9 (Aug 24, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.0.31 Bootcode : 6.0.22 bnx2x Version : 1.60.36 cnic : 2.2.5l
Fixes & Features ================ Fix Cont00049615: Lun/Tgt reset times out when issued to VMAX target
Version 0.6.8 (Aug 20, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.0.31 Bootcode : 6.0.22 bnx2x Version : 1.60.36 cnic : 2.2.5l
Fixes & Features ================ Fix Cont00049555: bnx2fc: FLOGI not issued for 4 secs even after Disc Adv Fix Cont00049542: Free ctx_base mapping when session is uploaded Fix Cont00049545: libfcoe: driver sends non-FIP FLOGI to brocade when RSTP is enabled
Version 0.6.7 (Aug 16, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.0.31 Bootcode : 6.0.22 bnx2x Version : 1.60.34 cnic : 2.2.5i
Fixes & Features ================ Fix Cont00048324 - bnx2fcd: Reloading bnx2x multiple times makes bnx2fcd hang
Version 0.6.6 (Aug 12, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.0.31 Bootcode : 6.0.22 bnx2x Version : 1.60.34 cnic : 2.2.5i
Fixes & Features ================ Fix Cont00049258 - fcinfo: stats parameter should be set to 0 Fix Cont00049334 - panic at libfc_exit Fix Cont00049311 - Kernel panic when enabling eth interface on i386 system
Version 0.6.5 (Aug 09, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.0.30 Bootcode : 6.0.22 bnx2x Version : 1.60.32 cnic : 2.2.5i
Fixes & Features ================ Fix Cont00049259: kernel bug while stressing random packet drop with IOs Fix Cont00048540: Reload bnx2fc driver in a loop causes system hang Fix Cont00048465: Reloading bnx2fc multiple times causes Missing Discovery Advertisement Fix Cont00048446: Reloading bnx2x with multipath causes system hang Fix Cont00048155: Kernel panic occurs when unloading driver on SLES11 u1 i386 Remove bnx2fc_debug_level description from modinfo output.
Version 0.6.4 (Aug 04, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.0.30 Bootcode : 6.0.22 bnx2x Version : 1.60.30 cnic : 2.2.5g
Fixes & Features =============== Fix Cont00048193 - IO causes Missing Discovery Advertisment from Brocade switch (SLES only) Fix Cont00049115 - Unable to reboot system with IOs Fix Cont00049117 - System hangs unloading bnx2x Fallback to common exchange pool, if percpu pool is full
Version 0.6.3 (July 21, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.0.29 Bootcode : 6.0.22 bnx2x Version : 1.60.28 cnic : 2.2.4d
Fixes & Features ================ Fix Cont0048874 - System hangs performing shut/noshut after creating 255 NPIV ports
Version 0.6.2 (July 16, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.35-rc3-fcoe-next4+ SUSE Kernel : SLES 11u1 Firmware Version : 6.0.29 Bootcode : 6.0.22 bnx2x Version : 1.60.28 cnic : 2.2.4d
Fixes & Features ================ Fix Cont00048764 - System reboots after injecting FC-CRC error libfc: Initiator doesnt retransmit if SCR/FLOGI gets rejected by the switch (open-fcoe review comments incorporated) libfcoe: Host does not handle CVL to NPIV instantiated port correctly (Fix duplicate descriptor bug
Version 0.6.1 (July 12, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.34-fcoe-next4 SUSE Kernel : SLES 11u1 Firmware Version : 6.0.28 Bootcode : 6.0.22 bnx2x Version : 1.60.27 cnic : 2.2.4c
Fixes & Features ================ Fix Cont00048515 - Change MTU causes NULL pointer dereference Fix Cont00048680 - Reset LUN/tgt every 60 - 120 secs causes kernel panic Fix Cont00048547 - Simple IO shows kernel panic against Brocade Fix Cont00048142 - SUT port wont log back to switch if port is swapped Fix Cont00047552 - No vlan discovery after restarting driver Fix Cont00047731 - Host doesnt handle CVL to NPIV initiated port (Not verified due to lack of setup)
Version 0.6.0 (July 02, 2010): ============================== Internal Release: Upstream Kernel Version : 2.6.34-fcoe-next3 SUSE Kernel : SLES 11u1 Firmware Version : 6.0.28 Bootcode : 6.0.22 bnx2x Version : 1.60.26 cnic : 2.2.3k
Fixes & Features ================ Fix Cont00047431 - Initiator doesnt retransmit if SCR/FLOGI gets rejected by the switch Fix Cont00048644 - disable/enable Brocade switch port causes stack trace Fix Cont00048535 - Host does not detect all 128 targets Fix Cont00048536 - Host takes long time to detect 128 targets Fix Cont00048476 - Kernel bug at slab.c:3006 during IO Fix Cont00048416 - ifup/down overnight causes system hang
Version 0.5.9 (Jun 18, 2010): =========================== Internal Release: Upstream Kernel Version : 2.6.34-fcoe-next1 SUSE Kernel : SLES 11u1 Firmware Version : 6.0.27 Bootcode : 6.0.17 bnx2x Version : 1.60.24 cnic : 2.2.3g
Fixes & Features ================
Fix Cont00048415 - do not offload non-fcp targets Fix Cont00048340 - Memory leak during driver unload Fix Cont00048303 - Changing MTU while IOs running causes bnx2x panic dump Fix Cont00048330 - link down from shut/noshut after 20 secs of down time Fix Cont00048404 - NULL pointer dereference at bnx2fc_fipvlan_send Fix Cont00048367 - SUT port doesnt login to cisco switch after switch reboot
Version 0.5.8 (Jun 14, 2010): =========================== Internal Release: Upstream Kernel Version : 2.6.34-fcoe-next1 SUSE Kernel : SLES 11u1 Firmware Version : 6.0.25 Bootcode : 6.0.17 bnx2x Version : 1.60.23 cnic : 2.2.3g
Fixes & Features ================ Fix Cont00048331: Stack trace at bnx2fc_netdev_cleanup and bnx2fc_get_vlan from modprobe Cancel timer when issuing lun/target reset Do not double complete the IO during cleanup & abts completion
Version 0.5.7 (Jun 11, 2010): =========================== Internal Release: Upstream Kernel Version : 2.6.34-fcoe-next1 SUSE Kernel : SLES 11u1 Firmware Version : 6.0.25 Bootcode : 6.0.17 bnx2x Version : 1.60.23 cnic : 2.2.3g
Fixes & Features ================ Fix Cont00048209: Data corruption with MSA device Fix Cont00048213: kernel panics when lun/target resets are done every 60-90 secs Fix Cont00047956: Host fails to login to fabric after VLAN ID change Fix Cont00048121: fcinfo shows invalid CRC count Fix Cont00048273: NULL pointer dereference at bnx2fc_link_ok
Version 0.5.5 (Jun 2, 2010): =========================== Internal Release: Upstream Kernel Version : 2.6.34-fcoe-next1 SUSE Kernel : SLES 11u1 Firmware Version : 6.0.25 Bootcode : 6.0.17 bnx2x Version : 1.60.22 cnic : 2.2.3b
Fixes & Features =============== Fix Cont00048071: kernel bug at bnx2fc_io.c:429! when running IO Fix Cont00048072: Spurious "missing Discovery Advertisement for fab..." messages when I/O Fix Cont00048058: syslog shows "bnx2fc: ERROR! active_ios < 0" when running IO Fix Cont00047905: Loading driver with incorrect parameters causes stack trace Fix Cont00048060: syslog shows "udevd Not inated" and a host gets kernel panic Fix Cont00047750: Initiator sends FCP_DATA packets sized larger than target's MAX_RX_SIZE Fix Cont00048055: IO failed in 5 mins when dropping random frames.
Version 0.5.3 (May 28, 2010): ============================ Internal Release: Upstream Kernel Version : 2.6.34-rc3-fcoe-next3 SUSE Kernel : SLES 11u1 Firmware Version : 6.0.24 Bootcode : 6.0.17 bnx2x Version : 1.60.21 cnic : 2.2.3b
Fixes & Features =============== Fix Cont00047695: target and lun reset overnight with IO causes losing target(s) Fix Cont00048026: cannot issue lun/target reset on RHEL Fix Cont00047297: restructure bnx2fc_cmd structure to optimize on size. Fix Cont00048031: syslog shows lots of Missing Discovery Advertisement Fix Cont00047752: driver does not support max IO size greater or equal to 64K Fix Cont00047921: wwpn & wwnn are 0 in sysfs Fix Cont00047917: host intermittently sends ABTS's during TEP 72 hours run Fix Cont00047927: bnx2fc_cmd_mgr_alloc failed when loading bnx2fc on SLES11 x86 Fix Cont00047928: Null pointer dereference at bnx2fc_start+0x90/0x140 on Sles11 SP1 RC3 X86 Fix Cont00047899: Host shows kernel panic regarding VLAN when loading bnx2fc driver on SLES 11 SP1 RC3 x86
Version 0.5.2 (May 24, 2010): ============================ Internal Release: Upstream Kernel Version : 2.6.34-rc3-fcoe-next1-00551-g1d0c2d2 SUSE Kernel : SLES 11u1 Firmware Version : 6.0.24 Bootcode : 6.0.17 bnx2x Version : 1.60.20 cnic : 2.2.3b
Fixes & Features ================ Discover vlan id across link up and link down Fix Cont00047474 - driver fails to send READ CAPACITY 16 Fix Cont00047731 - Host doesnt handle CVL to NPIV ports Check for order and missing critical descriptors for FIP ELS requests Do not offload sessions with initiator ports Do not offload non-FCP targets modified fixes that were submitted to open-fcoe: - Honor LS_ACC response codes for PRLI - Retry after LS_RJT for a PRLI request - Handle unsolicited PRLO request - Handle duplicate critical descriptors - Fix remote port restart problem
Version 0.5.1 (May 11, 2010): ============================ Internal Release: Upstream Kernel Version : 2.6.34-rc3-fcoe-next-00481-g317b11e (same kernel as 0.3.0) SUSE Kernel : SLES 11u1 Firmware Version : 6.0.22 Bootcode : 6.0.17 bnx2x Version : 1.60.18 cnic : 2.2.1c
Fixes & Features ================
Fix to find devices during startup Time IOs within driver, issue ABTS upon timer expiry Honor FW error codes and issue ABTS immediately Fix Cont00046931 - send solicitation after 2.5 * fka instead of 3 * fka (SLES only) Fix Cont00047434 - No PRLI to larget number of targets
Version 0.5.0 (Apr 30,2010): ============================ Internal Release: Upstream Kernel Version : 2.6.34-rc3-fcoe-next-00481-g317b11e (same kernel as 0.3.0) SUSE Kernel : SLES 11u1 Firmware Version : 6.0.20 Bootcode : 6.0.17 bnx2x Version : 1.60.16-1 cnic : 1.10.3b
Fixes & Features ================ VLAN discovery Common driver package for both upstream and SUSE. Fix Cont00047473 - FLOGI RJT causes NULL pointer dereference Fix race condition between rmmod and linkdown processing Double the size of SQ to handle non-SCSI commands Fail target offload if the number of offload sessions exceed 128.
Version 0.3.0 (Apr 23, 2010): ============================= Internal Release: Kernel Version : 2.6.34-rc3-fcoe-next-00481-g317b11e Firmware Version : 6.0.20 Bootcode : 6.0.17 bnx2x Version : 1.60.16-1 cnic : 1.10.3b
Fixes & Features: ================= Fix Cont00047299: offload compl goes in endless loop after unload bnx2fc from trying to discover 128 targets Fix Cont00047199: Do not allow creating duplicate vn_ports Retire ox_id for r_a_tov secs even when target responds with LS_RJT for an ABTS Rescan the CQ after arming it. Fix Cont00047316: Discovery failed for port with more than 128 targets resulted in no targets login Fix Cont00047142: Cable Pull: Immediate IO errors
Version 0.2.9 (Apr 09, 2010): ============================= Internal Release: Kernel Version : 2.6.34-rc1-fcoe-next-00039-g858742c Firmware Version : 6.0.18 Bootcode : 6.0.14 (PFC enabled bootcode) bnx2x Version : 1.60.13 cnic : 1.10.2D
bnx2fc Fixes: ------------- Fix Cont00046450 - Reject malformed PLOGI packet Fix Cont00046422 - System takes long time to logout 128 targets Fix Cont00046817 - Upload completion timeout Fix Cont00046986 - Offload error causes panic from cable pull Fix Cont00046936 - Panic dump from unload/load bnx2fc Fix panic caused due to BUG_ON(port_id != tgt->sid)
Version 0.2.8 (Mar 23, 2010): ============================= Internal Release: Kernel Version : 2.6.34-rc1 (fcoe-next) Firmware version : 6.0.15 bootcode : 6.0.11 bnx2x version : 1.60.12 cnic : 1.10.2c
Features & Fixes: =================
57712 Enablement release.
Kernel Fixes: ------------ 1. scsi_dh_emc: fix mode select request setup 2. Fix Cont00045892: Protect device shutdown from hotplug events 3. Fix Cont00046297: System becomes non-responsive reciving non-critical descrs. 4. Fix Cont00046296: Host doesnt accept disc adv frames with non-critical descrs. 5. Fix Cont00046410: System can't reboot after running 'LOGO from target' testcase. 6. Fix Cont00046290: Do not reject unsolicited PRLO 7. Fix Cont00046304: Retry after LS_RJT for a PRLI request 8. Fix Cont00046389: No solicitation if adv is dropped 9. Fix Cont00046371: Host does not drop Solicited Disc Adv reply 10.Fix Cont00046333:Drop packets with mismatched MAC address.
bnx2fc Fixes: ------------ 1. Fix bnx2fc_cmd_timeout to handle timeout of BNX2FC_SCSI_CMD 2. Complete cleanup only when a thread is waiting for it. 3. Avoid list_for_each_safe to traverse active_cmd_queue while flushing active ios 4. Fix race conditions and avoid holding host_lock 5. Avoid dropping the tgt_lock while traversing active_cmd_queue in lun/tgt reset 6. Change tgt->flags to bit fields 7. Do not hold tgt_lock while issuing RRQ 8. Fix Cont00046336 - Host returns Incorrect LESB error count 9. Fix cleanup completion panic 10. Fix Cont00046263: wrong host responses to unsolicited RNID 11. Fix Cont00046295: Do not reply to unsolicited ESTC, TEST, FAN, CSU requests 12. Change fcoe_percpu to bnx2fc_percpu 13. Fix Cont00046499: Unloading bnx2fc with multiple NPIV ports causes stack trace 14. Integrate upstream change to per_cpu variable for device stats. 15. Fix system hang when unloading bnx2x without unloading bnx2fc. 16. Fix rmmod hang when bnx2x is unloaded while IOs are going on.
Version 0.2.6 (Feb 22, 2010): =============================
Internal Release: Kernel Version : 2.6.33-rc4 (fcoe-next) Firmware version : 6.0.9 bootcode : 6.0.7 bnx2x version : 1.60.09 cnic : 1.10.1c (bnx2fc-only release)
Features & Fixes: =================
1. Works both on port 0 and port 1 2. PFC Enabled 3. Fix Cont00045558 - Vlan interface configuation on second port hang system 4. Fix Cont00045626 - ifconfig does not complete changing MTU 2300 -> 1500. 5. Fix Cont00045892 - Cannot shutdown a system 6. Fix Cont00045915 - No vfc link and system hang when unload bnx2fc on port 1 with bootcode 6.0.7 and 5.2.90. 7. Fix Cont00045944 - rmmod hang with "eth4: unknown type KCQE" 8. Fix Cont00045956 - IO fails with PFC 9. Fix Cont00045971 - Heavy IO with Link Level Pause shows a stack trace 10.Fix Cont00046003 - Too many 'unable to alloc io_req' 11.Fix Cont00046017 - FIP Keep Alive VN_Port send only 1 time
Version 0.2.3 (Feb 19, 2010): =============================
Internal Release: Kernel Version: 2.6.32 (fcoe-next) Firmware version: 6.0.7 bnx2x version: 1.60.05_1 (Plus some workarounds from bnx2x team)
Features: ========
1. PFC Enablement Changes 2. Fix Cont00045627 - Write failure when IO size is >= 4K 3. Resolve lock ordering between hba_mutex and lp_mutex 4. Remove hba_mutex during driver init and exit 5. Fix Cont00045621: Inconsistency discovering multiple targets 6. Synchronize modprobe and rmmod 7. Fix Cont00045503: Login to the fabric after link goes down and comes back up 8. Remove vlan id from the port wwn. 9. Ensure that bnx2fc is loaded only on a 10G device 10.Fix Cont00045593: A system hangs if rebooting the system while IO is running
Version 0.2.1 (Jan 27, 2010): =============================
3. Edit /boog/grub/menu.lst to make this as a default kernel OR Select this kernel in the boot menu while the system is booting up
4. reboot
5. Start vlan interface
ifconfig ethX mtu 2300 up modprobe 8021q vconfig add ethX ifconfig ethX. up
ethX is the ethernet interface connected to the FCF.
6. modprobe bnx2fc [default is 4]
[NOTE] 1. If bnx2fc rpm fails to install due to conflict with previosly installed bnx2x driver, remove it by running 'rpm -e bnx2x'
2. If bnx2x driver fails to load due to dependency with crc32c, manually run - modprobe crc32c - modprobe bnx2x 3. If there is a firmware loading error during system boot up after installing the kernel and bnx2fc drivers, install the firmware rpm as well. rpm -Uvh kernel-firmware-2.6.32.fcoe.next-5.bcm.x85_64.rpm
Current Limitations: ==================== 1. No PFC/DCBx 2. Upstread Only Release (This is not the driver that can be directly installable on RHEL5.4 kernel)
Debug Data to collect in case of failure: ========================================= 1. syslog (/var/log/messages) 2. uname -a output 3. grcDump (for FW asserts) brcm_dd_nic_nx2-2_2_1j-1_72_18_sles10_32-64_chg
**************************************************************** | | | | | IBM Online Tape Drive/Optical Update Program | | Revision: 1.11.00.1075 Build Date: 6.23.11 | | | | (C) Copyright International Business Machines Corporation | | 2000-2011 . All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Note: Before using this information and the product it | | supports, read the general information under "NOTICES AND | | TRADEMARKS" in this document. | | | | Updated: 6/23/2011 | | | ****************************************************************
CONTENTS:
Change History
ver 1.1
Increased the tape tension during drive cleaning from 4g to 7g, which improves the cleaning effectiveness significantly.
ver 1.0
This firmware will change the firmware of your DDS tape drive to the latest available. ibm_fw_tape_dds-1_1_linux_32-64_chg
Integrated Management Module II (IMM2) Firmware Update Change History
Version 2.00, 1AOO40E - Critical Fix: -- Improves the reliability of the CPU and/or memory VRDs. This improvement lowers the occurrence of CPU & memory VRD failures on the x3300 M4 - Corrected a problem that caused 3.3V and 5V faults to be reported by IMM2 firmware level 1a0034z(1.85) on the H23E blade
Version 1.97, 1AOO36R - Critical Fix: -- Improves the reliability of the CPU and/or memory VRDs. This improvement lowers the occurrence of CPU & memory VRD failures on x3650 M4, x3550 M4 and x3500 M4 - Thermal behavior enhancement on System X iDataPlex dx360 M4
Version 1.95, 1AOO36P (for System x iDataPlex servers) - Added support for NVIDIA K1,K2,K20,K20x GPUs on System x iDataPlex dx360 M4
Version 1.88, 1AOO40A (for PureFlex System Compute Nodes) - Critical Fix: -- Fixed a potential security vulnerability with node management user accounts (Reference to Security Bulletin CVE-2012-4838) - Fixed a problem on Flex Systems where the SNMP get and set authority levels did not work - Fixed a problem on Flex Systems where mounting of remote media in a Linux environment showed a USB error - Fixed a problem on Flex Systems that caused the Remote Control Video Viewer window on a RHEL5.8 client to move when the arrow key is pressed - Fixed a problem on Flex Systems where the SMTP "Test Connection" button did not work when the SMTP port is changed - Fixed a problem on Flex Systems where the SNMP get and set authority levels did not work - Fixed a problem on Flex Systems where mounting of remote media in a Linux environment showed a USB error - Fixed a problem on Flex Systems that caused the Remote Control Video Viewer window on a RHEL5.8 client to move when the arrow key is pressed - Fixed a problem on Flex Systems where the SMTP "Test Connection" button did not work when the SMTP port is changed - Corrected the Mezzanine card power fault monitoring on the Flex System x440 Compute Node - Corrected a problem with IBM Fabric Manager configuration from the Flex Chassis Management Module - Added support to retrieve configuration settings from an LDAP server - Added support for the Flex Storage Expansion Node - Added support for CIM indications over https - Added fingerprint checking for SFTP transfers - Added automatic recovery of corrupted UEFI firmware - Added support for authenticated SMTP alerts - Added a display of the users who have a Remote Control session in progress - Provided a request to a Remote Control client to disconnect the session - Added support for the server S3 (sleep) state - Changed the default NTP sync interval from 3 minutes to 24 hours - Fixed a problem where the ambient temperature is only displayed in degrees Fahrenheit - Fixed a problem on the web interface where 'local' is not accepted as a top level domain name in the email format when configuring event recipients - Corrected an IMM2 SNMP trap OID to match the prior IMM format - Fixed a problem that prevented an external USB device from being remotely mounted as a floppy drive in Windows Server 2003 - Changed the blue Location led behavior to not blink when a firmware update is in progress
Version 1.85, 1AOO34Z (for BladeCenter blades and System x Servers) - Critical Fix: -- Fixed a potential security vulnerability with node management user accounts (Reference to Security Bulletin CVE-2012-4838) - Fixed a problem where a Blade Open Fabric Manager uncorrectable error can occur when booting the HS23 - Fixed a problem that IMM IPMI command periodically timed out when using HS23 in Chassis with the management network being disabled in some special configurations - Added support for the HS23 to recognize NEBS/Enterprise Mode for Telco chassis (this feature needs Advanced Management Module Firmware BPET62U or later) - Fixed a problem where the ambient temperature is only displayed in degrees Fahrenheit - Fixed a problem where on rack systems that have 2 power supplies installed, the 'Redundancy Power unit has been restored' event is logged every time that the IMM2 is reset - Fixed a problem where a Fan Tach going low (lower critical) event is intermittently asserted when configuring the IMM2 to use an NTP server - Fixed a problem on the web interface where 'local' is not accepted as a top level domain name in the email format when configuring event recipients - Corrected an IMM2 SNMP trap OID to match the prior IMM format - Fixed a problem that prevented an external USB device from being remotely mounted as a floppy drive in Windows Server 2003 - Changed the blue Location led behavior to not blink when a firmware update is in progress - Fixed a problem on the HS23E that causes Preboot DSA to hang in CLI mode when a user accesses it using Serial over LAN - Fixed a problem on rack servers where ASU cannot set IMM.GRP_GroupName.1 and IMM.GRP_GroupName.2 if the string length is 16 characters or longer. The firmware was corrected to allow a maximum length of 64 characters - Added support for CIM indications over https - Added fingerprint checking for SFTP transfers - Added automatic recovery of corrupted UEFI firmware - Added support for authenticated SMTP alerts - Added a display of the users who have a Remote Control session in progress - Provided a request to a Remote Control client to disconnect the session - Added support for the server S3 (sleep) state
Version 1.85, 1AOO34Y (for PureFlex System V7000 Storage Node) - Added support for Flex System V7000 Storage Node
Version 1.79, 1AOO36F - Thermal behavior enhancement on System X iDataPlex dx360 M4
Version 1.78, 1AOO36E - Thermal behavior enhancement for 115W & 95W CPU on System X iDataPlex dx360 M4 - Added support for the Intel KNC 5110p card
Version 1.77, 1AOO32X - Thermal behavior enhancement for 115W CPU on System X iDataPlex dx360 M4
Version 1.75, 1AOO32S - Fixed a problem that a PCI uncorrectable error occurs when using HS23 with CFFh card (44W4479) in the BCS chassis - Fixed a problem where an "Unsupported blade/blower combination" error is reported when using the HS23 in the BCHT chassis configured in Enterprise mode - Fixed a problem in System x3530 M4, where the reported Active Energy Manager input/output power readings are inaccurate - Fixed a problem in System x3530 M4, x3630 M4, where an LDAP account can not login using the AD_CrossDomain tree - Fixed a problem in System x3530 M4, x3630 M4, where a user cannot use the "DNS to Find LDAP server/Extract search domain from login ID" setting from the IMM2 web to access an eDirectory server - Added support for Common Form Factor power supplies Oversubscription in System x3750 M4, Machine Types: 8722, 8733
Version 1.65, 1AOO32O - Support the power supply Over-Subscription feature - Support the 750 Watt DC power supply for System x3650 M4,x3550 M4 - Support IBM 1.2TB High IOPS MLC Mono Adapter, IBM 2.4TB High IOPS MLC Duo Adapter for System x3650 M4, x3550 M4 - Support IBM LLM-SM Dual Port 10GbE SFP+ Adapter for System x3650 M4 - Fixed an abnormal Fan Zone recovery problem - Fixed a problem that IMM2 Email notification doesn't support an e-mail address with the underscore '_' character - Fixed a power policy "Restore" problem - Fixed a problem where the LDAP hostname can't be changed by ASU - Fixed a problem that the length of email address (for SNMP notification) is limited to 32 characters
Version 1.60, 1AOO32P - Fixed a problem where the Chassis Management Module cannot correctly get the Mezzanine card information for the Flex System x220 Compute Node - Fixed a problem where the PreBoot DSA firmware could not be updated under VMWare ESXi 5 through the Flex System Manager's Update Manager - Fixed a problem where an IMM2 communications error can occur if an unexpected response causes VMware to spawn multiple processes when it does not receive the data it expects from the IMM2
Version 1.59, 1AOO32K - Supports System x3300 M4, Machine Types: 7382
Version 1.53, 1AOO30Z - Included an update to the FPGA that fixes an intermittent issue where the CPUs do not show up in a system with a RAID card installed, when the AC is removed and reapplied from the server without allowing sufficient time for the system hardware to completely discharge
Version 1.52, 1AOO34A - Added redundant power supply and hot swap hard drive support in System x3100 M4
Version 1.51, 1AOO30Y - Support for NVIDIA Tesla K10, M2070Q, M2090 GPU cards on System X iDataPlex dx360 M4 - Fixed a problem in System X iDataPlex dx360 M4 where the password expires after creating a new user in the IMM2 web interface - Fixed a problem in System X iDataPlex dx360 M4, when the memory sensor changes from 'critical' to 'warning,' but the severity is not updated in the syslog or the email notification
Version 1.50, 1AOO30W - Supports System HS23, Machine Types: 7875,1929 - Supports System x3650 M4, Machine Types: 7915 - Supports System x3550 M4, Machine Types: 7914 - Supports System x3500 M4, Machine Types: 7383 - Added support for the Intel Xeon E5-2643 processor on the HS23 in BCH-R3, BCS and BCHT chassis - Fixed a problem where the IMM2 incorrectly logged an "Unsupported blade/blower combination" on the HS23 in the BC-E 8677 chassis - Fixed a power restore problem on systems that have 2 Delta power supplies installed - Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where OpenLDAP Group Authentication filtering function doesn't work - Fixed a problem in System x3650 M4, x3550 M4, x3500 M4, where LDAP account can not login using the AD_CrossDomain tree
Version 1.45, 1AOO28S - Fixed a problem in Flex System x220 where the Chassis Management Module (CMM) Command Line Interface can't display the Mezzanine card information - Fixed a problem in Flex System x220 and x240 where the prebootDSA firmware cannot be updated through Flex System Manager's Update Manager
Version 1.40, 1AOO30T - Supports System x3750 M4, Machine Types: 8722, 8733
Version 1.38, 1AOO30D - Supports System x3630 M4, Machine Type: 7158 - Supports System x3530 M4, Machine Type: 7160
Version 1.36, 1AOO30P - Fixed an intermittent remote media failure in system HS23E - Fixed a problem in system HS23E where remote media does not work when two or more users have concurrent remote control sessions
Version 1.34, 1AOO28Q - Supports Flex System Manager Node, Machine Type: 8731 - Supports Flex System x240 Compute Node, Machine Types: 7863, 8737, 8738 - Supports Flex System x220 Compute Node, Machine Types: 2585, 7906
Version 1.32, 1AOO28N - Supports System x3630 M4, Machine Type: 7158 - Supports System x3530 M4, Machine Type: 7160 - Fixed a problem that may see unexpected fan events after power on in x3100 M4 and x3250 M4 systems - Enhanced robustness on I2C bus test
Version 1.30, 1AOO28M - Supports System HS23E, Machine Types: 8038,8039
Version 1.26, 1AOO26N - Supports System x3650 M4, Machine Types: 7915
Version 1.25, 1AOO26K - Supports System x3550 M4, Machine Types: 7914 - Supports System x3500 M4, Machine Types: 7383 - Supports System X iDataPlex dx360 M4, Machine Types: 7912,7913
Version 1.22, 1AOO26O - Supports System HS23, Machine Types: 7875,1929 Problems Fixed: - Fixed a problem where the BOFM configuration may be lost after a blade power cycle - Fixed an LED error indication that occurs on the BPE4 - Fixed a problem where the Info LED lights during the discovery stage - Fixed a problem where an ABR event is not logged - Fixed an intermittent communication problem between the AMM and IMM2 - Fixed a problem that causes the remote media function to hang when a second user attempts to mount remote media - Fixed a problem where the 'break' keyboard function doesn't work with Serial Over LAN
Version 1.21, 1AOO26L - Supports System HS23, Machine Types: 7875,1929
Version 1.10, 1AOO24B - Supports System dx360 M4, Machine Types: 7918,7919
Version 1.05, 1AOO10K - Fixed the false alert issue in redundant PSU model
Version 1.00, 1AOO10I - Initial Release - Supports System x3250 M4, Machine Types: 2583,2587 - Supports System x3100 M4, Machine Types: 2582,2586
(C) Copyright International Business Machines Corporation 2008 - 2013. All rights reserved.
ibm_fw_imm2_1aoo40e-2_00_anyos_noarch_chg
=============================================================================== Multiboot Image for QLogic 10 Gb Converged Network Adapter for IBM System x
Q8Q10042.BIN contains: ---------------------- * BIOS version 2.11 * UEFI version 3.12 * Fcode version 3.02 * Firmware version 5.01.02 * MPI version 1.35.02 * PXE Boot version 1.03 * NIC EFI version 1.02
================================================================================= Original Release Notes from QLogic...
Release Notes
QL24rom BIOS Release notes
Rev 1.00 Jan.20, 2005 Initial release. Rev 1.01 Feb.18, 2005 Added code to put Port ID of device in IOCB. Rev 1.02 Mar.28, 2005 Added support for Serial Link Control. Addded code to display slot, bus number and function in CTRL-Q utility. Rev 1.03 Apr.18, 2005 Fixed bug when no drives attached and connected to switch. Added code to reset ISP if ISP is paused when ISR is called. Rev 1.04 June 8, 2005 Fixed bug in CTRL-Q utility that caused adapter id to be displayed at invalid id's. Added code to set Write Protect in Flash Status reg. Fixed bug in CTRL-Q utility where EAX reg was being corrupted by timer interrupt routine. Fixed bug in setting up LUN field in IOCB. Fixed bug in not setting port ID when connected to a switch. Rev 1.05 Sept 27, 2005 Changed code to suppress padding firmware version with leading zero's. Fixed bug in setting data direction flags in IOCB for 'seek command'. Changed code to not count device if device disabled by system BIOS. Fixed bug in setting flash Write Protect. Rev 1.06 Oct. 13, 2005 Fixed bug where anykey could invoke Fastutil. Rev 1.09 Nov. 22, 2005 Changed buffer request size to 2056 bytes for 'Report Luns' command. Fixed bug where GAN_NXT IN_ID was not always being set to zero causing GAN_NXT to fail. Rev 1.10 an. 31, 2006 Added check for optional boot mode flag to allow code to configure 1 drive/port when enabled. Bit 6 of host parameters in NVRAM is set to enable this mode. Fixed bug when Spinup-Delay and link is down. Added code to not display Data Rate option in CTRL-Q for QME2462. Rev 1.11 Feb. 7, 2006 Added support for interrupt polling. This option is controlled by bit 7 of NVRAM Host Parameters and by new Advanced Settings option in CTRL-Q. Rev 1.12 Feb. 21, 2006 Changed format of PnP string to display when Opt Boot Mode enabled in NVRAM. Added check for ELS reject status from Login IOCB. Rev 1.13 Apr. 04, 2006 Fixed bug in not always setting port id for logout IOCB. Changed code to support up to 16 adapters and 16 drives. Rev 1.14 Apr. 17, 2006 Changed code to ignore CLP '_hss' string. Rev 1.15 Apr. 20, 2006 Added code to wait for Login to complete when login pending status detected. Rev 1.16 May. 4, 2006 Fixed bug in not setting up Luns/Target in CTRL-Q. Added code to support Restore Default option CLP string (PCI3.0 BIOS only). Changed timeout value waiting for Linkup status from 6 seconds to 23 seconds. Rev 1.17 June 29, 2006 Added support for restoring defaults using CLP string (Pci3.0 only). Optimized code waiting for Linkup status. Added code to use Memory Map I/O for PCI express. Added code to check for correct Max Payload Size on QLE2464. Rev 1.18 July 19, 2006 Added code to load Nec switch port 1 and 2 pci config regs offset 68h with port 0 config offset 54h value. Fixed bug where task attributes in IOCB type 7 were not always being initialized. Rev 1.19 July 24, 2006 Fixed bug in CTRL-Q utility configuring Luns using Report Luns data when lun list has more lun entries after lun 255. Rev 1.20 Aug 2, 2006 Added code to support QLE2xx. Rev 1.21 Aug 24, 2006 Fixed bug in CTRL-Q cursor positioning for some user input displays. Rev 1.22 Sept 11, 2006 Added support for 'exit' CLP string. Changed CLP string to support new format: 'PermanentAddresses' was changed to 'PermanentAddress. Rev 1.23 Oct 16, 2006 Fixed bug in not setting rc_hba when different adapter types installed in system. Rev 1.24 Nov 29, 2006 Removed Extended Error Logging option from CTRL-Q. Removed code to use Memory Map I/O for PCI express. Rev 1.25 Dec 12, 2006 Added code so that set Defaults only to restores factory setting when value was modified by CLP string Rev 1.26 Dec 20, 2006 Fixed issue with the handling of CLP WWNN string. Also added code to always set firmware nodename optiom when set Default CLP is received. Rev 1.27 Feb. 26, 2007 Added support for Set Capabilities CLP string. Added code to load PLX switch port 1 and 2 pci config regs offset 68h with port 0 config offset 54h value (this is same code used for NEC switch). Rev 1.28 Apr. 12, 2007 Added code to check if need to restore HBA default portname. Added check for command fail status after login cmd. Restored code to read block 0 to determine drive geometry. Added NVRAM option (host_params bit 8) to enable support for HP boot order. Fixed bug in handling CLP Set Capabilities data. Rev 1.29 May. 22, 2007 Restored CTRL-Q Lun per Target option and changed text from 'Boot order' option to 'Controller order'. Rev 2.00 Dec. 03, 2007 Added support for ISP2532. Rev 2.01 Jan. 17, 2008 Added support for 1Gb data rate for 4Gb HBA. Rev 2.02 Feb. 18, 2008 Changed code to clear 'Disable Serdes' flag for CLP string Restore Default. Rev 2.03 Mar. 12, 2008 Added support for ISP8423. Added code to support new CLP 'set capability' spec. Rev 2.04 Mar. 23, 2008 Changed code to not used bit 13 of Host parameters. This avoids potential confict with inbox driver. Rev 2.05 Jun. 3, 2008 Added code to allow 2 min for link to come up when spinup delay enabled. Added code to poll for keyboard status. Removed external Loopback test option for ISP8432. Added check if IO support valid. Added check to CLP set_capablity string for the correct HBA port. Rev 2.06 Jun. 18, 2008 Added support for new CLP 'set capability' serial link spec for ISP2532. Rev 2.07 Sept. 3, 2008 Added additional error message for Verify Disk utility when device does not support SCSI cmd 2fh. Add support for Extended HBA CLP strings. Rev 2.07.6 Sept. 12, 2008 Fixed bug with 'restore netport defaults' when restoring NPIV's. Added code to reset ISP before accessing NVRAM the first time. Rev 2.07.8 Oct. 22, 2008 Added support for IDT PCIe switch Fixed bug in restoring NPIV after updating with CLP. Rev 2.08 Oct. 30, 2008 Removed TEST ONLY from BIOS banner. Rev 2.09 Dec. 02, 2008 Added code to save some pci data. Added new option to Advanced Option menu in CTRL-Q for Virtual Fabric Enable/Disable. Rev 2.10 Feb. 24, 2008 Added support for ISP8001 Added check for INT Polling before updating interrupt controller(PCI3.0) Fixed bug where eax register was being corrupted in nvram_config routine. Removed option in CTRL-Q for Virtual Fabric Enable. Fixed cosmetic bug in displaying selectable boot lun in CTRL-Q utility. Rev 2.11 Apr. 28,2009 Fixed issue with setting up Init FW MB command for using Extended Init Control Block Added option in CTRL-Q utility for Primary FCF VLAN ID for ISP8001 HBA. Added code to check version field of Extended ICB. Added code to correctly identify pci switch on 4 port HBA's. Changed code to suppport Loopback mode with new version of FW. Rev 2.12 May, 15,2009 Changed code to handle HSS CLP vendor id 3 same as vendor id 2. Rev 2.13 July 16, 2009 Added code to save backup copy of VPD/NVRAM data. Rev 2.14 Oct 9, 2009 Changed code to use FS segment register instead of GS in find_device routine. Change code to preserve MSB of WWPN Set Capablity CLP when updating WWPN/WWNN.
Driver Name : Fibre Channel Driver for UEFI Version : 3.33 Date : 5/9/2010 OS platform : N/A FW version : See MultiBoot release notes for FW version. Efiutil Version : 2.86
Table of Contents I. Overview II. Enhancements III. Bug Fixes IV. Known Issues V. Additional Information
I. Overview
The following document provides details of the Fibre Channel UEFI driver version 3.33 Efiutil version 2.86.
II. Enhancements
None
III. Bug Fixes
Driver: * Rename "Reconnect and Exit from Main Menu" HII entry to "Exit from Main Menu".
Efiutil: * Add fix to display new firmware version correctly while updating multiboot image. (ER71468) * Add support for 82xx family in Adapter list. (ER69230)
IV. Known Issues
Driver: * The driver does not support 24xx/25xx based HBAs. * In the HII menus, Adding/Deleting a Target/LUN will require a reboot for changes to take effect.
V. Additional Information
None
******************* QLogic Fcode for IBM CNAs ***************** Release Notes
This software license applies only to QLogic customers. QLogic Corporation. All rights reserved.
Table of Contents
1. Version 2. Changes 3. Bug Fixes 4. Known Issues 5. Additional Information 6. Trademarks 7. Notices 8. Contacting Support
1. Version
These release notes describe the changes, fixes, known issues, and release details that apply to the multi-boot package for the Converged Network Adapter (CNA).
* Reference the Read1st.txt for the kit version information.
2. Changes
These release notes describe the changes, fixes, known issues, and release details that apply to FCOde version 3.09
Hardware Support
* Supports QMI8142 and p-QLE8142 CNA (requires FCode for PPC) * Supports QLE81xx_FCode (requires FCode for SPARC)
Software Components
N/A
Industry Standards Compliance
N/A
3. Bug Fixes
Version 3.09 * Fix Node-Name-Option bit preservation in restore-default-settings.
Version 3.08 * Fix default WWNN & WWPN preservation in restore-default-settings. * Add standard properties. Use m4 utility to automaticly create date string. * Add file rev_level.m4 which has the revision level strings only. * Remove "SFP state: Unknown" message (.isp) if the adapter is IBM mezz card. * Change messages "Login failed" to "Login Abort". "Error Subcode" to "Subcode". * Remove patch of PCI header image size byte at offset 0x2c from init version.
Version 3.07 * Fix read-cap16-cmd. Used when the LUN size is >2TB (i.e. #blocks > 32-bits). * Fix disk-test to work with large (>2TB) LUNs, where the LBA > 32-bits. * Remove command retry when 8048 AEN is received.
Version 3.06 * Add option for qlgc-debug? in nvramrc. If the diag-switch? is true, then the debug? flag is set is set to the value of qlgc-debug?. * Add lba64 large disk capability (read-blocks64 write-blocks64) for SUN only. * Add mbox1 & mbox2 display for 8048 interrupt if debug-asyc? flag (01) is on. * Fix bug in IBM fcp-luns method for the Controller LUN-0 check, lun0-check. * Check Inquiry Qualifier field of Controller LUN-0 in IBM fcp-luns method. * Add more IOCB debugging, Add Erase Response-Queue in mapmem. Had stale data. * Add more debugging for IOCBs, dma-map-in/out, & wait-for-interrupts.
Version 3.05 * Fix set-fc-address issue found with IBM ioinfo. PortID was not getting set. * Re-structure devicepresent.fth. Add set-phandle to set obp-target & obp-portid * Fix multiple close issue found with IBM ioinfo utility.
Version 3.04 * Add alloc-sec-buf & free-sec-buf words with debugging messages. * Add "ibm,write-supported" property to disk child node, as per IBM's request. * Removed VPD validation from validate-nvram due to bug in update utilities. * Fix enab-nvr-acc to alloc sec-buf & add disab-nvr-acc for BOFM word.
3.03 * Added console messages when validate-nvram finds corruption & copies a sector. * Change validate-nvram to check both FC ports on Dual-port CNAs at probe time. * Fix init-flt-offsets to mask FLT attributes. Now it finds FW & Feature-key. * Added restart-mpi after the beacon test finishes to reset LED functionality. * Add NVRAM backup Sector. Add validate-nvram at probe time to fix corruption.
3.02 Initial release.
4. Known Issues
None
5. Additional Information
6. Trademarks
QLogic, the QLogic logo, QLA, QLE, QMI, SANbox, SANsurfer, and SANblade are registered trademarks of QLogic Corporation.
SANtrack and SAN Express are trademarks of QLogic Corporation.
All other brand and product names are trademarks or registered trademarks of their respective owners.
7. Notices
Information furnished in this document is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications described in this document for any of these products are only for illustrative purposes. QLogic Corporation makes no representation nor warranty that such applications are suitable for the specified use without further testing or modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.
8. Contacting Support
Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods:
Web: http://support.qlogic.com North America Contact Information
Email: support@qlogic.com Phone: (952) 932-4040
Support contact information for other regions of the world is available at the QLogic website: http://support.qlogic.com
(c) Copyright 2010. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.
qlgc_fw_cna_qle8142-1_01_94a_linux_32-64_chg
**************************************************************** | | | Tape LTO firmware update | | | | | | (C) Copyright International Business Machines Corporation | | 2000-2010 . All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Note: Before using this information and the product it | | supports, read the general information under "NOTICES AND | | TRADEMARKS" in this document. | | | | Updated: 9/24/2010 | | | ****************************************************************
Change History
ver 1.4_01
updated firmware for LTO 4 to A23E
ver 1.4_00
updated firmware for LTO 5 to A6S1 updated firmware for LTO 4 to A231
ver 1.3_02
update .txt and .chg files
ver 1.3_01
corrected XML / TML file names for new firmware (A4Q1 -> A5M1)
ver 1.3_00
updated firmware for LTO 5 to A5M1
ver 1.2
updated firmware for LTO 5 to A4Q1
ver 1.1
updated XML / TML to add new systems
ver 1.0
This firmware will change the firmware of your LTO tape drive to the latest available, unless it is already at the latest level.
- IBM HH LTO5 SAS (49Y9898 - 3628L5X - 3628N5X) @ A2C1 - IBM HH LTO1 SCSI (24P2396 - Newton) @ N2CG - IBM HH LTO1 SCSI (24P2396 - Pompy) @ P63I - IBM HH LTO2 SCSI (39M5658) @ 0468 - IBM HH LTO3 SAS (43W8478) @ 93G1 - IBM HH LTO4 SAS (44E8895) @ 93Y1 - IBM FH LTO1 SCSI (00N8016) @ 59C0 - IBM FH LTO2 SCSI (59P6744) @ 8571 - IBM FH LTO3 SCSI (39M5657) @ 87G0 ibm_fw_tape_lto-1_4_linux_32-64_chg
IBM 7382 (IBM system x3300 M4 tower Server) uEFI Flash Update Version 1.10 (BuildID YAE124B) Change History
Version 1.10 - BuildID: YAE124B ------------------------------------------------- Problem(s) Fixed: - System occurs BSoD after onboard SATA been changed from "IDE" to "AHCI" mode. - 2nd Ethernet did not show up after changing IMM2 from dedicated to shared. - System will sometimes boots into Windows repair mode while rebooting System. - PCI Slot Error LED will light on after pressing the dump button of Hyperion PCIE NVRAM adapter. - iSCSI Attempt will disappear after rebooting in Legacy OS.
Enhancements: - Add support for automatic ROM recovery - Add support for dynamic debug capability - Improve Update Security - Improve Configuration Support - Add common support for OS-4690
Limitations: Dependencies:
Version 1.01 - BuildID: YAE116D ------------------------------------------------- Problem(s) Fixed: Enhancements: - Set PCH SKU A with uplink enable.
- All VFS on Port 1 on optional Card unreachable from outside the host (x3750 M4) - 'Logical Admin Link' not enabled after applying BOFM in Switch Agnostic mode - IBM pre-boot Diagnostics NIC physical loopback test fails in Command and GUI mode - Multiple cosmetic issues with iSCSI UEFI BIOS - 10Gb ports do not detect 'Link Down' with some switches - 1Gb ports on HS23 LOM not able link up with IBM ICPM (FRU part 44W4486) in BCS chassis - Performance issues with specific DAC cables and SND top of rack switch
Interoperability since previous release:
- UEFI 2.3.1 Compliance - Increased VF count in SR-IOV (was 16 VFs per port, is now 32 VFs per port) - Support for next generation 10GbaseT PHY
Known Issues:
- All 10Gb KX4 ports must be used with 10Gb switches. They will not link at 1Gb. This applies to HS23 LOM and IBM BladeCenter VFA adapters only. - IPv6 IP address not visible via IMM GUI for IBM Option 90Y6456 - Intermittent link status with IBM Virtual Fabric Switch when set to IBM Virtual Fabric Mode - The option to enable/disable SRIOV on HS23 LOM Port 0 is missing from OneCommand Manager. This selection is available in UEFI F1 setup.
Problems Fixed: - Fixed an issue where ASIC randomly hangs losing network connectivity when certain commands are sent from the host. Resulting behavior varies between OS's (Yellow bangs in Windows, PSOD in VMWare) - PHY Loopback fails on 10G ports - UE and hang on LOM or Robalo when powering off Janice in UEFI or PXESelect - Loopback on HS23 now functional in DSAp - DCBX does not converge with firmware on a FCoE fabric - Control C Broken on BE2 - 7 second delay in GET_CARD_ATTRIBUTES command - Emulex VF adapter FCoE link lost on VMware 5.0 - flow control set for 10G Base T phys for autonegotiation - Dynamic link update is not working with NIC UEFI driver - Remove unused definitions in UEFI NIC - Emulex driver expects that the Login Options field be zero - "map r" displays a iSCSI BLK device when no LUNs presented - "X/x Exit without save" does not work as expected - Display proper description as part of EFI Driver Model Related Information - Intermittent "Configuration changed. reset to apply it now?" - Garbled output being displayed at the LUN configuration section. - All Emulex Configuration settings get lost after a reset - Perform additional checks when no Luns are mapped to the target - CHAP name only accepts 6 to 10 characters - Hii ???iSCSI Initiator Configuration??? showing old version screen - iSCSI name is case sensitive - iSCSI HII allows user to select first 8 LUNs as bootable. - iSCSI Boot Enable/Disable option should be port specific - LUN Configuration shows LUN 0, even if no LUNs presented to initiator.
Interoperability Since Previous Release:
- Support for Emulex Virtual Fabric Adapter Advanced (CFFh, 2+2) for IBM BladeCenter
- NCSI transmit workaround for IBM - Issues with data reporting when BOFM enabled - Improved network performance throughput - Issues with IBM Management network performance - Logical link status for IBM mezz card shown as 'N/A' - Serial Over LAN fails when more than one blade installed with a single switch - Removed UEFI menu items for unsupported functions on a port - Issues with diagnositics in virtual NIC/UMC mode - Issues with MAC and PHY loopback on OneConnect devices - Several issues with FCoE on some OEM fabric switches
Interoperability Since Previous Release:
- Support for HS23 Virtual Fabric LAN on Motherboard - Support for VFA III (95Y3762, 95Y3768), 90Y6456 - Support for IBM's Features on Demand (FOD) - Formal support for SR-IOV
- iLab Tucson - lpfc Device Resets and path failures continue after error inject. - Writes do not complete when running LIP test on BE3 port 2 - IPV6 implementations no longer experience an unrecognized routing type error. - VLAN tagging is now disabled on the OneConnect UCNA when multichannel is disabled. - UEFI/BIOS-assigned LPVIDs now function properly on the OneConnect 10102-based UCNA. - OneConnect UCNAs no longer send and receive only double-tagged packets and discard all other packets. - PHY, MAC, and External loopback tests no longer fail on all platforms. - Firmware now returns the proper OneConnect UCNA model number. - IPV6 implementations no longer experience an unrecognized routing type error. - Installing Windows 2008 or Windows 2008 R2 on remote iSCSI disks no longer causes the system to hang. - Issues no longer occur when resetting a server configured for multipathing on VMware ESX systems. - VLAN tagging is now disabled on the OneConnect UCNA when multichannel is disabled. - UEFI/BIOS-assigned LPVIDs now function properly on the OneConnect 10102-based UCNA. - OneConnect UCNAs no longer send and receive only double-tagged packets and discard all other packets. - An adapter hardware error no longer occurs when running I/O with LUNs on x86 platforms. - Changing from Convergence Enhanced Ethernet (CEE) to Chassis Internal Network (CIN) and then rebooting no longer fails to link-flap (CIN Fabric Login (FLOGI) now occurs). - PHY, MAC, and External loopback tests no longer fail on all platforms. - Firmware now returns the proper OneConnect UCNA model number. - DCB settings can now be configured. - (iSCSISelect) When enabling DHCP for an iSCSI initiator, the Emulex iSCSI Network Configuration utility now waits approximately 20 seconds to make a DHCP connection before returning control. - (FCoE BootBIOS) FCF CEE parameters for Boot from SAN configuration are now saved properly.
Interoperability Since Previous Release:
- Added support for switch-independent multichannel mode. - Added support for IBM Virtual Fabric 10Gb RackSwitch firmware 6.8.1.0. - Added support for IBM Virtual Fabric 10G Switch Module firmware 6.8.1.0. - Added support for Fibre Channel over Ethernet (FCoE) on rack systems. - Added support for iSCSI hardware offload on rack systems. - Added support for Cisco Nexus 5000-series switches.
Broadcom Firmware Update Utility for IBM servers and options using the Broadcom NetXtreme and NetXtreme II ethernet adapter.
Version 2.1.8e, Aug 09, 2012
This package was modified to update UEFI code to "7.0.46" for 57110, 57111,57112 devices (46M6164,46M6168,44W4465, 44W4466, 81Y3133, 42C1790, 42C1791, 49Y7910). These are the only change from version 2.1.8d to 2.1.8e.
This package updates the Broadcom firmware for the following items:
For information regarding changes specific to your product, download the change history zip file (brcm_fw_nic_2.1.8e-chg_anyos_anycpu.zip). The name of the files containing changes for your product are listed above.
package version 2.1.8e (See brcm_fw_nic_2.1.8e-chg_anyos_anycpu.zip for details.) Problems Fixed: - "Cobia 712 card does not show in UEFI after BOFM is enabled". (Change were made to the UEFI code for 46M6164,46M6168, 44W4465, 44W4466, 81Y3133, 42C1790, 42C1791, 49Y7910)
package version 2.1.8d (See brcm_fw_nic_2.1.8d-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 46M6164, 46M6168, 49Y7910 and 81Y3133. - Changes were mande to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168, 49Y4220, 49Y7910 and 81Y3133. - Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168, 49Y4220, 49Y7910 and 81Y3133. - Changes were made to the iSCSI code for the 42C1780, 42C1781, 49Y4220 and 49Y7910.
package version 2.1.7e (See brcm_fw_nic_2.1.7e-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the UEFI code for the 42C1780, 42C1781, 44W4475 , 44W4479 , 44X1940
and 49Y4220. - Added support for the 49Y7910.
package version 2.1.7d (See brcm_fw_nic_2.1.7d-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4465 , 44W4466 , 44W4475 , 44W4479 , 44X1940 , 46M6164 , 46M6168, 49Y4220 and 81Y3133. - Fixed a problem where the MAC addresses for the HS22/HS22V LOM were incorrectly set to zero.
package version 2.1.7c (See brcm_fw_nic_2.1.7c-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 46M6164 and 46M6168. - Changes were made to the NCSI code for the 46M6164 and 46M6168. - Changes were made to the PXE code for the 42C1790, 42C1791, 46M6164, 46M6168, 44W4465 and 44W4466. - Changes were made to the UEFI code for the 42C1790, 42C1791, 46M6164, 46M6168, 44W4465 and 44W4466. - Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220.
package version 2.1.7b (See brcm_fw_nic_2.1.7b-chg_anyos_anycpu.zip for details.) Problems Fixed: - Fixed problem running the PPC firmware update tool on some PPC systems.
package version 2.1.7a (See brcm_fw_nic_2.1.7a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4195, 4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7148, 7149, 7164, 7233, 7234, 7378, 7379, 7380, 7809, 7836, 7837, 7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781, 42C1790, 42C1791, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220 - Changes were made to the NCSI code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4195, 4198, 4199, 4254, 4255, 7145, 7146, 7148, 7149, 7164, 7378, 7379, 7380, 7809, 7836, 7837, 7839, 7870, 7871, 7872, 7944, 7945, 7946, 7947, 44W4475, 44W4479, 46M6164 and 46M6168. - Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220. - Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220. - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220.
package version 2.1.6b (See brcm_fw_nic_2.1.6b-chg_anyos_anycpu.zip for details.) Problems Fixed: - The update tool was modified to fix a problem updating the firmware when certain option cards are installed in the system.
package version 2.1.6a (See brcm_fw_nic_2.1.6a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4195, 4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7148, 7149, 7164, 7233, 7234, 7378, 7379, 7380, 7809, 7836, 7837, 7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220 - Changes were made to the NCSI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790, and 42C1791. - Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220. - Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220. - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220.
package version 2.1.5b (See brcm_fw_nic_2.1.5b-chg_anyos_anycpu.zip for details.) Problems Fixed: - Added iSCSI config update support for mfg.
package version 2.1.5a (See brcm_fw_nic_2.1.5a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the NCSI code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4195, 4198, 4199, 4254, 4255, 7145, 7146, 7148, 7149, 7164, 7378, 7379, 7380, 7809, 7836, 7837, 7839, 7870, 7871, 7872, 7944, 7945, 7946, 7947, 44W4475, 44W4479, 42C1790 and 42C1791 - Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220. - Changes were made to the IPMI code for the 7141, 7144, 7233, 7234, 7901 and 7902.
package version 2.1.4a (See brcm_fw_nic_2.1.4a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168. - Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168.
package version 2.1.3c (See brcm_fw_nic_2.1.3c-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the iSCSI code for the 42C1780 and 42C1781. - Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168. - Changes were made to the boot code for the 46M6164 and 46M6168.
Enhancements: - Added version check to prevent firmware updates of code that is not newer than already installed code. - Added "-force" command line option to allow forcing the firmware update.
package version 2.1.3b (See brcm_fw_nic_2.1.3b-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7233, 7234, 7378, 7379, 7380, 7836, 7837, 7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781, 44W4475, 44W4479 and 44X1940. - Changes were made to the NCSI code for the 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 4254, 4255, 7145, 7146, 7378, 7379, 7380, 7836, 7837, 7839, 7870, 7871, 7944, 7945, 7946, 7947, 44W4475 and 44W4479. - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 44W4475, 44W4479 and 44X1940. - Changes were made to the UEFI code for the 42C1780, 42C1781, 44W4475, 44W4479 and 44X1940. - Changes were made to the iSCSI code for the 42C1780 and 42C1781.
package version 2.1.3a (See brcm_fw_nic_2.1.3a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the PXE code for the 26K4842, 39R8624, 39Y9306, 39Y9310, 42C1600, 42C1632, 46M6164, 46M6168, 44W4465, 44W4466, 73P9030, 22P7801, 31P6301, 31P6401, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 42C1790, 42C1791, 73P3501, 73P4001, 73P4101 and 73P4201. - Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790, and 42C1791. - Changes were made to the NCSI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790, and 42C1791. - Changes were made to the boot code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790, and 42C1791.
package version 2.1.1c (See brcm_fw_nic_2.1.1c-chg_anyos_anycpu.zip for details.) Problems Fixed: - none.
Enhancements: - Added support for the 1949, 4254, 4255, 7378, 7379, 7380, 7871, 7944 and 7945.
package version 2.1.1b (See brcm_fw_nic_2.1.1b-chg_anyos_anycpu.zip for details.) Problems Fixed: - Fixed problem where the firmware update failed to run correctly on RHEL5u4-XEN.
package version 2.1.1a (See brcm_fw_nic_2.1.1a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1885, 1913, 1914, 1915, 1936, 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 7141, 7144, 7163, 7233, 7234, 7809, 7836, 7837, 7839, 7870, 7901, 7902, 7946, 7947, 7978, 7979, 7995, 7996, 7997, 8853, 8877, 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 39Y6066, 42C1780, 42C1781, 42C1790 and 42C1791. - Changes were made to the NCSI code for the 1936, 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 7809, 7836, 7837, 7839, 7870, 7946, 7947, 44W4465, 44W4466, 44W4475, 44W4479, 42C1790 and 42C1791. - Changes were made to the PXE code for the 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 39Y6066, 42C1780, 42C1781, 42C1790 and 42C1791. - Changes were made to the UEFI code for the 44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 42C1780, 42C1781, 42C1790 and 42C1791. - Changes were made to the iSCSI code for the 42C1780 and 42C1781.
Enhancements: - Added support for the 46M6164 and 46M6168.
package version 2.1.0a (See brcm_fw_nic_2.1.0a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1936, 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 7141, 7144, 7233, 7234, 7836, 7837, 7839, 7870, 7901, 7902, 7946, 7947, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479 and 44X1940. - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479 and 44X1940. - Changes were made to the ISCSI code for the 42C1780 and 42C1781.
package version 2.0.9h (See brcm_fw_nic_2.0.9h-chg_anyos_anycpu.zip for details.) Problems Fixed: - Removed the minimum boot code level check for the 44W4465 and 44W4466.
Enhancements: - Added support for the 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 7836, 7837, 7839 and 9233.
package version 2.0.9g (See brcm_fw_nic_2.0.9g-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the UEFI code for 42C1780, 42C1781, 42C1790, 42C1791, 44W4465 44W4466, 44W4475, 44W4479 and 44X1940. - Fixed the problem where the PXE code for the 44W4465 and 44W4466 failed to update under 64bit Linux.
Enhancements: - Added support for the 7946 and 7947.
package version 2.0.9f (See brcm_fw_nic_2.0.9f-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7141, 7144, 7233, 7234,
7940, 7941, 7971, 7972, 7978, 7979, 7985, 7995, 7996, 7997, 8853, 8877, 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479. - Changes were made to the NCSI code for the 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479. - Changes were made to the PXE code for 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479.
Enhancements: - Added support for the 1936, 7870 and 44W4475. - Added UEFI code for 42C1790, 42C1791, 44W4465, 44W4466, 44W4479 and 44X1940.
package version 2.0.9e (See brcm_fw_nic_2.0.9e-chg_anyos_anycpu.zip for details.) Problems Fixed: - Added a bnx2 device driver version check for version 1.6.6b or greater.
package version 2.0.9c (See brcm_fw_nic_2.0.9c-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1885, 1915, 7901, 7902, 7971, 7972, 7995, 8853 and 44W4479. - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781 and 44W4479. - Changes were made to the iSCSI code for the 42C1780 and 42C1781 - Changes were made to the NCSI code for the 44W4479.
Enhancements: - Added support for the 44X1940.
package version 2.0.8f (See brcm_fw_nic_2.0.8f-chg_anyos_anycpu.zip for details.) Problems Fixed: - Fcode support was removed for the PXE code for the 44W4465 and 44W4466. This change does not result in a change in the PXE code version number. - Changes were made to the PXE code for the 39Y6066, 42C1780 and 42C1781 to fix a problem where some systems hang when loading PXE code.
package version 2.0.8e (See brcm_fw_nic_2.0.8e-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781 and 44W4479. - Changes were made to the IPMI code for the 7141, 7144, 7233 and 7234. - Changes were made to the UMP code for the 7901 and 7902.
Enhancements: - Added support for the 6388, 7942, 44W4465 and 44W4466.
package version 2.0.8d (See brcm_fw_nic_2.0.8d-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 7141, 7144, 7233 and 7234.
Enhancements: - Added support for the 42C1780 and 42C1781.
package version 2.0.8c (See brcm_fw_nic_2.0.8c-chg_anyos_anycpu.zip for details.) Problems Fixed: - None.
Enhancements: - Added support for the 7901 and 7902
package version 2.0.8b (See brcm_fw_nic_2.0.8b-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the PXE code for the 39Y6066.
Enhancements: - Added support for the 44W4479.
package version 2.0.8a (See brcm_fw_nic_2.0.8a-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7141, 7144, 7971, 7972, 7978, 7979, 7985, 7995, 7996, 7997, 8853, 8877, 9228, 9229, 9230 and 39Y6066. - Changes were made to the ASF code for the 6218, 6223, 6225, 6227, 6228, 8488, 8648, 9228, 9229, 9230. - Changes were made to the UMP code for the 39Y6066. - Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401, 39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600, 42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030. - Changes were made to the IPMI code for the 1916, 8014 and 8028.
Enhancements: - Added support for the 7233, 7234, 7940 and 7941.
package version 2.0.7 (See brcm_fw_nic_2.0.7-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401, 39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600, 42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030.
Enhancements: - Added support for the 1916, 8014 and 8028.
package version 2.0.6 (See brcm_fw_nic_2.0.6-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1913, 1914, 7141, 7143, 7144, 7978, 7979, 7996, 7997, 8877 and 39Y6066. - Changes were made to the UMP code for the 39Y6066. - Changes were made to the PXE code for the 39Y6066.
package version 2.0.5 (See brcm_fw_nic_2.0.5-chg_anyos_anycpu.zip for details.) Problems Fixed: - None
Enhancements: - Added support for the 4190, 4191, 4192, 4193, 4194, 4367 and 4368.
package version 2.0.4 (See brcm_fw_nic_2.0.4-chg_anyos_anycpu.zip for details.) Problems Fixed: - None
Enhancements: - Added support for the 7141, 7143 and 7144.
package version 2.0.3 (See brcm_fw_nic_2.0.3-lin-win-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7971, 7972, 7978, 7979, 7985, 7995, 8853, 8877, 39Y6066. - Changes were made to the IPMI code for the 1879, 1880, 1883, 1884, 1887, 4362, 4363, 4364, 4365, 4366, 7362, 7364, 7365, 7367, 7973, 7974, 7975, 7976, 7977, 7981, 7984, 7986, 8485, 8490, 8491, 8832, 8835, 8837, 8840, 8841, 8843, 8848, 8849, 8850, 8863, 8864, 8865, 8866, 8872, 8874, 8878, 8879. - Changes were made to the ASF code for the 6218, 6223, 6225, 6227, 6228, 8488, 8648, 9228, 9229, 9230. - Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401, 39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600, 42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030.
package version 2.0.0b (See brcm_fw_nic_2.0.0b-nx-nx2-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changed the firmware update process to NOT reset the ethernet devices during the firmware update process.
package version 2.0.0 (See brcm_fw_nic_2.0.0-nx-nx2-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the UMP (Universal Management Port) code for the 1885, 7971, 7972, 7995 and 8853.
package version 1.1.1 (See brcm_fw_nic_1.1.1-nx-nx2-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 1879, 1880, 1887, 4347, 4348, 4362, 4363, 4364, 4365, 4366, 6218, 6223, 6225, 6227, 6228, 7969, 7973, 7974, 7975, 7976, 7977, 7992, 8485, 8486, 8488, 8490, 8491, 8648, 8837, 8840, 8841, 8849, 39Y6098, 39Y9306, 42C1600, 42C1632 and 73P3501. - Changes were made to the IPMI code for the 1879, 1880, 1887, 4362, 4363, 4364, 4365, 4366, 7969, 7973, 7974, 7975, 7976, 7977, 7992, 8485, 8490, 8491, 8837, 8840, 8841 and 8849. - Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401, 39R8624, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600, 42C1632, 73P3501, 73P4001, 73P4101, 73P4201 and 73P9030.
package version 1.1.0 (See brcm_fw_nic_1.1.0-nx-nx2-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the Boot Code for the 1913, 1914, 4347, 6218, 6223, 6225, 6227, 6228, 7969, 7971, 7972, 7978, 7979, 7985, 7995, 8486, 8648, 8853, 8877, 9228 and 9229. - Changes were made to the ASF code for 6218, 6223, 6225, 6227, 6228, 8648, 9228 and 9229. - Changes were made to the PXE code for the 39Y6066. - Changes were made to the
Enhancements: - Added support for the 1879, 1880, 1883, 1884, 1887, 1913, 22P7801, 31P6301, 31P6401, 39Y9306, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9310, 4348, 4366, 7362, 7364, 7365, 73P3501, 73P4001, 73P4101, 73P4201, 7992, 7995, 8488 and 9230.
package version 1.0.0 (See brcm_fw_nic_1.0.0-nx-nx2-chg_anyos_anycpu.zip for details.) Problems Fixed: - Changes were made to the boot code for the 8832, 1914, 7971, 7972, 7978, 7979 7985, 8853 and 8877. - Changes were made to the UMP (Universal Management Port) code for the 7971, 7972 and 8853. brcm_fw_nic_2_1_8e_linux_32-64_chg