Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Jan 2010 15:33:06 +0000
From:      "Robert N. M. Watson" <rwatson@freebsd.org>
To:        =?iso-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net>
Cc:        pyunyh@gmail.com, weldon@excelsusphoto.com, freebsd-current@freebsd.org, Gavin Atkinson <gavin@freebsd.org>
Subject:   Re: FreeBSD 8.0 - network stack crashes?
Message-ID:  <3BC13C71-348A-49AD-94BA-FC28EB0648DE@freebsd.org>
In-Reply-To: <E8883290-0D35-44AC-9ED9-8464C4F7FF62@anduin.net>
References:  <A1648B95-F36D-459D-BBC4-FFCA63FC1E4C@anduin.net> <20091129013026.GA1355@michelle.cdnetworks.com> <74BFE523-4BB3-4748-98BA-71FBD9829CD5@anduin.net> <alpine.BSF.2.00.0911291427240.80654@fledge.watson.org> <34AD565D-814A-446A-B9CA-AC16DD762E1B@anduin.net> <A0C9ED20-5536-44E2-B26B-0F1AEC2AF79C@anduin.net> <BA47FDA1-1097-4C43-AF71-51E7227795B5@FreeBSD.org> <1DFC4992-E136-4674-BC0E-A6B1DAE12AF4@anduin.net> <EE2AA268-2309-4924-A3AD-1EC256E7BB2A@freebsd.org> <E8883290-0D35-44AC-9ED9-8464C4F7FF62@anduin.net>

next in thread | previous in thread | raw e-mail | index | archive | help

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=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BC13C71-348A-49AD-94BA-FC28EB0648DE>