All of lore.kernel.org
 help / color / mirror / Atom feed
From: Val Henson <val@nmt.edu>
To: "David S. Miller" <davem@redhat.com>
Cc: kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: Lost TCP retransmission timer
Date: Thu, 30 Aug 2001 16:11:39 -0600	[thread overview]
Message-ID: <20010830161139.A18224@boardwalk> (raw)
In-Reply-To: <20010829195259.B11544@boardwalk> <200108301621.UAA05134@ms2.inr.ac.ru> <20010830121025.A15880@boardwalk> <20010830.145609.42773013.davem@redhat.com>
In-Reply-To: <20010830.145609.42773013.davem@redhat.com>; from davem@redhat.com on Thu, Aug 30, 2001 at 02:56:09PM -0700

On Thu, Aug 30, 2001 at 02:56:09PM -0700, David S. Miller wrote:
> 
> BTW, you mentioned that you are seeing this on PPC, do you have any
> way to verify if the bug can be triggered on any other platform?

I'm currently away from my x86 workstation, but I can try it this
weekend.

The requirements for triggering this are:

2.4.6 or higher kernel
2.4.6 machine pushes lots of data on _first_ TCP connection after boot
Lots of packets from 2.4.6 machine are dropped (I'm using 10 Mb hub)

-VAL

  reply	other threads:[~2001-08-30 22:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010828171705.F890@boardwalk>
     [not found] ` <20010829082405.A5966@cubit.at>
2001-08-30  0:20   ` tcp connection hangs on connect Val Henson
2001-08-30  0:55     ` David S. Miller
2001-08-30  1:53       ` Val Henson
2001-08-30 16:21         ` kuznet
2001-08-30 18:10           ` Lost TCP retransmission timer (was Re: tcp connection hangs on connect) Val Henson
2001-08-30 21:56             ` Lost TCP retransmission timer David S. Miller
2001-08-30 22:11               ` Val Henson [this message]
2001-09-01 14:36                 ` kuznet
2001-09-04 21:07                   ` Val Henson
2001-09-05 15:23                     ` kuznet

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=20010830161139.A18224@boardwalk \
    --to=val@nmt.edu \
    --cc=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.