From: Dragan Stancevic <visitor@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.4.1 network problems
Date: Fri, 16 Feb 2001 06:10:58 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005156@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005146@msgid-missing>
On Wed, Feb 14, 2001, David Mosberger <davidm@hpl.hp.com> wrote:
; >>>>> On Wed, 14 Feb 2001 12:10:24 -0800, Michael Madore <mmadore@turbolinux.com> said:
;
; Mike> In addition to the >1024MB problem, I am also experiencing a
; Mike> reproducible nfs hang on Lions. If I copy this file
;
; Mike> ftp://frontier.turbolinux.com/pub/ia64/nfshang.bin
;
; Mike> from an nfs server to the local file system, the copy hangs
; Mike> after transferring 294912 bytes. If I copy the file from the
; Mike> local filesystem to the server, the copy completes
; Mike> successfully. The hang only occurs with certain files.
;
; That's a rather bizarre bug. I can confirm this is happening on one
; of our Lions as well. The Big Sur (also with eepro100) is fine
; though. The Lion has 4GB and the Big Sur only 1GB of RAM.
If I am right it's not the offset but it's rather the data combined with
a certain fragmentation of the packets, if you use these two files
to "cp" them over nfs you should see the hang at 0 bytes transfered,
don't know yet why not all systems are affected, I am still working on it.
ftp://ftp.valinux.com/pub/people/visitor/0xdeadbeef/
--
No Kernel Hackers were harmed during writing of this email.
-Dragan
prev parent reply other threads:[~2001-02-16 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 23:43 [Linux-ia64] 2.4.1 network problems Michael Madore
2001-02-14 18:49 ` David Mosberger
2001-02-14 20:10 ` Michael Madore
2001-02-14 20:35 ` David Mosberger
2001-02-14 20:39 ` Don Dugger
2001-02-15 9:46 ` Andreas Schwab
2001-02-16 6:10 ` Dragan Stancevic [this message]
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=marc-linux-ia64-105590693005156@msgid-missing \
--to=visitor@valinux.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.