

Release Notes for QLogic 32xx/82xx/83xx NIC Driver for ESXi 5.0/5.1 



                       QLogic Corporation.

                       All rights reserved. 



Table of Contents



1. Change History

2. Known Issues

3. Notices

4. Contacting Support



1. Change History

Version 5.3.190:

	a) ER0000000101727:

	Problem description:

	VMware Artifact NTXN57: Potential irrelevant netif_start_tx_queue usage found by DDV.

	Solution:

	Before calling netif_start_tx_queue , added check to verify that we have stopped the tx queue.



Version 5.3.188:

	a) ER0000000110923 

	Problem description:

	Flash the firmware image under ESXi 5.1 U1 IBM

	customized OS take too long to complete(8+ minutes).

	Solution:

	Added ioctl support for P3P flash operations.



Version 5.3.187:

	a) ER0000000114871

	Problem description:

	SRIOV : both wire and eswitch ping fails on windows VM

    Solution:

	PF driver converts the (MAC,star) filter request to (MAC, no-tag) filter.



	b) ER0000000115938

    Problem description:

	SRIOV : VF request for interrupt coalescing is not supported by PF driver.

    Solution:

	Added support for interrupt coalescing command in PF driver.



Version 5.3.186:

	a) ER0000000115084

	Problem description:

    SRIOV:Legacy:min_max_tx_bw file isn't acknowledging default value "0:100" as input

    Solution:

	Changed the default min-max tx bw to -1:-1, when vf isn't initialized.



	b) ER0000000115085

    Problem description:

    SRIOV:Legacy:changing bandwidth setting on PF1 VFs throws error

    Solution:

	Increased the vf vport bits to 14 from current 8. FW spec change required.



	c) ER0000000115038

    Problem description:

    SRIOV:Legacy:System crashed while trying to view min_max_bw file inside proc entry

    Solution:

	Don't return negative return value from proc read handler.



	d) ER0000000106911

    Problem description:

    Add support for setting driver version with firmware for OCBB.

    Solution:

	Added support for the requisite mailbox command in driver.



Version 5.3.185:

	a) ER0000000114876

	Problem description:

	Add flash update changes for pre-enablement phase.

	Solution:

	Added the changes for flash update pre-enablement phase.



Version 5.3.184:

    a) ER0000000114121

    Problem description:

    NIC Driver issues get WOL Capability command to firmware for ports that do not support WOL. 

    This causes some messages to be displayed in vmkernel logs, which may be misleading.

    Solution:

    Added additional check to verify WOL support in Flash NVRAM.






Version 5.3.182:

	a) ER0000000114299: 

	Problem description:

	Not able to enumerate NIC functions in VI plugin when more than 1 NIC functions

	are enabled on a port.

	Solution:

	Modified the driver to return error for SRIOV commands when SRIOV is disabled, so

	that NIC functions in other configurations can be enumerated.



Version 5.3.181:

	a)ER0000000114224:

     Problem Description:

     NIC functions goes down & not coming Up while doing UP/Down using esxcli command

     Solution:-

     Update adapter level flags in the health watchdog, even if link is down using esxcli.



Version 5.3.180:

	a) ER0000000114159:

	Problem description:

	SRIOV: ifconfig up for some VFs fail.

	Solution:

	Modified backchannel command processing task to keep history of previously 

	processed backchannel command list.



	b) ER0000000114049:

	Problem description:

	SRIOV: After powering on windows VM, creation of guest vlan on Linux VM fails.

	Solution:

	PF driver should not allow 'MAC + Any VLAN' mode on VF. 



	c) ER0000000108946, ER0000000112607, ER0000000113677:

	Problem description:

	SRIOV: Remove less important and ambiguous log messages.

	Solution:

	Less important and ambiguous log messages are removed.



Version 5.3.179:

	a) ER0000000114109:

	Problem description:

	Add support for SRIOV management interface.

	Solution:

	Added required changes to support SRIOV management.



Version 5.3.178:

	a) ER0000000106996:

	Problem description:

	Need proc interface for displaying MAC addresses and adjusting the filter

	limits for 83XX adapters.

	Solution:

	Added proc interface for displaying MAC address and adjusted the filter

	limits for 83XX adapters.

	

	b) ER0000000106996:

	Problem description:

	Enable filter flag 'NETIF_F_DEFQ_L2_FLTR' for more adapter configurations.

	Solution:

	Added changes to enable NETIF_F_DEFQ_L2_FLTR for some more adapter

	configurations.



	c) ER0000000110384:

	Problem description:

	The eswitch broadcast packets to some functions fail in certain adapter

	configurations.

	Solution:

	Added changes to set multicast flag for broadcast and multicast packets

	in command descriptors.

	

   	d) ER0000000103430:

	Problem description:

	Internal loopback test fails with Loopback cable connected in certain adapter

	configurations that enable the embedded switch on the adapter.

	Solution:

	In some adapter configurations, the driver needs to handle the case where

	loopback cable may be connected on that port and packets may be getting looped

	back.



Version 5.3.177:

	a) ER0000000110245:

	Problem description:

	SRIOV: Internal loopback test is failing for NIC on Port1.

	Solution:

    Issue fixed by using VP id in MAC Delete and restore.



	b) ER0000000110300:ER0000000110257:

	it gives Link test failed.

	Solution:

    Run irq test, without bringing down the interface.



	c) ER0000000111228:

	Problem description:

	WOL support is displaying as "NO" for Quinlan-526FLR VI client in ESXi5.1U1

	Solution:

	Added fix for WOL support in ESXi qlcnic driver.



Version 5.3.176:

	a) ER0000000107285:

	Problem description:

	Add support for RSS for vxlan traffic for 83XX and 82XX based adapters.

	Solution:

	Added support for RSS for vxlan traffic for 83XX and 82XX adapters.



	b) ER0000000110797:

	Problem description:

	Fix to avoid PSOD with VXLAN Traffic with RSS queue. 

    Solution:

	Added the ip_align bytes to Rx buffer at the time of allocation.



	c) ER0000000111408 :

	Problem description:

	Rx queues are not getting created for VXLAN enabled Fn0 and Fn1

    Solution:

	Reserve sufficient no of Rx queues for Fn0 and Fn1 in case of VXLAN.



Version 5.3.175:

	a) ER0000000102109 : 

	Problem description: 

	NIC driver does not recover after enforcing conflict between critical points:

	"ATTACH_ADD_TX_NAPI" and "NETQ_ALLOC_QUEUE_ALLOC_TX_CTX" CPs.

	Solution:

	After enforcing a conflict new Tx queue was getting allocated in place of default

	Tx queue. Now, index for default Tx queue is preserved.



	b) ER0000000105984 :

	Problem description: 

	Adapter pointer corruption during execution of "qlcnic_p3_sre_macaddr_vlan_change"

	Solution:

	There was a pointer of local variable, which was used out of the scope of that

	variable.



	c) ER0000000111240 :

	Problem description: 

	Lost connection after disabling and enabling the network interface.

	Solution:

	Added support for esxcli network down and up operations in the driver.



	d) ER0000000110046 :

	Problem description: 

	'Failed to add/delete MAC' messages are seen while doing ifconfig up on guests.

	Solution:

	Suppressed the message for duplicate add/del requests from Vmkernel.

	

	d) ER0000000103715 :

	Problem description: 

	Loss of VM Network Connectivity after vMotion in certain adapter configurations.

	Solution:

	Report Network Partitioning only for ports configured with it.



Version 5.3.174:

	a) ER0000000111603 : 

	Problem description: 

	PSOD seen while displaying statistics on certain adapter configurations.

	Solution:

	Driver was incorrectly processing the number of receive contexts which

	was causing the crash. Driver has been fixed to address this issue.

		

	b) ER0000000110579 : 

	Problem Description: 

	Display of stats under proc doesn't fit in one screen and wraps around to

	next row.

	Solution:

	Re-structured the proc interface for the display of stats to make the

	output more readable.



	c) ER0000000109752 : 

	Add debug information for internal crash analysis tool (qlcdde).



Version 5.3.173:

	a) ER0000000113731 :

	Problem Description:

	Alert Event message "Attributes are invalid" seen in Plain traffic.

	Solution:

	Alert Event message "Attributes are invalid" is removed from the driver.



Version 5.3.172:

	a) ER0000000112663 :

	Problem description:

	Driver unload hangs with more than one adapter SRIOV enabled in the system.

	Solution:	

	The while loop in backchannel processing thread is removed. Now, the

	function related to this thread is scheduled again using queue_work.

	Though, queue_work gets scheduled immediately, we have a waitqueue where our

	thread can wait for specified amount of time.



Version 5.3.171:

	a) ER0000000112512 : Fix to clear LRO state while deleting receive context.

	Problem description: 

	The proc nodes show LRO enabled for all receive contexts even when LRO 

	is not actually enabled.

	Solution:

	Driver has been modified to clear LRO and RSS state while deleting receive 

	Solution:

	Driver has been modified to clear LRO and RSS state while deleting receive 

	context.



Version 5.3.166:



	b) ER0000000109980: 

	Problem Description:

	During sustained negative testing in multi-protocol configuration by 

	repeatedly forcing adapter reset-recovery to happen, it was found that adapter 

	firmware was not successfully recovered in one case.

	Solution:

	There was a very small timing window where unavailability of hardware 

	semaphore was not being handled correctly. The driver has been updated to 

	address this case.

	

Version 5.3.163:

	

	b) ER0000000106911 : 

	Problem Description: 

	Add support for setting driver version with firmware.



	c) ER0000000106720 : 

	Problem Description:

	PSOD seen with delayed_work_timer_fn() in the backtrace. Crash happens 

	while trying to schedule driver health watchdog timer function.

	Solution:

	The driver learns and programs ip addresses for hardware LRO. Driver 

	maintains a table of IP addresses. In rare situations, when multiple driver 

	instances are trying to add IP address at the same time, driver may access 

	entries past the array limits causing corruption of the adjacent health 

	watchdog workqueue structure. Driver has been fixed.

	to address this condition.



        d) ER0000000106311 : 

	Problem Description: 

	During extended duration negative testing performed by forcing reset-recovery 

	through Ethernet driver it was observed that storage drivers can occasionally 

	miss the inter-driver acknowledgement which prevents them from moving to 

	operational state.

	Solution:

	The Ethernet driver was clearing the IDC ACK bits of other functions if it is 

	the reset owner. This was causing storage drivers to sometimes miss the 

	acknowledgement. Ethernet driver has been modified to fix issue. 



	e) ER0000000104757 : 

	Problem Description:

	Unable to unload qlcnic driver on QLE83XX adapters on ESXi 5.0 in certain 

	adapter configurations.

	Solution:

	The driver was updating reference count for VFs that were not configured. 

	This was causing unload to fail. Driver has been modified to update the 

	reference count correctly.





Version 5.1.157:

	a) Add support for QLE83XX adapters.



	b) ER0000000101204 :

	   Problem Description:

           Sometimes, during firmware minidump extraction during 

           reset-recovery, CPU lockup happens resulting in NMI.

           Messages similar to the following logged in vmkernel

           log files:

           "cpu2:4496)<6>qlcnic 0000:06:00.0: vmnic6:qlcnic_minidump:

            1703:Collecting firmware minidump, capture_mask is:0xf.

            cpu13:8105)ALERT: Heartbeat: HandleLockup:645: PCPU 2 

            didn't have a heartbeat for 5 seconds; *may* be locked up.

            cpu13:8105)VmkEvent: AlertHelper:389: Received message 

            1@LogSysAlertBH:309: 

            cpu13:8105)Heartbeat: HandleLockup:645: PCPU 2 didn't 

            have a heartbeat for 5

            cpu2:4496)ALERT: NMI: HandleBtOrHaltRequest:607: NMI IPI 

            received. Was eip(base):ebp:cs [0xbf3f2f(0x41802d200000):

            0x41224641aac0:0x4010](Src 0x1, CPU2)"

	   Solution:

           Driver has been modified to yield CPU periodically when

           collecting firmware dump.



	c) ER0000000099372 :

	   Problem Description:

	   Need capability for QLE82XX adapters to query remote and 

           operational DCBX TLVs and provide them to Management tools.

	   Solution:

	   A new ioctl has been implemented for QLogic managment tools

           to retrieve this information.





	d) ER0000000103747 :

	   Problem Description:

	   Add callback and capability to get notified by vmkernel 

           for VM MAc addresses on ESX5.1.

           Solution:

           Implement support for DEFQ_L2_FLTR in driver.



	e) ER0000000103802 :

	   Problem Description:

           Ethtool -a shows flow control always as OFF

	   Solution:

           Change driver to return appropriate values to ethtool.



	

	f) ER0000000104393 :

	   a) Problem description:

           Firmware dump capture mask is at module level.

           Solution:

	   Change capture mask to per pci function.





Version 5.1.122: 

	a) Add support for QEM8362-ORL and QLE8362-ORL adapters 

Version 5.0.750:

        a) ER0000000096266 : 

	   Problem Description: 

           In certain servers PXE driver was not performing

           cleanup during exit. This was causing ESX driver

           initialization to fail.

           Solution:

           Issue FLR to all NIC functions at driver load time.



        b) ER0000000095846 :

           Problem Description:

           Adapter firmware becomes non-operational during

           server shutdown was causing driver to perform reset-

           recovery and that was leading to system hang during

           shutdown operation.

           Solution: 

           Avoid performing reset-recovery when server shutdown

           or driver unload has been initiated.



        c) ER0000000094963 : 

           Problem Description:

           In certain adapters that have fan, a specific error

           code will be reported when firmware detects fan 

           failure. This error code needs to be checked and

           handled by driver.

           Solution:

           Driver checks for this specific error code, prints

           an appropriate error message and goes into failed

           state.



        d) ER0000000092740 : 

           Problem Description: 

           On some servers, after auto-deploy, the adapter that

           was used for auto-deploy was not getting initialized

           Solution: 

           Perform function level reset before attempting driver

           initialization. 



Version 5.0.746:

		a) ER0000000092740 : Fix PSOD during driver unload 

           in certain adapter configurations.



Version 5.0.745:

		a) ER0000000092212 : ESXi5 VM to VM connectivity lost

           after vmotion of VM to another ESX host in certain

           adapter configurations. 



Version 5.0.744:

		a) ER0000000089223 : Performance issue with single 

          VM traffic.

Version 5.0.743:

		a) ER0000000089545 : Memory leak while allocating

           memory for sds rings in error case.

Version 5.0.742:

		a) ER0000000085812 : Fix a PSOD seen during driver

           unload load test.

Version 5.0.741:

		a) ER0000000087664 : Implement modified adapter

           shutdown sequence identified by ER86705



		b) ER0000000087363 : ESXi 5.0 system PSOD after

           updating firmware via VI-plugin.

Version 5.0.740:

		a) ER0000000086645 : Intermittent device

           initialization failure during reset-recovery testing.



Version 5.0.739:

		a) ER0000000086565 : Need to reserve command

           descriptors for sending control commands to firmware.



Version 5.0.738:

		a) ER0000000086496 : Fix a race condition when

           accessing the driver trace buffer.



Version 5.0.737:

		a) ER0000000086190 : Display hw_lro status as part 

          of driver statistics.



Version 5.0.736:

		a) ER0000000085660 : Fix incorrect driver behavior

           with auto_fw_reset disabled.



Version 5.0.735:

		a) ER0000000084130 : Intermittent failure in resuming

           traffic after vmotion in certain adapter

           configurations.

		b) ER0000000085396 : PSOD seen while rebooting

           ESXi5.0 (PCPU0 didn't have heartbeat and NMI IPI

           received)



Version 5.0.734:

		a) Added additional debug information in the adapter

           reset path.



Version 5.0.733:

		a) Added debug information and statistics for mac

           hash table.

		b) Set the ocm window register for the fw tools to

           work correctly.

		c) Fix incorrect handling of error code returned by

           firmware when querying minidump template.

		d) Fix bug in error path while unloading the driver,

           if previous driver load failed.

		e) Fix failure in minidump capture when initiated in

           round robin fashion on different functions.



Version 5.0.732:

		a) Adjust number of entries in mac hash table

           depending upon number of nic functions enabled.

		b) Restructure proc statistics so that they take 

           less space while displaying.



Version 5.0.731:

		a) Firmware minidump will be collected by the

           function which initiates firmware recovery.

           b) Changes for allowing enable/disable of firmware

           minidump feature through /proc interface.

           c) Changes for allowing changing capture level for

           firmware minidump through /proc interface.

           d) Support for on demand firmware minidump is added.

           e) Fix incorrect handling of MTU change

           functionality.



Version 5.0.730:

		a) ER0000000084180 : Netq unstable in maxconfig for

           max netq traffic.



Version 5.0.729:

		a) ER0000000082735 : Failed to get ack in 10 sec

           message is seen when running traffic with peg halt

           test.

           b) ER0000000082729 : Panic happened while running

           traffic + driver load unload test in a loop.



Version 5.0.728:

           a) Added support for collecting firmware minidump.

           Although, this feature is disabled by default

           currently.



Version 5.0.727:

		a) ER0000000082934: Vmotion fails on jumbo mtu.

		b) Added device id and descriptions strings.



Version 5.0.726:

		a) Added support for following additional netqueue

           ops:

		  1) VMKNETDDI_QUEUEOPS_OP_SET_TX_PRIORITY

		  2) VMKNETDDI_QUEUEOPS_OP_ALLOC_QUEUE_WITH_ATTR

		  3) VMKNETDDI_QUEUEOPS_OP_GET_SUPPORTED_FEAT

		  4) VMKNETDDI_QUEUEOPS_OP_GET_SUPPORTED_FILTER_CLASS

		b) Moved the per adapter Rx stats to individual netq.

		c) Disabled support for enable/disable of hw_lro from

           /proc/net/qlcnic interface.

		d) Fixed traffic not being seen on netqueues issue,

           which is seen on certain adapter configurations.

		e) Enabled hw_lro support by default.

		f) ER0000000080010 : NMI seen while doing all

           processor halt with wire and loopback traffic running

           together.



Version 5.0.725:

		Initial version for ESXi 5.0 support.

	   



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 assisance, 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 2014. 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.

