sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

yocto-project-qs, ref-manual: Added note for "resources temporarily unavailable" error 

Fixes [YOCTO #10818]

There is a weird and intermittant error that can occur on any given
distribution that has a 4.3+ Linux kernel and a version 228+ systemd.
The error happens during an initial build of an image and indicates
that resources are unavailable.  Investigation determines that
resources are available.  The combination of the kernel and the
systemd in a distro is causing issues when a distro is upgraded.

yocto-project-qs:
I added a note in the two areas where the user is stepped through
the bitbake process to build an image.  The note mentions the
possibility of the error, the host configuration situation, and a
couple work-arounds, which are to reboot the machine or to set the
"DefaultTaskMax" systemd parameter to "infinity".

ref-manual:
Added the same note in the "Building an Image" section.

(From yocto-docs rev: 3516803f9e6b5a29e4f95d31742c6e03ff63ef41)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2017-01-06 08:16:09 -08:00 committed by Richard Purdie
parent 3ecc502b8d
commit 81021bc0aa
2 changed files with 101 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
documentation/ref-manual/usingpoky.xml
View File

@ -69,6 +69,39 @@
<literallayout class='monospaced'>
$ bitbake <replaceable>target</replaceable>
</literallayout>
<note>
<para>
If you experience a build error due to resources
temporarily being unavailable and it appears you
should not be having this issue, it might be due
to the combination of a 4.3+ Linux kernel and
<filename>systemd</filename> version 228+
(i.e. see this
<ulink url='http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel'>link</ulink>
for information).
</para>
<para>
To work around this issue, you can try either
of the following:
<itemizedlist>
<listitem><para>
Try the build again.
</para></listitem>
<listitem><para>
Modify the "DefaultTasksMax"
<filename>systemd</filename> parameter
by uncommenting it and setting it to
"infinity".
You can find this parameter in the
<filename>system.conf</filename> file
located in
<filename>/etc/systemd</filename>
on most systems.
</para></listitem>
</itemizedlist>
</para>
</note>
</para>
<para>

70
documentation/yocto-project-qs/yocto-project-qs.xml
View File

@ -566,14 +566,47 @@
<note>
Depending on the number of processors and cores, the
amount of RAM, the speed of your Internet connection
and other factors, the build process could take several
hours the first time you run it.
and other factors, the build process could take
several hours the first time you run it.
Subsequent builds run much faster since parts of the
build are cached.
</note>
<literallayout class='monospaced'>
$ bitbake core-image-sato
</literallayout>
<note>
<para>
If you experience a build error due to resources
temporarily being unavailable and it appears you
should not be having this issue, it might be due
to the combination of a 4.3+ Linux kernel and
<filename>systemd</filename> version 228+
(i.e. see this
<ulink url='http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel'>link</ulink>
for information).
</para>
<para>
To work around this issue, you can try either
of the following:
<itemizedlist>
<listitem><para>
Try the build again.
</para></listitem>
<listitem><para>
Modify the "DefaultTasksMax"
<filename>systemd</filename> parameter
by uncommenting it and setting it to
"infinity".
You can find this parameter in the
<filename>system.conf</filename> file
located in
<filename>/etc/systemd</filename>
on most systems.
</para></listitem>
</itemizedlist>
</para>
</note>
For information on using the
<filename>bitbake</filename> command, see the
"<ulink url='&YOCTO_DOCS_REF_URL;#usingpoky-components-bitbake'>BitBake</ulink>"
@ -724,6 +757,39 @@
<literallayout class='monospaced'>
$ bitbake core-image-base
</literallayout>
<note>
<para>
If you experience a build error due to resources
temporarily being unavailable and it appears you
should not be having this issue, it might be due
to the combination of a 4.3+ Linux kernel and
<filename>systemd</filename> version 228+
(i.e. see this
<ulink url='http://unix.stackexchange.com/questions/253903/creating-threads-fails-with-resource-temporarily-unavailable-with-4-3-kernel'>link</ulink>
for information).
</para>
<para>
To work around this issue, you can try either
of the following:
<itemizedlist>
<listitem><para>
Try the build again.
</para></listitem>
<listitem><para>
Modify the "DefaultTasksMax"
<filename>systemd</filename> parameter
by uncommenting it and setting it to
"infinity".
You can find this parameter in the
<filename>system.conf</filename> file
located in
<filename>/etc/systemd</filename>
on most systems.
</para></listitem>
</itemizedlist>
</para>
</note>
Once the build completes, the resulting console-only image
is located in the Build Directory here:
<literallayout class='monospaced'>