From: Dorn Hetzel <kernel@dorn.hetzel.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Dorn Hetzel <kernel@dorn.hetzel.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
jgarzik@pobox.com
Subject: Re: r8169.c
Date: Mon, 22 Nov 2004 13:13:07 -0500 [thread overview]
Message-ID: <20041122181307.GA3625@lilah.hetzel.org> (raw)
In-Reply-To: <20041120002946.GA18059@electric-eye.fr.zoreil.com>
On Sat, Nov 20, 2004 at 01:29:46AM +0100, Francois Romieu wrote:
> Dorn Hetzel <kernel@dorn.hetzel.org> :
>
> You have two options (or more) on top of 2.6.10-rc2:
> - ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc2/2.6.10-rc2-mm2/2.6.10-rc2-mm2.bz2
> - http://www.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/2.6.10-rc2-netdev1.patch.bz2
>
I have gotten as far as rc2-mm2, which was a fairly complete failure. After
just a couple of pings on the interface, the whole system started to freeze
up fairly hard. Please see http://www.hetzel.org/8169/rc2-mm2/ for a
set of information on the system state this time around. The last two
lines in messages.txt are:
illyria kernel: NETDEV WATCHDOG: eth0: transmit timed out
illyria kernel: eth0: interrupt 0001 taken in poll
Then things go south pretty hard and fast...
I'll try the other patches on top of rc2-mm2 tonight and see if that turns
out any better :)
> Once you have applied one of the patch above, the patch below will improve
> your "transmit timed out" (please apply in order and enable NAPI):
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.10-rc2-mm1/r8169-250.patch
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.10-rc2-mm1/r8169-255.patch
>
> If things perform better you may want to use bigger frames and apply as
> well r8169-260.patch and r8169-265.patch.
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.10-rc2-mm1/r8169-260.patch
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.10-rc2-mm1/r8169-265.patch
>
Thanks again for all your help!
-Dorn
next prev parent reply other threads:[~2004-11-22 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 16:29 r8169.c Dorn Hetzel
2004-11-19 20:12 ` r8169.c Francois Romieu
2004-11-20 0:37 ` r8169.c Dorn Hetzel
2004-11-20 0:29 ` r8169.c Francois Romieu
2004-11-22 18:13 ` Dorn Hetzel [this message]
2004-11-23 14:49 ` r8169.c Dorn Hetzel
2004-11-23 19:47 ` r8169.c Francois Romieu
2004-11-25 20:00 ` r8169.c Dorn Hetzel
2004-11-25 22:02 ` r8169.c Dorn Hetzel
2004-11-25 20:54 ` r8169.c Francois Romieu
2004-11-26 0:36 ` r8169.c Dorn Hetzel
2004-12-05 23:55 ` r8169.c Dorn Hetzel
2004-12-05 23:37 ` r8169.c Francois Romieu
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=20041122181307.GA3625@lilah.hetzel.org \
--to=kernel@dorn.hetzel.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--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 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).