From owner-freebsd-net@FreeBSD.ORG Fri Feb 28 22:38:38 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 104198AC; Fri, 28 Feb 2014 22:38:38 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id B4E4110C8; Fri, 28 Feb 2014 22:38:37 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqIEABkPEVODaFve/2dsb2JhbABZg0FXgwO+HIErdIIlAQEFI1YbGAICDRkCIzYGE4dlAxENqmuZRg2HHReBKYsWgWIBMweCboFJBIlKjQODH4sxhUiDSx6Bbg X-IronPort-AV: E=Sophos;i="4.97,564,1389762000"; d="scan'208";a="100841733" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 28 Feb 2014 17:38:29 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id ACA7279283; Fri, 28 Feb 2014 17:38:29 -0500 (EST) Date: Fri, 28 Feb 2014 17:38:29 -0500 (EST) From: Rick Macklem To: Markus Gebert Message-ID: <1581623680.15157356.1393627109696.JavaMail.root@uoguelph.ca> In-Reply-To: <76CCBE2B-D89E-40AE-9A58-8F022D70913B@hostpoint.ch> Subject: Re: Network loss MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.17.91.209] X-Mailer: Zimbra 7.2.1_GA_2790 (ZimbraWebClient - FF3.0 (Win)/7.2.1_GA_2790) Cc: Johan Kooijman , FreeBSD Net , Jack Vogel , 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 22:38:38 -0000 Markus Gebert wrote: >=20 >=20 >=20 > On 27.02.2014, at 18:02, Jack Vogel < jfvogel@gmail.com > wrote: >=20 >=20 > 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 >=20 > 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? >=20 >=20 > At the time we checked, 9.2 included the most recent driver AFAIR. > But this was 3 months ago, I=E2=80=99ll check if something was commited i= n > the meantime that could help us. >=20 >=20 > 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. >=20 >=20 > Rick was so kind to point me to this other thread here: >=20 >=20 > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D279182+0+current/freebsd-n= et >=20 >=20 > It=E2=80=99s about FreeBSD 10 and his links are flapping, which they didn= =E2=80=99t > 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=E2=80=99m 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=E2=80=99s has been fi= xed > in a more recent firmware release? >=20 In the above post, it was mentioned that booting Linux from a live-CD resulted in some info (he referred to it as "spam") in dmesg. I'd suggest trying that if you can have the box offline for a few minutes. rick >=20 >=20 >=20 > Markus >=20 >=20