Open source projects are continuously working on correcting reported problems. Fixes and workarounds to bugs detected by Enea are submitted upstream, and included in Enea Linux regardless of when they will be included by the open source project. Issues that still affect the current release are listed below.INFO: The Release-Specific Problems section further down is generated from JIRA with gen_known_issues.py, but that script is HARDCODED with affectedversion "Enea Linux 6" and needs to be adapted when a release info for another EL version changes.

The Yocto Project community uses a Bugzilla database to track information on reported bugs and other issues.

The SDK image cannot be exported in the .hddimg format due to the size of the generated binary. If this format is needed the package content needs to be adjusted to fit the size this format can support.

The KGDB kernel debugging scenario described in section 7.5 Debugging the Linux Kernel in Eclipse in the , was not validated for this release.

Building the kernel might fail if GNU Make of version 3.82 has been installed on the host. The mandatory recovery action is to revert to version 3.81.INFO It is possible to hide this entire subsection by setting condition hidden on the section element Installing a second toolchain in the same directory as a previous one will break the $PATH variable of the first one.LXCR-3624

The Eclipse tools provided together with Enea Linux are part of the Yocto Project Application Development Toolkit (ADT) and are maintained by different open source projects. The list below outlines current problems with the plug-ins as such, as well as kernel limitations when using a tool towards the mentioned target:INFO It is possible to hide this setting condition hidden on the section element HOB is currently not supported on Red Hat.LXCR-2994, LXCR-3222 SystemTap is currently not supported on Red Hat.LXCR-3274 When running SystemTap for the first time on a target, you may need to manually ssh into the target beforehand, in order to add the RSA key of the host to the file known_hosts. Failing to do so will result in Eclipse freezing with the progress window displayed, and a terminal message The authenticity of host <target_ip> can't be established. SystemTap scripts sometimes result crosstap error messages about inaccessible variables. This is not an issue with the tool itself, but stems from the compiler optimizing away some of the variables. See workaround in the User's Guide.LXCR-2204 Currently BitBake Commander projects can only be created for a local connection. Due to an upstream bug, selecting a remote connection causes the Eclipse GUI to freeze such that it must be killed.LXCR-2801 A limitation currently makes Eclipse non-responding when running a streaming script, i.e. a script that runs continuously. The LatencyTop plug-in for the P2041 target reports some errors due to the permissions configuration on the target, but it works correctly if the latencytop command is issued from the Eclipse console.LXCR-6303 Currently LatencyTOP is not available for ARM kernels built with SMP support due to an ARM specific limitation in the Linux kernel. PowerTOP sometimes freezes Eclipse after displaying a progress bar with message Gathering powertop data file remotely.LXCR-3143 When running powertop from the Eclipse terminal towards p2020rdb targets it is necessary to specify the full path in order to find the command.LXCR-2265 When running powertop from the Eclipse terminal towards zynq ZC702 targets it is necessary to specify the full path in order to find the command.LXCR-2265 The PowerTOP console in Eclipse might display messages like Cannot load /var/cache/powertop/<filename>. As a workaround, run powertop --calibrate for a while to generate the missing files. See Bugzilla #698020.LXCR-3575 ssh-only is currently the only supported connection type when running Eclipse tools towards a target.LXCR-2799 Hyphen character '-' in the name of the Yocto Project ADT AutoTools project can cause configuration errors.LXCR-2290 The LTTng tool does not work on ARM targets, neither from within Eclipse nor when run directly on target, due to a problem with lttng-modules and gcc-4.8.x. See Bugzilla #6015.LXCR-2653, LXCR-3053 When running LTTng from Eclipse, it sometimes happens that a new session created in the Control View does not immediately appear under Sessions for that target. However, the session is created and will appear after right-clicking "Sessions" and selecting "Refresh". The yocto-bsp properties page has some problems in the graphical user interface. Occasionally it is not possible to resize and scroll which makes it impossible to see the lower part of the properties window.LXCR-3128 When connecting an Eclipse project configured for KGDB (GDB Hardware Debugging) to a 64-bit PowerPC target, GDB fails to connect unless the architecture is specified in .gdbinit. See Bugzilla #457697.LXCR-3984

The target-side tools can be run stand-alone on target or from Eclipse on host. The issues below are only observed when running the tools directly on target:INFO It is possible to hide this setting condition hidden on the section element The perf report command hangs or crashes due to segmentation fault on ARM targets.LXCR-2708 The perf report does not show any output for the PandaBoard target.LXCR-2710 perf top displays for a few seconds the error message Failed to open /tmp/perf-388.map. Any attempt to exit the subsequent window causes the system to hang.LXCR-3113 When running the perf top command on the i.MX 6Quad SABRE Lite target, the console text may become red after running for some time (~ 1 minute).LXCR-3631 The LTTng tool does not work on ARM targets, neither from within Eclipse nor when run directly on target, due to a problem with lttng-modules and gcc-4.8.x. See Bugzilla #6015.LXCR-2653, LXCR-3053 The powertop --calibrate command does not work on the Keystone k2hk-evm target.LXCR-2660 The powertop command run with --calibrate or --time arguments may show some warnings on PowerPC targets. When running powertop on ARM targets, the following warning/error is repeated: clk_set_rate: failed to set i2c0_aper rate . Then powertop stops and the statistics are no longer updated. What probably happens here is that the cpufreq governor tries to scale the CPU frequency, but since the I2C clock is derived from the CPU frequency, the I2C driver implements some policy to stay within legal frequency limits and rejects the frequency changes, ending up with the warning message. A fix has been merged in the linux-xlnx kernel but is not yet propagated into meta-xilinx.LXCR-3205, LXCR-3106, LXCR-2660 If you get an error message like Cannot load from file /var/cache/powertop/saved_results.powertop when running powertop, there is most likely not enough measurement data collected yet. All you have to do is to keep powertop running for a certain time.LXCR-2176, LXCR-2660, LXCR-3106 The message Model-specific registers (MSR) not found (try enabling CONFIG_X86_MSR) appears when you run powertop on non-x86 targets. powertop is mainly an x86n tool, so it expects X*^_MSR config to be enabled in the kernel. For non-x86 targets this config is not available in the kernel, hence, powertop warns about it, but the message can be ignored on those targets. LXCR-2176, LXCR-2660, LXCR-3106 powertop issues a message sh: /usr/bin/xset: No such file or directory when it tries to use xset to configure X display preferences but cannot find the binary since the image by default contains no X system. The message can simply be ignored.LXCR-2176

virtualization: CONFIG_BRIDGE is not included in the default p2020rdb kernel.LXVTCR-273 lxc: User namespace is not available on PowerPC targets as it is an experimental feature in the 3.8 kernel. If multiple Linux containers are started from the same process and share resources, destroying the containers might result in a race condition with error message "Error in `./lxc-test-concurrent': double free or corruption (fasttop)" followed by an application crash."LXVTCR-365 libvirt: Default network does not start.LXVTCR-240

PDF navigation: When using links to open other PDFs, or jump to another place in the same PDF, jumping back sometimes fails. This has been observed when opening a PDF in Adobe Reader, inside a browser with PDF add-on, as well as when the browser is configured to open PDF files in an external PDF reader. As a workaround, open the HTML version of the document.LXCR-3283 Internet Explorer (IE) cannot display some web pages: It is recommended to use Firefox or another non-IE browser for opening external links. If you prefer reading the documentation in PDF format in Adobe Reader (not in an Adobe plug-in in a browser), remember to configure a non-IE browser as default browser to be able to follow all links from within Adobe Reader. Example of a link that does not work in IE: https://rt.wiki.kernel.org/. LXCR-3281

Running QEMU from an exported rootfs requires sudo privileges on the host. menuconfig requires Ncurses. If the terminal that pops up immediately closes instead of showing the menuconfig interface, check that the Ncurses development library is installed.