Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bf.cfg files are limited to 16 KB in size and if they are larger bfb-install fails silently #9

Open
lgarbarini opened this issue Jun 14, 2024 · 0 comments

Comments

@lgarbarini
Copy link

lgarbarini commented Jun 14, 2024

Wanted to post this in case others get tripped up and in the hope that the BSP docs are updated:

We can end up producing decently large bf.cfg files on the fly to do customization. Most of this involves injecting cloud-init mime-multipart user-data for things like systemd units/config files. This means that occasionally our bf.cfg files exceeded 16 KB which resulted in sporadically failing deployments.

This limit appears to be only documented in the code here:

boot_fifo_path="/sys/bus/platform/devices/MLNXBF04:00/bootfifo"
if [ -e "${boot_fifo_path}" ]; then
cfg_file=$(mktemp)
# Get 16KB assuming it's big enough to hold the config file.
dd if=${boot_fifo_path} of=${cfg_file} bs=4096 count=4 > /dev/null 2>&1

It would be great if the BSP docs covered this and/or bfb-install warned that this will likely fail.

EDIT: also cross-filed as nvidia bug 4704764

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant