All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jurriaan <thunder7@xs4all.nl>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Pasi Sjoholm <ptsjohol@cc.jyu.fi>, netdev@oss.sgi.com
Subject: Re: strange network performance degradation 2.6.8-rc3-mm1 -> 2.6.8-rc4-mm1
Date: Sun, 15 Aug 2004 12:44:27 +0200	[thread overview]
Message-ID: <20040815104427.GA2157@middle.of.nowhere> (raw)
In-Reply-To: <20040815095900.GA2846@electric-eye.fr.zoreil.com>

From: Francois Romieu <romieu@fr.zoreil.com>
Date: Sun, Aug 15, 2004 at 11:59:00AM +0200
> 
> Ok, the early read of the interrupt status register is the culprit.
> 
> I have modified 8139too-10.patch so that it behaves like patch #1 and 
> resynced the whole serie.
> 
> Can you both apply the updated patches below ?
> 
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.8-rc4-mm1/8139too-mm-revert.patch
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.8-rc4-mm1/8139too-10.patch
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.8-rc4-mm1/8139too-20.patch
> 
2.6.8-rc4-mm1 with those patches applied boots, and the network isn't
slow either.

Thanks,
Jurriaan
-- 
Sort of a pregnant Johnny Cash, actually.
	Rev Hammer describing his voice in Elizabeth's Great Gallop
Debian (Unstable) GNU/Linux 2.6.8 2x6078 bogomips load 0.01

  reply	other threads:[~2004-08-15 10:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-14  6:09 strange network performance degradation 2.6.8-rc3-mm1 -> 2.6.8-rc4-mm1 Jurriaan
2004-08-14 12:15 ` Francois Romieu
2004-08-14 13:56   ` Jurriaan
2004-08-14 15:08     ` Francois Romieu
2004-08-14 16:10       ` Jurriaan
2004-08-14 17:28         ` Francois Romieu
2004-08-14 19:01           ` Jurriaan
2004-08-14 19:27             ` Francois Romieu
2004-08-15  5:54               ` Jurriaan
2004-08-15  9:59                 ` Francois Romieu
2004-08-15 10:44                   ` Jurriaan [this message]
2004-08-15 17:16                   ` Pasi Sjoholm

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=20040815104427.GA2157@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --cc=netdev@oss.sgi.com \
    --cc=ptsjohol@cc.jyu.fi \
    --cc=romieu@fr.zoreil.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 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.