Dma_atomic_pool allocation failed on boot

I just built a new platform with intel Arrow lake
ASUS Pro WS W880-ACE SE + Core Ultra 7 265K

the system boots fine, but when inspecting kernel logs for anything odd, i observed these trace.
``
[Sat Nov 29 09:15:01 2025] swapper/0: page allocation failure: order:12, mode:0xcc1(GFP_KERNEL|GFP_DMA), nodemask=(null),cpuset=/,mems_allowed=0
[Sat Nov 29 09:15:01 2025] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.33-production+truenas #1
[Sat Nov 29 09:15:01 2025] Hardware name: ASUS System Product Name/Pro WS W880-ACE SE, BIOS 1802 09/23/2025
[Sat Nov 29 09:15:01 2025] Call Trace:
[Sat Nov 29 09:15:01 2025]
[Sat Nov 29 09:15:01 2025] dump_stack_lvl+0x64/0x80
[Sat Nov 29 09:15:01 2025] warn_alloc+0x164/0x1e0
[Sat Nov 29 09:15:01 2025] ? __alloc_pages_direct_compact+0xaf/0x2b0
[Sat Nov 29 09:15:01 2025] __alloc_pages_slowpath.constprop.0+0x323/0xe20
[Sat Nov 29 09:15:01 2025] __alloc_pages_noprof+0x30e/0x330
[Sat Nov 29 09:15:01 2025] alloc_pages_mpol_noprof+0x8f/0x1f0
[Sat Nov 29 09:15:01 2025] atomic_pool_expand+0x74/0x1f0
[Sat Nov 29 09:15:01 2025] __dma_atomic_pool_init+0x49/0xb0
[Sat Nov 29 09:15:01 2025] dma_atomic_pool_init+0x13d/0x160
[Sat Nov 29 09:15:01 2025] ? __pfx_dma_atomic_pool_init+0x10/0x10
[Sat Nov 29 09:15:01 2025] do_one_initcall+0x58/0x320
[Sat Nov 29 09:15:01 2025] kernel_init_freeable+0x31b/0x460
[Sat Nov 29 09:15:01 2025] ? __pfx_kernel_init+0x10/0x10
[Sat Nov 29 09:15:01 2025] kernel_init+0x1a/0x1c0
[Sat Nov 29 09:15:01 2025] ret_from_fork+0x31/0x50
[Sat Nov 29 09:15:01 2025] ? __pfx_kernel_init+0x10/0x10
[Sat Nov 29 09:15:01 2025] ret_from_fork_asm+0x1a/0x30
[Sat Nov 29 09:15:01 2025]
[Sat Nov 29 09:15:01 2025] Mem-Info:
[Sat Nov 29 09:15:01 2025] active_anon:0 inactive_anon:0 isolated_anon:0
active_file:0 inactive_file:0 isolated_file:0
unevictable:0 dirty:0 writeback:0
slab_reclaimable:26 slab_unreclaimable:2118
mapped:0 shmem:0 pagetables:70
sec_pagetables:516 bounce:0
kernel_misc_reclaimable:0
free:24487007 free_pcp:0 free_cma:61440
[Sat Nov 29 09:15:01 2025] Node 0 active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:0kB dirty:0kB writeback:0kB shmem:0kB shmem_thp:0kB shmem_pmdmapped:0kB anon_thp:0kB writeback_tmp:0kB kernel_stack:2668kB pagetables:280kB sec_pagetables:2064kB all_unreclaimable? no
[Sat Nov 29 09:15:01 2025] Node 0 DMA free:15360kB boost:0kB min:0kB low:0kB high:0kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[Sat Nov 29 09:15:01 2025] lowmem_reserve: 0 0 0 0 0
[Sat Nov 29 09:15:01 2025] Node 0 DMA: 04kB 08kB 016kB 032kB 064kB 0128kB 0256kB 0512kB 11024kB (U) 12048kB (M) 14096kB (M) 18192kB (M) 016384kB 032768kB 0*65536kB = 15360kB
[Sat Nov 29 09:15:01 2025] 0 total pagecache pages
[Sat Nov 29 09:15:01 2025] 0 pages in swap cache
[Sat Nov 29 09:15:01 2025] Free swap = 0kB
[Sat Nov 29 09:15:01 2025] Total swap = 0kB
[Sat Nov 29 09:15:01 2025] 24962977 pages RAM
[Sat Nov 29 09:15:01 2025] 0 pages HighMem/MovableOnly
[Sat Nov 29 09:15:01 2025] 465707 pages reserved
[Sat Nov 29 09:15:01 2025] 65536 pages cma reserved
[Sat Nov 29 09:15:01 2025] 0 pages hwpoisoned
``
after some googling, this seems to allocate 16MB on dma area where system only provides 15MB. Can i safely ignore these messages on boot? I am not sure if this is a kernel config issue, or a motherboard BIOS issue.

Boot-time memory errors like this usually point to hardware limitations or BIOS settings that don’t play well with TrueNAS. I tend to double-check reserved memory options, IOMMU settings, and any unusual PCIe devices that might be claiming resources early in the boot process. Stable operation often comes from keeping the configuration simple and ensuring the system firmware matches TrueNAS requirements.