Re: FreeBSD 8.0 - network stack crashes?

On 8. jan. 2010, at 16.33, Robert N. M. Watson wrote:
> On 30 Nov 2009, at 19:13, Eirik Øverby 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.
>> 
>> 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.

Happens all the time. ;)


> 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.

I got a patch from Rick early december which I have tried, but that one unfortunately did not seem to make any difference. I cvsup'ed (RELENG_8_0), patched, compiled, installed, booted and tested on the 12th - any reason to think things might have changes on 8.0 since then? I'm assuming not, in which case the answer is yes, I am still experiencing this problem (except I've made all our OpenBSD boxen speak TCP now, avoiding the problem entirely).

I'll perform whichever tests you'd like me to on that particular system. Just send me the scripts or pseudocode, and I'll get it done as soon as I can.

I was also planning on setting up a pair of VMs (one FreeBSD and one OpenBSD) and try to reproduce there - but that month that zipped past has not allowed the time to do so.

Thanks,
/Eirik