Doc Makefile autofetch buglist from Jira at init

Makefile: Add autofetch buglist from Jira
via initissues. add cleanissues, add initissues to init.
Add autocreated XML as section in known_bugs chapter.
gen_known_issues.py: Correct DOCTYPE, remove empty
lines in created XML file, move the Jira search
parameters into hidden remark.
Adjust known_bugs chapter to correct xmlmind format
Delete the known_bugs doc issue with special characters
that are not used any more (checkmarks and crosses).

Signed-off-by: Lennart Johansson <lennart.johansson@enea.com>

3 files changed, 442 insertions, 551 deletions

diff --git a/doc/Makefile b/doc/Makefile
index f3cc297..aa26339 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -22,10 +22,11 @@ CURRENTHASH := $(shell git log -1 --pretty=format:%H 2>/dev/null)
 CURRENTURL := $(shell git remote show origin | sed -n '/Fetch URL: /s/^.*URL: //p' 2>/dev/null)
 
 # ******************* AutoGenerated chapter from template and target READMEs *******
-BUILDBOOT_XML      := book-enea-linux-release-info/doc/build_boot_generated.xml
-BUILDBOOT_TEMPLATE := book-enea-linux-release-info/doc/build_boot_template.xml
+BUILDBOOT_XML       := book-enea-linux-release-info/doc/build_boot_generated.xml
+BUILDBOOT_TEMPLATE  := book-enea-linux-release-info/doc/build_boot_template.xml
 
-PKGDIFF_GEN_XML    := book-enea-linux-release-info/doc/pkgdiff_generated.xml
+PKGDIFF_GEN_XML     := book-enea-linux-release-info/doc/pkgdiff_generated.xml
+JIRA_ISSUES_GEN_XML := book-enea-linux-release-info/doc/jiraissues_generated.xml
 
 
 # -----------------------------------------------------
@@ -130,7 +131,7 @@ ifeq ($(DOCBOOK_TOOLS_VERSIONS),yes)
 endif
 
 # We rely on make doing these in order left to right
-init: initbuild inittargets initpardoc initbuildboot initpkgdiff
+init: initbuild inittargets initpardoc initbuildboot initpkgdiff initissues
 pullall: pullbuild pulltargets
 
 # If no COMP, iterate over books-* in COMPONENTS with make doc
@@ -189,7 +190,7 @@ endif
 endif
 
 # cleaninit cleans ALL tmpcommon and all s_* and generated build_boot chapter xml
-clean:  cleaninit cleanbuildboot cleanpkgdiff
+clean:  cleaninit cleanbuildboot cleanpkgdiff cleanissues
         $(VERB)rm -rf doc tmp 2>/dev/null
 ifneq ($(filter book-%, $(COMPONENTS)),)
         $(VERB)for comp in $(filter book-%, $(COMPONENTS)); do \
@@ -282,7 +283,7 @@ $(BUILDBOOT_XML): s_targets $(BUILDBOOT_TEMPLATE)
           fi
 
 # ****************************************************************************
-# ***** Create XML section with package diff
+# ***** Create Package DIFF XML section
 
 initpkgdiff: $(PKGDIFF_GEN_XML)
 
@@ -291,7 +292,20 @@ cleanpkgdiff:
 
 $(PKGDIFF_GEN_XML):
         $(VERB)PREVIOUS_BL=`egrep '"prev_baseline"' docsrc_common/pardoc-distro.xml | sed 's/^.*<phrase>//;s/<\/phrase>.*$$//'` ; \
-          echo "Generating $(PKGDIFF_GEN_XML) compared to $$PREVIOUS_BL" ; \
+          echo "Generating $(PKGDIFF_GEN_XML) compared to $$PREVIOUS_BL, using gen_pkgdiff.py" ; \
           python gen_pkgdiff.py >$(PKGDIFF_GEN_XML)
 
+
+# ****************************************************************************
+# ***** Create Jira Issues XML section for the known bugs chapter
+
+initissues: $(JIRA_ISSUES_GEN_XML)
+
+cleanissues:
+        $(VERB)rm -f $(JIRA_ISSUES_GEN_XML) 2>/dev/null
+
+$(JIRA_ISSUES_GEN_XML):
+        @echo "Generating $(JIRA_ISSUES_GEN_XML), fetching from Jira using gen_known_issues.py"
+        $(VERB)python gen_known_issues.py >$(JIRA_ISSUES_GEN_XML)
+
 # ****************************************************************************
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 2a9598b..5058404 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
@@ -14,87 +14,86 @@
   targetptr="book_enea_linux_users_guide"><trademark
   class="registered">Enea</trademark> Linux User's Guide</olink>.</para>
 
-    <section id="bugs-limitations-yocto">
-      <title>Yocto</title>
+  <section id="bugs-limitations-yocto">
+    <title>Yocto</title>
 
-      <para>Open source projects often use bug databases for much more than
-      tracking bugs. The Yocto Project's Bugzilla database also functions as a
-      feature tracking program, both for the current release and for future
-      releases, and a way to track non-software issues, like documentation
-      changes.</para>
+    <para>Open source projects often use bug databases for much more than
+    tracking bugs. The Yocto Project's Bugzilla database also functions as a
+    feature tracking program, both for the current release and for future
+    releases, and a way to track non-software issues, like documentation
+    changes.</para>
 
-      <para>The following page shows a sampling of the database: <ulink
-      url="https://www.yoctoproject.org/tools-resources/bugs">https://www.yoctoproject.org/tools-resources/bugs</ulink>.</para>
+    <para>The following page shows a sampling of the database: <ulink
+    url="https://www.yoctoproject.org/tools-resources/bugs">https://www.yoctoproject.org/tools-resources/bugs</ulink>.</para>
 
-      <para>For the full database, visit <ulink
-      url="https://bugzilla.yoctoproject.org">https://bugzilla.yoctoproject.org</ulink>.</para>
-    </section>
+    <para>For the full database, visit <ulink
+    url="https://bugzilla.yoctoproject.org">https://bugzilla.yoctoproject.org</ulink>.</para>
+  </section>
 
-    <section 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.</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 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.</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 id="bugs-package-manager">
-      <title>Smart Package Manager</title>
-
-      <para>Installation of some packages might currently fail when installing
-      using the Smart Package Manager. An example is the qemu package. Errors
-      can e.g. be reported by smart about conflicts with files from other
-      packages.</para>
-
-      <para>The recommended solution to this problem is to install the failing
-      package using rpm, already available in enea-image-base. In order to
-      install it using rpm, first install rpm using the command <command>smart
-      install rpm</command>, then download the package to the target, and
-      finally on the target use <command>rpm -i
-      &lt;packagename&gt;.rpm</command>. If not installed, several
-      dependencies can be reported as "Failed dependencies" with lines "x is
-      needed by y". In that case, install the required packages "x" found by
-      dependencies by using the smart package manager. Add a channel to an
-      accessible directory containing all missing rpm packages. Add packages
-      detected to be missing, until all dependencies are
-      resolved.<remark>FIXME It would be nice to add also a PowerPC example
-      with qemu failing, the example below is for ARM.</remark></para>
-
-      <section>
-        <title>Example with Failing QEMU Package</title>
-
-        <para>As an example, the qemu installation can show the following
-        error.</para>
-
-        <note>
-          <para>The example below is for ARM, including the RPM names. For
-          PowerPC similar errors can occur and other packages are
-          needed.</para>
-        </note>
-
-        <para><emphasis role="bold">error: file /var/run from install of
-        qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 conflicts with file from
-        package base-files-3.0.14-r89.0.hierofalcon</emphasis></para>
-
-        <para>A solution to this problem is to install the above qemu package
-        using rpm, already available in enea-image-base. In order to install
-        it using rpm, first install rpm using the command <command>smart
-        install rpm</command>, then download the above package from
-        &lt;build_dir&gt;/tmp/deploy/rpm/aarch64. On target, use <command>rpm
-        -i qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm</command>. If not
-        installed, several dependencies can be seen, e.g.:</para>
-
-        <programlisting>error: Failed dependencies:
+  <section id="bugs-package-manager">
+    <title>Smart Package Manager</title>
+
+    <para>Installation of some packages might currently fail when installing
+    using the Smart Package Manager. An example is the qemu package. Errors
+    can e.g. be reported by smart about conflicts with files from other
+    packages.</para>
+
+    <para>The recommended solution to this problem is to install the failing
+    package using rpm, already available in enea-image-base. In order to
+    install it using rpm, first install rpm using the command <command>smart
+    install rpm</command>, then download the package to the target, and
+    finally on the target use <command>rpm -i
+    &lt;packagename&gt;.rpm</command>. If not installed, several dependencies
+    can be reported as "Failed dependencies" with lines "x is needed by y". In
+    that case, install the required packages "x" found by dependencies by
+    using the smart package manager. Add a channel to an accessible directory
+    containing all missing rpm packages. Add packages detected to be missing,
+    until all dependencies are resolved.<remark>FIXME It would be nice to add
+    also a PowerPC example with qemu failing, the example below is for
+    ARM.</remark></para>
+
+    <section>
+      <title>Example with Failing QEMU Package</title>
+
+      <para>As an example, the qemu installation can show the following
+      error.</para>
+
+      <note>
+        <para>The example below is for ARM, including the RPM names. For
+        PowerPC similar errors can occur and other packages are needed.</para>
+      </note>
+
+      <para><emphasis role="bold">error: file /var/run from install of
+      qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64 conflicts with file from package
+      base-files-3.0.14-r89.0.hierofalcon</emphasis></para>
+
+      <para>A solution to this problem is to install the above qemu package
+      using rpm, already available in enea-image-base. In order to install it
+      using rpm, first install rpm using the command <command>smart install
+      rpm</command>, then download the above package from
+      &lt;build_dir&gt;/tmp/deploy/rpm/aarch64. On target, use <command>rpm -i
+      qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm</command>. If not installed,
+      several dependencies can be seen, e.g.:</para>
+
+      <programlisting>error: Failed dependencies:
         libpixman-1-0 &gt;= 0.32.6 is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
         libpixman-1.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
         libglib-2.0.so.0()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
@@ -104,473 +103,351 @@
         libbluetooth.so.3()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64
         libcap.so.2()(64bit) is needed by qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64</programlisting>
 
-        <para>Install the required packages found by dependencies by using the
-        smart package manager, as specified in the User's Guide, by adding a
-        channel to an accessible directory containing all of the above rpm
-        packages. Suggestion for installing required packages, as in the
-        following example for qemu and ARM:</para>
+      <para>Install the required packages found by dependencies by using the
+      smart package manager, as specified in the User's Guide, by adding a
+      channel to an accessible directory containing all of the above rpm
+      packages. Suggestion for installing required packages, as in the
+      following example for qemu and ARM:</para>
 
-        <programlisting>smart install bash
+      <programlisting>smart install bash
         smart install libcap
         smart install bluez4
         smart install libpixman-1-0
         rpm -i qemu-2.1.0+git0+541bbb07eb-r0.0.aarch64.rpm</programlisting>
 
-        <para>Add packages detected to be missing until all dependencies are
-        resolved.</para>
-      </section>
-    </section>
-
-    <section id="bugs-limitations-eclipse">
-      <title>Eclipse Tools</title>
-
-      <para>The Eclipse tools provided together with Enea Linux are part of
-      the Yocto 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:</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 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 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:</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 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 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>
-
-        <listitem>
-          <para><emphasis role="bold">Characters not displayed properly in
-          PDF</emphasis>: When viewing PDF files in a browser, checkmarks (V)
-          and crosses (x) might display as 4 and 7, respectively. This has
-          been observed when reading <link
-          linkend="relinfo-supported-targets">Supported Targets</link> in
-          Firefox. Installing the Adobe Acrobat add-on should fix the
-          problem.<remark>LXCR-3266</remark></para>
-        </listitem>
-      </itemizedlist>
+      <para>Add packages detected to be missing until all dependencies are
+      resolved.</para>
     </section>
+  </section>
 
-    <section 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>
-
-  <section id="relinfo-extracted-from-jira">
-    <title>Extracted from Jira</title>
-
-    <para>This section lists open bugs in Jira.</para>
-
-    <para><programlisting>project = "Linux CR" \
- and issuetype = Bug \
- and affectedVersion = "Enea Linux 6" \
- and resolution = Unresolved</programlisting></para>
-
-    <informaltable>
-      <tgroup cols="2">
-        <colspec align="center" colwidth="1*" />
-
-        <colspec colwidth="6*" />
-
-        <thead>
-          <row>
-            <entry align="center">Key</entry>
-
-            <entry align="center">Summary</entry>
-          </row>
-        </thead>
-
-        <tbody>
-          <row>
-            <entry>LXCR-7094</entry>
-
-            <entry>meta-enea-bsp-arm: conf/machine: proliant-m400.conf must be
-            removed</entry>
-          </row>
-
-          <row>
-            <entry>LXCR-7093</entry>
-
-            <entry>meta-enea-bsp-* layers: README files should contain build
-            &amp; boot instructions</entry>
-          </row>
-
-          <row>
-            <entry>LXCR-7092</entry>
-
-            <entry>public layers: none of the 5 public layers can be found
-            within the OE index</entry>
-          </row>
-
-          <row>
-            <entry>LXCR-7085</entry>
-
-            <entry>powerpc-enea-linux-gnuspe-gdb not available in
-            sdk-ext</entry>
-          </row>
-
-          <row>
-            <entry>LXCR-7064</entry>
-
-            <entry>ABI compliance: an ABI dump cannot be created for any
-            SDK</entry>
-          </row>
-
-          <row>
-            <entry>LXCR-7056</entry>
-
-            <entry>README:s on krogoth branch refer to master branch</entry>
-          </row>
-
-          <row>
-            <entry>LXCR-7055</entry>
-
-            <entry>Templates set the wrong POKY_BBLAYERS_CONF_VERSION</entry>
-          </row>
-
-          <row>
-            <entry>LXCR-7053</entry>
-
-            <entry>[Doc] Eclipse PMD section should use the SDK</entry>
-          </row>
-
-          <row>
-            <entry>LXCR-7025</entry>
-
-            <entry>LTP test package does not run correctly for p2041rdb
-            target</entry>
-          </row>
-
-          <row>
-            <entry>LXCR-7020</entry>
-
-            <entry>Eclipse project configure fails with extensible sdk</entry>
-          </row>
+  <section id="bugs-limitations-eclipse">
+    <title>Eclipse Tools</title>
+
+    <para>The Eclipse tools provided together with Enea Linux are part of the
+    Yocto 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:</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 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>
 
-          <row>
-            <entry>LXCR-7019</entry>
+  <section 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:</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>
 
-            <entry>LTP test package does not run correctly for ls1021aiot
-            target</entry>
-          </row>
+  <section 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>
 
-          <row>
-            <entry>LXCR-6997</entry>
+  <section 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>
 
-            <entry>[Eclipse] Launching QEMU from Eclipse does not work</entry>
-          </row>
+  <section 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>
 
-          <row>
-            <entry>LXCR-6970</entry>
+  <!-- The file with a section below is autocreated by make init  -->
 
-            <entry>Reporting bugs from TestLink does not work</entry>
-          </row>
-        </tbody>
-      </tgroup>
-    </informaltable>
-  </section>
-</chapter>
+  <xi:include href="jiraissues_generated.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+</chapter>
\ No newline at end of file
diff --git a/doc/gen_known_issues.py b/doc/gen_known_issues.py
index 387fc49..b11f547 100755..100644
--- a/doc/gen_known_issues.py
+++ b/doc/gen_known_issues.py
@@ -38,41 +38,41 @@ for issue in jira_query(" and ".join(conditions)):
     bugs.append((issue["key"], issue["fields"]["summary"]))
 
 print '<?xml version="1.0" encoding="ISO-8859-1"?>'
-print '<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"'
+print '<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"'
 print '"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">'
 print '<section id="relinfo-extracted-from-jira">'
 print '  <title>Extracted from Jira</title>'
-print '  '
+print ''
 print '  <para>'
 print '    This section lists open bugs in Jira. Extracted at %s.' % time_str
 print '  </para>'
-print '  '
-print '  <para><programlisting>project = "Linux CR" \\'
+print ''
+print '  <remark>project = "Linux CR" \\'
 print '  and issuetype = Bug \\'
 print '  and affectedVersion = "Enea Linux 6" \\'
-print '  and resolution = Unresolved</programlisting></para>'
-print '  '
+print '  and resolution = Unresolved</remark>'
+print ''
 print '  <informaltable>'
 print '    <tgroup cols="2">'
 print '      <colspec colwidth="6*" />'
-print '      '
+print ''
 print '      <colspec align="center" colwidth="1*" />'
-print '      '
+print ''
 print '      <thead>'
 print '        <row>'
 print '          <entry align="center">Summary</entry>'
-print '          '
+print ''
 print '          <entry>Enea Ref</entry>'
 print '        </row>'
 print '      </thead>'
-print '      '
-print '      <tbody>',
+print ''
+print '      <tbody>'
 
 for bug in sorted(bugs):
     print ''
     print '        <row>'
     print '          <entry>%s</entry>' % bug[1]
-    print '          '
+    print ''
     print '          <entry>%s</entry>' % bug[0]
     print '        </row>'