summaryrefslogtreecommitdiffstats
path: root/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml
blob: df4f30a6f50d75b51a85992217b9086f1941c2f8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<chapter id="bugs-limitations">
  <title>Known Problems in this Release</title>

  <para>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.<remark>INFO: The <emphasis
  role="bold">Release-Specific Problems</emphasis> 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.</remark></para>

  <section id="bugs-limitations-yocto">
    <title>Yocto Project</title>

    <para>The Yocto Project community uses a <ulink
    url="https://bugzilla.yoctoproject.org">Bugzilla database</ulink> to track
    information on reported bugs and other issues.</para>
  </section>

  <section id="bugs-limitations-hddimg">
    <title>SDK image as hddimg</title>

    <para>The SDK image cannot be exported in the <literal>.hddimg</literal> 
      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.</para>
  </section>

  <section condition="hidden" id="bugs-limitations-sdk">
    <title>Toolchain / SDK</title>

    <itemizedlist spacing="compact">
      <listitem>
        <para>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.<remark>INFO It is possible to hide this entire
        subsection by setting condition hidden on the section
        element</remark></para>
      </listitem>

      <listitem>
        <para>Installing a second toolchain in the same directory as a
        previous one will break the $PATH variable of the first
        one.<remark>LXCR-3624</remark></para>
      </listitem>
    </itemizedlist>
  </section>

  <section condition="hidden" id="bugs-limitations-eclipse">
    <title>Eclipse Tools</title>

    <para>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:<remark>INFO It is possible to hide this
    setting condition hidden on the section element</remark></para>

    <itemizedlist spacing="compact">
      <listitem>
        <para><emphasis role="bold">HOB</emphasis> is currently not supported
        on Red Hat.<remark>LXCR-2994, LXCR-3222</remark></para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">SystemTap</emphasis> is currently not
        supported on Red Hat.<remark>LXCR-3274</remark></para>
      </listitem>

      <listitem>
        <para>When running <emphasis role="bold">SystemTap</emphasis> 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 <literal>The
        authenticity of host &lt;target_ip&gt; can't be
        established</literal>.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">SystemTap</emphasis> 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.<remark>LXCR-2204</remark></para>
      </listitem>

      <listitem>
        <para>Currently <emphasis role="bold">BitBake Commander</emphasis>
        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.<remark>LXCR-2801</remark></para>
      </listitem>

      <listitem>
        <para>A limitation currently makes <emphasis
        role="bold">Eclipse</emphasis> non-responding when running a streaming
        script, i.e. a script that runs continuously.</para>
      </listitem>

      <listitem>
        <para>The <emphasis role="bold">LatencyTop</emphasis> plug-in for the
        P2041 target reports some errors due to the permissions configuration
        on the target, but it works correctly if the
        <literal>latencytop</literal> command is issued from the Eclipse
        console.<remark>LXCR-6303</remark></para>
      </listitem>

      <listitem>
        <para>Currently <emphasis role="bold">LatencyTOP</emphasis> is not
        available for ARM kernels built with SMP support due to an ARM
        specific limitation in the Linux kernel.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">PowerTOP</emphasis> sometimes freezes
        Eclipse after displaying a progress bar with message
        <literal>Gathering powertop data file
        remotely</literal>.<remark>LXCR-3143</remark></para>
      </listitem>

      <listitem>
        <para>When running <emphasis role="bold">powertop</emphasis> from the
        Eclipse terminal towards p2020rdb targets it is necessary to specify
        the full path in order to find the
        command.<remark>LXCR-2265</remark></para>
      </listitem>

      <listitem>
        <para>When running <emphasis role="bold">powertop</emphasis> from the
        Eclipse terminal towards zynq ZC702 targets it is necessary to specify
        the full path in order to find the
        command.<remark>LXCR-2265</remark></para>
      </listitem>

      <listitem>
        <para>The <emphasis role="bold">PowerTOP</emphasis> console in Eclipse
        might display messages like <literal>Cannot load
        /var/cache/powertop/&lt;filename&gt;</literal>. As a workaround, run
        <emphasis role="bold">powertop --calibrate</emphasis> for a while to
        generate the missing files. See <ulink
        url="https://bugzilla.redhat.com/show_bug.cgi?id=698020">Bugzilla
        #698020</ulink>.<remark>LXCR-3575</remark></para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">ssh-only</emphasis> is currently the only
        supported connection type when running Eclipse tools towards a
        target.<remark>LXCR-2799</remark></para>
      </listitem>

      <listitem>
        <para>Hyphen character '-' in the name of the <emphasis
        role="bold">Yocto Project ADT AutoTools project</emphasis> can cause
        configuration errors.<remark>LXCR-2290</remark></para>
      </listitem>

      <listitem>
        <para>The <emphasis role="bold">LTTng</emphasis> tool does not work on
        <emphasis role="bold">ARM</emphasis> targets, neither from within
        Eclipse nor when run directly on target, due to a problem with
        lttng-modules and gcc-4.8.x. See <ulink
        url="https://bugzilla.yoctoproject.org/show_bug.cgi?id=6015">Bugzilla
        #6015</ulink>.<remark>LXCR-2653, LXCR-3053</remark></para>
      </listitem>

      <listitem>
        <para>When running <emphasis role="bold">LTTng</emphasis> 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".</para>
      </listitem>

      <listitem>
        <para>The<emphasis role="bold"> yocto-bsp</emphasis> 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.<remark>LXCR-3128</remark></para>
      </listitem>

      <listitem>
        <para>When connecting an Eclipse project configured for <emphasis
        role="bold">KGDB</emphasis> (GDB Hardware Debugging) to a 64-bit
        PowerPC target, GDB fails to connect unless the architecture is
        specified in <filename>.gdbinit</filename>. See <ulink
        url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=457697">Bugzilla
        #457697</ulink>.<remark>LXCR-3984</remark></para>
      </listitem>
    </itemizedlist>
  </section>

  <section condition="hidden" id="bugs-limitations-target-side-tools">
    <title>Target-Side Tools</title>

    <para>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:<remark>INFO It is possible to hide this setting
    condition hidden on the section element</remark></para>

    <itemizedlist spacing="compact">
      <listitem>
        <para>The <emphasis role="bold">perf report</emphasis> command hangs
        or crashes due to segmentation fault on ARM
        targets.<remark>LXCR-2708</remark></para>
      </listitem>

      <listitem>
        <para>The <emphasis role="bold">perf report</emphasis> does not show
        any output for the PandaBoard target.<remark>LXCR-2710</remark></para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">perf top</emphasis> displays for a few
        seconds the error message <literal>Failed to open
        /tmp/perf-388.map</literal>. Any attempt to exit the subsequent window
        causes the system to hang.<remark>LXCR-3113</remark></para>
      </listitem>

      <listitem>
        <para>When running the <command>perf top</command> command on the i.MX
        6Quad SABRE Lite target, the console text may become red after running
        for some time (~ 1 minute).<remark>LXCR-3631</remark></para>
      </listitem>

      <listitem>
        <para>The <emphasis role="bold">LTTng</emphasis> tool does not work on
        <emphasis role="bold">ARM</emphasis> targets, neither from within
        Eclipse nor when run directly on target, due to a problem with
        lttng-modules and gcc-4.8.x. See <ulink
        url="https://bugzilla.yoctoproject.org/show_bug.cgi?id=6015">Bugzilla
        #6015</ulink>.<remark>LXCR-2653, LXCR-3053</remark></para>
      </listitem>

      <listitem>
        <para>The <emphasis role="bold">powertop --calibrate</emphasis>
        command does not work on the Keystone k2hk-evm
        target.<remark>LXCR-2660</remark></para>
      </listitem>

      <listitem>
        <para>The <emphasis role="bold">powertop</emphasis> command run with
        <emphasis role="bold">--calibrate</emphasis> or -<emphasis
        role="bold">-time</emphasis> arguments may show some warnings on
        PowerPC targets.</para>
      </listitem>

      <listitem>
        <para>When running <emphasis role="bold">powertop</emphasis> on
        <emphasis role="bold">ARM</emphasis> targets, the following
        warning/error is repeated: <literal>clk_set_rate: failed to set
        i2c0_aper rate</literal> . 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 <ulink
        url="https://github.com/Xilinx/linux-xlnx/commit/0fdd34575efae5c8eced09b6b0a1b723bff4d225">fix</ulink>
        has been merged in the linux-xlnx kernel but is not yet propagated
        into meta-xilinx.<remark>LXCR-3205, LXCR-3106,
        LXCR-2660</remark></para>
      </listitem>

      <listitem>
        <para>If you get an error message like <literal>Cannot load from file
        /var/cache/powertop/saved_results.powertop</literal> when running
        <emphasis role="bold">powertop</emphasis>, there is most likely not
        enough measurement data collected yet. All you have to do is to keep
        powertop running for a certain time.<remark>LXCR-2176, LXCR-2660,
        LXCR-3106</remark></para>
      </listitem>

      <listitem>
        <para>The message <literal>Model-specific registers (MSR) not found
        (try enabling CONFIG_X86_MSR)</literal> appears when you run <emphasis
        role="bold">powertop</emphasis> on <emphasis
        role="bold">non-x86</emphasis> 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.<remark> LXCR-2176, LXCR-2660, LXCR-3106</remark></para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">powertop</emphasis> issues a message
        <literal>sh: /usr/bin/xset: No such file or directory</literal> 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.<remark>LXCR-2176</remark></para>
      </listitem>
    </itemizedlist>
  </section>

  <section condition="hidden" id="bugs-limitations-virtualization">
    <title>Virtualization</title>

    <itemizedlist spacing="compact">
      <listitem>
        <para><emphasis role="bold">virtualization</emphasis>: CONFIG_BRIDGE
        is not included in the default p2020rdb
        kernel.<remark>LXVTCR-273</remark></para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">lxc</emphasis>:</para>

        <itemizedlist spacing="compact">
          <listitem>
            <para>User namespace is not available on PowerPC targets as it is
            an experimental feature in the 3.8 kernel.</para>
          </listitem>

          <listitem>
            <para>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."<remark>LXVTCR-365</remark></para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para><emphasis role="bold">libvirt</emphasis>: Default network does
        not start.<remark>LXVTCR-240</remark></para>
      </listitem>
    </itemizedlist>
  </section>

  <section condition="hidden" id="bugs-limitations-doc">
    <title>Documentation</title>

    <itemizedlist spacing="compact">
      <listitem>
        <para><emphasis role="bold">PDF navigation</emphasis>: 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.<remark>LXCR-3283</remark></para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">Internet Explorer (IE) cannot display some
        web pages</emphasis>: 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: <ulink
        url="https://rt.wiki.kernel.org/">https://rt.wiki.kernel.org/</ulink>.
        <remark>LXCR-3281</remark></para>
      </listitem>
    </itemizedlist>
  </section>

  <section condition="hidden" id="bugs-limitations-other">
    <title>Miscellaneous</title>

    <itemizedlist spacing="compact">
      <listitem>
        <para>Running <emphasis role="bold">QEMU from an exported
        rootfs</emphasis> requires sudo privileges on the host.</para>
      </listitem>

      <listitem>
        <para><emphasis role="bold">menuconfig</emphasis> requires <emphasis
        role="bold">Ncurses</emphasis>. If the terminal that pops up
        immediately closes instead of showing the menuconfig interface, check
        that the Ncurses development library is installed.</para>
      </listitem>
    </itemizedlist>
  </section>

  <!-- The file with a section below is autocreated by make init  -->

  <!--  <xi:include href="jiraissues_generated.xml"
              xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
</chapter>