From owner-freebsd-current@FreeBSD.ORG Fri Jan 8 15:33:09 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 131481065695; Fri, 8 Jan 2010 15:33:09 +0000 (UTC) (envelope-from rwatson@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D8CA68FC1A; Fri, 8 Jan 2010 15:33:08 +0000 (UTC) Received: from lemongrass.sec.cl.cam.ac.uk (lemongrass.sec.cl.cam.ac.uk [128.232.18.47]) by cyrus.watson.org (Postfix) with ESMTPSA id 0341A46B09; Fri, 8 Jan 2010 10:33:07 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=iso-8859-1 From: "Robert N. M. Watson" In-Reply-To: Date: Fri, 8 Jan 2010 15:33:06 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <3BC13C71-348A-49AD-94BA-FC28EB0648DE@freebsd.org> References: <20091129013026.GA1355@michelle.cdnetworks.com> <74BFE523-4BB3-4748-98BA-71FBD9829CD5@anduin.net> <34AD565D-814A-446A-B9CA-AC16DD762E1B@anduin.net> <1DFC4992-E136-4674-BC0E-A6B1DAE12AF4@anduin.net> To: =?iso-8859-1?Q?Eirik_=D8verby?= X-Mailer: Apple Mail (2.1077) Cc: pyunyh@gmail.com, weldon@excelsusphoto.com, freebsd-current@freebsd.org, Gavin Atkinson Subject: Re: FreeBSD 8.0 - network stack crashes? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2010 15:33:09 -0000 On 30 Nov 2009, at 19:13, Eirik =D8verby wrote: > I meant NFS-UDP ... However I was wrong even there; Using NFS over UDP = from FreeBSD boxes does not cause the same issue. So OpenBSD seems to be = a special case here. >=20 > I'm no Wireshark expert (to be fair, I've seen it a few times and = tried it once or twice, and that's so long ago it's almost no longer = true), so I'd need some input on how to gather useful data. I assume = tcpdump, which options? And would it be OK if I made the dump available = for download somewhere, so you or someone else can take a look with = whichever tools you'd like? Aii. Over a month zips past in the blink of an eye. Are you still experiencing this problem? I can certainly look at a = wireshark trace, but make no promises. If you do do a trace, then what = we should do is have you do run a script that dumps a bunch of relevant = stats with nfsstat, netstat, vmstat, etc, before the trace starts, grabs = exactly ${someval} seconds of trace data, then dumps all the same stats = afterwards. Then we can use the stats to work out about how many leaked = packets (or whatever) were present, and try to correlate it to a count = of some type of event in the trace. Robert=