Release Notes
=============
Copyright (c) 2001-2013 Broadcom Corporation
All rights reserved.
Broadcom NetXtreme Unified iSCSI Crash Dump Driver
For Windows Server 2003, 2008, 2008R2 and 2012
NOTE: This driver requires KB939875 (http://support.microsoft.com/kb/939875)
when running on Windows 2003 when system is booted with MSFT iSCSI
Initiator (v2.0.5 or newer).
Version 7.6.50 Jan 11, 2013
-------------------------------
Fix:
=========
1. Problem: CQ#67278-Crashdump: Memory dump does not start when iBoot via 4th port.
Cause: Device ID for the 57840 device is not detected correctly.
Fix: Changed the crashdump driver to detect the device correctly.
Version 7.6.1 October 29, 2012
-------------------------------
Enhancements:
=============
1. Added support for new PCI device ID (0x1665) of BCM5717 C0 silicon.
Version 7.6.0 Oct 08, 2012
------------------------------
Enhancements:
=============
1. Added support for BCM84834 PHY.
Version 7.4.5 Aug 3, 2012
------------------------------
Enhancements:
=============
1. Request: Sync-up to the latest hardware access code from MBA.
Version 7.4.4 July 11,2012
-------------------------
Fix:
=========
1. Problem: CQ#64550 - iboot_Win2008-SP2-32: Memory dump does not start after Bang
Cause: Mismatched function prototype and calling convention in IPV6 setup path.
Fix: Changed the calling convention to match function prototype.
Version 7.4.3 June 27,2012
-------------------------
Fix:
=========
1. Problem: CQ#63588 Failed to generate crashdump on Wintarget.
Cause: Wintarget would fail login request with invalid session code
under some conditions.
Fix: Changed driver to handle invalid session code in a way to
workaround this problem.
Version 7.4.2 June 5,2012
-------------------------
Enhancements:
=============
1. Added support for BCM57840 devices with new PCI ID's.
Version 7.4.1 May 22, 2012
------------------------------
Fix:
=============
1. Problem: CQ#63410 Win8 security cookie corruption.
Cause: Stack overrun in processing login response.
Change: Prevent stack from overrun.
Version 7.4.0 May 02, 2012
------------------------------
Enhancements:
=============
1. Added support for BCM57811 devices.
Version 7.2.51 Apr 25, 2012
------------------------------
Fixes:
=============
1. Updated legal copyright year to 2012.
Version 7.2.50 Mar 15, 2012
------------------------------
Enhancements:
=============
1. Request: Sync-up to the latest hardware access code from MBA.
Version 7.2.4 Mar 5, 2012
------------------------------
Fixes:
======
1. Problem: Link detection problem in AFEX mode.
Change: In AFEX mode, eliminate link toggling before setting up PHY and
give sufficient time to wait for link to come up to cover extreme case
seen on some switch reported by PQA.
Enhancement:
===========
1. Added post mortem debugging facility.
Version 7.2.3 Feb 17, 2012
------------------------------
Enhancement
======
Initial support for AFEX mode.
Version 7.2.2 Feb 15, 2012
------------------------------
Fixes:
======
1. Problem: IPv6 stack may run into a dead loop under some specific network traffic
condition causing crashdump to hang.
Cause: IPV6 netif link-list is not initialized correctly.
Change: Initialize the Netif list correctly.
Version 7.2.1 Feb 09, 2012
------------------------------
Fixes:
======
1. Problem: CQ#60866-Crashdump: Dump process does not start on target MD3220i
when initiator is using static IP fe80::1221
Cause: LWIP uses source IP address (Link Local) to update ARP cache which
is different from the ICMPV6 target address.
Change: Changed LWIP to use ICMPv6 target address to update ARP table.
2. Problem: CQ#59766-iSCSI boot - 57810: Can't get the dump file when testing MPIO
with Router IPv6 adress
Change: Added DHCPv6 support for crashdump driver.
Enhancements:
=============
1. Request: Sync-up to the latest hardware access code to pick up fixes made to MBA.
Fixed the following problems:
CQ#61506-iBoot: Activity LED stays on solid when the Crashdump is running.
CQ#61534-57800S rNDC: iSCSI Boot Environment- Crashdump fails to create dump file
Version 7.2.0 Dec 13, 2011
------------------------------
Enhancements:
======
1. Request: Initial support for BCM84833.
Version 7.0.9 Nov 08, 2011
------------------------------
Fixes:
======
1. Problem: Sporadically after crash, dump does not complete (CQ#59654)
Cause: Internal buffer allocated to handle certain types IPV6 packets
may not be freed.
Changes: Fixed the memory leaks in the IPV6 handling code path.
Version 7.0.8 October 26, 2011
------------------------------
Fixes:
======
1. Problem: Hibernation intermittently failed after many iterations with
BCM57800 devices. (CQ#59424)
Changes: Updated PHY initialization code to optimize Warp Core reset
logic.
Version 7.0.7 October 11, 2011
------------------------------
Fixes:
======
1. Problem: Hibernation failed with iSCSI target that doesn't support
Immediate Data feature. (CQ#59169)
Cause: Crash dump driver uses single iSCSI command header. iSCSI
command header was not reinitialized after on the second or
subsequent iSCSI requests.
Changes: Fixed logic to reinitialize iSCSI command header in each
iteration.
Version 7.0.6 Sep 09, 2011
-------------------------
Fixes:
======
1. Problem: CQ#58429 In iSCSI boot configuration, system may fail to hibernate
to certain iSCSI targets.
Cause: Write requests may not be initialized correctly under some conditions
such that certain iSCSI targets may reject the requests.
Changes: Fixed the driver to initialize Write requests correctly.
Version 7.0.5 Aug 31, 2011
-------------------------
Enhancements:
=============
1. Integrated WC changes from PXE/MBA.
Version 7.0.4 Aug 18, 2011
---------------------------
Fixes:
======
1. Problem: CQ#56817 In iSCSI boot configuration, 57711 fails to go into S4.
Cause: PCI DMA master bit was turned off by the bus driver
during S3/S4 shutdown.
Change: Turn the PCI DMA master bit back on in crashdump
driver initialization.
Version 7.0.3 Aug 10, 2011
---------------------------
Fixes:
======
1. Problem: Crashdump failed with target redirect configuation (CQ#57432)
Change: Updated session code to handle Target Redirect scenario.
2. Problem: 578xx BSOD when SUT went to hibernation (CQ#55506)
Change: Updated Driver to fine-tune WC initialization.
Enhancements:
=============
1. Compilable with Tool kits for next generation of Windows.
2. Rename the binary to satisfy Windows INBOX program requirement.
Version 7.0.2 July 28, 2011
---------------------------
Fixes:
======
1. Problem: Crashdump failed with BCM578xx-based NIC when iSCSI boot
was configured to run in forced 1Gbps mode. (CQ#56866)
Change: Updated low-level driver to configure PHY link using MBA
link speed configuration.
Enhancements:
=============
1. Added support for BCM578xx B0 silicon.
Version 7.0.1 July 7, 2011
--------------------------
Fixes:
======
1. Problem: Hibernation to iSCSI boot LUN may fail.
Cause : iSCSI code doesn't handle 64K block write
requests correctly in WRITE I/O operations.
Change: Break down the large WRITE I/O into smaller requests.
2. Problem: Hibernation with free build x86 will crash.
Cause: Parameter mismatch in some internal routine.
Change: Fix the driver to pass in correct parameters.
Version 7.0.0 May 20, 2011
--------------------------
Enhancements:
=============
1. Added support for 4x10G or 2x10G+2x1G NICs.
Version 6.4.2 May 5, 2011
-------------------------
Fixes:
======
1. Problem: Crash dump file was not created correctly on EMC CX4
iSCSI target. (CQ#54958)
Cause : iSCSI session code doesn't handle partial block write
requests correctly in WRITE I/O operations.
Change: Fixed session code to handle partial block write requests
correctly.
Version 6.4.1 March 28, 2011
----------------------------
Fixes:
======
1. Fixed a problem where crash dump doesn't work with BCM5720. (CQ#54025)
Version 6.4.0 February 18, 2011
-------------------------------
Enhancements:
=============
1. Driver to read from register instead of from shared memory to determine
Copper/Serdes configuration.
Impact: BCM5718 B0, BCM5719, and BCM5720 family controllers only.
2. Add support for BCM57810 devices.
Version 6.2.1 December 23, 2010
-------------------------------
Enhancements:
=============
1. Updated Copyright banner to reflect year of 2011.
Fixes:
======
1. Fixed a problem where crash dump doesn't work with NetXtremeI Serdes
devices. (CQ#50429)
2. Problem: Crash dump might not complete successfully in some targets
when the targets are loaded/busy. (CQ#40626)
Cause : When targets are loaded/busy, these targets don't respond to
I/O write requests in a few seconds. Time-out for I/O request was too
short in the driver.
Change: Increased I/O timeout so that crash dump driver doesn't
terminate the write request too early.
Version 6.2.0 October 18, 2010
-----------------------------
Enhancements:
=============
1. Add fiber support for BCM5718 devices. (CQ#50429)
Version 6.0.2 August 13, 2010
-----------------------------
Fixes:
======
1. Fixed a problem where UNDI driver doesn't select PHY to use correctly
based on PHY selection configuration in a dual-media configuration.
2. Problem: Crash dump doesn't work with 1G mode with 10G devices.
(CQ#48803)
Cause : EMAC mode register was incorrectly programmed to 1G Half
duplex mode.
Change: Updated NX2 10G lower level driver to program EMAC mode
correctly.
Version 6.0.1 May 24, 2010
--------------------------
Fixes:
======
1. Problem: Crash dump doesn't work with 10G devices if VLAN is enabled.
(CQ#47923)
Change: Fixed a problem in the RX path of 10G low-level driver where
VLAN is not stripped correctly.
Version 6.0.0 May 18, 2010
--------------------------
Enhancements:
=============
1. Add support for BCM57712 devices.
2. Added support for BCM84823.
Version 5.2.0 November 3, 2009
------------------------------
Enhancements:
=============
1. Add support for BCM57761,BCM57765,BCM5717, BCM5718, and BCM5724.
Version 5.0.11 September 30, 2009
---------------------------------
Fixes:
======
1. Problem: Crash dump doesn't work with 10G devices where system is
booted with an iSCSI offload MPIO configuration. (CQ#43910)
Cause : There is a logic in the code that checks for association of
virtual address of the devices and the entry in the iBFT. In this
early stage, PCI function number was not initialized at that stage.
Change: Changed driver to initialize PFN in the early stage of
the initialization so that it can access the device registers.
Version 5.0.10 September 15, 2009
--------------------------------
Fixes:
======
1. Problem: 10G Link LED is not ON when CX-4 links at 10G-KX4 when
it's connected to CL73-capable switch.
Cause : There is a bug in BCM57710/11 where it doesn't drive
10G SPD LED if the internal PHY links at 10G-KX4.
Change: Changed driver to turn ON LED with software when device
PHY links at 10G-KX4.
Version 5.0.9 September 11, 2009
--------------------------------
Enhancements:
=============
1. Added CL73 support for CX4 PHY.
Version 5.0.8 July 1, 2009
---------------------------
Fixes:
======
1. Problem: BCM8727-based NICs will link up at 1G with Cisco 10G CX1
cable.
Cause : PHY FW doesn't detect Cisco 10G CX1 cable correctly. It
configures device in 1G mode.
Change: Changed NX2_10G Layer driver to disable AUTO detection of
PHY FW and program EDC parameters based on the SFF data from the
SFP+ module.
Version 5.0.7 June 30, 2009
---------------------------
Fixes:
======
1. Problem: Driver failed to create dump when MPIO failover occurs in
a corner case of MPIO configuration: (CQ#42396)
* Boot with secondary NIC with primary NIC disconnected.
* Fail over to primary NIC after OS is booted.
* Disconnect secondary NIC and crash with primary NIC.
* OIS driver passes swapped device's memory mapping.
Cause: In the above rare scenario, L2 driver of crashdump driver
doesn't initialize channel number correctly. This issue should only
occur with NX2_1G and NX2_10G dual-port devices.
Change : Fixed L2 driver to initialize channel number in the
above rare condition.
2. Problem: Crash Dump driver took a long time to detect link
intermittently with BCM8727-based NIC. (CQ#42157)
Cause : With PHY firmware v4.03 or newer, auto-detection feature was
disabled by default. This causes EDC mode not configured correctly.
Change: Changed the L2 driver to enable auto-detection so that EDC
is configured correctly by PHY F/W.
Version 5.0.6 June 24, 2009
---------------------------
Fixes:
======
1. Problem: Driver failed to create dump if iSCSI target is EqualLogic
IPv6 with target redirection.
Change : Added support for ICMPv6 echo/reply support.
Version 5.0.5 June 23, 2009
---------------------------
Fixes:
======
1. Problem: Driver failed to create dump in the following IPv4 MPIO
configurations:
* System boots with only cable attached to the primary NIC.
* System then fails over to the secondary NIC in the OS environment.
* Cable is then removed from the primary NIC.
* System crashes with only cable attached to the Secondary NIC.
(CQ#42227)
Change : Changed DHCPv4 code so that it's compiled with correct
flags.
Version 5.0.4 June 22, 2009
---------------------------
Fixes:
======
1. Problem: Driver failed to create dump when MPIO failover occurs in
an MPIO configuration. (CQ#42138)
Change : Fixed the shutdown code to pass correct parameters to
stack shutting down routine.
Version 5.0.3 June 12, 2009
---------------------------
Fixes:
======
1. Problem: Driver failed to create dump if the iSCSI target is on the
different subnet.
Change : Fixed the IPv6 code to use default gateway as next hop
address if the iSCSI target is on the different subnet.
Version 5.0.2 June 05, 2009
----------------------------
Enhancements:
=============
1. Added IPv6 support. (CQ#41524)
Version 5.0.1 April 20, 2009
----------------------------
Enhancements:
=============
1. Added support for Broadcom SFP+ PHY (BCM8727). This PHY
supports 1Gbps and 10Gbps mode.
Version 5.0.0 April 9, 2009
---------------------------
Enhancements:
=============
1. Added support for Broadcom 10Gb-T PHY (BCM8481). This PHY
supports all speeds (10Mbps,100Mbps,1Gbps, and 10Gbps).
Version 4.8.5 March 2, 2009
---------------------------
Fixes:
======
1. Problem : Crashdump driver doesn't create dump file in an MPIO
configuration where there are more than 3 offload devices in the system.
(CQ#39712)
Cause: In the above scenario, OIS driver would pass valid iBFT to the
crash dump library and virtual addresses of devices might get swapped.
Change: Changed the iSCSI crash dump driver to check this condition to
make sure that virtual addresses of devices match with NIC0 and NIC1
in the iBFT table.
Version 4.8.4 February 13, 2009
-------------------------------
Fixes:
======
1. Problem : Crashdump driver doesn't work with 10G-based devices with NCSI
is enabled. (CQ#39484)
Cause: For 10G-based devices, vendor ID/device ID are mapped to BASE +
0x2000. This address is mapped to BASE + 0x0 for 1G-based devices. Unified
crash dump driver fetches ID's from from BASE + 0x2000 if value of register
@ BASE is zero. When NCSI is enabled, value of register @ BASE is not zero.
Change: Changed device type detection so that it now checks register value
of BASE for Broadcom Vendor ID. If it's not, then fetch it from BASE +
0x2000.
Version 4.8.3 February 11, 2009
-------------------------------
Fixes:
======
1. Problem : Crashdump driver doesn't create dump in some corner cases with
10G-based devices. (CQ#39518)
Cause: Context block was not fully initialized before submitting to the
device.
Change: Driver initialization routine was changed to initialize context
block completely.
Version 4.8.2 January 5, 2009
------------------------------
Enhancements:
=============
1. Added support for BCM5761S devices.
2. Updated Copyright banner to reflect year of 2009.
Version 4.8.1 December 1, 2008
------------------------------
Enhancements:
=============
1. Added support for BCM5716S devices.
Version 4.8.0 November 14, 2008
------------------------------
Enhancements:
=============
1. Added support for BCM57711 with SFP+ support.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.