diff options
Diffstat (limited to 'doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml')
-rw-r--r-- | doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml | 377 |
1 files changed, 377 insertions, 0 deletions
diff --git a/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml new file mode 100644 index 0000000..6fafb8d --- /dev/null +++ b/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml | |||
@@ -0,0 +1,377 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | ||
3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> | ||
4 | <chapter id="bugs-limitations"> | ||
5 | <title>Known Problems in this Release</title> | ||
6 | |||
7 | <para>Open source projects are continuously working on correcting reported | ||
8 | problems. Fixes and workarounds to bugs detected by Enea are submitted | ||
9 | upstream, and included in Enea Linux regardless of when they will be | ||
10 | included by the open source project. Issues that still affect the current | ||
11 | release are listed below.<remark>INFO: The <emphasis | ||
12 | role="bold">Release-Specific Problems</emphasis> section further down is | ||
13 | generated from JIRA with gen_known_issues.py, but that script is HARDCODED | ||
14 | with affectedversion "Enea Linux 6" and needs to be adapted when a release | ||
15 | info for another EL version changes.</remark></para> | ||
16 | |||
17 | <section id="bugs-limitations-yocto"> | ||
18 | <title>Yocto Project</title> | ||
19 | |||
20 | <para>The Yocto Project community uses a <ulink | ||
21 | url="https://bugzilla.yoctoproject.org">Bugzilla database</ulink> to track | ||
22 | information on reported bugs and other issues.</para> | ||
23 | </section> | ||
24 | |||
25 | <section condition="hidden" id="bugs-limitations-sdk"> | ||
26 | <title>Toolchain / SDK</title> | ||
27 | |||
28 | <itemizedlist spacing="compact"> | ||
29 | <listitem> | ||
30 | <para>Building the kernel might fail if GNU Make of version 3.82 has | ||
31 | been installed on the host. The mandatory recovery action is to revert | ||
32 | to version 3.81.<remark>INFO It is possible to hide this entire | ||
33 | subsection by setting condition hidden on the section | ||
34 | element</remark></para> | ||
35 | </listitem> | ||
36 | |||
37 | <listitem> | ||
38 | <para>Installing a second toolchain in the same directory as a | ||
39 | previous one will break the $PATH variable of the first | ||
40 | one.<remark>LXCR-3624</remark></para> | ||
41 | </listitem> | ||
42 | </itemizedlist> | ||
43 | </section> | ||
44 | |||
45 | <section condition="hidden" id="bugs-limitations-eclipse"> | ||
46 | <title>Eclipse Tools</title> | ||
47 | |||
48 | <para>The Eclipse tools provided together with Enea Linux are part of the | ||
49 | Yocto Project Application Development Toolkit (ADT) and are maintained by | ||
50 | different open source projects. The list below outlines current problems | ||
51 | with the plug-ins as such, as well as kernel limitations when using a tool | ||
52 | towards the mentioned target:<remark>INFO It is possible to hide this | ||
53 | setting condition hidden on the section element</remark></para> | ||
54 | |||
55 | <itemizedlist spacing="compact"> | ||
56 | <listitem> | ||
57 | <para><emphasis role="bold">HOB</emphasis> is currently not supported | ||
58 | on Red Hat.<remark>LXCR-2994, LXCR-3222</remark></para> | ||
59 | </listitem> | ||
60 | |||
61 | <listitem> | ||
62 | <para><emphasis role="bold">SystemTap</emphasis> is currently not | ||
63 | supported on Red Hat.<remark>LXCR-3274</remark></para> | ||
64 | </listitem> | ||
65 | |||
66 | <listitem> | ||
67 | <para>When running <emphasis role="bold">SystemTap</emphasis> for the | ||
68 | first time on a target, you may need to manually ssh into the target | ||
69 | beforehand, in order to add the RSA key of the host to the file | ||
70 | known_hosts. Failing to do so will result in Eclipse freezing with the | ||
71 | progress window displayed, and a terminal message <literal>The | ||
72 | authenticity of host <target_ip> can't be | ||
73 | established</literal>.</para> | ||
74 | </listitem> | ||
75 | |||
76 | <listitem> | ||
77 | <para><emphasis role="bold">SystemTap</emphasis> scripts sometimes | ||
78 | result crosstap error messages about inaccessible variables. This is | ||
79 | not an issue with the tool itself, but stems from the compiler | ||
80 | optimizing away some of the variables. See workaround in the User's | ||
81 | Guide.<remark>LXCR-2204</remark></para> | ||
82 | </listitem> | ||
83 | |||
84 | <listitem> | ||
85 | <para>Currently <emphasis role="bold">BitBake Commander</emphasis> | ||
86 | projects can only be created for a local connection. Due to an | ||
87 | upstream bug, selecting a remote connection causes the Eclipse GUI to | ||
88 | freeze such that it must be killed.<remark>LXCR-2801</remark></para> | ||
89 | </listitem> | ||
90 | |||
91 | <listitem> | ||
92 | <para>A limitation currently makes <emphasis | ||
93 | role="bold">Eclipse</emphasis> non-responding when running a streaming | ||
94 | script, i.e. a script that runs continuously.</para> | ||
95 | </listitem> | ||
96 | |||
97 | <listitem> | ||
98 | <para>The <emphasis role="bold">LatencyTop</emphasis> plug-in for the | ||
99 | P2041 target reports some errors due to the permissions configuration | ||
100 | on the target, but it works correctly if the | ||
101 | <literal>latencytop</literal> command is issued from the Eclipse | ||
102 | console.<remark>LXCR-6303</remark></para> | ||
103 | </listitem> | ||
104 | |||
105 | <listitem> | ||
106 | <para>Currently <emphasis role="bold">LatencyTOP</emphasis> is not | ||
107 | available for ARM kernels built with SMP support due to an ARM | ||
108 | specific limitation in the Linux kernel.</para> | ||
109 | </listitem> | ||
110 | |||
111 | <listitem> | ||
112 | <para><emphasis role="bold">PowerTOP</emphasis> sometimes freezes | ||
113 | Eclipse after displaying a progress bar with message | ||
114 | <literal>Gathering powertop data file | ||
115 | remotely</literal>.<remark>LXCR-3143</remark></para> | ||
116 | </listitem> | ||
117 | |||
118 | <listitem> | ||
119 | <para>When running <emphasis role="bold">powertop</emphasis> from the | ||
120 | Eclipse terminal towards p2020rdb targets it is necessary to specify | ||
121 | the full path in order to find the | ||
122 | command.<remark>LXCR-2265</remark></para> | ||
123 | </listitem> | ||
124 | |||
125 | <listitem> | ||
126 | <para>When running <emphasis role="bold">powertop</emphasis> from the | ||
127 | Eclipse terminal towards zynq ZC702 targets it is necessary to specify | ||
128 | the full path in order to find the | ||
129 | command.<remark>LXCR-2265</remark></para> | ||
130 | </listitem> | ||
131 | |||
132 | <listitem> | ||
133 | <para>The <emphasis role="bold">PowerTOP</emphasis> console in Eclipse | ||
134 | might display messages like <literal>Cannot load | ||
135 | /var/cache/powertop/<filename></literal>. As a workaround, run | ||
136 | <emphasis role="bold">powertop --calibrate</emphasis> for a while to | ||
137 | generate the missing files. See <ulink | ||
138 | url="https://bugzilla.redhat.com/show_bug.cgi?id=698020">Bugzilla | ||
139 | #698020</ulink>.<remark>LXCR-3575</remark></para> | ||
140 | </listitem> | ||
141 | |||
142 | <listitem> | ||
143 | <para><emphasis role="bold">ssh-only</emphasis> is currently the only | ||
144 | supported connection type when running Eclipse tools towards a | ||
145 | target.<remark>LXCR-2799</remark></para> | ||
146 | </listitem> | ||
147 | |||
148 | <listitem> | ||
149 | <para>Hyphen character '-' in the name of the <emphasis | ||
150 | role="bold">Yocto Project ADT AutoTools project</emphasis> can cause | ||
151 | configuration errors.<remark>LXCR-2290</remark></para> | ||
152 | </listitem> | ||
153 | |||
154 | <listitem> | ||
155 | <para>The <emphasis role="bold">LTTng</emphasis> tool does not work on | ||
156 | <emphasis role="bold">ARM</emphasis> targets, neither from within | ||
157 | Eclipse nor when run directly on target, due to a problem with | ||
158 | lttng-modules and gcc-4.8.x. See <ulink | ||
159 | url="https://bugzilla.yoctoproject.org/show_bug.cgi?id=6015">Bugzilla | ||
160 | #6015</ulink>.<remark>LXCR-2653, LXCR-3053</remark></para> | ||
161 | </listitem> | ||
162 | |||
163 | <listitem> | ||
164 | <para>When running <emphasis role="bold">LTTng</emphasis> from | ||
165 | Eclipse, it sometimes happens that a new session created in the | ||
166 | Control View does not immediately appear under Sessions for that | ||
167 | target. However, the session is created and will appear after | ||
168 | right-clicking "Sessions" and selecting "Refresh".</para> | ||
169 | </listitem> | ||
170 | |||
171 | <listitem> | ||
172 | <para>The<emphasis role="bold"> yocto-bsp</emphasis> properties page | ||
173 | has some problems in the graphical user interface. Occasionally it is | ||
174 | not possible to resize and scroll which makes it impossible to see the | ||
175 | lower part of the properties window.<remark>LXCR-3128</remark></para> | ||
176 | </listitem> | ||
177 | |||
178 | <listitem> | ||
179 | <para>When connecting an Eclipse project configured for <emphasis | ||
180 | role="bold">KGDB</emphasis> (GDB Hardware Debugging) to a 64-bit | ||
181 | PowerPC target, GDB fails to connect unless the architecture is | ||
182 | specified in <filename>.gdbinit</filename>. See <ulink | ||
183 | url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=457697">Bugzilla | ||
184 | #457697</ulink>.<remark>LXCR-3984</remark></para> | ||
185 | </listitem> | ||
186 | </itemizedlist> | ||
187 | </section> | ||
188 | |||
189 | <section condition="hidden" id="bugs-limitations-target-side-tools"> | ||
190 | <title>Target-Side Tools</title> | ||
191 | |||
192 | <para>The target-side tools can be run stand-alone on target or from | ||
193 | Eclipse on host. The issues below are only observed when running the tools | ||
194 | directly on target:<remark>INFO It is possible to hide this setting | ||
195 | condition hidden on the section element</remark></para> | ||
196 | |||
197 | <itemizedlist spacing="compact"> | ||
198 | <listitem> | ||
199 | <para>The <emphasis role="bold">perf report</emphasis> command hangs | ||
200 | or crashes due to segmentation fault on ARM | ||
201 | targets.<remark>LXCR-2708</remark></para> | ||
202 | </listitem> | ||
203 | |||
204 | <listitem> | ||
205 | <para>The <emphasis role="bold">perf report</emphasis> does not show | ||
206 | any output for the PandaBoard target.<remark>LXCR-2710</remark></para> | ||
207 | </listitem> | ||
208 | |||
209 | <listitem> | ||
210 | <para><emphasis role="bold">perf top</emphasis> displays for a few | ||
211 | seconds the error message <literal>Failed to open | ||
212 | /tmp/perf-388.map</literal>. Any attempt to exit the subsequent window | ||
213 | causes the system to hang.<remark>LXCR-3113</remark></para> | ||
214 | </listitem> | ||
215 | |||
216 | <listitem> | ||
217 | <para>When running the <command>perf top</command> command on the i.MX | ||
218 | 6Quad SABRE Lite target, the console text may become red after running | ||
219 | for some time (~ 1 minute).<remark>LXCR-3631</remark></para> | ||
220 | </listitem> | ||
221 | |||
222 | <listitem> | ||
223 | <para>The <emphasis role="bold">LTTng</emphasis> tool does not work on | ||
224 | <emphasis role="bold">ARM</emphasis> targets, neither from within | ||
225 | Eclipse nor when run directly on target, due to a problem with | ||
226 | lttng-modules and gcc-4.8.x. See <ulink | ||
227 | url="https://bugzilla.yoctoproject.org/show_bug.cgi?id=6015">Bugzilla | ||
228 | #6015</ulink>.<remark>LXCR-2653, LXCR-3053</remark></para> | ||
229 | </listitem> | ||
230 | |||
231 | <listitem> | ||
232 | <para>The <emphasis role="bold">powertop --calibrate</emphasis> | ||
233 | command does not work on the Keystone k2hk-evm | ||
234 | target.<remark>LXCR-2660</remark></para> | ||
235 | </listitem> | ||
236 | |||
237 | <listitem> | ||
238 | <para>The <emphasis role="bold">powertop</emphasis> command run with | ||
239 | <emphasis role="bold">--calibrate</emphasis> or -<emphasis | ||
240 | role="bold">-time</emphasis> arguments may show some warnings on | ||
241 | PowerPC targets.</para> | ||
242 | </listitem> | ||
243 | |||
244 | <listitem> | ||
245 | <para>When running <emphasis role="bold">powertop</emphasis> on | ||
246 | <emphasis role="bold">ARM</emphasis> targets, the following | ||
247 | warning/error is repeated: <literal>clk_set_rate: failed to set | ||
248 | i2c0_aper rate</literal> . Then powertop stops and the statistics are | ||
249 | no longer updated. What probably happens here is that the cpufreq | ||
250 | governor tries to scale the CPU frequency, but since the I2C clock is | ||
251 | derived from the CPU frequency, the I2C driver implements some policy | ||
252 | to stay within legal frequency limits and rejects the frequency | ||
253 | changes, ending up with the warning message. A <ulink | ||
254 | url="https://github.com/Xilinx/linux-xlnx/commit/0fdd34575efae5c8eced09b6b0a1b723bff4d225">fix</ulink> | ||
255 | has been merged in the linux-xlnx kernel but is not yet propagated | ||
256 | into meta-xilinx.<remark>LXCR-3205, LXCR-3106, | ||
257 | LXCR-2660</remark></para> | ||
258 | </listitem> | ||
259 | |||
260 | <listitem> | ||
261 | <para>If you get an error message like <literal>Cannot load from file | ||
262 | /var/cache/powertop/saved_results.powertop</literal> when running | ||
263 | <emphasis role="bold">powertop</emphasis>, there is most likely not | ||
264 | enough measurement data collected yet. All you have to do is to keep | ||
265 | powertop running for a certain time.<remark>LXCR-2176, LXCR-2660, | ||
266 | LXCR-3106</remark></para> | ||
267 | </listitem> | ||
268 | |||
269 | <listitem> | ||
270 | <para>The message <literal>Model-specific registers (MSR) not found | ||
271 | (try enabling CONFIG_X86_MSR)</literal> appears when you run <emphasis | ||
272 | role="bold">powertop</emphasis> on <emphasis | ||
273 | role="bold">non-x86</emphasis> targets. powertop is mainly an x86n | ||
274 | tool, so it expects X*^_MSR config to be enabled in the kernel. For | ||
275 | non-x86 targets this config is not available in the kernel, hence, | ||
276 | powertop warns about it, but the message can be ignored on those | ||
277 | targets.<remark> LXCR-2176, LXCR-2660, LXCR-3106</remark></para> | ||
278 | </listitem> | ||
279 | |||
280 | <listitem> | ||
281 | <para><emphasis role="bold">powertop</emphasis> issues a message | ||
282 | <literal>sh: /usr/bin/xset: No such file or directory</literal> when | ||
283 | it tries to use xset to configure X display preferences but cannot | ||
284 | find the binary since the image by default contains no X system. The | ||
285 | message can simply be ignored.<remark>LXCR-2176</remark></para> | ||
286 | </listitem> | ||
287 | </itemizedlist> | ||
288 | </section> | ||
289 | |||
290 | <section condition="hidden" id="bugs-limitations-virtualization"> | ||
291 | <title>Virtualization</title> | ||
292 | |||
293 | <itemizedlist spacing="compact"> | ||
294 | <listitem> | ||
295 | <para><emphasis role="bold">virtualization</emphasis>: CONFIG_BRIDGE | ||
296 | is not included in the default p2020rdb | ||
297 | kernel.<remark>LXVTCR-273</remark></para> | ||
298 | </listitem> | ||
299 | |||
300 | <listitem> | ||
301 | <para><emphasis role="bold">lxc</emphasis>:</para> | ||
302 | |||
303 | <itemizedlist spacing="compact"> | ||
304 | <listitem> | ||
305 | <para>User namespace is not available on PowerPC targets as it is | ||
306 | an experimental feature in the 3.8 kernel.</para> | ||
307 | </listitem> | ||
308 | |||
309 | <listitem> | ||
310 | <para>If multiple Linux containers are started from the same | ||
311 | process and share resources, destroying the containers might | ||
312 | result in a race condition with error message "Error in | ||
313 | `./lxc-test-concurrent': double free or corruption (fasttop)" | ||
314 | followed by an application | ||
315 | crash."<remark>LXVTCR-365</remark></para> | ||
316 | </listitem> | ||
317 | </itemizedlist> | ||
318 | </listitem> | ||
319 | |||
320 | <listitem> | ||
321 | <para><emphasis role="bold">libvirt</emphasis>: Default network does | ||
322 | not start.<remark>LXVTCR-240</remark></para> | ||
323 | </listitem> | ||
324 | </itemizedlist> | ||
325 | </section> | ||
326 | |||
327 | <section condition="hidden" id="bugs-limitations-doc"> | ||
328 | <title>Documentation</title> | ||
329 | |||
330 | <itemizedlist spacing="compact"> | ||
331 | <listitem> | ||
332 | <para><emphasis role="bold">PDF navigation</emphasis>: When using | ||
333 | links to open other PDFs, or jump to another place in the same PDF, | ||
334 | jumping back sometimes fails. This has been observed when opening a | ||
335 | PDF in Adobe Reader, inside a browser with PDF add-on, as well as when | ||
336 | the browser is configured to open PDF files in an external PDF reader. | ||
337 | As a workaround, open the HTML version of the | ||
338 | document.<remark>LXCR-3283</remark></para> | ||
339 | </listitem> | ||
340 | |||
341 | <listitem> | ||
342 | <para><emphasis role="bold">Internet Explorer (IE) cannot display some | ||
343 | web pages</emphasis>: It is recommended to use Firefox or another | ||
344 | non-IE browser for opening external links. If you prefer reading the | ||
345 | documentation in PDF format in Adobe Reader (not in an Adobe plug-in | ||
346 | in a browser), remember to configure a non-IE browser as default | ||
347 | browser to be able to follow all links from within Adobe Reader. | ||
348 | Example of a link that does not work in IE: <ulink | ||
349 | url="https://rt.wiki.kernel.org/">https://rt.wiki.kernel.org/</ulink>. | ||
350 | <remark>LXCR-3281</remark></para> | ||
351 | </listitem> | ||
352 | </itemizedlist> | ||
353 | </section> | ||
354 | |||
355 | <section condition="hidden" id="bugs-limitations-other"> | ||
356 | <title>Miscellaneous</title> | ||
357 | |||
358 | <itemizedlist spacing="compact"> | ||
359 | <listitem> | ||
360 | <para>Running <emphasis role="bold">QEMU from an exported | ||
361 | rootfs</emphasis> requires sudo privileges on the host.</para> | ||
362 | </listitem> | ||
363 | |||
364 | <listitem> | ||
365 | <para><emphasis role="bold">menuconfig</emphasis> requires <emphasis | ||
366 | role="bold">Ncurses</emphasis>. If the terminal that pops up | ||
367 | immediately closes instead of showing the menuconfig interface, check | ||
368 | that the Ncurses development library is installed.</para> | ||
369 | </listitem> | ||
370 | </itemizedlist> | ||
371 | </section> | ||
372 | |||
373 | <!-- The file with a section below is autocreated by make init --> | ||
374 | |||
375 | <!-- <xi:include href="jiraissues_generated.xml" | ||
376 | xmlns:xi="http://www.w3.org/2001/XInclude" /> --> | ||
377 | </chapter> \ No newline at end of file | ||