From owner-freebsd-hackers@FreeBSD.ORG  Mon Aug 24 08:54:41 2009
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 76494106568C
	for <freebsd-hackers@freebsd.org>; Mon, 24 Aug 2009 08:54:41 +0000 (UTC)
	(envelope-from yuri@rawbw.com)
Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 4C8C98FC16
	for <freebsd-hackers@freebsd.org>; Mon, 24 Aug 2009 08:54:41 +0000 (UTC)
Received: from eagle.syrec.org (c-24-6-221-126.hsd1.ca.comcast.net
	[24.6.221.126]) (authenticated bits=0)
	by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id n7O8seDW093751
	for <freebsd-hackers@freebsd.org>; Mon, 24 Aug 2009 01:54:40 -0700 (PDT)
Message-ID: <4A92554F.1040506@rawbw.com>
Date: Mon, 24 Aug 2009 01:54:39 -0700
From: Yuri <yuri@rawbw.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090724)
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: ral0 interface hangs with the message "No buffer space available"
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: yuri@rawbw.com
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Aug 2009 08:54:41 -0000

Almost every time when I leave system to download a large file I get ral 
device inoperable after a while.
Pinging the other peer causes these messages:

 > ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
ping: sendto: No buffer space available
ping: sendto: No buffer space available

I don't believe that TCP buffer is legitimately filled up to the max 
because after I bring it down and back up it works fine for a long 
while. So why didn't this data go through before down/up?

If TCP connections are slow buffers shouldn't just fill up: system can 
and should be preventing this letting apps to hold data streams.

Something isn't quite right.

Why would network device hang in a steady download scenaio?

7.2-STABLE

Yuri