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 | 183 |
1 files changed, 0 insertions, 183 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 index 5058404..e92d90e 100644 --- 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 | |||
@@ -120,164 +120,11 @@ | |||
120 | </section> | 120 | </section> |
121 | </section> | 121 | </section> |
122 | 122 | ||
123 | <section id="bugs-limitations-eclipse"> | ||
124 | <title>Eclipse Tools</title> | ||
125 | |||
126 | <para>The Eclipse tools provided together with Enea Linux are part of the | ||
127 | Yocto Application Development Toolkit (ADT) and are maintained by | ||
128 | different open source projects. The list below outlines current problems | ||
129 | with the plug-ins as such, as well as kernel limitations when using a tool | ||
130 | towards the mentioned target:</para> | ||
131 | |||
132 | <itemizedlist spacing="compact"> | ||
133 | <listitem> | ||
134 | <para><emphasis role="bold">HOB</emphasis> is currently not supported | ||
135 | on Red Hat.<remark>LXCR-2994, LXCR-3222</remark></para> | ||
136 | </listitem> | ||
137 | |||
138 | <listitem> | ||
139 | <para><emphasis role="bold">SystemTap</emphasis> is currently not | ||
140 | supported on Red Hat.<remark>LXCR-3274</remark></para> | ||
141 | </listitem> | ||
142 | |||
143 | <listitem> | ||
144 | <para>When running <emphasis role="bold">SystemTap</emphasis> for the | ||
145 | first time on a target, you may need to manually ssh into the target | ||
146 | beforehand, in order to add the RSA key of the host to the file | ||
147 | known_hosts. Failing to do so will result in Eclipse freezing with the | ||
148 | progress window displayed, and a terminal message <literal>The | ||
149 | authenticity of host <target_ip> can't be | ||
150 | established</literal>.</para> | ||
151 | </listitem> | ||
152 | |||
153 | <listitem> | ||
154 | <para><emphasis role="bold">SystemTap</emphasis> scripts sometimes | ||
155 | result crosstap error messages about inaccessible variables. This is | ||
156 | not an issue with the tool itself, but stems from the compiler | ||
157 | optimizing away some of the variables. See workaround in the User's | ||
158 | Guide.<remark>LXCR-2204</remark></para> | ||
159 | </listitem> | ||
160 | |||
161 | <listitem> | ||
162 | <para>Currently <emphasis role="bold">BitBake Commander</emphasis> | ||
163 | projects can only be created for a local connection. Due to an | ||
164 | upstream bug, selecting a remote connection causes the Eclipse GUI to | ||
165 | freeze such that it must be killed.<remark>LXCR-2801</remark></para> | ||
166 | </listitem> | ||
167 | |||
168 | <listitem> | ||
169 | <para>A limitation currently makes <emphasis | ||
170 | role="bold">Eclipse</emphasis> non-responding when running a streaming | ||
171 | script, i.e. a script that runs continuously.</para> | ||
172 | </listitem> | ||
173 | |||
174 | <listitem> | ||
175 | <para>The <emphasis role="bold">LatencyTop</emphasis> plug-in for the | ||
176 | P2041 target reports some errors due to the permissions configuration | ||
177 | on the target, but it works correctly if the | ||
178 | <literal>latencytop</literal> command is issued from the Eclipse | ||
179 | console.<remark>LXCR-6303</remark></para> | ||
180 | </listitem> | ||
181 | |||
182 | <listitem> | ||
183 | <para>Currently <emphasis role="bold">LatencyTOP</emphasis> is not | ||
184 | available for ARM kernels built with SMP support due to an ARM | ||
185 | specific limitation in the Linux kernel.</para> | ||
186 | </listitem> | ||
187 | |||
188 | <listitem> | ||
189 | <para><emphasis role="bold">PowerTOP</emphasis> sometimes freezes | ||
190 | Eclipse after displaying a progress bar with message | ||
191 | <literal>Gathering powertop data file | ||
192 | remotely</literal>.<remark>LXCR-3143</remark></para> | ||
193 | </listitem> | ||
194 | |||
195 | <listitem> | ||
196 | <para>When running <emphasis role="bold">powertop</emphasis> from the | ||
197 | Eclipse terminal towards p2020rdb targets it is necessary to specify | ||
198 | the full path in order to find the | ||
199 | command.<remark>LXCR-2265</remark></para> | ||
200 | </listitem> | ||
201 | |||
202 | <listitem> | ||
203 | <para>When running <emphasis role="bold">powertop</emphasis> from the | ||
204 | Eclipse terminal towards zynq ZC702 targets it is necessary to specify | ||
205 | the full path in order to find the | ||
206 | command.<remark>LXCR-2265</remark></para> | ||
207 | </listitem> | ||
208 | |||
209 | <listitem> | ||
210 | <para>The <emphasis role="bold">PowerTOP</emphasis> console in Eclipse | ||
211 | might display messages like <literal>Cannot load | ||
212 | /var/cache/powertop/<filename></literal>. As a workaround, run | ||
213 | <emphasis role="bold">powertop --calibrate</emphasis> for a while to | ||
214 | generate the missing files. See <ulink | ||
215 | url="https://bugzilla.redhat.com/show_bug.cgi?id=698020">Bugzilla | ||
216 | #698020</ulink>.<remark>LXCR-3575</remark></para> | ||
217 | </listitem> | ||
218 | |||
219 | <listitem> | ||
220 | <para><emphasis role="bold">ssh-only</emphasis> is currently the only | ||
221 | supported connection type when running Eclipse tools towards a | ||
222 | target.<remark>LXCR-2799</remark></para> | ||
223 | </listitem> | ||
224 | |||
225 | <listitem> | ||
226 | <para>Hyphen character '-' in the name of the <emphasis | ||
227 | role="bold">Yocto ADT AutoTools project</emphasis> can cause | ||
228 | configuration errors.<remark>LXCR-2290</remark></para> | ||
229 | </listitem> | ||
230 | |||
231 | <listitem> | ||
232 | <para>The <emphasis role="bold">LTTng</emphasis> tool does not work on | ||
233 | <emphasis role="bold">ARM</emphasis> targets, neither from within | ||
234 | Eclipse nor when run directly on target, due to a problem with | ||
235 | lttng-modules and gcc-4.8.x. See <ulink | ||
236 | url="https://bugzilla.yoctoproject.org/show_bug.cgi?id=6015">Bugzilla | ||
237 | #6015</ulink>.<remark>LXCR-2653, LXCR-3053</remark></para> | ||
238 | </listitem> | ||
239 | |||
240 | <listitem> | ||
241 | <para>When running <emphasis role="bold">LTTng</emphasis> from | ||
242 | Eclipse, it sometimes happens that a new session created in the | ||
243 | Control View does not immediately appear under Sessions for that | ||
244 | target. However, the session is created and will appear after | ||
245 | right-clicking "Sessions" and selecting "Refresh".</para> | ||
246 | </listitem> | ||
247 | |||
248 | <listitem> | ||
249 | <para>The<emphasis role="bold"> yocto-bsp</emphasis> properties page | ||
250 | has some problems in the graphical user interface. Occasionally it is | ||
251 | not possible to resize and scroll which makes it impossible to see the | ||
252 | lower part of the properties window.<remark>LXCR-3128</remark></para> | ||
253 | </listitem> | ||
254 | |||
255 | <listitem> | ||
256 | <para>When connecting an Eclipse project configured for <emphasis | ||
257 | role="bold">KGDB</emphasis> (GDB Hardware Debugging) to a 64-bit | ||
258 | PowerPC target, GDB fails to connect unless the architecture is | ||
259 | specified in <filename>.gdbinit</filename>. See <ulink | ||
260 | url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=457697">Bugzilla | ||
261 | #457697</ulink>.<remark>LXCR-3984</remark></para> | ||
262 | </listitem> | ||
263 | </itemizedlist> | ||
264 | </section> | ||
265 | |||
266 | <section id="bugs-limitations-target-side-tools"> | 123 | <section id="bugs-limitations-target-side-tools"> |
267 | <title>Target-Side Tools</title> | 124 | <title>Target-Side Tools</title> |
268 | 125 | ||
269 | <para>The target-side tools can be run stand-alone on target or from | ||
270 | Eclipse on host. The issues below are only observed when running the tools | ||
271 | directly on target:</para> | ||
272 | |||
273 | <itemizedlist spacing="compact"> | 126 | <itemizedlist spacing="compact"> |
274 | <listitem> | 127 | <listitem> |
275 | <para>The <emphasis role="bold">perf report</emphasis> command hangs | ||
276 | or crashes due to segmentation fault on ARM | ||
277 | targets.<remark>LXCR-2708</remark></para> | ||
278 | </listitem> | ||
279 | |||
280 | <listitem> | ||
281 | <para>The <emphasis role="bold">perf report</emphasis> does not show | 128 | <para>The <emphasis role="bold">perf report</emphasis> does not show |
282 | any output for the PandaBoard target.<remark>LXCR-2710</remark></para> | 129 | any output for the PandaBoard target.<remark>LXCR-2710</remark></para> |
283 | </listitem> | 130 | </listitem> |
@@ -296,15 +143,6 @@ | |||
296 | </listitem> | 143 | </listitem> |
297 | 144 | ||
298 | <listitem> | 145 | <listitem> |
299 | <para>The <emphasis role="bold">LTTng</emphasis> tool does not work on | ||
300 | <emphasis role="bold">ARM</emphasis> targets, neither from within | ||
301 | Eclipse nor when run directly on target, due to a problem with | ||
302 | lttng-modules and gcc-4.8.x. See <ulink | ||
303 | url="https://bugzilla.yoctoproject.org/show_bug.cgi?id=6015">Bugzilla | ||
304 | #6015</ulink>.<remark>LXCR-2653, LXCR-3053</remark></para> | ||
305 | </listitem> | ||
306 | |||
307 | <listitem> | ||
308 | <para>The <emphasis role="bold">powertop --calibrate</emphasis> | 146 | <para>The <emphasis role="bold">powertop --calibrate</emphasis> |
309 | command does not work on the Keystone k2hk-evm | 147 | command does not work on the Keystone k2hk-evm |
310 | target.<remark>LXCR-2660</remark></para> | 148 | target.<remark>LXCR-2660</remark></para> |
@@ -318,22 +156,6 @@ | |||
318 | </listitem> | 156 | </listitem> |
319 | 157 | ||
320 | <listitem> | 158 | <listitem> |
321 | <para>When running <emphasis role="bold">powertop</emphasis> on | ||
322 | <emphasis role="bold">ARM</emphasis> targets, the following | ||
323 | warning/error is repeated: <literal>clk_set_rate: failed to set | ||
324 | i2c0_aper rate</literal> . Then powertop stops and the statistics are | ||
325 | no longer updated. What probably happens here is that the cpufreq | ||
326 | governor tries to scale the CPU frequency, but since the I2C clock is | ||
327 | derived from the CPU frequency, the I2C driver implements some policy | ||
328 | to stay within legal frequency limits and rejects the frequency | ||
329 | changes, ending up with the warning message. A <ulink | ||
330 | url="https://github.com/Xilinx/linux-xlnx/commit/0fdd34575efae5c8eced09b6b0a1b723bff4d225">fix</ulink> | ||
331 | has been merged in the linux-xlnx kernel but is not yet propagated | ||
332 | into meta-xilinx.<remark>LXCR-3205, LXCR-3106, | ||
333 | LXCR-2660</remark></para> | ||
334 | </listitem> | ||
335 | |||
336 | <listitem> | ||
337 | <para>If you get an error message like <literal>Cannot load from file | 159 | <para>If you get an error message like <literal>Cannot load from file |
338 | /var/cache/powertop/saved_results.powertop</literal> when running | 160 | /var/cache/powertop/saved_results.powertop</literal> when running |
339 | <emphasis role="bold">powertop</emphasis>, there is most likely not | 161 | <emphasis role="bold">powertop</emphasis>, there is most likely not |
@@ -433,11 +255,6 @@ | |||
433 | 255 | ||
434 | <itemizedlist spacing="compact"> | 256 | <itemizedlist spacing="compact"> |
435 | <listitem> | 257 | <listitem> |
436 | <para>Running <emphasis role="bold">QEMU from an exported | ||
437 | rootfs</emphasis> requires sudo privileges on the host.</para> | ||
438 | </listitem> | ||
439 | |||
440 | <listitem> | ||
441 | <para><emphasis role="bold">menuconfig</emphasis> requires <emphasis | 258 | <para><emphasis role="bold">menuconfig</emphasis> requires <emphasis |
442 | role="bold">Ncurses</emphasis>. If the terminal that pops up | 259 | role="bold">Ncurses</emphasis>. If the terminal that pops up |
443 | immediately closes instead of showing the menuconfig interface, check | 260 | immediately closes instead of showing the menuconfig interface, check |