From: Ian Kumlien <pomac@vapor.com>
To: linux-kernel@vger.kernel.org
Subject: [netdev watchdog/b44] is something broken?
Date: Tue, 22 Jun 2004 15:27:03 +0200 [thread overview]
Message-ID: <1087910823.2971.145.camel@big> (raw)
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
Hi,
I mailed before about dlinks 4 port alta card using sundance...
Now i'm trying to transfer some data to my laptop and after about 1
minute of ~12mb/s this happens:
NETDEV WATCHDOG: eth0: transmit timed out
b44: eth0: transmit timed out, resetting
b44: eth0: Link is down.
eth0: no IPv6 routers present
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is on for TX and on for RX.
This is a udp link, but i disabled all tcp tweaks that i have been
playing with as well. Btw, this worked just fine for a while, then this
started. (tcp tweaks like westwood and bic)
Imho something is wrong with the watchdog (or the staircase scheduler
7.1 changes some behavior that the watchdog is depending on... Other
than that this is a pure 2.6.7 kernel)
Any comments clues suggestions?
I'm copying this to a firewire disk if that could have any
implications... But after seeing this in the sundance driver i'm
assuming that something else is broken.
Just prior to the watchdog timeout the transfer seems to act like a sine
wave, ie 8mb/s -> 533 b/s -> 12 mb/s -> 733b/s -> etc
(observations from gkrellm)
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-06-22 13:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1087910823.2971.145.camel@big \
--to=pomac@vapor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox