From owner-freebsd-net@FreeBSD.ORG Fri Feb 28 17:07:56 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 75F944CB; Fri, 28 Feb 2014 17:07:56 +0000 (UTC) Received: from mail.adm.hostpoint.ch (mail.adm.hostpoint.ch [IPv6:2a00:d70:0:a::e0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 026CB10C0; Fri, 28 Feb 2014 17:07:56 +0000 (UTC) Received: from 46-127-132-15.dynamic.hispeed.ch ([46.127.132.15]:60829 helo=[172.16.1.156]) by mail.adm.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1WJQud-0004Zp-Bv; Fri, 28 Feb 2014 18:07:51 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: Network loss From: Markus Gebert In-Reply-To: Date: Fri, 28 Feb 2014 18:07:46 +0100 Message-Id: <76CCBE2B-D89E-40AE-9A58-8F022D70913B@hostpoint.ch> References: <532475749.13937791.1393462831884.JavaMail.root@uoguelph.ca> <76EBC5F0-DA4E-4A60-A10E-093F4E1BD1EF@hostpoint.ch> To: Jack Vogel X-Mailer: Apple Mail (2.1874) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Johan Kooijman , FreeBSD Net , Rick Macklem , John Baldwin X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2014 17:07:56 -0000 On 27.02.2014, at 18:02, Jack Vogel wrote: > I would make SURE that you have enough mbuf resources of whatever size = pool > that you are > using (2, 4, 9K), and I would try the code in HEAD if you had not. >=20 > Jack Thanks for the suggestion, but I do not think it has anything to do with = resource problems. We checked netstat -m among other things all the time = when the problem was occurring, and never saw any indication of an mbuf = shortage or anything similar. Looking at the symptoms we experienced, = especially the TCP connections that never timed out, could that even be = explained by mbuf shortage? At the time we checked, 9.2 included the most recent driver AFAIR. But = this was 3 months ago, I=92ll check if something was commited in the = meantime that could help us. What I remember now is that we did see some error counter sysctl within = dev.ix rise during the network problem. It suggested that something went = wrong on the MAC layer when sending packages. I disabled flow control, = but that did not help. Rick was so kind to point me to this other thread here: = http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D279182+0+current/freebsd-ne= t It=92s about FreeBSD 10 and his links are flapping, which they didn=92t = in our case, so I did not read that thread carefully at first. But now = the OP has found out that his issues were caused by bad firmware, I=92m = not sure anymore, if our problems could be related to his (instead of = the nfs/mbuf problem). What do you think Jack? Is there a way to tell = what firmware we have, and what=92s has been fixed in a more recent = firmware release? Markus