SDK v1.1 Software Errata
|
Reference |
Description |
Workaround |
|
ENGR148155 |
SRIO functionality is not supported under Hypervisor. |
None. |
|
ENGR151644 |
Attempting to execute valgrind (3.6.1) will result in a segmentation fault. |
None. |
|
ENGR155098 |
Under high-load, netperf TCP tests may cause a memory corruption after several hours of running on P4080 rev2. The issue occurs in the Linux TCP stack and contaminates the DPAA-Ethernet driver. The problem has not been observed with netperf UDP or in other test environments |
None. |
|
ENGR155760 |
Linux IPFwd performance has degraded slightly compared to SDK v1.0 on P4080, P3041 and P5020. The amount of degradation varies across supported processors by 9-15%. |
1) With SDK v1.1, no
workaround exists. Patches may be provided post release as they become
available. |
|
ENGR156088 |
SATA PMP card is not supported P2041RDB, P5020DS, P3041DS using the native SATA port. |
Use a PCIe-SATA card for PMP on P2041, P5020, P3041. |
|
ENGR156134 |
On P5020, RAID6 with the hardware accelerator Is not supported. |
1) Use software based
RAID6 |
|
ENGR156155 |
USDPAA requires the "fsl_usdpaa_shmem" device to be compiled into the kernel, which causes a contiguous memory allocation to occur early during kernel boot. This driver does not support kernels operating with a non-zero base-address, which means it is not safe when operating as a guest under KVM. (So USDPAA cannot be used in a KVM guest.) In particular, for a kernel to be usable as a KVM guest, it must be compiled *without* CONFIG_FSL_USDPAA_SHMEM defined. |
When building a kernel that needs to be usable as a KVM guest (and so USDPAA support will be unavailable), disable the USDPAA "shmem" device in the kernel build configuration. If editing the ".config" file directly, ensure that CONFIG_FSL_USDPAA_SHMEM is undefined. If using the kernel "menuconfig" interface, go into "Device Drivers" -> "Misc devices" and disable the option marked "NXP® USDPAA shared memory driver". |
|
ENGR158331 |
Linux IPSec performance has significantly degraded due to several changes in the Linux network stack. |
1) With SDK v1.1, no
workaround exists. NXP is actively working to resolve. Patches will be
provided post release as they become available. |
|
ENGR158382 |
The glibc packaged with
gcc 4.5.2 included in this release has an issue which can result in the
following glibc error: More information on this topic: |
None. The fix requires an update from CodeSourcery. |
|
ENGR158626 |
The 64-bit Linux kernel
does not support External Proxy (CoreInt) Interrupt mode. Without this
support the interrupts are always working in legacy mode which is
incompatible with 64-bit Hypervisor. 64-bit Hypervisor does not support
mixing virtual interrupts and physical interrupts. |
Use 32-bit Linux with either 32-bit or 64-bit Hypervisor. |
|
ENGR160042 |
USDPAA RMan application cannot support type 11 protocol when packets are sent continuously. |
1) Use type 9 protocol for continuous packet transfer. 2) Use type 11 protocol only with single packet. |
|
ENGR160219 |
On P1023, the FMan module must receive only frame buffers that are 16-byte aligned. The DPAA ehternet driver may in some circumstances populate the BMan buffer pool used by FMan ports with unaligned buffers. |
A workaround for this
issue is available in the form of a patch: |
|
ENGR160307 |
At the time of this release, Secure Boot could not be verified on P2041 and P3060. However, there is no known issues would prevent Secure Boot from functioning on these targets. |
N/A |
|
ENGR160619 |
On P3060, MAC-less Ethernet between 2 Linux partitions on Hypervisor is not supported. |
None. |
|
ENGR160789 |
For P3060, when selecting the PME kernel driver option to enable scan test at kernel boot time, the PME database that is created fails. Issue is specific to processors with PME HW ver. 2.2 (e.g. P3060). |
Don't enable the PME driver option to enable scan test. |