Known Issues and Limitations
============================
-This section describes known issues with the DPDK software, Release 1.8.0.
+This section describes known issues with the DPDK software.
+
+Unit Test for Link Bonding may fail at test_tlb_tx_burst()
+----------------------------------------------------------
++--------------------------------+--------------------------------------------------------------------------------------+
+| Title | Unit Test for Link Bonding may fail at test_tlb_tx_burst() |
+| | |
++================================+======================================================================================+
+| Reference # | IXA00390304 |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Description | Unit tests will fail at test_tlb_tx_burst function with error for uneven distribution|
+| | of packets. |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Implication | Unit test link_bonding_autotest will fail |
+| | |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Resolution/ Workaround | There is no workaround available. |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Affected Environment/ Platform | Fedora 20 |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Driver/Module | Link Bonding |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+
+
Pause Frame Forwarding does not work properly on igb
----------------------------------------------------
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Implication | Any configuration for these items in the VF register will be ignored. The behavior |
-| | is dependant on the current PF setting. |
+| | is dependent on the current PF setting. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| Resolution/ Workaround | For the PF (Physical Function) status on which the VF driver depends, there is an |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-GCC might generate Intel® AVX instructions forprocessors without Intel® AVX support
------------------------------------------------------------------------------------
+GCC might generate Intel® AVX instructions for processors without Intel® AVX support
+------------------------------------------------------------------------------------
+--------------------------------+--------------------------------------------------------------------------------------+
| Title | Gcc might generate Intel® AVX instructions for processors without Intel® AVX support |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-Cannot set link speed on Intel® 40G ethernet controller
+Cannot set link speed on Intel® 40G Ethernet controller
-------------------------------------------------------
+--------------------------------+--------------------------------------------------------------------------------------+
-| Title | Cannot set link speed on Intel® 40G ethernet controller |
+| Title | Cannot set link speed on Intel® 40G Ethernet controller |
| | |
+================================+======================================================================================+
| Reference # | IXA00386379 |
| | It cannot set the link to specific speed. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-| Implication | The link speed cannot be changed forcedly, though it can be configured by |
+| Implication | The link speed cannot be changed forcibly, though it can be configured by |
| | application. |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
-Stopping the port does not down the link on Intel® 40G ethernet controller
+Stopping the port does not down the link on Intel® 40G Ethernet controller
--------------------------------------------------------------------------
+--------------------------------+--------------------------------------------------------------------------------------+
-| Title | Stopping the port does not down the link on Intel® 40G ethernet controller |
+| Title | Stopping the port does not down the link on Intel® 40G Ethernet controller |
| | |
+================================+======================================================================================+
| Reference # | IXA00386380 |
| Driver/Module | Poll Mode Driver (PMD) |
| | |
+--------------------------------+--------------------------------------------------------------------------------------+
+
+Devices bound to igb_uio with VT-d enabled do not work on Linux* kernel 3.15-3.17
+---------------------------------------------------------------------------------
+
++--------------------------------+--------------------------------------------------------------------------------------+
+| Title | Devices bound to igb_uio with VT-d enabled do not work on Linux* kernel 3.15-3.17 |
++================================+======================================================================================+
+| Description | | When VT-d is enabled (iommu=pt intel_iommu=on), devices are 1:1 mapped. |
+| | In the Linux* kernel unbinding devices from drivers removes that mapping which |
+| | result in IOMMU errors. |
+| | | Introduced in Linux `kernel 3.15 commit <https://git.kernel.org/cgit/linux/kernel/ |
+| | git/torvalds/linux.git/commit/drivers/iommu/ |
+| | intel-iommu.c?id=816997d03bca9fabcee65f3481eb0297103eceb7>`_, |
+| | solved in Linux `kernel 3.18 commit <https://git.kernel.org/cgit/linux/kernel/git/ |
+| | torvalds/linux.git/commit/drivers/iommu/ |
+| | intel-iommu.c?id=1196c2fb0407683c2df92d3d09f9144d42830894>`_. |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Implication | | Devices will not be allowed to access memory, resulting in following kernel errors:|
+| | | ``dmar: DRHD: handling fault status reg 2`` |
+| | | ``dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr a0c58000`` |
+| | | ``DMAR:[fault reason 02] Present bit in context entry is clear`` |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Resolution/ Workaround | | Use earlier or later kernel versions, or avoid driver binding on boot by |
+| | blacklisting the driver modules. |
+| | | ie. in the case of ixgbe, we can pass the kernel command line option: |
+| | | ``modprobe.blacklist=ixgbe`` |
+| | | This way we do not need to unbind the device to bind it to igb_uio. |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Affected Environment/ Platform | Linux* systems with kernel versions 3.15 to 3.17 |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Driver/Module | igb_uio module |
++--------------------------------+--------------------------------------------------------------------------------------+
+
+VM power manager may not work on systems with more than 64 cores
+----------------------------------------------------------------
+
++--------------------------------+--------------------------------------------------------------------------------------+
+| Title | VM power manager may not work on systems with more than 64 cores |
+| | |
++================================+======================================================================================+
+| Description | When using VM power manager on a system with more than 64 cores, |
+| | VM(s) should not use cores 64 or higher. |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Implication | VM power manager should not be used with VM(s) that are using cores 64 or above. |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Resolution/ Workaround | Do not use cores 64 or above. |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Affected Environment/ Platform | Platforms with more than 64 cores. |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+
+| Driver/Module | VM power manager application |
+| | |
++--------------------------------+--------------------------------------------------------------------------------------+