From: Hans-Peter Schadler <blade.runner@gmx.at>
To: linux-kernel@vger.kernel.org
Subject: 2.4.22-pre3-ac1: bcm4400 transfer problems
Date: Tue, 8 Jul 2003 01:54:23 +0200 [thread overview]
Message-ID: <20030708015423.35f59b47.blade.runner@gmx.at> (raw)
Hello
I have some strange problems with the bcm4400 driver
Bigger transfers from any other PC to my PC doesnt work (so receiving seams to be the problem)
Very easy to reproduce this problem is, to ping a other pc with packages greater then approximatly 3000byte (ping -s 3000)
The Other thing is nfs. This also shows this problem very fast. I couldnt copy a file bigger then some bytes from server to my PC. From my PC to the server works without any problems.
I don't know what infos i should give you, and what infos could be usefull. There are no errors or messages in /var/log/messages or /var/log/syslog.
I have activated acpi, but i also have the problem, without it.
Best regards
Hans-Peter Schadler
reply other threads:[~2003-07-07 23:39 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=20030708015423.35f59b47.blade.runner@gmx.at \
--to=blade.runner@gmx.at \
--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;
as well as URLs for NNTP newsgroup(s).