		      QLogic Driver Release Notes

		       QLogic Corporation
		       All rights reserved


Table of Contents

1. Change History
2. Known Issues
3. Notices
4. Contacting Support


1. Change History

This section contains:

 * 1.1 Hardware Support
 * 1.2 Software Component
 * 1.3 Bug Fixes


1.1 Hardware Support

Initial Drop 2.1.1.0:

 * Support for 2400/2500/2600/2700 Series Fibre Channel adapters
 * Support for 8100/8200/8300 Series Converged Network Adapters
 * Mt. Rainier support.

Between versions 2.1.1.0 and 2.1.13.0:

 * None

Between versions 2.1.13.0 and 2.1.14.0:

 * Support for device id 0x2261. This is Dual-port 2700 Series
Fibre Channel ASIC.

Between versions 2.1.14.0 and 2.1.41.0:

 * None

1.2 Software Components

Between versions 2.1.1.0 and 2.1.3.0:

 * None

Between versions 2.1.3.0 and 2.1.4.0:

 * Update ISP24XX and ISP25XX fw to version 7.04.00

Between versions 2.1.4.0 and 2.1.23.0:

 * None.

Between versions 2.1.23.0 and 2.1.24.0:

 * Update ISP24XX and ISP25XX fw to version 8.01.02

Between versions 2.1.24.0 and 2.1.43.0:

 * None.

Between versions 2.1.43.0 and 2.1.44.0:

 * Update ISP25XX fw version to 8.02.00.

Between versions 2.1.44.0 and 2.1.50.0:

 * None.

1.3 Bug Fixes

Between versions 2.1.1.0 and 2.1.2.0:

 * Improvement: Add support to unload driver with QLFXXX.

 * Problem Description: Vmkmgmt-keyval instance does not display all
NPIV port's information.
 * Solution: Create multiple key value management instances per vmhba.

 * Problem Description: When new opcode added to existing template,
we often see data size mismatch between collected data and total
minidump data size.
 * Solution: Skip the entry and adjust the total buffer size by
subtracting the size of skipped opcode from total minidump size.

 * Improvement: Remove unnecessary delays from fw dump code path and add
features to track the failure at various different stages during capturing
the firmware dump.

 * Improvement: Adding support for FA-WWPN functionality.

 * Improvement: Updated Release Notes recommended by Marketing Team.

 * Problem Description: Setting extended error logging causes the system
to PSOD.
 * Solution: PSOD was caused because of dereferencing a invalid pointer.
Added check before dereferencing pointer.

 * Improvement: Add D-Port functionality.

 * Problem Description: PSOD seen in case of 8G ISP reset recovery path.
 * Solution: In case of FCET enable mbx failure, we try to free the fcet
dma buffer using unassigned dma address. We need to use the global
ha->fcet_dma address instead.

 * Problem Description: PSOD seen while running CT_Ping from application.
 * Solution: Allocation DMA memory for msiocb_passthru ioctl command with
maximum size between request_length and response_length.

 * Problem Description: Driver frees the cmd and returns error in case of
timeout and when we receive response after 66 sec we hit an invalid condition.
 * Solution: Increase driver timeout to (66 * 5) sec.

 * Improvement: Adding Application level support for D-port feature.

 * Improvement: Improvement in FDMI attributes

 * Improvement: Allow nvram bit to enable/disable FA-WWPN

 * Improvement: In case of FAWWPN, revert back to the factory wwpn
when the driver marks the LOOP as DEAD.

Between versions 2.1.2.0 and 2.1.3.0:

 * Improvement: Added support for Fabric QoS feature.

Between versions 2.1.3.0 and 2.1.4.0:

 * Problem Description: PSOD after installing on ESX5.5 with QLA82XX and
QLA83XX adapter.
 * Solution: Provide module heap ID when creating the spinlock
specific to QLA82XX and QLA83XX adapter.

 * Problem Description: V-Port creation failed.
 * Solution: Driver should drop all references from the vport during
last VPort deletion.

Between versions 2.1.4.0 and 2.1.5.0:

 * Problem Description: Hitting PSOD when using Vport with Fabric QoS.
 * Solution: Correctly check whether or not Fabric QoS is enabled or not.

Between versions 2.1.5.0 and 2.1.6.0:

 * Problem Description: Under certain circumstances, VPort creation failed.
 * Solution: Correctly drop the reference from a vport during the service
of vmk-Mgmt API request.

 * Problem Description: PSOD while fw-dump capture from Application.
 * Solution: Free fw dump DMA memory to correct heap pool.

 * Problem Description: Hitting PSOD when using Vport with Fabric QoS.
 * Solution: Correctly check whether or not Fabric QoS is enabled or not.

Between versions 2.1.6.0 and 2.1.7.0:

 * Problem Description: Seen invalid packet entry while updating QoS
Value for running vport.
 * Solution: Do not reinitialise request queue in pointer for existing vport.

 * Improvement: Change QoS feature that vCenter Plug-in will only display the entity
from the NVRAM.

 * Problem Description: With ISP27XX adapter in system bootup taking longer time.
 * Solution: Removed the 500 msec delay between reading of each fwdump template
entry.

 * Improvement: Improvement regarding firmware dump collection in ISP27XX adapter.

Between versions 2.1.7.0 and 2.1.8.0:

 * Problem Description: LUN Related data is not present in VI Client using
Qlogic vCenter Plug-in.
 * Solution: If LUN 0 is not present, driver needs to create a dummy LUN.

 * Problem Description: Internal loopback operations fail when loop is down.
 * Solution: No need to check the loop status when performing internal
loopback operations.

 * Problem Description: PSOD when trying to discover Adapters using Qlogic CIM
Adapter Provider.
 * Solution: In case the scsi command is generated by the driver,
driver should not use the second level LunID API.

Between versions 2.1.8.0 and 2.1.9.0:

 * Problem Description: Driver did not update VP count during ISP Abort.
 * Solution: Update VP count every time ISP abort happens.

 * Improvement: While enabling Fabric QoS, removing the check for QoS
support target.

Between versions 2.1.9.0 and 2.1.10.0:

 * Problem Description: Not able to save certain HBA Parameters
using the Qlogic vCenter Plug-in.
 * Solution: Correct operating mode in case of a Point to Point mode.

 * Improvement: For ISP27xx use the request/response queue index
shadow registers to avoid directly accessing them on the PCI bus.

 * Problem Description: Fabric QoS feature is disabled by default.
 * Solution: Enable the Fabric QoS feature by passing correct attributes
to the firmware.

Between versions 2.1.10.0 and 2.1.11.0:

 * Problem Description: For QLA27XX firmware dump collected did not contain
complete valid information.
 * Solution: Correct processing of the FW dump template.

 * Improvement: For QLA27XX disabling the interrupt handshaking by default.

 * Problem Description: 32G port speed missing from FC attributes.
 * Solution: Adding 32G FC port speed in the FC attributes.

 * Problem Description: For QLA27XX Beacon feature is not working.
 * Solution: Correct the beacon feature for QLA27XX adapter.

 * Improvement: For QLA27XX, added FCP Priority Data support.

 * Improvement: For QLA27XX, correcting procedure for chip reset.

 * Improvement: For QLA27XX, call get FW version mbx command in
case of ISP Abort.

 * Improvement: For QLA27XX, various interrupt related enhancements.

 * Improvement: For QLA27XX, display additional information in vmkMgmgt
key value pair.

 * Problem Description: For QLA27XX, various features for vmkMgmt interface
was not working.
 * Solution: Enabling all ioctl interface features for QLA27XX adapters.

 * Problem Description: For QLA27XX, BB credit setting in the NVRAM was not
being used.
 * Solution: Honor the BB credit setting in the NVRAM.

 * Improvement: For QLA27XX, remove excessive logging during FW Dump Template
routine.

Between versions 2.1.11.0 and 2.1.12.0:

 * Problem Description: For QLA27XX, beacon and QoS features are not working.
 * Solution: Add QLA27XX check in update_beacon path and Provide
QoS vender as QLogic for noentry.

 * Problem Description: During Chip reset CPU lockup causes PSOD.
 * Solution: Remove busy wait while holding a spinlock.

Between versions 2.1.12.0 and 2.1.13.0:

 * Improvement : Adding FSC related Port Attributes for
RPA and RPRT services.

 * Improvement: For QLA27XX, allocate one FW dump buffer. This would
considerably decrease the demand for heap.

 * Improvement: OEM Specific T10 DIF support.

 * Problem Description: PSOD while HBA initialization fails.
 * Solution: Properly check for invalid pointers during clean up.

Between versions 2.1.13.0 and 2.1.14.0:

 * Improvement: Fix various issues with attributes related to RPA and RPRT.

 * Problem Description: System PSOD After QMI2672 Flash in ESXi6.0.
 * Solution: IO's generated via IOCTL interface should use the
normal IO path and not the T10 DIF IO path.

 * Improvement: For QLA27XX, adding support for T10 DIF.

Between versions 2.1.14.0 and 2.1.15.0:

 * None

Between versions 2.1.15.0 and 2.1.16.0:

 * Improvement: Implemented the OEM Specific RDP support.

 * Problem Description: OEM Specific RHBA is getting rejected.
 * Solution: Fill default values to attributes in RHBA.

Between versions 2.1.16.0 and 2.1.17.0:

 * Problem Description: PSOD while starting VM with NPIV enabled.
 * Solution: Disable the Vendor unique T10 Dif support.

Between versions 2.1.17.0 and 2.1.18.0:

 * Problem Description: PSOD while testing loopback test.
 * Solution: Correctly decrement the reference counter.

 * Improvement: Display status of FEC feature in proc entry information.

 * Improvement: Renaming RPA/RPRT parameters.

 * Improvement: Adding SFP/SFP+ bit support in the RDP Response.

 * Problem Description: Incorrect Fabric portname and Fabric nodename
in the RDP response.
* Solution: Get the Fabric portname and nodename, from the switch before
sending the RDP response.

 * Problem Description: Diagnostic Loopback failed with command error.
 * Solution: Do ISP reset when driver get command error with MBX[1] =17h
for Diagnostic loopback for all adapter.

 * Problem Description: Checking failure of memory allocation in
RDP Response handling.
 * Solution: Gracefully handle the failure to allocate memory while
preparing the RDP response frame.

 * Improvement: Assign default values to RHBA attributes.

 * Problem Description: PSOD occurred during normal testing in inquiry
snoop function when copying data from inquiry buffer.
 * Solution: Check scatter-gather element length before copying to local
buffer as it could be greater than size of buffer.

 * Problem Description: PSOD while booting with pre-boot host configuration.
 * Solution: Correcting the initialization of global vha list. Also, disabling
pre-boot host configuration.

Between versions 2.1.18.0 and 2.1.19.0:

 * Improvement: Allocate correct size of global dump buffer for Baker adapters.

 * Problem Description: Pre-boot NPIV is not working.
 * Solution: Implement end to end pre-boot NPIV.

Between versions 2.1.19.0 and 2.1.20.0:

 * Improvement: OEM Specific SAN feature is only for ISP25XX and ISP2031 adapters.

 * Improvement: Disable the Vendor unique T10 Dif support.

Between versions 2.1.20.0 and 2.1.21.0:

 * Problem Description: In a NPIV environment, sometime the VM ends up
in a hung state.
 * Solution: Properly exit the vmk World, when a related vmk status is
returned.

 * Improvement: Enable the Vendor unique T10 Dif support.

 * Problem Description: Pre-boot NPIV information not showing correctly.
 * Solution : Store the correct vmk device per pre-boot NPIV adapter.

Between versions 2.1.21.0 and 2.1.22.0:

 * Improvement: For QLA27XX adapter, add support for MPI version and PEP version.

 * Problem Description: For QLA27XX adapters, only showing 32Gb speed.
 * Solution: Fix the description to include the 16Gb speed as well.

 * Improvement: For QLA27XX adapters, add support for online flash update.

Between versions 2.1.22.0 and 2.1.23.0:

 * Improvement: For OEM Specific T10 DIF, added support for Inquiry Data Changed UA.

Between versions 2.1.23.0 and 2.1.24.0:

 * Problem Description: For T10 DIF, Inquiry Data Change UA not working as
expected.
 * Description: Provide sufficient buffer for Inquiry response. Also, clear
feature flag before rediscovery.

Between versions 2.1.24.0 and 2.1.25.0:

 * Problem Description: PSOD while driver unload/load test.
 * Description: Disable the hardware handshake when driver is unloaded.

 * Improvement: Remove unnecessary vmk device checks in QuiesceDevice
function.

 * Improvement: Setting OEM Specific SAN Security support value to 1.

 * Improvement: Correcting the description of CPU Affinity module parameter.

 * Improvement: Vendor unique T10 Dif, check response length before protection
bit in Inquiry Command.

 * Problem Description: Continuous logging of Vendor Specific T10 DIF support
messages.
 * Description: Putting the log messages under debug level.

Between versions 2.1.25.0 and 2.1.26.0:

 * Problem Description: Vendor unique T10 Dif, dynamically turning off T10
Dif not working as expected.
 * Description: Do not use stale copy of the SCSI CDB from firmware.

Between versions 2.1.26.0 and 2.1.27.0:

 * Problem Description: ATS miscompare check conditions were not being reported
to upper layer.
 * Solution: Driver was interpreting the error condition as a "dropped frame"
scenario and the issue was never rectified.  Fix was to check for this miscompare
condition before determining if it was indeed a "dropped frame".

Between versions 2.1.27.0 and 2.1.28.0

 * Problem Description: With certain storage array, IO's are failing with T10
DIF errors.
 * Solution: For T10 DIF, correctly check the vendor string while verifying if
vendor specific T10 DIF is applicable.

Between versions 2.1.28.0 and 2.1.29.0

 * Problem Description: Omit SCSI opcode check in ATS miscompare check condition.
 * Solution: Omit SCSI opcode check and rely on sense key and ASC to determine if
this scenario is encountered.

 * Improvement: IOCB-based Fabric Priority support added.

 * Problem Description: PSOD is encountered during chip reset.
 * Solution: During ISP abort procedure, cleanup all outstanding commands
on all the active V-Ports.

Between versions 2.1.29.0 and 2.1.30.0:

 * Improvement: Remove switch capability check in IOCB-base Fabric Priority feature.

Between versions 2.1.30.0 and 2.1.31.0:

 * Improvement: Add feature for BBCredit Stats and Private stats.

 * Problem Description: System PSOD's when driver is unloaded.
 * Solution: Free firmware dump buffer only once.

Between versions 2.1.31.0 and 2.1.33.0:

 * Problem Description: System panics while running scsi passthru traffic.
 * Solution: Create global dummy lun for use while executing scsi passthru
commands.

Between versions 2.1.33.0 and 2.1.34.0:

 * Problem Description: Missed 8014 async events were observed periodically
during reboot test which resulted in the link state never being "ready" and
targets would not get discovered.
 * Solution: Remove clearing of RISC interrupt during initialization.

Between versions 2.1.34.0 and 2.1.35.0:

 * Improvement: Forcing Diagnostic Echo test to be done using ECHO ELS.

Between versions 2.1.35.0 and 2.1.36.0:

 * Improvement: Changing FDMI Port State values in accordance with latest
SNIA standards.

 * Problem Description: In some systems, driver fails to allocated contiguous
dump memory.
 * Solution: For firmware dump memory, allocated memory should be
physically contiguous.

 * Problem Description: Certain port states are not being displayed properly
in user-space application.
 * Solution: Application needs mailbox 1 register data in user space to display
correct port state.

Between versions 2.1.36.0 and 2.1.37.0:

 * Problem Description: PSOD CPU tried to re-acquire lock hardware_lock.
 * Solution: From the start scsi context, driver should be calling cmd done
without any lock.

 * Problem Description: BBCR initial value is not populated correctly.
 * Solution: Read from the correct location in the report ID acquisition IOCB.

Between versions 2.1.37.0 and 2.1.38.0:

 * Improvement: Reverting the "Forcing Diagnostic Echo test to be done using ECHO ELS".

Between versions 2.1.38.0 and 2.1.39.0:

 * Improvement: Reverting the "ESXOPNATIVEFC-5: PSOD CPU tried to re-acquire lock
 hardware_lock".

Between versions 2.1.39.0 and 2.1.40.0:

 * Problem Description: ER138356: ESX6.0 IOVP DDV testing fails with PSOD.
 * Solution: Added memory allocation checks. Use correct vmk API's while
using vmk_Name.

Between versions 2.1.40.0 and 2.1.41.0:

 * Problem Description: For Baker adapter, when link speed is 32G, port speed is
being displayed as unknown.
 * Solution: Correctly display the port speed for the baker adapter.

 * Problem Description: System Panics while performing HBA failover test.
 * Solution: Check the return status of memory allocation. Also made the
change to the fw dump heap, changing it to type "simple".

Between versions 2.1.41.0 and 2.1.42.0:

 * Problem Description: System panic with 8G FC HBA; driver used un-initialized parameter during vmk_PCIMapIOResource function.
It leads qlnativefc driver FW failure during system bootup. 
 * Solution: Use initialized parameters while calling vmk_PCIMapIOResource.

 * Problem Description: PSOD is observed while running IO.
 * Solution: Defer calling cmd done in a workqueue.

 * Problem Description: PSOD due to IOMMU fault due to driver not checking the failure case when
memory allocation failed..
 * Solution: Check the return status for all memory allocation point.

 * Problem Description: OEM specific Smart SAN fixes.
 * Solution: Found during testing.

 * Problem Description: PSOD encountered when enabling T10 DIF operation on Baker adapters. 
 * Solution: Special slabs used for Command CRC_2 IOCBs were not getting created at start
of day due to incorrect isp_ops function pointer.

 * Problem Description: A PSOD is encountered when an 8070h AEN indicating temperature of adapter
has passed threshold value.
 * Solution: Release hw spinlock before calling reset_adapter as the function assumes lock will not be held.

 * Improvement: Added three new SmartSAN RDP Descriptors

Between versions 2.1.42.0 and 2.1.43.0:

* Problem Description: T10 DIF is not working for Qlipper and Baker adapters.
* Solution: Enable T10 DIF support for Qlipper and Baker adapters.

Between versions 2.1.43.0 and 2.1.44.0:

* Problem Description: Code improvement.
* Solution: Change source files to support BSD license.

* Problem Description: Smart SAN 2.0 needed.
* Solution: Various SmartSAN 2 improvements

* Problem Description: B2B credit not correctly passed in the RDP Response.
* Solution: Get the B2B credit from firmware before placing
it in the RDP Response.

* Problem Description: When VP decoupling enabled, there could be a window where,
FLOGI from initiators can be dropped before VP0 is enabled, causing link level recovery.
* Solution: Retry FLOGI to avoid link level recovery. Set regardless of topology for now.

* Problem Description: Code improvement.
* Solution: Various fixes found at VMware during vSphere 2016 inbox testing.

Between versions 2.1.44.0 and 2.1.45.0:

* Improvement: Add support/interface for DPORT.

* Improvement: Add support/interface for statistics reset.

* Problem Description: DPORT enable is hard-coded.
* Solution: Remove the hard-coding and let the nvram do the enable.

Between versions 2.1.45.0 and 2.1.46.0:

* Improvement: Return correct sense data error to vmkernel when sense data
buffer not available

* Problem Description: BBCR enable bit and value adjustment through VI Plugin was not
taking effect after reboot.
* Solution: Get Adapter ID mailbox command function was failing to read the Mailbox 15
output and so BBCR values were always returned as zero from this function. Fix was to set
the Mailbox 15 value in the bit mask before execution.

Between versions 2.1.46.0 and 2.1.47.0

Problem Description: RDP Optical Product Data Descriptor field 'revision' was incorrect (zeros),
it was being read from the wrong sfp offset (36, 37) and in wrong endianess.
Solution: Read the OPDD revision from correct sfp offset (38, 39) in correct endianess.

Problem: RDP Optical Product Data Descriptor field 'revision' has been redefined in FC-LS.
Solution: Redefine the Revision field in the OPDD structure, and rework its access method.

Between versions 2.1.47.0 and 2.1.48.0

Problem Description: VVOL support was not working properly when T10 DIF was enabled.
Solution: Correctly populate Second Level LUN ID info in T10 DIF I/O path.

Problem Description:
Driver correctly writes the ELS opcode 0x18 to the opcode field in
the ELS iocb, but due to an incorrect BUG check in earlier FW (8.02.51),
the FW sets the OXID of the RDP response to 0xFFFF.
Solution:
Since the customer cannot/willnot change their FW, the driver will
write zero to the opcode field in the ELS iocb, this causes the FW to
bypass the incorrect BUG check and apply the correct OXID.

Between versions 2.1.48.0 and 2.1.49.0

Problem Description:
Baker/Qlipper based adapters showed a generic description that did not
differentiate QLE names and link speeds in vSphere GUI and lspci output.
Solution:
Add entries in qlnativefc_devices.py to distinguish Baker/Qlipper based adapters.

Minor improvement:
Print message where sense data buffer is zero in verbose logging mode only.

Problem Description:
Require LR Distance support for 27xx.
Solution:
Copy LR distance from nvram to Execute Firmware MBC.

Problem Description:
FDMI and RDP data show incorrect supported speeds for 16G 27xx boards.
Solution:
Check the fw ability and set the FDMI/RDP supported speeds correctly.

Problem Description:
Driver cannot receive RDP request for 27xx cards.
Solution:
Include 27xx in RDP purex driver intercept.

Problem Description:
BOOT BIOS STATE FDMI parameter can't be obtained and is optional anyway.
Solution:
Remove this parameter from FDMI RHBA registration.

Between versions 2.1.49.0 and 2.1.50.0

Problem Description:
RHBA was getting rejected by the switch due to incorrect attribute count.
Solution:
Dynamically calculate attribute count rather than hard code value in header file.

Problem Description:
qla2xenablesmartsan module parameter wasn't showing up in vmkmgmt
module query.
Solution:
Added to GetDriverInfo display.


2. Known Issues

None


3. Notices

Information furnished in this document is believed to be accurate and
reliable. However, QLogic Corporation assumes no responsibility for
its use, nor for any infringements of patents or other rights of
third parties which may result from its use. QLogic Corporation
reserves the right to change product specifications at any time
without notice. Applications described in this document for any of
these products are only for illustrative purposes. QLogic Corporation
makes no representation nor warranty that such applications are
suitable for the specified use without further testing or
modification. QLogic Corporation assumes no responsibility for any
errors that may appear in this document.


4. Contacting Support

   For further assistance, contact QLogic Technical Support at:
   http://support.qlogic.com


Trademarks

Accelera, Accelerating Cluster Performance, InfiniCon Systems,
InfiniNIC, InfiniPath, InfiniView, QLA, QLogic, the QLogic logo,
ReadyPath, SANdoctor, SANsurfer, and SilverStorm are registered
trademarks of QLogic Corporation. All other brand and product names
are trademarks or registered trademarks of their respective owners.



(c) Copyright 2016. 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.
