These are harmless, next/font just can’t compute fallback metrics for these two fonts since they aren’t in its internal lookup table. It means the adjustFontFallback feature won’t work, but the fonts themselves load fine. You can suppress the noise by explicitly disabling it:

adjustFontFallback: false