From: Richard Dawe <rich@phekda.gotadsl.co.uk>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@oss.sgi.com, Me <rich@phekda.gotadsl.co.uk>
Subject: Re: Acer Aspire 1524WLMi and RealTek 8169 - very slow
Date: Tue, 08 Feb 2005 23:00:59 +0000 [thread overview]
Message-ID: <420944AB.5090501@phekda.gotadsl.co.uk> (raw)
In-Reply-To: <20050205204135.GA13986@electric-eye.fr.zoreil.com>
Hello.
Francois Romieu wrote:
[snip]
> If you can do an extra test, I'd like to know if you can safely bring
> the r8169 interface down on your computer once the patch below if applied:
> http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.11-rc3/r8169/patches/r8169-380.patch
>
> (it should apply correctly on top of you current setup)
I can, with and without that patch.
But I encounter problems bringing the interface back up and down again.
If I do the following after a reboot:
/etc/init.d/network stop
/etc/init.d/network start
/etc/init.d/network stop
I find that the "ip link set dev eth0 down" command hangs, consuming
most of the CPU time (~99%). Note that I issued the "network" commands
with about a second's delay between each command.
This is with a static IP address. If the IP address is assigned via
DHCP, then the DHCP client hangs in the "network start" command.
I'm running Fedora Core 3 + all the latest security updates.
>>One more thing:
>>
>>With 1.6LK + my PHY patch, I see the message "eth0: PHY reset until link
>>up" every 5 seconds or so, when there is no Ethernet cable plugged in.
>>This is annoying. I think it should only log it once.
>
>
> Hmmm... One could argue that 1) syslog will cope and 2) the printk level
> of the console can be lowered. Some event kamasutra can probably be done
> from userspace too so I am a bit reluctant to special case this code
> (read as: I'd welcome more requests/complaints).
>
> Is it enough for you if I salt the code with a few netif_msg_xxx() here
> and there to control the messages ?
That sounds good.
I'm happy to submit a patch to do this, if you'd like. Note that I'm new
to kernel programming, so it might take me a while.
Bye, Rich =]
--
Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ]
"You can't evaluate a man by logic alone."
-- McCoy, "I, Mudd", Star Trek
next prev parent reply other threads:[~2005-02-08 23:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 13:16 Acer Aspire 1524WLMi and RealTek 8169 - very slow Richard Dawe
2004-11-21 13:24 ` Richard Dawe
2004-11-21 19:47 ` Richard Dawe
2004-11-21 20:58 ` Francois Romieu
2004-11-22 20:42 ` Richard Dawe
2004-11-22 21:30 ` Francois Romieu
2004-11-22 22:07 ` Richard Dawe
2004-11-24 19:36 ` Richard Dawe
2004-11-30 19:52 ` Jon Mason
2004-12-29 10:17 ` Richard Dawe
2004-12-29 23:52 ` Francois Romieu
2005-01-02 13:51 ` Richard Dawe
2005-01-02 15:23 ` Richard Dawe
2005-01-22 13:10 ` Richard Dawe
2005-01-22 15:22 ` Richard Dawe
2005-01-22 23:01 ` Francois Romieu
2005-01-23 19:08 ` Richard Dawe
2005-01-25 21:47 ` Francois Romieu
2005-02-05 13:26 ` Richard Dawe
2005-02-05 20:41 ` Francois Romieu
2005-02-06 10:54 ` Richard Dawe
2005-02-08 23:00 ` Richard Dawe [this message]
2005-02-12 0:07 ` Francois Romieu
2004-11-21 23:28 ` [patch] ethtool (was Re: Acer Aspire 1524WLMi and RealTek 8169 - very slow) Francois Romieu
2005-01-27 20:27 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 22:00 Acer Aspire 1524WLMi and RealTek 8169 - very slow Brandeburg, Jesse
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=420944AB.5090501@phekda.gotadsl.co.uk \
--to=rich@phekda.gotadsl.co.uk \
--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).