From: Michael Guntsche <mike@it-loops.com>
To: linux-kernel@vger.kernel.org
Subject: Network problems with b44 in 2.6.0
Date: Mon, 29 Dec 2003 18:00:25 +0100 [thread overview]
Message-ID: <20031229180025.00b88096.mike@it-loops.com> (raw)
Recently I activated my BCM4401 network card on my notebook,
using the b44 module, to do some large file transfers
(normally I use my wireless connection).
While copying around several MB between 2 computers I noticed something
very strange.
Scp'ing a file FROM the notebook TO my gateway, I got a throughput of
1.2MB. This looks normal, since the gateway is a very old machine.
--------
The problems started when copying a file in the opposite direction
(FROM the gateway TO the notebook).
As soon as I started the process, the following error messages started
appearing in my syslog.
b44: eth0: Link is down.
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is on for TX and on for RX.
b44: eth0: Link is down.
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is on for TX and on for RX.
b44: eth0: Link is down.
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is on for TX and on for RX.
b44: eth0: Link is down.
After a few seconds the whole transfer -stalled--.
The Link just went down and up and the messages filled my syslog.
For me it looks like that something is seriously wrong on the RX side,
since sending a file works without a problem.
System Info:
Acer TravelMate 800
Debian unstable
Kernel 2.6.0 no modifications
Broadcom Corporation BCM4401 100Base-T (rev 01)
Please CC: me if you have hints/need more information since I am not
subscribed to the list
Thanks in advance,
Michael
next reply other threads:[~2003-12-29 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 17:00 Michael Guntsche [this message]
2003-12-29 20:14 Michael Guntsche
2003-12-30 9:25 Michael Guntsche
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=20031229180025.00b88096.mike@it-loops.com \
--to=mike@it-loops.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
all inboxes | Powered by JetHome®