Re: -current network buffer exhaustion on RPi2 armv7

On 2/21/26 17:13, bob prohaska wrote:
> On Sat, Feb 21, 2026 at 03:40:45PM -0800, Mark Millard wrote:
>> On 2/21/26 13:43, bob prohaska wrote:
>>>
>>> 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. 
>>
>> Good hunting. (I did not show all the steps for tracking down what I
>> showed.)
>>
> 
> It appears that the hunting is rather too good. Both "no buffer space
> available" and "Can't assign requested address" have numerous possible
> sources. Using wpa_cli as a logger distinct from the console output
> is likely more productive. 

I'll remind of your original text message report:
(expect line wrapping)

Feb 16 08:23:34 generic syslogd: last message repeated 1 times, op=20,
val=0, arg_len=7]: Can't assign requested address send_packet: No buffer
space available

So. looking for 'send_packet:' . . .

# grep -r 'send_packet:' /usr/src/
/usr/src/sbin/dhclient/bpf.c:		warning("send_packet: %m");
/usr/src/libexec/tftpd/tftp-io.c:	tftp_log(LOG_ERR, "send_packet: %s",
strerror(errno));
/usr/src/usr.sbin/bhyve/slirp/slirp-helper.c:	
warn("slirp_cb_send_packet: send");
/usr/src/sys/netgraph/ng_vlan.c:send_packet:

How many of your examples have 'send_packet:' as a likely prefix (given
the : character)? Just some from the above list?

> 
> My first thought was to use something like
> wpa_cli > wpa_cli.log &
> on the serial console, but backgrounding the job seems to suspend wpa_cli.
> 
> Strangely, starting 
> wpa_cli > wpa_ci.log
> in the foreground, suspending it and then putting it in the background
> with bg lets it keep running. That's aberrant. 
> 
> I'll let it run overnight.

-- 
===
Mark Millard
marklmi at yahoo.com