Date: Sat, 21 Feb 2026 11:10:39 -0800 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: -current network buffer exhaustion on RPi2 armv7 Message-ID: <0b6093e0-400c-4e0d-a674-d7b425e7a910@yahoo.com> In-Reply-To: <aZih74o0d2mB7ljR@www.zefox.net> References: <aZNQKmWzZTBBkobG@www.zefox.net> <bed432c0-0e88-4654-b109-c21b02462e33@yahoo.com> <aZih74o0d2mB7ljR@www.zefox.net>
index | next in thread | previous in thread | raw e-mail
On 2/20/26 10:03, bob prohaska wrote:
> On Mon, Feb 16, 2026 at 12:08:53PM -0800, Mark Millard wrote:
>>
>> I've not found anything else that looks to be a match.
>>
>> So, apparently, 802.11 WiFi as the communication channel "media".
>>
>> My guess for op:
>>
>> sys/net80211/ieee80211_ioctl.h:
>> #define IEEE80211_IOC_DELKEY 20
>>
>> "Can't assign requested address" Looks to be from EADDRNOTAVAIL in:
>>
>> sys/net80211/ieee80211_ioctl.c :
>>
>> . . .
>> static int
>> ieee80211_ioctl_delkey(struct ieee80211vap *vap, struct ieee80211req *ireq)
>> . . .
>> if (dk.idk_keyix == (uint8_t) IEEE80211_KEYIX_NONE) {
>> struct ieee80211_node *ni;
>>
>> if (vap->iv_opmode == IEEE80211_M_STA) {
>> ni = ieee80211_ref_node(vap->iv_bss);
>> if (!IEEE80211_ADDR_EQ(dk.idk_macaddr,
>> ni->ni_bssid)) {
>> ieee80211_free_node(ni);
>> return EADDRNOTAVAIL;
>> }
>> } else {
>> . . .
>>
>>
>>> (I think the numerical values repeat, but I'm not certain of it)
>>> n
>>> In this case, the ethernet network (via a usb-wifi adapter) remained up:
>>
>> Yep: Looks to be that WiFi usage that is involved.
>>
>>>
>>> Anybody have an idea what the machine is complaining about?
>>
>> I've not managed to get the point of referencing any specifics for the
>> "No buffer space available", so: not me.
>
> 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.
--
===
Mark Millard
marklmi at yahoo.com
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0b6093e0-400c-4e0d-a674-d7b425e7a910>