From: "Tango Tiger" <klistener@eudoramail.com>
To: linux-kernel@vger.kernel.org
Subject: Somewhat bizzare network/kernel problem
Date: Tue, 31 Jul 2001 23:31:39 +0600 [thread overview]
Message-ID: <KCGIPDEGAOALKAAA@shared1-mail.whowhere.com> (raw)
Since upgrading to kernel 2.4.5+ I have been having problems transferring files
over the network. After a seemingly random number of bytes (normally a few 100k)
the operation seems to hang. This occurs regardless of transfer mechanism
(I've tried scp,ftp and smb). This leads me to conclude that it is a kernel/driver
issue. Using smb it hangs such that the mount point will not unmount (at all - reboot
required) and the mount becomes unusable, with any access hanging.
The network driver I use is tulip, and this problem occurs if I use the either
development version of the tulip driver or the version shipped with the kernel.
NICs in use are Linksys EtherFast (mostly) and one Cnet card.
This did not occur using 2.2.x.
I am unsure as to what would help with diagnostics - but this is _very_ easy to
reproduce so I'll be glad to help in any way.
Thank you.
David.
Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com
reply other threads:[~2001-07-31 17:32 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=KCGIPDEGAOALKAAA@shared1-mail.whowhere.com \
--to=klistener@eudoramail.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