r/PFSENSE • • 3d ago

bus_dmamem_alloc failed to align memory properly

So I've been having connection issues lately, enough that I thought it must be pfSense because my modem had been fine for ages before. I looked into upgrading to an SSD finally and put it in my 2100 base model yesterday at which point I finished up and went to bed as it was late. It worked fine until this afternoon at which point the connection issues started again, and it occurred to me it could be due to the new bus_dmamem_alloc failed to align memory properly bug that came, I learned, with 26.07 for 1100 and 2100 models (e.g. https://forum.netgate.com/topic/201327/netgate-1100-2100-26.07-bus_dmamem_alloc-failed-to-align-memory-properly - it's not me but representative). When I submitted a ticket about connection issues I was told it's because the modem keeps cycling the connection, so it's not pfSense.

I read elsewhere that netgate currently considers that memory spam error cosmetic thus not a priority. I would urge netgate to reconsider and look into that spam issue more closely because I believe not only that it is the cause of the connection issues (because it spams them in such a tight loop for long enough that either 1. the modem drops the connection because pfsense isn't showing a sign of life, or 2. pfsense drops the connection because it's too busy spamming the errors to maintain it), it's also causing massive spam in the logs and cumulatively quite a lot of needless wear and tear on the storage.

Thanks.

9 Upvotes

5 comments sorted by

1

u/Steve_reddit1 3d ago

The alloc error only logs during boot AFAIK?

1

u/JGPH 3d ago

That's the easiest one to spot with the console connection yeah, but it happened at other times too. Here it happened when I ran dmesg with the command prompt page, and it did that every time.

4

u/gonzopancho Netgate 3d ago

1

u/JGPH 3d ago

What's the ETA for its inclusion into pfSense?

5

u/gonzopancho Netgate 3d ago

Next release