From: Martin Pool <mbp@samba.org>
To: James Morris <jmorris@intercode.com.au>
Cc: netdev@oss.sgi.com
Subject: Re: FIN_WAIT1 / TCP_CORK / 2.2 -- reproducible bug and test case
Date: Sat, 5 Oct 2002 09:27:16 +1000 [thread overview]
Message-ID: <20021004232715.GC3030@sourcefrog.net> (raw)
In-Reply-To: <Mutt.LNX.4.44.0210050053000.21202-100000@blackbird.intercode.com.au>
On 5 Oct 2002, James Morris <jmorris@intercode.com.au> wrote:
> Martin,
>
> I'm not able to reproduce the bug exactly as described. What kind of
> network connection were you using between the boxes, and what was the
> kernel version at the server end?
I was using VMware over 100Mbps to a 2.4.19 server. I am pretty sure
it could also be reproduced over localhost TCP just in 2.2.21 inside
VMware. I don't remember the exact hardware; I can let you know later.
It seems to not happen every time, but at least one time in three.
--
Martin
next prev parent reply other threads:[~2002-10-04 23:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 15:06 FIN_WAIT1 / TCP_CORK / 2.2 -- reproducible bug and test case James Morris
2002-10-04 23:27 ` Martin Pool [this message]
2002-10-05 7:51 ` Martin Pool
2002-10-05 11:53 ` James Morris
2002-10-08 10:21 ` Martin Pool
2002-10-08 10:28 ` James Morris
2002-10-10 16:36 ` James Morris
2002-10-10 16:43 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2002-09-18 2:03 Martin Pool
2002-09-18 1:58 ` David S. Miller
2002-09-18 2:09 ` Martin Pool
2002-09-18 23:38 ` Alexey Kuznetsov
2002-09-26 5:47 ` Martin Pool
2002-09-26 13:09 ` kuznet
2002-09-26 20:46 ` David S. Miller
2002-09-30 9:59 ` Martin Pool
2002-09-30 10:32 ` David S. Miller
2002-09-30 12:23 ` Alan Cox
2002-10-03 3:30 ` James Morris
2002-10-03 3:54 ` Andi Kleen
2002-10-03 7:59 ` David S. Miller
2002-10-03 7:56 ` David S. Miller
2002-09-18 2:30 ` Martin Pool
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021004232715.GC3030@sourcefrog.net \
--to=mbp@samba.org \
--cc=jmorris@intercode.com.au \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).