From: hmh@rcm.org.br (Henrique de Moraes Holschuh)
To: Jes Sorensen <jes@linuxcare.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with 2.2.19pre9 (Connection closed.)
Date: Thu, 22 Feb 2001 15:52:51 -0300 [thread overview]
Message-ID: <20010222155251.A8207@godzillah> (raw)
In-Reply-To: <94ae7g9o8t.fsf@religion.informatik.uni-bremen.de> <E14VZCs-00023R-00@the-village.bc.nu> <14996.14604.348038.42765@pizda.ninka.net> <948zmy97zc.fsf@religion.informatik.uni-bremen.de> <d3y9uyj1is.fsf@lxplus015.cern.ch>
In-Reply-To: <d3y9uyj1is.fsf@lxplus015.cern.ch>; from jes@linuxcare.com on Qui, Fev 22, 2001 at 02:22:19 +0100
On Thu, 22 Feb 2001, Jes Sorensen wrote:
> Alan forwarded a patch to me from DaveM which fixed it for me.
Jes, could you forward it here as well?
> The problems I were seeing were much more than every 2 hrs, more like
> every 10-15 mins. Anyway it seems it got fixed.
I've seen IRC sessions getting dropped every 10-15 minutes as well, and
about 70% outgoing http connections (to a FreeBSD proxy) dropping in less
than 1 second. It was so bad here I had to downgrade to 2.2.18 (which fixed
all the issues, so I'm pretty sure it was kernel trouble and not network
trouble).
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
prev parent reply other threads:[~2001-02-22 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 13:09 Problem with 2.2.19pre9 (Connection closed.) Markus Germeier
2001-02-21 13:21 ` Alan Cox
2001-02-21 13:32 ` Jes Sorensen
2001-02-21 13:55 ` Markus Germeier
2001-02-21 15:48 ` Jes Sorensen
2001-02-21 21:54 ` David S. Miller
2001-02-22 13:12 ` Markus Germeier
2001-02-22 13:22 ` Jes Sorensen
2001-02-22 18:52 ` Henrique de Moraes Holschuh [this message]
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=20010222155251.A8207@godzillah \
--to=hmh@rcm.org.br \
--cc=jes@linuxcare.com \
--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