From: Domen Puncer <domen@coderock.org>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3c59x on 2.6.0-test3->test6 slow
Date: Mon, 13 Oct 2003 02:22:03 +0200 [thread overview]
Message-ID: <200310130222.03175.domen@coderock.org> (raw)
In-Reply-To: <200310100155.53205.domen@coderock.org>
On Friday 10 of October 2003 01:55, Domen Puncer wrote:
> On Friday 10 of October 2003 01:10, Zwane Mwaikambo wrote:
> > On Thu, 9 Oct 2003, Domen Puncer wrote:
> > > > > eth0: negotiated 100baseTx-FD, link ok
> > > > > when it is ok (reloaded -test2 module)
> > > >
> > > > What does mii-tool -r do?
> > >
> > > Doesn't help, neither do -R or -F.
> >
> > Ok to recap, backing out the WOL change fixes things? If not, can you
> > isolate which kernel version it is?
>
> -after the WOL change... works slow, no matter what i do.
> -before the WOL change... works slow, but rmmod/modprobe fixes this.
>
> Will try with drivers from older kernels, when i wake up.
Ok... i woke up :-)
Tried a bunch of 2.5.x kernels... no better.
Then i tried 2.4.22... and my nic still doesn't work fast.
What can i do?
Domen
next prev parent reply other threads:[~2003-10-13 0:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 13:29 3c59x on 2.6.0-test3->test6 slow Domen Puncer
2003-10-06 21:23 ` Zwane Mwaikambo
2003-10-06 22:33 ` Domen Puncer
2003-10-06 22:43 ` Zwane Mwaikambo
2003-10-06 23:44 ` Domen Puncer
2003-10-07 0:18 ` Zwane Mwaikambo
2003-10-07 4:31 ` Malte Schröder
2003-10-07 11:05 ` Malte Schröder
2003-10-07 12:58 ` Profiling disk usage on selected branches of a file system Stephen Satchell
2003-10-07 7:49 ` 3c59x on 2.6.0-test3->test6 slow Domen Puncer
2003-10-07 23:43 ` Zwane Mwaikambo
2003-10-08 15:05 ` Domen Puncer
2003-10-09 1:53 ` Zwane Mwaikambo
2003-10-09 8:49 ` Domen Puncer
2003-10-09 23:10 ` Zwane Mwaikambo
2003-10-09 23:55 ` Domen Puncer
2003-10-13 0:22 ` Domen Puncer [this message]
2003-10-13 0:37 ` Andrew Morton
2003-10-13 2:28 ` Domen Puncer
2003-10-13 3:03 ` Andrew Morton
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=200310130222.03175.domen@coderock.org \
--to=domen@coderock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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