u-boot 2025.01 fails with exit 137 after including fastboot menuconfig options

edwardtyrrell — Thu, 04 Sep 2025 13:17:50 GMT

Hi All,

Frustrating issue after adding fastboot options to u-boot build via bitbake u-boot-fslc -c menuconfig. One the build is set in motion the host machine grinds to a halt then errors with: ......recipes-bsp/u-boot/u-boot-fslc_2025.01.bb:do_compile) failed with exit code '137'

I've tried a number of possible fixes i.e limiting build threads, other CONFIGs but nothing works. Apparently its a memory consumption issue to do with config files? U-boot is small in comparison and typically takes under a minute to build, adding the FB options in it takes 4-5 minutes before it crashes the build.

Build machine is Ubuntu 22.04, Yocto 6.12.20, u-boot 2025.01

Thanks!

Re: u-boot 2025.01 fails with exit 137 after including fastboot menuconfig options

Bio_TICFSL — Mon, 08 Sep 2025 13:35:05 GMT

Hello,

Exit code 137 specifically signifies termination by SIGKILL (signal 9), as 128 + 9 = 137. SIGKILL is a non-catchable, non-ignorable signal that forces a process to terminate immediately. During the compilation process of U-Boot, especially in environments with limited resources (e.g., virtual machines, containers, or embedded systems with constrained memory), the build process might exceed available memory, leading to its termination by the 137 error.

Regards

i.MX Processorsのトピックu-boot 2025.01 fails with exit 137 after including fastboot menuconfig options

u-boot 2025.01 fails with exit 137 after including fastboot menuconfig options

Re: u-boot 2025.01 fails with exit 137 after including fastboot menuconfig options