Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Feb 2026 13:43:06 -0800
From:      bob prohaska <fbsd@www.zefox.net>
To:        Mark Millard <marklmi@yahoo.com>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: -current network buffer exhaustion on RPi2 armv7
Message-ID:  <aZom6vbtSPiYroPA@www.zefox.net>
In-Reply-To: <0b6093e0-400c-4e0d-a674-d7b425e7a910@yahoo.com>
References:  <aZNQKmWzZTBBkobG@www.zefox.net> <bed432c0-0e88-4654-b109-c21b02462e33@yahoo.com> <aZih74o0d2mB7ljR@www.zefox.net> <0b6093e0-400c-4e0d-a674-d7b425e7a910@yahoo.com>

index | next in thread | previous in thread | raw e-mail

On Sat, Feb 21, 2026 at 11:10:39AM -0800, Mark Millard wrote:
> On 2/20/26 10:03, bob prohaska wrote:
> > It looks rather as if the "no buffer space available" text isn't
> > coming from wpa_cli, but rather from syslogd reporting directly
> > to the console (at the moment the serial console is the only
> > interactive connection to the Pi2). 
> 
> 
> You previously supplied text indicating that one source of "send_packet:
> No buffer space available" was dhclient's activity:
> 
> QUOTE
> daemon.log:Feb 16 03:53:37 generic dhclient[35171]: send_packet: No
> buffer space available
> END QUOTE
> 
> I've not noticed your reports indicating anyplace else so far.

I'm running wpa_cli on the serial console. The output contains
system console messages interleaved with wpa_cli messages.  

It's dawned on me that line breaks aren't always preserved and
so I could be seeing run-on output from more than one source. 
This can be seen if a top session is left running for several
hours; the formatting begins to mix fragments of different
process outputs.
 
As a result, it's possible that the above quote mixes contents
of different messages. It isn't certain that the  "no buffer space
available" has anything to do with dhclient.

One thought is a brute-force search for the phrase "No buffer space
available" anywhere in /usr/src. I've not seen that message again
and knowing where it came from might be interesting. 

In the meantime a grep search for "Can't assign requested address" has
turned up several sources: libdtrace, libdxo, libntp and libc. There
are a few more, but they're in places like test or unbound, which is 
inactive now. 

I plan to attempt a similar search for "No buffer space available"
when the present search finishes. 

My hope is that knowing which process can report what error will
clarify what's going wrong. If there are more fruitful things to
explore please indicate. 

Thanks for writing!

bob prohaska



home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aZom6vbtSPiYroPA>