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 | 267 |
1 files changed, 0 insertions, 267 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 deleted file mode 100644 index 173046b..0000000 --- a/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml +++ /dev/null | |||
@@ -1,267 +0,0 @@ | |||
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>The open source projects are continuously working on correcting | ||
8 | reported problems. Corrections to bugs detected by Enea are submitted | ||
9 | upstream, and the corrections are included in Enea Linux regardless of when | ||
10 | they will be included by the open source project. Remaining issues are | ||
11 | listed below.<remark>INFO: The <emphasis role="bold">Release-Specific | ||
12 | Problems</emphasis> section further down is generated from JIRA with | ||
13 | gen_known_issues.py, but that script is HARDCODED with affectedversion "Enea | ||
14 | Linux 6" and needs to be adapted when a release info for another EL version | ||
15 | changes.</remark></para> | ||
16 | |||
17 | <section id="bugs-limitations-yocto"> | ||
18 | <title>Yocto</title> | ||
19 | |||
20 | <para>The Yocto Project community uses a Bugzilla database to track | ||
21 | information on reported bugs and other issues: <ulink | ||
22 | url="https://bugzilla.yoctoproject.org"> | ||
23 | https://bugzilla.yoctoproject.org</ulink>.</para> | ||
24 | </section> | ||
25 | |||
26 | <section condition="hidden" id="bugs-limitations-sdk"> | ||
27 | <title>Toolchain / SDK</title> | ||
28 | |||
29 | <itemizedlist spacing="compact"> | ||
30 | <listitem> | ||
31 | <para>Building the kernel might fail if GNU Make of version 3.82 has | ||
32 | been installed on the host. The mandatory recovery action is to revert | ||
33 | to version 3.81.<remark>INFO It is possible to hide this entire | ||
34 | subsection by setting condition hidden on the section | ||
35 | element</remark></para> | ||
36 | </listitem> | ||
37 | |||
38 | <listitem> | ||
39 | <para>Installing a second toolchain in the same directory as a | ||
40 | previous one will break the $PATH variable of the first | ||
41 | one.<remark>LXCR-3624</remark></para> | ||
42 | </listitem> | ||
43 | </itemizedlist> | ||
44 | </section> | ||
45 | |||
46 | <section condition="hidden" id="bugs-package-manager"> | ||
47 | <title>Smart Package Manager</title> | ||
48 | |||
49 | <para>Installation of some packages might currently fail when installing | ||
50 | using the Smart Package Manager. An example is the qemu package. Errors | ||
51 | can e.g. be reported by smart about conflicts with files from other | ||
52 | packages.<remark>INFO It is possible to hide this setting condition hidden | ||
53 | on the section element</remark></para> | ||
54 | |||
55 | <para>The recommended solution to this problem is to install the failing | ||
56 | package using rpm, already available in enea-image-base. In order to | ||
57 | install it using rpm, first install rpm using the command <command>smart | ||
58 | install rpm</command>, then download the package to the target, and | ||
59 | finally on the target use <command>rpm -i | ||
60 | <packagename>.rpm</command>. If not installed, several dependencies | ||
61 | can be reported as "Failed dependencies" with lines "x is needed by y". In | ||
62 | that case, install the required packages "x" found by dependencies by | ||
63 | using the smart package manager. Add a channel to an accessible directory | ||
64 | containing all missing rpm packages. Add packages detected to be missing, | ||
65 | until all dependencies are resolved.<remark>FIXME It would be nice to add | ||
66 | also a PowerPC example with qemu failing, the example below is for | ||
67 | ARM.</remark></para> | ||
68 | |||
69 | <section> | ||
70 | <title>Example with Failing QEMU Package</title> | ||
71 | |||
72 | <para>As an example, the qemu installation can show the following | ||
73 | error.<remark>INFO It is possible to hide this setting condition hidden | ||
74 | on the section element</remark></para> | ||
75 | |||
76 | <note> | ||
77 | <para>The example below is for ARM, including the RPM names. For | ||
78 | PowerPC similar errors can occur and other packages are needed.</para> | ||
79 | </note> | ||
80 | |||
81 | <para><emphasis role="bold">error: file /var/run from install of | ||
82 | qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 conflicts with file from package | ||
83 | base-files-3.0.14-r89.0.hierofalcon</emphasis></para> | ||
84 | |||
85 | <para>A solution to this problem is to install the above qemu package | ||
86 | using rpm, already available in enea-image-base. In order to install it | ||
87 | using rpm, first install rpm using the command <command>smart install | ||
88 | rpm</command>, then download the above package from | ||
89 | <build_dir>/tmp/deploy/rpm/aarch64. On target, use <command>rpm -i | ||
90 | qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm</command>. If not installed, | ||
91 | several dependencies can be seen, e.g.:</para> | ||
92 | |||
93 | <programlisting>error: Failed dependencies: | ||
94 | libpixman-1-0 >= 0.32.6 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
95 | libpixman-1.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
96 | libglib-2.0.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
97 | libcap2 >= 2.22 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
98 | libglib-2.0-0 >= 2.40.0 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
99 | bluez4 >= 4.101 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
100 | libbluetooth.so.3()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 | ||
101 | libcap.so.2()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64</programlisting> | ||
102 | |||
103 | <para>Install the required packages found by dependencies by using the | ||
104 | smart package manager, as specified in the User's Guide, by adding a | ||
105 | channel to an accessible directory containing all of the above rpm | ||
106 | packages. Suggestion for installing required packages, as in the | ||
107 | following example for qemu and ARM:</para> | ||
108 | |||
109 | <programlisting>smart install bash | ||
110 | smart install libcap | ||
111 | smart install bluez4 | ||
112 | smart install libpixman-1-0 | ||
113 | rpm -i qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm</programlisting> | ||
114 | |||
115 | <para>Add packages detected to be missing until all dependencies are | ||
116 | resolved.</para> | ||
117 | </section> | ||
118 | </section> | ||
119 | |||
120 | <section condition="hidden" id="bugs-limitations-target-side-tools"> | ||
121 | <title>Target-Side Tools</title> | ||
122 | |||
123 | <itemizedlist spacing="compact"> | ||
124 | <listitem> | ||
125 | <para>The <emphasis role="bold">perf report</emphasis> does not show | ||
126 | any output for the PandaBoard target.<remark>LXCR-2710</remark></para> | ||
127 | </listitem> | ||
128 | |||
129 | <listitem> | ||
130 | <para><emphasis role="bold">perf top</emphasis> displays for a few | ||
131 | seconds the error message <literal>Failed to open | ||
132 | /tmp/perf-388.map</literal>. Any attempt to exit the subsequent window | ||
133 | causes the system to hang.<remark>LXCR-3113</remark></para> | ||
134 | </listitem> | ||
135 | |||
136 | <listitem> | ||
137 | <para>When running the <command>perf top</command> command on the i.MX | ||
138 | 6Quad SABRE Lite target, the console text may become red after running | ||
139 | for some time (~ 1 minute).<remark>LXCR-3631</remark></para> | ||
140 | </listitem> | ||
141 | |||
142 | <listitem> | ||
143 | <para>The <emphasis role="bold">powertop --calibrate</emphasis> | ||
144 | command does not work on the Keystone k2hk-evm | ||
145 | target.<remark>LXCR-2660</remark></para> | ||
146 | </listitem> | ||
147 | |||
148 | <listitem> | ||
149 | <para>The <emphasis role="bold">powertop</emphasis> command run with | ||
150 | <emphasis role="bold">--calibrate</emphasis> or -<emphasis | ||
151 | role="bold">-time</emphasis> arguments may show some warnings on | ||
152 | PowerPC targets.</para> | ||
153 | </listitem> | ||
154 | |||
155 | <listitem> | ||
156 | <para>If you get an error message like <literal>Cannot load from file | ||
157 | /var/cache/powertop/saved_results.powertop</literal> when running | ||
158 | <emphasis role="bold">powertop</emphasis>, there is most likely not | ||
159 | enough measurement data collected yet. All you have to do is to keep | ||
160 | powertop running for a certain time.<remark>LXCR-2176, LXCR-2660, | ||
161 | LXCR-3106</remark></para> | ||
162 | </listitem> | ||
163 | |||
164 | <listitem> | ||
165 | <para>The message <literal>Model-specific registers (MSR) not found | ||
166 | (try enabling CONFIG_X86_MSR)</literal> appears when you run <emphasis | ||
167 | role="bold">powertop</emphasis> on <emphasis | ||
168 | role="bold">non-x86</emphasis> targets. powertop is mainly an x86n | ||
169 | tool, so it expects X*^_MSR config to be enabled in the kernel. For | ||
170 | non-x86 targets this config is not available in the kernel, hence, | ||
171 | powertop warns about it, but the message can be ignored on those | ||
172 | targets.<remark> LXCR-2176, LXCR-2660, LXCR-3106</remark></para> | ||
173 | </listitem> | ||
174 | |||
175 | <listitem> | ||
176 | <para><emphasis role="bold">powertop</emphasis> issues a message | ||
177 | <literal>sh: /usr/bin/xset: No such file or directory</literal> when | ||
178 | it tries to use xset to configure X display preferences but cannot | ||
179 | find the binary since the image by default contains no X system. The | ||
180 | message can simply be ignored.<remark>LXCR-2176</remark></para> | ||
181 | </listitem> | ||
182 | </itemizedlist> | ||
183 | </section> | ||
184 | |||
185 | <section condition="hidden" id="bugs-limitations-virtualization"> | ||
186 | <title>Virtualization</title> | ||
187 | |||
188 | <itemizedlist spacing="compact"> | ||
189 | <listitem> | ||
190 | <para><emphasis role="bold">virtualization</emphasis>: CONFIG_BRIDGE | ||
191 | is not included in the default p2020rdb | ||
192 | kernel.<remark>LXVTCR-273</remark></para> | ||
193 | </listitem> | ||
194 | |||
195 | <listitem> | ||
196 | <para><emphasis role="bold">lxc</emphasis>:</para> | ||
197 | |||
198 | <itemizedlist spacing="compact"> | ||
199 | <listitem> | ||
200 | <para>User namespace is not available on PowerPC targets as it is | ||
201 | an experimental feature in the 3.8 kernel.</para> | ||
202 | </listitem> | ||
203 | |||
204 | <listitem> | ||
205 | <para>If multiple Linux containers are started from the same | ||
206 | process and share resources, destroying the containers might | ||
207 | result in a race condition with error message "Error in | ||
208 | `./lxc-test-concurrent': double free or corruption (fasttop)" | ||
209 | followed by an application | ||
210 | crash."<remark>LXVTCR-365</remark></para> | ||
211 | </listitem> | ||
212 | </itemizedlist> | ||
213 | </listitem> | ||
214 | |||
215 | <listitem> | ||
216 | <para><emphasis role="bold">libvirt</emphasis>: Default network does | ||
217 | not start.<remark>LXVTCR-240</remark></para> | ||
218 | </listitem> | ||
219 | </itemizedlist> | ||
220 | </section> | ||
221 | |||
222 | <section condition="hidden" id="bugs-limitations-doc"> | ||
223 | <title>Documentation</title> | ||
224 | |||
225 | <itemizedlist spacing="compact"> | ||
226 | <listitem> | ||
227 | <para><emphasis role="bold">PDF navigation</emphasis>: When using | ||
228 | links to open other PDFs, or jump to another place in the same PDF, | ||
229 | jumping back sometimes fails. This has been observed when opening a | ||
230 | PDF in Adobe Reader, inside a browser with PDF add-on, as well as when | ||
231 | the browser is configured to open PDF files in an external PDF reader. | ||
232 | As a workaround, open the HTML version of the | ||
233 | document.<remark>LXCR-3283</remark></para> | ||
234 | </listitem> | ||
235 | |||
236 | <listitem> | ||
237 | <para><emphasis role="bold">Internet Explorer (IE) cannot display some | ||
238 | web pages</emphasis>: It is recommended to use Firefox or another | ||
239 | non-IE browser for opening external links. If you prefer reading the | ||
240 | documentation in PDF format in Adobe Reader (not in an Adobe plug-in | ||
241 | in a browser), remember to configure a non-IE browser as default | ||
242 | browser to be able to follow all links from within Adobe Reader. | ||
243 | Example of a link that does not work in IE: <ulink | ||
244 | url="https://rt.wiki.kernel.org/">https://rt.wiki.kernel.org/</ulink>. | ||
245 | <remark>LXCR-3281</remark></para> | ||
246 | </listitem> | ||
247 | </itemizedlist> | ||
248 | </section> | ||
249 | |||
250 | <section condition="hidden" id="bugs-limitations-other"> | ||
251 | <title>Miscellaneous</title> | ||
252 | |||
253 | <itemizedlist spacing="compact"> | ||
254 | <listitem> | ||
255 | <para><emphasis role="bold">menuconfig</emphasis> requires <emphasis | ||
256 | role="bold">Ncurses</emphasis>. If the terminal that pops up | ||
257 | immediately closes instead of showing the menuconfig interface, check | ||
258 | that the Ncurses development library is installed.</para> | ||
259 | </listitem> | ||
260 | </itemizedlist> | ||
261 | </section> | ||
262 | |||
263 | <!-- The file with a section below is autocreated by make init --> | ||
264 | |||
265 | <xi:include href="jiraissues_generated.xml" | ||
266 | xmlns:xi="http://www.w3.org/2001/XInclude" /> | ||
267 | </chapter> \ No newline at end of file | ||