linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: kuznet@ms2.inr.ac.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: rsync over ssh on 2.4.2 to 2.2.18
Date: Tue, 27 Feb 2001 20:43:15 +0000 (GMT)	[thread overview]
Message-ID: <200102272043.UAA01056@raistlin.arm.linux.org.uk> (raw)
In-Reply-To: <200102272035.XAA21341@ms2.inr.ac.ru> from "kuznet@ms2.inr.ac.ru" at Feb 27, 2001 11:35:12 PM

kuznet@ms2.inr.ac.ru writes:
> Moreover, even not _one_ wakeup is missing. At least two, because
> wakeups in read and write are separate and you have stuck in both directions.
> 8)8)

I'll see if I can strace it from the start until it hangs tomorrow.

> Well, if it was one I would start to dig ground inside tcp instantly.
> But as soon as two of them are missing, I have to suspect wake_up itself.
> At least, we had such bugs there until 2.4.0.

I was running at one point a 2.4.0-test kernel, but I didn't see these
effects back then (but then I wasn't monitoring the system as closely as
I am at the moment).

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2001-02-27 22:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 10:02 rsync over ssh on 2.4.2 to 2.2.18 Russell King
2001-02-27 10:18 ` Rasmus Andersen
2001-02-27 10:58   ` bert hubert
2001-02-27 10:49 ` David S. Miller
2001-02-27 19:46   ` Russell King
2001-02-27 13:18 ` Anton Blanchard
2001-02-27 16:48   ` Russell King
2001-02-27 20:35 ` kuznet
2001-02-27 20:43   ` Russell King [this message]
2001-02-28 20:27     ` kuznet
2001-02-27 23:01 ` Eugene Crosser
2001-02-28 20:20   ` kuznet
2001-03-19  7:37     ` Russell King
2001-03-19 18:56       ` kuznet
2001-03-21 21:54         ` Rusty Russell

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=200102272043.UAA01056@raistlin.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --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 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).