From: "David S. Miller" <davem@redhat.com>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: Ralf Nyren <ralf@nyren.net>,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: 2.4.4: Kernel crash, possibly tcp related
Date: Sun, 29 Apr 2001 23:58:20 -0700 (PDT) [thread overview]
Message-ID: <15085.3340.784923.77844@pizda.ninka.net> (raw)
In-Reply-To: <3AED0A7A.7263E27B@uow.edu.au>
In-Reply-To: <Pine.LNX.4.31.0104291552190.523-100000@HADDOCK.100Mbit.nyren.net> <15084.62398.56283.772414@pizda.ninka.net> <3AED0A7A.7263E27B@uow.edu.au>
Andrew Morton writes:
> "David S. Miller" wrote:
> >
> > I'm having a devil of a time finding the tcpblast sources on the
> > net, can you point me to where I can get them?
>
> I seem to have a copy.
>
> http://www.zip.com.au/~akpm/tcpblast-19990504.tar.gz
Thanks to everyone who pointed me at this and the debian copy :-)
Anyways, I just tried to reproduce Ralf's problem on two of my
machines. One was an SMP sparc64 system, and the other was my
uniprocessor Athlon.
What kind of machine are you reproducing this on Ralf? I'm not
even getting the very strange errors from tcpblast on the command
line, it is functioning perfectly fine and sending a stream of
data to the other machine. Are you doing something weird like
making the remote machine the local machine in your tcpblast run?
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-04-30 6:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3AED0A7A.7263E27B@uow.edu.au>
2001-04-29 14:29 ` Ralf Nyren
2001-04-30 5:10 ` David S. Miller
2001-04-30 6:42 ` J Sloan
2001-04-30 6:58 ` David S. Miller [this message]
2001-04-30 14:41 ` Ralf Nyren
2001-04-30 16:46 ` Andrea Arcangeli
2001-04-30 17:22 ` Ingo Oeser
2001-04-30 17:00 ` kuznet
2001-05-01 10:47 ` Andrea Arcangeli
2001-05-01 16:44 ` kuznet
2001-05-01 17:09 ` Andrea Arcangeli
2001-05-01 17:25 ` kuznet
2001-05-01 17:32 ` Andrea Arcangeli
2001-05-01 18:10 ` kuznet
2001-05-01 23:08 ` David S. Miller
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=15085.3340.784923.77844@pizda.ninka.net \
--to=davem@redhat.com \
--cc=andrewm@uow.edu.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@nyren.net \
/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®