Date: Fri, 28 Feb 2014 18:07:46 +0100 From: Markus Gebert <markus.gebert@hostpoint.ch> To: Jack Vogel <jfvogel@gmail.com> Cc: Johan Kooijman <mail@johankooijman.com>, FreeBSD Net <freebsd-net@freebsd.org>, Rick Macklem <rmacklem@uoguelph.ca>, John Baldwin <jhb@freebsd.org> Subject: Re: Network loss Message-ID: <76CCBE2B-D89E-40AE-9A58-8F022D70913B@hostpoint.ch> In-Reply-To: <CAFOYbc=m0yatfuMZZD=0Een8LQcxg89aQWdUVmZ0940yvMxGxg@mail.gmail.com> References: <532475749.13937791.1393462831884.JavaMail.root@uoguelph.ca> <76EBC5F0-DA4E-4A60-A10E-093F4E1BD1EF@hostpoint.ch> <CAFOYbc=m0yatfuMZZD=0Een8LQcxg89aQWdUVmZ0940yvMxGxg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27.02.2014, at 18:02, Jack Vogel <jfvogel@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76CCBE2B-D89E-40AE-9A58-8F022D70913B>