From 81021bc0aa0f64e67535f6a9551e921a64fe4395 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 6 Jan 2017 08:16:09 -0800 Subject: [PATCH] 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 Signed-off-by: Richard Purdie --- documentation/ref-manual/usingpoky.xml | 33 +++++++++ .../yocto-project-qs/yocto-project-qs.xml | 70 ++++++++++++++++++- 2 files changed, 101 insertions(+), 2 deletions(-) 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: