During the power-on startup phase, there are occasional cases of memblock_alloc_low allocation failure

"Background: The project requires reserving 512M of memory starting from 0x80000000, which leads to a reduction in the amount of low memory. memblock_alloc_low allocation failure occurs occasionally.
I observed that in successful startup cases, the memory allocated by swiotlb starts from 0xb3800000 for 256M. How should I modify it to ensure that swiotlb allocation is successful every time?
image

Which jetpack release is this?

root@ems-desktop:~# cat /etc/nv_tegra_release

R35 (release), REVISION: 4.1, GCID: 33958178, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug 1 19:57:35 UTC 2023

How did you configure to reserve the memory here?

“This reserved memory is used for pushing data by FPGA, so a block of low memory is reserved. The FPGA side only supports pushing data to low memory. Therefore, in my case, how should I avoid the occurrence of memblock_alloc_low allocation failure?”
image

please also share the error log you hit as full text file.

"It should be this log. I previously added some print statements and checked, confirming that the issue was caused by memblock_alloc_low allocation failure.
nv_dmesg.txt (20.3 KB)