diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml
index f7345547c5..dcf0b95ae4 100644
--- a/documentation/ref-manual/usingpoky.xml
+++ b/documentation/ref-manual/usingpoky.xml
@@ -69,6 +69,39 @@
$ bitbake target
+
+
+ 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
+ systemd version 228+
+ (i.e. see this
+ link
+ for information).
+
+
+
+ To work around this issue, you can try either
+ of the following:
+
+
+ Try the build again.
+
+
+ Modify the "DefaultTasksMax"
+ systemd parameter
+ by uncommenting it and setting it to
+ "infinity".
+ You can find this parameter in the
+ system.conf file
+ located in
+ /etc/systemd
+ on most systems.
+
+
+
+
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index e2c33d2f50..c1d3bf5927 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -566,14 +566,47 @@
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.
$ bitbake core-image-sato
+
+
+ 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
+ systemd version 228+
+ (i.e. see this
+ link
+ for information).
+
+
+
+ To work around this issue, you can try either
+ of the following:
+
+
+ Try the build again.
+
+
+ Modify the "DefaultTasksMax"
+ systemd parameter
+ by uncommenting it and setting it to
+ "infinity".
+ You can find this parameter in the
+ system.conf file
+ located in
+ /etc/systemd
+ on most systems.
+
+
+
+
For information on using the
bitbake command, see the
"BitBake"
@@ -724,6 +757,39 @@
$ bitbake core-image-base
+
+
+ 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
+ systemd version 228+
+ (i.e. see this
+ link
+ for information).
+
+
+
+ To work around this issue, you can try either
+ of the following:
+
+
+ Try the build again.
+
+
+ Modify the "DefaultTasksMax"
+ systemd parameter
+ by uncommenting it and setting it to
+ "infinity".
+ You can find this parameter in the
+ system.conf file
+ located in
+ /etc/systemd
+ on most systems.
+
+
+
+
Once the build completes, the resulting console-only image
is located in the Build Directory here: