All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Joris Neujens <joris@discosmash.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Possible network issue in 2.6.8.1
Date: Tue, 07 Sep 2004 19:09:58 -0400	[thread overview]
Message-ID: <1094598598.16954.215.camel@krustophenia.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0409071544570.6867@asus.discosmash.com>

On Tue, 2004-09-07 at 09:55, Joris Neujens wrote:
> Hello,
> 
> We've got a weird problem at our university network.  Since we upgraded to
> kernel 2.6.8 our download rate never gets higher than 10kB/sec.  Upload
> remains at original rate.  This problem does not occur with previous
> kernels (works fine again after downgrading to 2.6.7, without changing
> anything at the kernel config).
> 

This is quickly becoming a FAQ:

http://lwn.net/Articles/92727/

Short answer: you have a broken router.

Lee


      parent reply	other threads:[~2004-09-07 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 13:55 Possible network issue in 2.6.8.1 Joris Neujens
2004-09-07 13:35 ` Alan Cox
2004-09-07 14:29 ` Paolo Ornati
2004-09-07 23:09 ` Lee Revell [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=1094598598.16954.215.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=joris@discosmash.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 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.