Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 May 2017 23:02:43 +0200
From:      Hans Petter Selasky <hps@selasky.org>
To:        Karl Denninger <karl@denninger.net>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: Possible -HEAD problem with the Pi3 onboard ethernet
Message-ID:  <e5f9d528-f579-5d63-454a-bd2fc14e7340@selasky.org>
In-Reply-To: <ae04f5db-8f58-550b-1fb8-de22433b5319@denninger.net>
References:  <ae04f5db-8f58-550b-1fb8-de22433b5319@denninger.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 05/12/17 19:45, Karl Denninger wrote:
> Under fairly heavy stress (~50% of the 100Mbps possible FDX performance)
> I've now run into a problem that is turning into something I can repeat
> without too much trouble by transmitting a large file through the device.
> 
> The system appears to "crash" from the outside.  It's not dead, however
> -- it's got some sort of network buffer hang going on.  This is a Pi3
> with current (-HEAD, FreeBSD 12.0-CURRENT #0 r318193M: Thu May 11
> 16:18:20 CDT 2017) software on it -- reverting to a mid-March kernel did
> NOT change the behavior.
> 
> The symptomology is that the unit will start printing this on the console:
> 
> May 12 12:25:46 IPGw dhcpd: send_packet: No buffer space available
> May 12 12:25:46 IPGw dhcpd: dhcp.c:3974: Failed to send 300 byte long
> packet over ue0.3 interface.
> 
> ue0.3 is a VLAN for a private subnet and is not specific to the issue;
> it also complains about no space on the primary too:
> 
> May 12 12:27:06 IPGw dhcpd: dhcp.c:3974: Failed to send 300 byte long
> packet over ue0 interface.
> May 12 12:27:13 IPGw dhcpd: send_packet: No buffer space available
> 
> netstat -m does /not /show any denied or delayed requests for network
> buffers or mbuf exhaustion.  Systat -vm shows plenty of RAM available
> (roughly half.)
> 
> An ifconfig ue0 down / ifconfig ue0 up sequence from the console clears
> the hang.
> 
> Has anyone else seen anything similar to this?
> 

Hi,

It might be a bug in the USB network driver for the RPI.

You can try to run usbdump on ugenX.Y for the network interface.

usbdump -i usbusX -f Y

And see what is going on.

--HPS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e5f9d528-f579-5d63-454a-bd2fc14e7340>