random build failures on kirkstone with custom TX2 hardware about tegra-demo-distro HOT 9 CLOSED

After moving that ^^ build dir out of the way, then doing setup-env and copying local.conf/bblayers.conf to the new/clean build dir, tried building the same image again and it works fine. => demo-image-sato

from tegra-demo-distro.

@sarnold these are typically the types of errors you see when you run out of memory on your build host in my experience. Doing a clean on the specific image which is failing typically resolves.

from tegra-demo-distro.

Sorry, i thought that was more clear - I couldn't clean my way out of that one, only a fresh build dir helped.

from tegra-demo-distro.

It sounds environmental... what are you using for a build host (OS, CPU count, RAM size) and for storage of your build tree (device type, filesystem type, size/occupied/free)? Are there any kernel errors logged when you run into the problem?

from tegra-demo-distro.

Build host is intel core-i7 with 8 cpu threads and 32 GB ram plus ~130 GB free (for tegra) on nvme ssd. I have several build trees for rpi, pine64, rockchip, marvell and I don't normally have issues; most of it is "bare" user account, but xilinx needs to build in a VM running bionic as project is stuck on 2020.x release of petalinux.

$ free
               total        used        free      shared  buff/cache   available
Mem:        32732296     4214848     2811928         348    25705520    28041948
Swap:        4194300       41472     4152828

and

$ df -h
Filesystem                                       Size  Used Avail Use% Mounted on
devtmpfs                                          10M     0   10M   0% /dev
tmpfs                                             16G   68K   16G   1% /dev/shm
tmpfs                                             16G  708K   16G   1% /run
/dev/nvme0n1p3                                   464G  345G   96G  79% /
cgroup_root                                       10M     0   10M   0% /sys/fs/cgroup
/dev/nvme0n1p1                                   973M  383M  536M  42% /boot
/dev/sda1                                        110G  612M  104G   1% /public
tmpfs                                            3.2G  5.7M  3.2G   1% /run/user/1000

The above is post-error on the graphics demos but still building rust-native.

from tegra-demo-distro.

The RAM and free disk space should be enough, I think, although more free disk space would probably be safer. No kernel messages about either OOM or filesystem errors on whichever drive you're running the build from? Does the filesystem ever hit usage of 90% or more?

The Rust compiler build is pretty resource-intensive, and CUDA application builds are, too. I wouldn't expect the graphics demos to be that bad, though - no CUDA there, just EGL.

from tegra-demo-distro.

Hey @sarnold
Any updates about this issue ?

from tegra-demo-distro.

Sorry, got busy with xilinx again and we already gave the tegra customer a workable meta layer for his camera stuff. I suspect the cause of our build issue was most likely too much distro feature hacking, as I ended up going with less of that and a really light openbox config which seemed stable enough for dev work.

from tegra-demo-distro.

I will close this ticket. You can reopen new one if you have any issue.

from tegra-demo-distro.