Re: -current network buffer exhaustion on RPi2 armv7

On Wed, Feb 18, 2026 at 04:01:30PM -0800, bob prohaska wrote:
> On Mon, Feb 16, 2026 at 03:55:56PM -0800, Adrian Chadd wrote:
[snippage]
> > 
> > Yup, it looks like for some reason it's hung; wpa_supplicant should be
> > kicking off a scan and well,
> > the above is telling me that it is stuck.
> > 
> > Try running "wpa_cli" to see what decisions its making. it logs them
> > to the wpa_cli tool whilst its running.
> > You may first need to put this in /etc/wpa_supplicant.conf :
> > 
> > ctrl_interface=/var/run/wpa_supplicant
> > 
> > Meanwhile I'll go test out that NIC in a test device as its primary
> > internet connection and report back.
> 
> With wpa_cli running on the serial console for most of a day there appeared:
> 
> 
> root@generic:/usr/src # wpa_cli
> wpa_cli v2.11
> Copyright (c) 2004-2024, Jouni Malinen <[email protected]> and contributors
> 
> This software may be distributed under the terms of the BSD license.
> See README for more details.
> 
> 
> Selected interface 'wlan0'
> 
> Interactive mode
> 
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>CTRL-EVENT-DISCONNECTED bssid=00:13:46:86:6d:0c reason=1 locally_generated=1
> <3>Added BSSID 00:13:46:86:6d:0c into ignore list, ignoring for 10 seconds
> <3>CTRL-EVENT-DSCP-POLICY clear_all
> > Feb 18 14:33:38 generic syslogd: last message repeated 1 times
> <3>CTRL-EVENT-SCAN-RESULTS 
> <3>WPS-AP-AVAILABLE 
> <3>Removed BSSID 00:13:46:86:6d:0c from ignore list (clear)
> <3>Trying to associate with 00:13:46:86:6d:0c (SSID='d-link.zefox.net' freq=2417 MHz)
> <3>Associated with 00:13:46:86:6d:0c
> <3>WPA: Key negotiation completed with 00:13:46:86:6d:0c [PTK=CCMP GTK=TKIP]
> <3>CTRL-EVENT-CONNECTED - Connection to 00:13:46:86:6d:0c completed [id=0 id_str=]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
> <3>RSN: Group rekeying completed with 00:13:46:86:6d:0c [GTK=TKIP]
>  
> 
> I don't see any complaints about buffers on the console and 
> after quitting wpa_cli both ping and ifconfig agreed the network
> was up and running. It's unfortunate there are no timestamps,
> I'd guess the events above represent about six hours. The host
> was running buildworld with -j4. At the time of reporting this
> buildworld hadn't reached the point of maximum swap activity.
> 
> If there's some trick for making wpa_cli run in the background
> and log output to a file that would be very helpful.

This morning, after running buildworld overnight, wpa_cli reported:

root@generic:/usr/src # wpa_cli
wpa_cli v2.11
Copyright (c) 2004-2024, Jouni Malinen <[email protected]> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.


Selected interface 'wlan0'

Interactive mode

<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
<3>Reject scan trigger since one is already pending
<4>Failed to initiate AP scan
root@generic:/usr/src # Feb 21 07:34:29 generic ntpd[4057]: error resolving pool 2.freebsd.pool.ntp.org: Name could not be resolved at this time (2)
Feb 21 07:34:54 generic ntpd[4057]: error resolving pool 0.freebsd.pool.ntp.org: Name could not be resolved at this time (2)

I don't recall seeing scan trigger and initiate messages before. 

Manually cycling wlan0 down and up seems to restore connectivity,
at least for the moment.

As an aside, similar behavior has been seen with RasberryPiOS: The
network connection drops, but the host fails to notice and fix the
problem. So, the fault may not be unique to FreeBSD.