1. Meta-Freescale
  2. Topics

u-boot-fslc 2022.10 failed with exit code '137' (using too much memory) #yocto #kirkstone #meta-freescale #u-boot

Livius
 

New u-boot-fslc_2022.10.bb is failed always with exit code '137' which means the available memory has been exhausted, so 16 GB DDR4 RAM memory was not enough for this single recipe build on Ubuntu 20.04 desktop Linux.
https://www.containiq.com/post/exit-code-137
 
Similar problem was happened in mender forum: https://hub.mender.io/t/uboot-auto-configure-exit-code-137/3624
 
Please fix it, i think it is not normally that 16 GB RAM is not enough for a single recipe build.
Otavio Salvador
 



Em ter., 29 de nov. de 2022 às 06:33, Livius <egyszeregy@...> escreveu:
New u-boot-fslc_2022.10.bb is failed always with exit code '137' which means the available memory has been exhausted, so 16 GB DDR4 RAM memory was not enough for this single recipe build on Ubuntu 20.04 desktop Linux.
https://www.containiq.com/post/exit-code-137
 
Similar problem was happened in mender forum: https://hub.mender.io/t/uboot-auto-configure-exit-code-137/3624
 
Please fix it, i think it is not normally that 16 GB RAM is not enough for a single recipe build.

You reported this on GH too so we'll keep it there and reply there.

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750
Livius
 

Yes, i reported it in GitHub also

https://github.com/Freescale/meta-freescale/issues/1318

I have no any other Linux desktop machine to try it in a different host PC but i could see my eyes in htop GUI that total memory usage was in full 16 GB in 3-4 minutes at compiling task of u-boot then finally i got the error code 137.
Bas Mevissen
 

On 2022-11-29 14:47, Livius wrote:

Yes, i reported it in GitHub also
https://github.com/Freescale/meta-freescale/issues/1318
I have no any other Linux desktop machine to try it in a different host PC but i could see my eyes in htop GUI that total memory usage was in full 16 GB in 3-4 minutes at compiling task of u-boot then finally i got the error code 137.
You know you can reduce the memory consumption by:
1) Lowering the number of parallel makes (using PARALLEL_MAKE in local.conf or maybe in a .bbappend for the package)
2) Limit the number of bitbake threads (using BB_NUMBER_THREADS in local.conf)
3) Create a swap file on an SSD?

I use the latter with Android AOSP builds as they really need more than 16GB RAM by default.
Livius
 

1 - 5 of 5